In my previous post on this topic, I mentioned that Windows XP Service Pack 2 will copy the Administrators settings to Default User (see sections B & C). The new profile copy is the default behavior in SP2 with no built-in way to disable it. To disable it you had to request the hotfix from KB887816 from Microsoft Customer Support.
This has changed with Windows XP Service Pack 3. The fix from KB887816 is included in SP3. (See KB946480 for a list of fixes included in SP3.) Therefore, the behavior for SP3 is no profile copy by default. To enable the profile copy, you now have to add UpdateServerProfileDirectory=1 to the [Unattended] section of Sysprep.inf before running Sysprep. Unfortunately, due to an oversight you will not find this documented in the Microsoft Windows Preinstallation Reference (ref.chm) included with the SP3 Deployment Tools. KB887816 is currently one of the only references for this setting, as far as I know. (KB908784 also references this setting with respect to a problem that the profile copy can cause on Windows Server 2003)
In this post I orginally provided some instrutions about slipstreaming SP 3 into an installation source with the Tablet PC Edition CMPNENTS folder in it. Well it turns out that slipstreaming SP3 into the CMPNENTS will not be supported. See my August 3rd post for details.
This post was contributed by Michael Murgolo, a Senior Consultant with Microsoft Services - U.S. East Region.
i recently changed the base installation of our images from Windows XP with integrated SP2 to Windows XP with integrated SP3 and changed the sysprep files to the SP3 files, too.
Everything works fine and in the same way as in the SP2 image, but the duration of the minisetup process, especially the hardware detection, takes much longer on on our target pcs and laptops with the same hardware, drivers and configuration.
I already have posted this in the TechNet-Forum, but no-one seems to have the same issue...
I have not see any such issues with SP3. Perhaps a comparison of the setup logs (setup*.log in the Windows folder) from an SP2 and an SP3 image deployed onto the same hardware might reveal some differences.
Thanks for your response.
I have compared the setup.log files of the SP2 and SP3 image and found the cause of the long delay at the hardware detection process:
The DIF_INSTALLDEVICE routine for "Intel(R) ICH8DO LPC Interface Controller - 2814" took 1 second in SP2 and 53 seconds in SP3.
The DIF_INSTALLDEVICE routine for "Realtek High Definition Audio" took 4 seconds in SP2 and 120 seconds in SP3 and ended with "Class Installer appears to be hung. Device = Realtek High Definition Audio", "Skipping installation of enumerated device. Device = Realtek High Definition Audio"
At the 1st boot after minisetup, the system starts with no sound. When i look into device manager directly after startup i see the Realtek device (driver is installed and the tray symbol of the realtek tool comes up), but the device "Microsoft WINMM WDM Audio Compatibility Driver" (wdmaud) is marked as code 18, "driver must be new installed". The installation of the driver begins automatically and some Kernel drivers, i.e. Kernel system audio driver (sysaudio) appear and install. After reboot the sound works normally and all devices are ok.
What could cause this problem?
Why isn't the Administrator account deleted after running sysprep /generalize?
I get to the welcome page and the Administrator account it's still active although the log file says that it has been removed:
[msoobe.exe] Successfully removed administrator profile
I added a run command line after the sysprep task in MDT, "Net user administrator /active:no", but the account is still on.
I tried to put the cmd line in unattend.xml, but I don't know where. OObe branch?