I have just integrated SP3 RC into a copy of an already existing installation share for Windows XP SP2 with an unattended .sif install file with a proper product key, but have now found that this key that has worked for ages is not recognised anymore when SP3 is integrated.
If I go back to the normal SP3 installation, then everything is working as it should,
Can you check the installation media for VL compatibility?
War59312 wrote: Look I was not trying to accuse you, just came accross that way, sorry. Forgive me...
Anyhow, if you run setup from windows you shoud see this screen where you enter the product key:
Notice it says "Volume License product key" . So does your still say that? If not then yes some how it got switched to a different distro some how.
Also, open SETUPP.INI within the I386 folder and see if the the third line "Pid=" ends with 270. That tells setup it is a VL copy.
For info sake:
Retail = 335
Volume License = 270
OEM = OEM
We've got the same issue -- as have many others throughout the XP SP3 beta period.
I haven't seen a clear statement from Microsoft as to what the problem is and when they plan to fix it. I had hoped that this would have been taken care of by the time the beta went public, but apparently not.
It would be helpful if someone from MS would state definitively what the policy or process will be with regards to the installation of SP3 integrated into volume license media. As it is, we're simply not able to test XP SP3 using any of our standard deployment processes. It's unfortunate.
For all those who have noticed an issue with VLK keys failing post integration of SP3, please check the build version that was integrated.
We should be using the RC1 build (3264).
To check the build version, pleasefollow the following steps:
1. Obtain the update exe (windowsxp-kb936929-sp3-x86-xxx.exe)
2. Execute windowsxp-kb936929-sp3-x86-xxx.exe /x
3. Point it to a path with suitable disk space (approximately 400MB)
4. Navigate to the path provided in step 3 and locate the file "autochk.exe" in the i386 folder.
5. Determine the file version of autochk.exe (right click --> properties --> version).
6. The last four digit number in the version tell us about the build
Do let us know, if you notice the issue after integrating build 3264 of XP SP3.
Nlite is not a supported mechanism for creating integrated images.
Please try with the method illustrated in http://support.microsoft.com/default.aspx/kb/900871
Looking back all the post.. is interesting to see this forum have grow
Cisco Certified Network Associate
Cisco Certified Internetwork professional - MPLS
Certified Information Systems Security Professional
Microsoft Partner Network 2011
Microsoft Certified Professional
Microsoft Certified Systems Administrator:Security
Microsoft Certified Systems Engineer: Security
Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
Microsoft Certified Technology Specialist: Windows 7, Configuring
Microsoft Certified IT Professional: Enterprise Administrator
Microsoft Certified IT Professional: Server Administrator
Certified Ethical Hacker
Computer Hacking Forensics Investigator
Certified Sonicwall Security Administrator