Windows Server 2000/2003 Thread, Changing the PID on a 2003 std server in Technical; Hi there
We have quite a few servers which were imaged and all have the same PID. This is apparantly ...
27th August 2009, 04:33 PM #1
- Rep Power
Changing the PID on a 2003 std server
We have quite a few servers which were imaged and all have the same PID. This is apparantly stopping WSUS from working and therefore I have been asked to find out how to change the PID's on these machines.
Ive found a few things via Google etc but has anyone actually done this? Im not on site to test it yet but would putting our current volume licensing key in (that was used originally, the servers dont have individual license keys) even change the PID?
Can anyone shed any light on this?
27th August 2009, 05:17 PM #2
It isn't the PID which is problem. I presume you or someone ran Sysprep when installing/deploying the servers? If not then the SID will be identical and it's not just WSUS where you'll have problems.
Fortunately the Windows SID and WSUS SID are two different things. You should be able to use this script on 2003 Server (I have never tried) and this will require a restart:
TITLE Logistix WSUS Reset Authorisation
Echo Save the batch file "AU_Clean_SID.cmd". This batch file will do the following:
Echo 1. Stops the wuauserv service
Echo 2. Deletes the AccountDomainSid registry key (if it exists)
Echo 3. Deletes the PingID registry key (if it exists)
Echo 4. Deletes the SusClientId registry key (if it exists)
Echo 5. Restarts the wuauserv service
Echo 6. Resets the Authorization Cookie
Echo 6. More information on http://msmvps.com/Athif
net stop wuauserv
REG DELETE "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v AccountDomainSid /f
REG DELETE "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v PingID /f
REG DELETE "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v SusClientId /f
net start wuauserv
wuauclt /resetauthorization /detectnow
2 Thanks to Michael:
ngreenwood (1st September 2009), Redfive (28th August 2009)
28th August 2009, 09:01 AM #3
- Rep Power
Thanks for the quick reply, I wasnt involved in imaging these servers but I am told they probably were not syspreped. However when I was asked to look into it it was pretty much told to me it was the PID that was the problem so this wouldnt affect WSUS at all?
I will try that script above and Ill try a sid changer too on 1 of the servers to see if that helps. thanks
28th August 2009, 10:19 AM #4
If you have a corporate license the PID would be the same on every workstation. I would be careful changing the Windows SID on any server!
I'm pretty sure you can break Active Directory and other critical services doing this. Changing the SID should of been done at the initial setup stage. I believe the only way you can resolve this is to transfer any roles, demote the server as a domain controller to a member server, then run Sysprep. Re-promote to a domain controller, then transfer any roles back. You'll need to do this with every server you have.
Thanks to Michael from:
Redfive (28th August 2009)
28th August 2009, 10:22 AM #5
- Rep Power
Thanks Michael, I tried your script and it fixed it no problems, thanks again!
By OverWorked in forum Windows Server 2008
Last Post: 3rd April 2009, 10:00 AM
By SYNACK in forum Hardware
Last Post: 27th February 2008, 10:27 AM
By ronanian in forum Windows
Last Post: 5th February 2008, 04:24 PM
By tosca925 in forum Windows
Last Post: 22nd August 2007, 10:17 PM
By pooley in forum Windows
Last Post: 23rd November 2005, 03:08 PM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)