Changing the PID on a 2003 std server

[Redfive]

Hi there

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?

[Michael]

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:

@echo off
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
Pause
@echo on
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
Pause

[Redfive]

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

[Michael]

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.

[Redfive]

Thanks Michael, I tried your script and it fixed it no problems, thanks again!