Quote:

Thank you for the suggestion. Sadly, this is not sufficient. I face some major infrastructure network changes in our network. So I have to change IP settings (DNS, WINS, etc.) on a quite large scale for lots of computers that are not feed by DHCP. The main goal for this script is to CHANGE settings on target machines. Finding the current NIC settings is only the beginning ...
Therefore I need reliable read/write access the remote registries of the target machines. And yes, I know of netsh.exe and reg.exe , but if I decide to use these tools I need some wrapper shell script around them anyway to plumb it all together: netsh for querying the current settings, parsing the result by some means (awk or whatever ...) , refeeding the changes to netsh or reg, and so on. So I prefer doing it ALL unsing KIX.

And if it is a bug, it should be fixed anyway ...



Wouln't it be easier to have the loginscript process everything and log it to an ini file, compare the settings to what it should be and then have the loginscript do the settings for you? This way you evade this "bug" and you'd only have to sit back and relax.

Unless they aren't connected to the network anymore due to the IP changes.
[edit]
Then again you wouln't remotely be able to connect to them either...
[/edit]

Edited by apronk (2006-08-15 05:57 PM)