none
SCCM 2012 R2: Build and Capture - Windows 8.1 prompting for network

    Question

  • I have upgraded my SCCM 2012 SP1 (CU2) to SCCM 2012 R2 and I am attempting to Build and Capture Windows 8.1 Enterprise. Everything is perfect except for the OS prompting for a network selection during the process, if I click "next" on that screen the Capture finishes without incident. The same is true of the Deploy as well...

    Is this a bug from my upgrade?


    Portland Public Schools / Systems Administrator II


    • Edited by Adam Seitz Friday, November 01, 2013 9:02 PM spelling
    Friday, November 01, 2013 9:00 PM

Answers

  • Hi Adam,

    This is a normal behavior unless you use an unattend.xml response file, since the 1st Windows 8 release.

    You need to provide the response for the oobeSystem pass with the following parameters (for x64 version):

    <settings pass="oobeSystem">
            <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>
                    <HideEULAPage>true</HideEULAPage>
                    <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
                    <NetworkLocation>Work</NetworkLocation>
                    <HideOnlineAccountScreens>true</HideOnlineAccountScreens>
                    <HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
                    <HideLocalAccountScreen>true</HideLocalAccountScreen>
                </OOBE>
                <RegisteredOwner>Microsoft</RegisteredOwner>
            </component>
        </settings>

    • Marked as answer by Adam Seitz Monday, November 25, 2013 9:59 PM
    Friday, November 08, 2013 11:19 AM

All replies

  • I haven't observed that screen yet - are you able to supply a screen capture?


    Jamie Courtes MCTS - SCCM 2007 MCTS - SCCM 2012

    Friday, November 01, 2013 9:02 PM
  • I had 6 photos to upload that told the story, but apprently two is a forum limit. So here is a screen shot of what happens after the "Deploy Image" Step and before the "Configuration Manger" step. After that everything else proceeds normally.


    Portland Public Schools / Systems Administrator II

    Friday, November 01, 2013 9:44 PM
  • Hi,

    Please check the log file smsts.log.

    General location for all operating system deployment and task sequence log events.

    Log file location:

    If task sequence completes when running in the full operating system with an Configuration Manager client installed on the computer: <ConfigMgrInstallationPath>\logs

    If task sequence completes when running in the full operating system with no Configuration Manager client installed on the computer: %temp%\SMSTSLOG

    If task sequence completes when running in WindowsPE: <largest fixed partition>\SMSTSLOG


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.


    Tuesday, November 05, 2013 8:13 AM
    Moderator
  • Please check the log file smsts.log.

    Just out of curiosity: what do you (Xin) expect to see there?

    Adam: are you using a customized unattend xml somehow?


    Torsten Meringer | http://www.mssccmfaq.de

    Tuesday, November 05, 2013 8:37 AM
  • Hi Torsten,

    Based on my understanding, smsts.log will records the task sequence activities.
    If I have any problem, please feel free to point out.

    Thank you.


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

    Tuesday, November 05, 2013 9:11 AM
    Moderator
  • Based on my understanding, smsts.log will records the task sequence activities.
    True, but it does not list any activities that are initiated by the OS or minisetup itself.

    Torsten Meringer | http://www.mssccmfaq.de

    Tuesday, November 05, 2013 9:28 AM
  • Please check the log file smsts.log.

    Just out of curiosity: what do you (Xin) expect to see there?

    Adam: are you using a customized unattend xml somehow?


    Torsten Meringer | http://www.mssccmfaq.de

    Torsten: I am not using a customized XML file just the built-in OSD task sequence for image deployment and image capture. I have had years of success with SCCM (since 2007) using the same process I am using today. Up until Windows 8.1 it ran without any intervention from the user, now it requires a selection of network after the OS deployment and Before the ConfigMgr Setup step.

    I was trying on a Laptop and maybe something with that particular model is the cause, I will try it on a desktop today and see if it is wireless glitch or something. 

    Xin: I will try to get a look at the log later today, but the image completes with 100% success as long as I select a network (both during the capture and the deploy). I was wondering if maybe my "Setup network" step in my OSD is bugged from my upgrade from SCCM 2012 SP1 CU2 to SCCM 2012 R2.

    Thanks,


    Portland Public Schools / Systems Administrator II


    • Edited by Adam Seitz Tuesday, November 05, 2013 4:42 PM
    Tuesday, November 05, 2013 4:40 PM
  • Hi Adam,

    This is a normal behavior unless you use an unattend.xml response file, since the 1st Windows 8 release.

    You need to provide the response for the oobeSystem pass with the following parameters (for x64 version):

    <settings pass="oobeSystem">
            <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>
                    <HideEULAPage>true</HideEULAPage>
                    <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
                    <NetworkLocation>Work</NetworkLocation>
                    <HideOnlineAccountScreens>true</HideOnlineAccountScreens>
                    <HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
                    <HideLocalAccountScreen>true</HideLocalAccountScreen>
                </OOBE>
                <RegisteredOwner>Microsoft</RegisteredOwner>
            </component>
        </settings>

    • Marked as answer by Adam Seitz Monday, November 25, 2013 9:59 PM
    Friday, November 08, 2013 11:19 AM
  • Thanks! I finally got some time to try this and it worked!This link helped too: http://scug.be/sccm/2010/02/02/sccm-windows-7-deployments-amp-unattended-xml/

    Thanks,


    Portland Public Schools / Systems Administrator II

    Monday, November 25, 2013 10:00 PM
  • Hi LillonelC

    Can you point out how and where to do this?

    When capturing with MDT 2013 on VMware I do not see this, naturaly, since the "machine" only has one network adapter.

    But when deploying to a Laptop I get the wireless Setup screen...

    On beforehand Thank You!
    With kind regards

    Wednesday, November 19, 2014 8:21 PM
  • Hi LillonelC

    Can you point out how and where to do this?

    When capturing with MDT 2013 on VMware I do not see this, naturaly, since the "machine" only has one network adapter.

    But when deploying to a Laptop I get the wireless Setup screen...

    On beforehand Thank You!
    With kind regards

    We aren't using MDT but what we did was create a package called Windows 8.1 - Compnents. In it  placed a file named "32Bit-Unattend.xml" and 1 named "64Bit-Unattend.xml". 

    During the capture in the "Apply Operating System Image" I put a check in the box "Use an unattended or Sysprep answer file for a custom installation". The package was Windows 8.1 - Compnents the File name was "32Bit-Unattend.xml".

    I did the same for 64-bit and used the 64-bit version.

    Here is content of the 32-bit file:

    <?xml version="1.0" encoding="utf-8"?>
    <unattend xmlns="urn:schemas-microsoft-com:unattend">
        <settings pass="oobeSystem">
            <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>
                    <HideOnlineAccountScreens>true</HideOnlineAccountScreens>
                    <HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
                    <HideLocalAccountScreen>true</HideLocalAccountScreen>
                </OOBE>
            </component>
        </settings>
        <cpi:offlineImage cpi:source="wim://SERVERNAME/e$/osimages/win_8.1_x86/sources/install.wim#Windows 8.1 Enterprise" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
    </unattend>



    Here is the content of the 64-bit file:

    <?xml version="1.0" encoding="utf-8"?>
    <unattend xmlns="urn:schemas-microsoft-com:unattend">
        <settings pass="oobeSystem">
            <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>
                    <HideEULAPage>true</HideEULAPage>
                    <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
                    <NetworkLocation>Work</NetworkLocation>
                    <HideOnlineAccountScreens>true</HideOnlineAccountScreens>
                    <HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
                    <HideLocalAccountScreen>true</HideLocalAccountScreen>
                </OOBE>
            </component>
        </settings>
        <cpi:offlineImage cpi:source="wim://SERVERNAME/e$/osimages/win_8.1_x64/sources/install.wim#Windows 8.1 Enterprise" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
    </unattend>

    If that doesn't help I can try to clarify it a bit further.

    PS You won't need to do this for the deploy, only the capture.


    Portland Public Schools / Systems Administrator II



    • Edited by Adam Seitz Wednesday, November 19, 2014 9:31 PM
    Wednesday, November 19, 2014 9:25 PM
  • You said you created a package for these? How did you handle the command line in the package?
    Tuesday, April 28, 2015 2:07 PM
  • The key part is: "During the capture in the "Apply Operating System Image" I put a check in the box "Use an unattended or Sysprep answer file for a custom installation". The package was Windows 8.1 - Compnents the File name was "32Bit-Unattend.xml"."
    You don't have to create a program at all. The package is just needed in order to "store" the xml file. 

    Torsten Meringer | http://www.mssccmfaq.de

    Tuesday, April 28, 2015 2:24 PM