Archived from groups: microsoft.public.win2000.group_policy (More info?)
I recently deployed a group policy to resolve some DNS problems within the
envinronment. The group policy runs the following VBscript at system
startup:
'--------------------------
' This script removes any
' local hardcoded DNS suffix search list entries.
const HKEY_LOCAL_MACHINE = &H80000002
strComputer = "." 'set computer to local computer
Set oReg=GetObject("winmgmts:{impersonationLevel=impersonate}!\\" &_
strComputer & "\root\default:StdRegProv" )
'navigate to the specific registry key.
strKeyPath = "system\currentcontrolset\services\tcpip\parameters"
strStringValueName = "searchlist"
oReg.DeleteValue HKEY_LOCAL_MACHINE,strKeyPath,strStringValueName
'WScript.Echo "The DNS settings have been adjusted."
The group policy also changes the Primary DNS Suffix to Fabrikam.MSFT.com
and sets the DNS Suffix search list to Fabrikam.MSFT.com, and MSFT.com.
The policy works fine on for Windows XP machines, but on some Windows 2000
machines (SP2 and above)
the installations of MS 2000 Office, Cisco's IPTV viewer, and Symantec
Antivirus Corporate Edition 8.01 and above are requiring to be pointed to
the original MSI to reverify the installation. I am only able to fix the
problem by pointing the Windows installer at a network share or CD
containing the original MSI.
Does anyone know why a DNS registry change would cause these MSI based
applications to need re-verification? I have since removed the policy from
the domain.
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.