Sysprep Windows 8.1

Hi,
I am trying to build my companys first Windows 8.1 image for use with Windows Deployment Services.
I have sysprep'd as I would normally do in the past. I chose OOBE, Generalize and Shutdown. No other options and no answer file specified.
However after successfully syspreping and shutting down, the PC on boot up then displays this error message:
"Windows could not parse of process the unattend answer file for pass Specialize. A component specified more than once..."
Where is it getting this answer file from?
I have a cloned backup of the drive before sysprep so can resolve this today if anyone knows what the problem is, at present I am currently going through the image that was captured using Windows System Image Manager from WAIK to see if I can find the unattend
file.
Please do the following:
1. Navigate to C:\Windows\Panther\Unattend\
Delete all files under this directory (do NOT remove folders inside this folder).
2. If above did not worked, please try to produce the error again .... and once you have it, try to copy the
C:\Windows\Panther folder into the USB and post it (you can use sky drive or google drive for example).
N.A.Malik

Similar Messages

Not able to install sysprepped Windows 8.1 image, an OfflineServicing error appears.

Hello
I have Windows 8.1 Enterprise image failing at the end of the PE phase from a
WDS Server. I´ve searching through every related post but nothing solves the issue. My scenario is similar to this one (http://social.technet.microsoft.com/Forums/en-US/7ce4c49d-e8a4-460a-ae17-240daaf5f50e/deploying-a-win7-image-via-wds-fails-with-offlineservicing-error?forum=w7itproinstall),
but with Windows 8.1 Enterprise instead.
Basically, I have sysprepped Windows 8.1 and capture the image successfully without any problem. Then, I´ve uploaded the image to my WDS without any unattend xml file, but when trying to install it I get the following error message after completing the "Expanding
Windows Files" phase:
“Windows could not apply unattend settings during pass [offlineServicing]”
I´ve used the official image release, plus the only one partition disk is formatted before the installation. Every configuration seems to be set correctly. I wonder if there is any particular issue related to Windows 8.1.
I´ve already done this procedure with many other OS images and I´ve never got this error message.
Furthermore, I also tried to perform the installation with an empty unattend answer file attached to the deployed image, but the error still appears.
I wonder if the Win8.1 image needs a proper configuration of the unattend answer file, specially on the
Pass 2 of OfflineServicing. Unfortunately I don´t know how to configure it. I would like to keep the credentials and partition configuration be set manually.
Thank you for any help you can give me.

Hello, thanks for the replay but I didn't found any relevant log file on the client machine.
Unattend mode is unchecked, and I haven't used DISM at all when creating the image. I haven't also opened nor updated any metroApp (although if this were the case, it would raise an issue on sysprep phase).
X:\Windows\panther directory does not exists; (C: volume is not available at installation phase)
X:\Windows\diagerr.xml doesn't have any relevant information (it defines some AtrributeType tags with a number in a xml format but it has no content on any tag.)
X:\windows\tracing\ folder is empty;
X:\windows\Logs & \Logs\CBS folders are empty;
I've checked all the volume and I couldn't find any relevant log which shows an error on the instalation.
In addition, I tried to look into WDS server, but the Enable Log property that the article refers for Windows Server 2012 (WDS is installed in a Windows Server 2012), is not shown at the
EventViewer - Deployment-Services-Diagnostics section. Plus, I search the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Tracing\WDSMGMT
entry in order to enable it, but it does not exist.
WDS worked and is working without any issue regardless this Windows 8.1 image. I don't think it has a somthing to do with its configuration.
Looking forward to hearing from you.

Office 2013 apps showing templates error after Sysprepping Windows 7 with CopyProfile setting

Here is my setup:
I installed Windows 7 Professional.
I entered Audit Mode (which automatically logged me in as the built-in Administrator user) and installed the entire Office 2013 Professional Plus suite.
In Audit Mode, I opened Word 2013 to get through the "new user" prompts, such as the opening movie that plays in all Office 2013 programs. I did this to ensure that any new users who log into the computer would not need to sit through these "new
user" prompts. I also rearmed Office 2013.
I ran Sysprep with the CopyProfile setting in the Unattend.xml file, with the /generalize switch, and the /oobe switch. The CopyProfile setting copies settings from the built-in Administrator account to any new user who logs into the system.
Both Windows and Office were successfully activated using KMS.
Everything seemed to work, but there is one problem: when any user -- all of which are standard users rather than administrator users -- logs into Windows and runs any Office 2013 program that has templates (such as Word, Excel, and PowerPoint), the templates
on the Start page do not appear. In their place, the following error message appears on the Start page where the templates would normally have been listed:
"Sorry, we had trouble getting the featured templates and can't show them right now."
Below the error message is a link that reads “Work Offline.” If you click the “Work Offline” link, the error message disappears and the templates appear as they should. However, the error message re-occurs when the application is closed and re-opened.
If I login as the built-in Administrator account (i.e., the account I used to modify the default profile), this problem does not occur at all when using Office 2013 programs.
Any ideas?

"logs into Windows and runs any Office 2013 program that has templates (such as Word, Excel, and PowerPoint), the templates on the Start page do not appear. In their place, the following error message appears on the Start page where the templates would normally
have been listed:
"Sorry, we had trouble getting the featured templates and can't show them right now." "
Is there any chance to let you skip the Start page for Office application? I mean that try to open Office application (such Word)and go to File > Options > Untick the option "Show the Start screen when this application starts". Try to re-launch
the application again to check if the error still pop-up. If yes, I'm afraid the default build-in template is corrupted somehow and we need to copy a healthy one from another computer or totally rename normal.dotm documents from %userprofile%\AppData\Roaming\Microsoft\template.
Afte that, please check if the issue still persists.
Here is another thread with the similar topic for your reference:
http://social.technet.microsoft.com/Forums/ie/en-US/09a69d4c-9e5f-489d-ba7b-2af79ff83596/deploying-normaldotm-through-oct-doesnt-work-in-office-2013?forum=officesetupdeploy
http://answers.microsoft.com/en-us/office/forum/office_2013_release-office_install/can-not-sign-into-office-2013-version/b6951c25-2fb5-4fc1-a667-2327b9da2f7f
Tony Chen
TechNet Community Support

Error with syspreped windows 7 image related to capisp.dll execution...

Hi Folks,
some time ago I crafted an windows 7 image with sysprep generalization for WDS deployment. In real there are 2 images: one dumped w/o sysprep and the another w/ (dumping with ImageX Tool from WAIK for W7/W2K8R2). The syspreped one I delivered to our WDS
Server. In the past I made several changes based on the non-syspreped image (incl. WUs) and afterward I've generated a new syspreped version from it. ...and now, since the last revision und sysprep run the last syspreped version (stored at the WDS) is no longer
installable onto any target machine... Ervery time I tried to deploy this version from the WDS at the target machine an error popup occurs and says that this image cannot be installed at this target machine type (see *** - the german message). Examinig the
SETUPACT.LOG / SETUPERR.LOG files the following problem has been stated:
2010-06-21 14:22:54, Info       [0x0f0081] SYSPRP LaunchDll:Successfully executed 'C:\Windows\System32\sppnp.dll,Sysprep_Specialize_Pnp' without error
2010-06-21 14:22:54, Info       [0x0f008b] SYSPRP RunRegistryDlls:Found entrypoint in registry at SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\SysPrep\Specialize\{2172c981-2c23-e969-b30d-046ffeeb096e}; will try to launch 'C:\Windows\system32\capisp.dll,CryptoSysPrep_Specialize'
2010-06-21 14:22:54, Info       [0x0f0080] SYSPRP LaunchDll:Found 'C:\Windows\system32\capisp.dll,CryptoSysPrep_Specialize'; executing it
2010-06-21 14:22:54, Info                         capisp.dll::CheckIFCryptoSysPrepSpecialized: returning 0
2010-06-21 14:22:55, Info                         capisp.dll::CryptoSysPrep_Specialize: assigned CAPI machine guid "44d42aa2-dee4-4023-bea5-d2f166bbb42c"
2010-06-21 14:22:55, Info                         capisp.dll::DisableAdministratorIfApplicable disabled the admin account.
2010-06-21 14:22:55, Info                         capisp.dll::CryptoSysPrep_Specialize: returning 5
2010-06-21 14:22:55, Error      [0x0f0082] SYSPRP LaunchDll:Failure occurred while executing 'C:\Windows\system32\capisp.dll,CryptoSysPrep_Specialize', returned error code 5[gle=0x000003e5]
2010-06-21 14:22:55, Info                  IBS    Callback_Specialize: Internal Providers Specialized Failed. System can't proceed to handle Internal Providers
2010-06-21 14:22:55, Info                  IBS    Callback_Specialize: Specialize return: [5]
2010-06-21 14:22:55, Error      [0x060435] IBS    Callback_Specialize: An error occurred while either deciding if we need to specialize or while specializing; dwRet = 0x5
2010-06-21 14:22:55, Info       [0x0640ae] IBSLIB PublishMessage: Publishing message [***Windows kann nicht für die Ausführung auf der Hardware dieses Computers konfiguriert werden.]
The mentioned error is the only one.
ANY help is very appreciated!
From Colonel Gizmo

Hi,
Regarding the returned error code, error code 0x5 is a “Access denied” error. It seems that the sysprep disables the administrator account, it can’t
process the capisp.dll and pass CryptoSysPrep_Specialize. To resolve this kind of issue, I would like to suggest:
1.
Ensure that you deploy image running as Administrator account.
2.
Mount the image and check if the capisp.dll file exists and try taking ownership of it.
3.
Open Registry Editor and navigate to the following path:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\Sysprep\Specialize
Check if there is an entry with the Data:
C:\Windows\system32\capisp.dll,CryptoSysPrep_Specialize , make sure it is spelled correctly and check the permissions on the above key.
4.
Then deploy again.
Best Regards
Dale
Please remember to click “Mark as Answer” on the post that helps you.

Windows Services not starting in OOBE after Sysprep - Windows 7 Professional 64bit

So, I'm attempting to create an image to deploy to our Lenovo Thinkpad T540p's using Windows 7 Proffesional 64bit. At this point I'm simply setting up the image and running Sysprep /oobe/ generalize and then trying to boot into windows to make sure it works
before we store and deploy it.
When I do, I'm getting an error message that the services failed to start and restart the PC. I started the process listed here:
https://social.technet.microsoft.com/Forums/windows/en-US/658528ce-6eb5-403b-ae41-458147c2c044/sysprep-failling-after-reboot-into-oobe
But my issue seems to be a bit more complicated than that, as the issues for me seem to be coming from the registry key [\REGISTRY\MACHINE\SYSTEM\ControlSet001\Enum\ROOT\LEGACY_KL1] as being the one that: <Data Name="Message">(c0000022):
Failed to process reg key or one of its descendan
I've tried starting from the Lenovo image, or our previos image but cannot avoid this error. Any ideas? Here is the logfile in full:
https://docs.google.com/spreadsheets/d/1RlStS8OyNTsL7Y_VO2HniDz0FI0jUi-ZGnUCVlowVvs/edit#gid=192385465

It's an image that was created by the previous tech. He appears to have modified the lenovo image (it has a bunch of lenovo bloatware still on it) and then run sysprep on it. His image works, but if I make any changes to it, it seems to break.
Yeah, I wish I could get a hold of him and ask, but that's not really an option ><
Edit: Interestingly enough I ran sysprep just from the image and it did the same thing...I'm not really sure what the last guy must've done to set this up

After SysPrep Windows Logs Users In With Temporary Profile

I have created a Windows 8.1 Pro image which was created by installing from the DVD. On first login I put windows into audit mode and installed all software and customised. I then ran sysprep with an unattend file with "copy profile" set to true.
Once the image is loaded onto a new PC it is joined to our domain and if I login as a Domain Admin things are fine, but if I login as a Domain User it logs the user in with a temporary profile which disappears at log off. The fact that Domain Admins
can login successfully suggests it is permissions but I am not sure where or why. To create the image I used Microsoft best practice as detailed on the MSDN. It is not a corrupted profile as there are no domain users have been logged on prior to capturing
the image. I am using DISM to capture and deploy. I did use the ADK to create the unattend file.
Does anyone have any suggestions as to what might be causing this behaviour?
Thanks
JeffW

Hi,
We have not heard from you in a couple of days. Please post back at your convenience if we can assist further.
If the above suggestions doesn't work, We'd collect PROFILE.ETL to further troubleshoot the issue.
a. Log onto the machine as an administrator.
b. Select the start menu
c. Type cmd in "Start Search"
d. Right click on cmd under “programs”
e. Select "Run as administrator"
f. Enable the User Profile Service Tracing using the following command in the new-opened elevated command prompt at the root of the C drive:
logman -start profile -p {eb7428f5-ab1f-4322-a4cc-1f1a9b2c5e98} 255 3 -ets
g. Do not Log off as the current user and switch to logon as the user who receives the profile problem (please tell me the user name).
h. Once the user experiences profile issue, please switch back as the administrator.
i. Stop the User Profile Service Tracing using the following command in an elevated command prompt
logman -stop profile -ets
j. Gather the profile.etl file in the root of the C drive and upload it to a shared space like Onedrive and shared the link here.
Kate Li
TechNet Community Support

SYSPREP Windows 8.1 Update 1 x64 - Drivers

Hi,
I currently have a problem with the automated install of the drivers with SYSPREP of Windows 8.1 x64.
I have a collection of drivers in c:\Drivers subfolders containing all the machine specific drivers. Unfortunately, with Windows 8, it does not seems to install the drivers the same way as Windows 7.
The trick i used with Windows 7 to get the drivers to install...
add "C:\Drivers;%SystemRoot%\inf" to the key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\DevicePath when syspreping the image.
The following entry in the unattend.xml file do not seem to be working :(
<component name="Microsoft-Windows-PnpCustomizationsNonWinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<DriverPaths>
<PathAndCredentials wcm:action="add" wcm:keyValue="1">
<Path>C:\Drivers</Path>
</PathAndCredentials>
</DriverPaths>
</component>
Unfortunately all my tricks are not working anymore with this version of Windows :(. i also tried modifying the DevicePath key in the
Wow6432Node instead... still no luck...
(HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\DevicePath)
Any idea how to get Windows 8 to install my drivers ?
Note that i don't use MDT or SCCM,
i used WSIM to create/validate the unattend.xml file. So everything is fine there...

Just letting you know guys that someone helped me on another forum to get the drivers to install. Here's the answer, if it can help others :
DpInst Method
Basically using the DPInst.exe (provided in the Windows Drivers Kit )and DPInst.xml file i was able to call DPInst within the Specialize phase asking it to install all drivers from a specified drivers folder ex. C:\Drivers

Sysprep Windows 7

Hi
I get the sysprep xml file from my friend and it work for him . Then when i use back my friend sysprep.xml file to create a new image it no longer able to work? Having error "Windows could not parse or process unattended answer file
[Specialize]". But it work for my friends. I use command during do sysprep
sysprep.exe /generalize /oobe /shutdown /unattend:xxx.xml
I check the setuperr.log in panther folder it show me
SYSPRP WinMain: The sysprep dialog box returned FALSE
SYSPRP ParseCommands:Found unsupported command line option '/?' [gle=0x000036b7]
SYSPRP WinMain:Unable to parse command-line arguments to sysprep; GLE = 0x36b7
SYSPRP WinMain:The sysprep dialog box returned FALSE
Do i need to uninstall any software after or after sysprep?.
Thank you..

Hi,
Try to add the full path to the .XML file to the SysPrep path switch, for example:
sysprep.exe /generalize /oobe /shutdown /unattend:"c:\windows\system32\sysprep\sysprep.xml"
BTW, please also refer to the following site:
A Windows 7 or a Windows Server 2008 R2 image deployment process stops when you try to deploy the image on another
computer
Best Regards
Dale

Windows 8.1 first boot time too long

After Sysprep, windows 8.1 tooks long time to boot, is it normal?
N.A.Malik

Hi,
Generally, when you sysprep an image and deploy it to other devices, it would prepare the device settings, registry update and other computer configuration. This phase would take some time. We call it as specialize and OOBE pass.
Here we have a metric to assess the first boot time, you can take a look at this guide:
First Boot Performance
http://msdn.microsoft.com/en-us/library/windows/hardware/jj130825.aspx
Alex Zhao
TechNet Community Support

Failed to run syspref "Test for CloneTag in registry to verify Sysprep completed"

Hi All
After install windows 7 and some application i try to capture and sysypref from running script
cscript \\server\DeploymentShare\Scripts\LiteTouch.wsf
i get below error
<![LOG[FAILURE (Err): -2147024894 0x80070002: Test for CloneTag in registry to verify Sysprep completed. - Unable to open registry key "HKEY_LOCAL_MACHINE\System\Setup\CloneTag" for reading.]LOG]!><time="12:47:30.000+000" date="01-31-2010" component="LTISysprep" context="" type="2" thread="" file="LTISysprep">
<![LOG[FAILURE ( 6191 ): Test for CloneTag in registry to verify Sysprep completed. - Unable to open registry key "HKEY_LOCAL_MACHINE\System\Setup\CloneTag" for reading.]LOG]!><time="12:47:30.000+000" date="01-31-2010" component="LTISysprep" context="" type="3" thread="" file="LTISysprep">
<![LOG[Litetouch deployment failed, Return Code = -2147467259 0x80004005]LOG]!><time="12:47:31.000+000" date="01-31-2010" component="LiteTouch" context="" type="3" thread="" file="LiteTouch">
<![LOG[For more information, consult the task sequencer log ...\SMSTS.LOG.]LOG]!><time="12:47:31.000+000" date="01-31-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property RetVal is now = -2147467259]LOG]!><time="12:47:31.000+000" date="01-31-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
Thanks ,
Davide

Hello
Just thought I would add my fix for this issue for anyone who is still getting it:
Go into Services.msc and stop and disable the following service: "Windows Media Player Network Sharing Service"
Then sysprep continues on past the stage where it gives the warning about the CloneTag key and successfully completes (hopefully!).
In this instance if you instead manually re-add the CloneTag key the image will give a BSOD on restart if you try to deploy it (mine did anyway).
It appears the error occurs and the sysprep stage fails so the CloneTag is not set to stop the deployment going any further.
If the task sequence is failing then it may be better to run a local sysprep and generalize from c:\windows\system32\sysprep\sysprep.exe as this gives better error messages.
It's also good to build the reference computer image in a virtual machine which you can snapshot before you start so can quickly revert back and try again if it messes up (as mine did a few times until I worked out the cause).
Your issue may not be the same as mine though but hope it helps someone.
Robin
P.S. Looking online it looks like the bug with the windows media sharing service goes back as far as pre RTM builds.
Robin Wilson
Thanks, this worked for me trying to sysprep Windows 7 x64 Home Premium.

Restore image failure with Windows 7 and 10.3.2 boot disc

I'm working on a sysprepped Windows 7 image. I took an image to a USB hard drive using ntfs-3g just before running sysprep then another afterward. I found some issues in the image so I reloaded the image taken before sysprep. Message on screen is Windows failed to start. A recent hardware or software change might be the cause... Status 0xc0000225, the boot selection failed because a required device is inaccessible.
This is the same computer that the image was created on - the sysprepped image installed just fine on another PC. Anyone run into this before?

Other information that might be useful - Windows 7 Enterprise 32 bit. HP 500B MT computer, Core 2 Duo, 4GB RAM. The imaging disc is the 10.3.2 January 2011 update.
I have several images that were taken at various stages of the installation process and none of them work.

Sysprep poppup after deploy image

I sysprepped the machine with sysprep tool. Selected Out-Of-Box Experience and Generalize then restart. Then I capture the image. Then I'm deploying the image. When the laptop is ready to use I get the sysprep tool window automatically opened everytime.
I can use MSOOBE tool then it wont appear anymore in C:\Windows\System32\oobe. You can use this tool but you need to select country,computername,password,wifi etc.
Is there another way to close this sysprep tool after deploying an image? I put the WDSClient.xml in WDS server and in the image my unattend.xml I have the Reseal option configured mode: Audit. I tried to change the mode to OOBE but it didnt work.
WDSClientunattend.xml
<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="windowsPE">
<component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SetupUILanguage>
<UILanguage>nl-nl</UILanguage>
</SetupUILanguage>
<InputLocale>nl-nl</InputLocale>
<SystemLocale>nl-nl</SystemLocale>
<UILanguage>nl-nl</UILanguage>
<UserLocale>nl-nl</UserLocale>
<UILanguageFallback>en-US</UILanguageFallback>
</component>
<component name="Microsoft-Windows-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<DiskConfiguration>
<WillShowUI>OnError</WillShowUI>
<Disk wcm:action="add">
<CreatePartitions>
<CreatePartition wcm:action="add">
<Order>1</Order>
<Size>300</Size>
<Type>Primary</Type>
</CreatePartition>
<CreatePartition wcm:action="add">
<Extend>true</Extend>
<Order>2</Order>
<Type>Primary</Type>
</CreatePartition>
</CreatePartitions>
<ModifyPartitions>
<ModifyPartition wcm:action="add">
<Active>true</Active>
<Format>NTFS</Format>
<Label>System</Label>
<Order>1</Order>
<PartitionID>1</PartitionID>
</ModifyPartition>
<ModifyPartition wcm:action="add">
<Format>NTFS</Format>
<Label>System</Label>
<Order>2</Order>
<PartitionID>2</PartitionID>
</ModifyPartition>
</ModifyPartitions>
<DiskID>0</DiskID>
<WillWipeDisk>true</WillWipeDisk>
</Disk>
</DiskConfiguration>
<ImageInstall>
<OSImage>
<InstallTo>
<DiskID>0</DiskID>
<PartitionID>2</PartitionID>
</InstallTo>
<InstallToAvailablePartition>false</InstallToAvailablePartition>
<WillShowUI>OnError</WillShowUI>
</OSImage>
</ImageInstall>
<UserData>
<ProductKey>
<WillShowUI>OnError</WillShowUI>
<Key>hidden due security</Key>
</ProductKey>
<AcceptEula>true</AcceptEula>
</UserData>
<EnableNetwork>true</EnableNetwork>
<ComplianceCheck>
<DisplayReport>OnError</DisplayReport>
</ComplianceCheck>
<DynamicUpdate>
<Enable>true</Enable>
</DynamicUpdate>
<UpgradeData>
<WillShowUI>Never</WillShowUI>
</UpgradeData>
</component>
</settings>
<cpi:offlineImage cpi:source="wim:d:/w7dvd/sources/install.wim#Windows 7 PROFESSIONAL" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>
Unattend.xml
<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="oobeSystem">
<component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Reseal>
<Mode>Audit</Mode>
</Reseal>
</component>
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<OOBE>
<ProtectYourPC>1</ProtectYourPC>
<HideEULAPage>true</HideEULAPage>
<NetworkLocation>Work</NetworkLocation>
</OOBE>
<AutoLogon>
<Enabled>true</Enabled>
<Username>Administrator</Username>
</AutoLogon>
<UserAccounts>
<LocalAccounts>
<LocalAccount wcm:action="add">
<Description>First Admin User</Description>
<DisplayName>User</DisplayName>
<Group>administrators</Group>
<Name>User</Name>
</LocalAccount>
</LocalAccounts>
</UserAccounts>
</component>
</settings>
<settings pass="specialize">
<component name="Microsoft-Windows-IE-InternetExplorer" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Home_Page>www.google.nl</Home_Page>
<AllowedSites></AllowedSites>
</component>
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ProductKey></ProductKey>
</component>
</settings>
<cpi:offlineImage cpi:source="wim:d:/w7dvd/sources/install.wim#Windows 7 PROFESSIONAL" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>

Hi,
Sysprep window usually appears when entering audit mode, I think you got into audit mode automatically after each reboot.
<settings pass="oobeSystem">
         <component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
             <Reseal>
                 <Mode>Audit</Mode>
             </Reseal>
After a computer boots to audit mode, the computer will continue to boot to audit mode until you configure the computer to boot to Windows Welcome
You can open registry editor, locate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\State
is there a modify key? delete it, reboot your PC.
Or in the sysprep pop-up box, choose the out of the box experience (oobe) and quit.
If this doesn't work, you can run “sysprep /oobe” command to return to the Windows Welcome screen, The /oobe option instructs Windows to run Windows Welcome the next time the computer boots, use this way to enter the audio mode.
Yolanda Zhu
TechNet Community Support

T400 with ATI Radeon HD 3400. Driver not found after running ImageX.exe /Capture

Hello,
I was able to reproduce the following problem on a T400.
- unattended installation of WXP-SP3 (slipstreamed)
- reboot
- install latest ATI driver from Lenovo/IBM site (8.503.2.2-080818a-069536C)
- reboot
At this point, the video driver is well configured.
- Reboot once or twice, video driver still good.
- Boot the T400 on WinPE 2.0
- Capture the C:\ to a network file share using ImageX.exe (from Microsoft's WAIK 1.1)
- Shutdown the T400, and reboot on C:\
- At this point, video driver is "lost". The Hardware Wizard says "new driver found", but stick with default VGA.
Then I get an ATI error telling the driver is missing or not well installed.
- When rebooting several times, suddenly the card is back in the device manager as a Radeon HD 3400.
(without re-installing the driver ...)
Anyone has an explanation ?
Please not I did not run "sysprep.exe" before capturing with ImageX.exe
stefan

Update on this problem.
After running "sysprep.exe -mini -quiet -reseal -shutdown", I ran the "ImageX.exe /capture".
After rebooting the T400, the ATI driver was fine.
Either is a coincidence (but I could repeat it 3 times...) or it is not advised to run "ImageX.exe /Capture" on a non-syspreped Windows XP.
I know that a non-syspreped Vista system has a limitation if captured with ImageX.exe. But I am not aware on any limitation with XP.
Stefan

CopyProfile causes search shortcuts on all users search screen to point to the default user profile

So, I'm sysprepping Windows 8.1 with an answer file set to CopyProfile=True. I log in to my customized account and sysprep /generalize /oobe /shutdown /unattend:unattend.xml. Everything copies over just fine. I get my layout in the Metro
start menu, etc, etc...
However, when I log in to the default profile I originally customized after sysprep, everything works great. But when I log into any other account created during sysprep or thereafter and I hit the windows key and do a search for "Update" -
and select "Windows Update" I get an error:
Title: C:\Users\ORIGINALDEFAULTACCOUNT\AppData\Local\Packages\windows.immersivecontrol.....
Message: "Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item."
It's not every single shortcut... Only a certain fiew.
I get a nearly identical message when trying to launch "Programs and Features" from start. If I manually navigate to these controls, they load up just fine. Just the search items seem to be pointing to the wrong point. Is there like
a cache that copyprofile seems to be copying over for some reason?
I've tried modifying the built in administrator account thinking Microsoft has gotten a bit stricter on which account I can use, but I get the same error.
Can anybody help?

Thanks for the response!
I ran SFC and all files come up good.
I know I can take permissions/ownership to access the file, but I'm not sure I would want to do this.
I may not have been clear and perhaps I need to clarify.
Here is my process:
I create account1 prior to sysprepping. I customize this profile to my liking and copy it over with copyprofile during the sysprep phase.
account1 is now my default profile.
During the sysprep phase I also create account2. After sysprep completes, when I login to account2 and attempt to access "Programs and Features" or "Windows Update" from metro search, I get the error with the following title:
C:\Users\account1\AppData\Local\Packages\windows.immersivecontrol
So even though I'm logged into account2, if I do a search and try to run these two shortcuts, they point to a file in account1's profile.
If I create a new profile at this point, the same problem occurs, as account1 is the default profile and it appears that the shortcuts are being carried over as part of the default profile.
Taking ownership/changing permissions of the file/folder does not fix the fact that the shortcuts pointing to the account were copied over the in the first place.
I could change it so that Everyone has read permissions to this part of the default profiles folder, but I've been lead to believe that this is not best practice.
I've reimaged the computer and started over from scratch, but it appears that the default profile still includes these broken shortcuts.
Perhaps there is a cached search history I need to delete somewhere before sysprepping?
I also noticed that these "shortcuts" are in a 'packages' folder - are these 'shortcuts' actually windows 8 apps? If so, maybe there's something that's being missed in the provisioning process?

Microsoft VDI Pooled Workgroup VMs

I'm trying to create pooled workgroup VMs. That means that the VMs that the VDI pool creates wouldn't be domain joined. Is this possible?
Also, does anyone have any working syspreped Windows 7 SP1 answer file? Every time I try, I get an error "vdi unable to retrieve the details of the virtual desktop collection". I have removed the top line shown below as some threads mentioned but
I still get the error. I've tried this using the GUI, would doing it through powershell make a difference?
<?xmlversion="1.0"encoding="utf-8"?>
Thanks!

Hi,
Thank you for your posting in windows Server Forum.
As per my research, I can say that this is prerequisites for installing RDS role on server. (Quoted from below article)
1. All RDS Servers must be joined to the same Active Directory Domain.
2. Before you can create a VDI collection, the template (gold image) Virtual Machine must be sys-prepped.
More information:
Windows 8 / Windows Server 2012: Pooled Virtual Desktop Infrastructure
Custom answer file for New-RDVirtualDesktopCollection fails!
Hope it helps!
Thanks,
Dharmesh

Sysprep Windows 8.1

Similar Messages

Maybe you are looking for