forum.opsi.org

uncle_scrooge hat geschrieben:Winexe, und damit der opsi-deploy-client-agent, sollte per default auf Port 445 gehen.

And it does not use port 137, 138 and 139?

Please try to update your opsi-server. There has been an update, released about a week ago. Something to do with a out of date certificate in configed. You could also try to put the url to your opsi server on the exception list. Control Panel -> Java -> Security -> edit site list. (Sorry, these are ...

Ok, das ist auch eine Möglichkeit. Ich simuliere einfach das fehlende Laufwerk mit der nachfolgenden Routine. Das hat den charmanten Vorteil, dass ich einfach eine product property anlege, in die ich den Pfad schreibe, und wenn nötig, wird mit dazu ein Laufwerk generiert, oder auch nicht, wenn der ...

Using a verbose log can clear up a lot of confusion. I am using folder redirection for 'my documents' and 'desktop', and this works well. However, some programs do not install correctly. This is because the default user also gets folder redirection, and somehow it makes a new user on installation. D...

SisterOfMercy hat geschrieben:So now it works! I don't think .inf files are case sensitive in windows, are they?

No they are not.

Topic summarised: create_driver_links.py parses files case sensitive, while windows does not, and thus misses some drivers.

If one set opsi-client-agent=setup, the setup-script updates per default the mac address which may lead to this problem Ah, ok! I will look there, because you probably have something implemented to not pick a wireless mac address. I might be able to change the TAP adapter registry settings so it do...

What version of opsi are you running? Did you attempt to debug the problem yourself with a high loglevel and then seeing through the logs? I'm running 4.0.5, of course. I have not yet tried to debug it myself, because I didn't exactly know where to start, and what causes the change in mac address. ...

It only parses the "Ralink.NTx86.6.1" part, and not the "Ralink.NTamd64.6.1".. Are these parts case sensitive in Opsi? Yes, oh yes they are. [1814:3090] Ralink corp. : RT3090 Wireless 802.11n 1T/1R PCIe No driver - vendor directory '/var/lib/opsi/depot/win7-x64-nlite/drivers/pci...

And now with x86 files included: [1814:3090] Ralink corp. : RT3090 Wireless 802.11n 1T/1R PCIe Including file 'netr28.inf' Including file 'netr28x.inf' Found inf files: [u'/var/lib/opsi/depot/win7-x64-nlite/drivers/drivers/preferred/Ralink WLAN PCIe 5.0.46.0/netr28.inf', u'/var/lib/opsi/depot/win7-x...

I have a wireless Ralink card, which gives a bit of a problem. Of course I worked around the problem by putting it in the byAudit directory, but I don't get why it does not work. [1814:3090] Ralink corp. : RT3090 Wireless 802.11n 1T/1R PCIe No driver - vendor directory '/var/lib/opsi/depot/win7-x64-...