Hi, I was searching around Google and I found this forum. Hopefully someone can help!

I have a Win2K3 server, and our clients are Win2K. Several clients have the wrong DNS IP in their network settings.
Since I haven't found a way to change this in Active Directory, I'm trying to create an MSI which only change the DNS settings. The problem is, WinINSTALL doesn't pick up the changes. Is it even possible to do this?

Thanks!
SG
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Hi SoylentGreen (love the name...)

Yes it is possible but I'd its not recommended. These settings should be deployed via a DHCP server (assuming you have one that is). I'm not familiar with WinInstall all that well, but it probably by default excludes the registry keys associated with this - have a look at its exclusion list, and if you have to get rid of everything and do another snap and you'll get it (use Regmon to see what the reg keys are if you need to, regmon is a sysinternals tool www.sysinternals.com)

Hope that helps

Rgds

Paul
Answered 11/22/2004 by: plangton
Second Degree Blue Belt

Please log in to comment
0
Hi plangton, thanks for replying!

I tried to remove all excluded items, but all I got after that were errors when WinInstall was trying to access NTUSER.DAT, SYSTEM.ALT and a few others. I assume the settings are in those files, but I'm thinking those can't be modified with MSI's. Am I right about that?

SG
Answered 11/22/2004 by: SoylentGreen
Senior Yellow Belt

Please log in to comment
0
Hi SoylentGreen,

No, those files are permanently locked by the system... the settings you want are registry keys (though NTUSER.DAT is a copy of the users registry, thats looking for FILE changes not REGISTRY changes if that makes sense)

I'd seriously look for getting the settings out via DHCP first. The reason I say this is that if there is a DHCP server pumping these settings out then your MSI will be overwritten by it (perhaps, I'd test it pretty seriously anyway). If you can't change the DHCP (or if there is no DHCP for whatever reason), then do a snap, but if you can just snap registry keys then do that - don't worry about the file exceptions, just remove the registry exceptions.

If you are having trouble identifying the registry keys use a utility like regmon.

Rgds

Paul
Answered 11/22/2004 by: plangton
Second Degree Blue Belt

Please log in to comment
0
The setting you're after is here somewhere:

"HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{ADAPTERGUID}\NameServer".

Could be under "DHCPNameServer" if the clients use DHCP - in which case you should definately use DHCP to distribute the changes.

The network most probably requires a restart to register changes made to TCPIP parameters through the registry, although I can't remember ever trying this.

It might be more interesting to try the "SetDNSServerSearchOrder" Method in the "Win32_NetworkAdapterConfiguration" class of WMI. You could run a script as a custom action.
Answered 11/22/2004 by: WiseUser
Fourth Degree Brown Belt

Please log in to comment
0
The other way to do it might be to create a custom action to reset the CLASSID on the network adapter. This will force a full reset of the DHCP settings on the client.

Your CA should have in it

ipconfig /release
ipconfig /setclassid *

ipconfig /setclassid * [CLASSID NAME] you use. Leave out the [ ]

If you need to see the commands for ipconfig then open a cmd prompt and type ipconfig /?
Answered 11/23/2004 by: MSIMaker
Second Degree Black Belt

Please log in to comment
Answer this question or Comment on this question for clarity