Help Please-Profile

[Netmedic]

I am at the last point of getting my Windows 7 image ready for deployement. I have all my task sequences for Side-by-side migration and my bare metal sequences working great. I can get my image to load and install all my applications and even get my files from one computer to another. When I thought I was all done and new problem came up.

 

I use the SCCM capture media to capture my image. Not sure why except its seems easier and i have been going it that way for 4 years. Anyway.. I have my unattend file in the syspre folder and have the copy profile parameters listed. I only have the administrator profile on the reference machine. I run the SCCM capture utility and my image is captured and I am able to deploy it. When I login to a new machine with this image for the first time with a new user I get the profile (look and feel) as I did when I was the administrator. Great! that is what I wanted. However if I login again with a another new person I do not get the desktop and such the same. It resorts the the basic Windows Aero interface.

 

What am I doing wrong! I read something about having to place another unattend file into my Task sequence with a copy profile. Any time I have tried to put a unattent file in my task sequence I get some wierd "Checking Video" performance in the back ground while my applications install. Not the cleanest looking interfact. It's almost as if the task sequence is not wating for the sysprep and the windows to come back into PE before continuing with the task sequence. I also was confused on what sections of the unattend file I need to supply in the image file and the task sequence. I thought that SYSPEP would ingnore the sections depending on what phase its on.

 

So in summary I am looking for someone to hold my hand a little and help me with this last piece of this puzzle.

[Lucid]

Does this help?

http://myitforum.com/cs2/blogs/rbennett806/pages/using-sccm-to-capture-and-deploy-windows-7.aspx

 

About 3/4 of the way down is a link to a sample .XML file we use when we deploy our OS. And while we use an automated Build and Capture process (which I recommend you think about trying to set up), it may give you an idea of what sections are safe to start with (not all of the selections available when building your .XML will work when using SCCM OSD)...

[Netmedic]

Does this help?

http://myitforum.com/cs2/blogs/rbennett806/pages/using-sccm-to-capture-and-deploy-windows-7.aspx

 

About 3/4 of the way down is a link to a sample .XML file we use when we deploy our OS. And while we use an automated Build and Capture process (which I recommend you think about trying to set up), it may give you an idea of what sections are safe to start with (not all of the selections available when building your .XML will work when using SCCM OSD)...

 

 

Ok I tried you steps and put the unattend.xml file in my OSD TS and the copy profile seems to work now, but after the configuration manager client installs the rest of my task sequence does not seem to install the rest of my applications. If I take out the unattend file then the applications complete but my profile does not copy. If I have the unattend file in the TS then the system reboots after configuration manager install and I get the checking video performance where it seems the rest of my TS seems to want to run rather than in the WinPE. I tried putting a reboot in the TS but that fails as well.

[Lucid]

Do you specifically place an unattend file in the sysprep folder within your captured image? I don't quite understand that related statement in your original post - so maybe I missed something.

 

You say that if you leave the file in your TS then it reboots after the configuration manager client installs, and that your TS wants to run rather than in WinPE? I don't quite understand that statement either (might have just been too long of a day for me). At this point in the deployment process, things should not be running in Windows PE. They should be running the installation process for the OS you're installing. Would you be able to post a screenshot of your TS or something to help clarify how you've got it configured?

[Netmedic]

Do you specifically place an unattend file in the sysprep folder within your captured image? I don't quite understand that related statement in your original post - so maybe I missed something.

 

You say that if you leave the file in your TS then it reboots after the configuration manager client installs, and that your TS wants to run rather than in WinPE? I don't quite understand that statement either (might have just been too long of a day for me). At this point in the deployment process, things should not be running in Windows PE. They should be running the installation process for the OS you're installing. Would you be able to post a screenshot of your TS or something to help clarify how you've got it configured?

 

I will try to explain further.

 

I do not have any unattend.xml file on my image that was captured. I place the unattend.xml file in the task sequence. When the task sequence runs it gets to the step where it installs the Configuration Manager Client. When finished it will reboot the client being imaged. When it finished the reboot it does not go back into the WinPE screen that I see when I first start our Task Sequence. The WinPE screens have our Corporate logon on them. What I get is a black screen with the words "checking video performance". That will stay there while the rest of the task sequence runs. The task sequence installs applies certain settings and applications. If I place a reboot in the Task Sequence after the Configuration Manager install then my WinPE "Corporate" page comes up but the task sequence does not run. It does goes through the rest of the programs realy fast. In other words I can see the group names and the names of the actions like "Install Access" but like I said there is no further progress bar it just burns through all my group names and such until it completes. Nothing gets processed. I tired putting a reboot in one of my applicatons programs which rebooted and the task sequence restarted but insted of seeing the "Checking Video Performance" I see something about peparing for fist logon which stays on the screen until the rest of the task sequence completes.

 

If I perform an image with my unattend.xml file in the image then my WinPE (with corporate logo) is there in the beginning and after the client reboots it reboots back into WinPE to complete the rest of the Task Sequence.

 

Not sure what I am doing wrong here. Its getting realy frustrating.

[Lucid]

So if you have an .XML file in the image the background displays correctly? But if you add the .XML to the task sequence it does not? Have you checked the .XML to make sure there's no odd video related setting that might be causing a conflict/problem? If you think there's a problem with your .XML file, would you want to post it to let us see if we spot anything?

 

Also, if you can access the machine after a failed install, take a look through the SCCM OSD log files on it. Also, depending what's happening, you might be able to get some basic info back by checking the OS advertisement logs from within the ConfigMgr console...

[Netmedic]

So if you have an .XML file in the image the background displays correctly? But if you add the .XML to the task sequence it does not? Have you checked the .XML to make sure there's no odd video related setting that might be causing a conflict/problem? If you think there's a problem with your .XML file, would you want to post it to let us see if we spot anything?

 

Also, if you can access the machine after a failed install, take a look through the SCCM OSD log files on it. Also, depending what's happening, you might be able to get some basic info back by checking the OS advertisement logs from within the ConfigMgr console...

 

 

Here is my XML file

 

<?xml version="1.0" encoding="utf-8"?>

<unattend xmlns="urn:schemas-microsoft-com:unattend">

<settings pass="specialize">

<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<CopyProfile>true</CopyProfile>

<TimeZone>Eastern Standard Time</TimeZone>

<ShowWindowsLive>false</ShowWindowsLive>

</component>

<component name="Microsoft-Windows-Deployment" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<RunSynchronous>

<RunSynchronousCommand wcm:action="add">

<Description>Add Administrator</Description>

<Order>1</Order>

<Path>net user administrator /active:yes</Path>

</RunSynchronousCommand>

</RunSynchronous>

</component>

<component name="Microsoft-Windows-Security-SPP-UX" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<SkipAutoActivation>true</SkipAutoActivation>

</component>

</settings>

<settings pass="generalize">

<component name="Microsoft-Windows-Security-SPP" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<SkipRearm>0</SkipRearm>

</component>

<component name="Microsoft-Windows-PnpSysprep" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<DoNotCleanUpNonPresentDevices>true</DoNotCleanUpNonPresentDevices>

<PersistAllDeviceInstalls>true</PersistAllDeviceInstalls>

</component>

</settings>

<settings pass="oobeSystem">

<component name="Microsoft-Windows-International-Core" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<InputLocale>en-us</InputLocale>

<SystemLocale>en-us</SystemLocale>

<UILanguage>en-us</UILanguage>

<UILanguageFallback>en-us</UILanguageFallback>

<UserLocale>en-us</UserLocale>

</component>

<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" 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>

<HideEULAPage>true</HideEULAPage>

<HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>

<NetworkLocation>Work</NetworkLocation>

<ProtectYourPC>3</ProtectYourPC>

<SkipMachineOOBE>true</SkipMachineOOBE>

<SkipUserOOBE>true</SkipUserOOBE>

</OOBE>

<UserAccounts>

<AdministratorPassword>

<Value>SQB0AGkAcwBnADAAMABkAEEAZABtAGkAbgBpAHMAdAByAGEAdABvAHIAUABhAHMAcwB3AG8AcgBkAA==</Value>

<PlainText>false</PlainText>

</AdministratorPassword>

<LocalAccounts>

<LocalAccount wcm:action="add">

<Description>Local Administrator</Description>

<DisplayName>Administrator</DisplayName>

<Group>Administrators</Group>

<Name>Administrator</Name>

</LocalAccount>

</LocalAccounts>

</UserAccounts>

<RegisteredOrganization>Knape & Vogt</RegisteredOrganization>

<RegisteredOwner>Infomation Tecnology</RegisteredOwner>

<ShowWindowsLive>false</ShowWindowsLive>

</component>

</settings>

<cpi:offlineImage cpi:source="catalog:c:/win7/install_windows 7 enterprise.clg" xmlns:cpi="urn:schemas-microsoft-com:cpi" />

</unattend>

[Lucid]

Well, I don't see anything obviously out of whack in your .XML (hopefully another set of eyes will chime in if they spot anything). So if it was me, I'd first try removing most of the non-required items in the oobeSystem pass and see if that fixes the issue. In the past I remember spending a ton of time adding things one by one because it kept blowing up on me when I deployed the OS. So start with the bare, bare, minimums and build it up...