Share via

How to prevent Windows 10 OSD prompting for network discovery

  • Article

Question

Wednesday, August 17, 2016 9:28 PM

Hello,

We are running SCCM 2012 R2 SP1 (Cumulative Update 2) and we are deploying Windows 7 and 8.1 without any issues.

The Windows 10 (Education) OS actually deploys fine it is the first login that I am prompted "Do you want to allow your PC to be discoverable by other PC's and devices on this network?".

This is my districts domain so I am always going to want that to be a consistent answer that is scripted. I honestly don't care if it is a Yes or a No.

I have tried adding the network location, set to work, in my unattend xml and it didn't have any effect on this.

I have tried all sorts of services and firewall settings to allow everything to be public, none of that worked.

Any thoughts on how to fix this?

Thanks in advance!

Portland Public Schools / Systems Administrator II

All replies (10)

Thursday, August 18, 2016 3:52 AM âś…Answered | 1 vote

Just to be sure, did you configure the network location on the oobeSystem -component with Microsoft-Shell-Setup/OOBE? Haven't seen the behavior in Windows 10 myself, but found out that you're not the only one having the problem... Another work around that crossed my sight:

<unattend xmlns="urn:schemas-microsoft-com:unattend">
    <settings pass="oobeSystem">
        <component name="Microsoft-Windows-Shell-Setup"........>
            <FirstLogonCommands>
                <SynchronousCommand wcm:action="add">
                    <Order>1</Order>
                    <CommandLine>REG ADD &quot;HKLM\System\CurrentControlSet\Control\Network\NewNetworkWindowOff&quot; /F</CommandLine>
                    <Description>No New Network Block</Description>
                    <RequiresUserInput>true</RequiresUserInput>
                </SynchronousCommand>
            </FirstLogonCommands>
        </component>
    </settings>
</unattend>

Thursday, August 18, 2016 4:29 AM

Just a quick look, perhaps this can be set via GPO. See if disabling the "Preventd the computer from joining a homegroup" prevents this prompt on first logon.

Computer Configuration/Administrative Templates/Windows Components/HomeGroup/Prevent the computer from joining a homegroup

Thursday, August 18, 2016 9:20 AM

Just a quick look, perhaps this can be set via GPO. See if disabling the "Preventd the computer from joining a homegroup" prevents this prompt on first logon.

Computer Configuration/Administrative Templates/Windows Components/HomeGroup/Prevent the computer from joining a homegroup

Domain GPOs have no effect during OSD.

Jason | http://blog.configmgrftw.com | @jasonsandys

Thursday, August 18, 2016 4:30 PM

Just a quick look, perhaps this can be set via GPO. See if disabling the "Preventd the computer from joining a homegroup" prevents this prompt on first logon.

Computer Configuration/Administrative Templates/Windows Components/HomeGroup/Prevent the computer from joining a homegroup

Domain GPOs have no effect during OSD.

Jason | http://blog.configmgrftw.com | @jasonsandys

Yeah exactly, no domain yet no GPO yet.

Portland Public Schools / Systems Administrator II

Thursday, August 18, 2016 4:32 PM

Just to be sure, did you configure the network location on the oobeSystem -component with Microsoft-Shell-Setup/OOBE? Haven't seen the behavior in Windows 10 myself, but found out that you're not the only one having the problem... Another work around that crossed my sight:

<unattend xmlns="urn:schemas-microsoft-com:unattend">
    <settings pass="oobeSystem">
        <component name="Microsoft-Windows-Shell-Setup"........>
            <FirstLogonCommands>
                <SynchronousCommand wcm:action="add">
                    <Order>1</Order>
                    <CommandLine>REG ADD &quot;HKLM\System\CurrentControlSet\Control\Network\NewNetworkWindowOff&quot; /F</CommandLine>
                    <Description>No New Network Block</Description>
                    <RequiresUserInput>true</RequiresUserInput>
                </SynchronousCommand>
            </FirstLogonCommands>
        </component>
    </settings>
</unattend>

Thanks for this!

I have updated my unattend and I am testing it now.

Portland Public Schools / Systems Administrator II

Thursday, August 18, 2016 4:57 PM

Hello,

 My 64-bit unattend.xml that has been in use for me was this:

<?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://wnsccm.ad.ppsnet/e$/OSImages/WIN_10_64_EDUCATION/sources/install.wim#Windows 10 Education" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>

and now I have edited it to look like this:

<?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">
           <FirstLogonCommands>
             <SynchronousCommand wcm:action="add">
              <Order>1</Order>
               <CommandLine>REG ADD &quot;HKLM\System\CurrentControlSet\Control\Network\NewNetworkWindowOff&quot; /F</CommandLine>
                <Description>No New Network Block</Description>
                <RequiresUserInput>true</RequiresUserInput>
            </SynchronousCommand>
            <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://wnsccm.ad.ppsnet/e$/OSImages/WIN_10_64_EDUCATION/sources/install.wim#Windows 10 Education" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>

I can tell that my unattend is not working because it is now back to prompting for wireless network during the OOBE and then on first login I am still seeing Network Discovery Wizard.

Did implement that incorrectly?

Portland Public Schools / Systems Administrator II

Thursday, August 18, 2016 5:41 PM | 1 vote

Did you check the registry, is the value setted there? Suspecting that &quot does not work, so change it to "

Thursday, August 18, 2016 8:41 PM

Hello,

 My 64-bit unattend.xml that has been in use for me was this:

<?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://wnsccm.ad.ppsnet/e$/OSImages/WIN_10_64_EDUCATION/sources/install.wim#Windows 10 Education" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>

and now I have edited it to look like this:

<?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">
           <FirstLogonCommands>
             <SynchronousCommand wcm:action="add">
              <Order>1</Order>
               <CommandLine>REG ADD &quot;HKLM\System\CurrentControlSet\Control\Network\NewNetworkWindowOff&quot; /F</CommandLine>
                <Description>No New Network Block</Description>
                <RequiresUserInput>true</RequiresUserInput>
            </SynchronousCommand>
            <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://wnsccm.ad.ppsnet/e$/OSImages/WIN_10_64_EDUCATION/sources/install.wim#Windows 10 Education" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>

I can tell that my unattend is not working because it is now back to prompting for wireless network during the OOBE and then on first login I am still seeing Network Discovery Wizard.

Did implement that incorrectly?

Portland Public Schools / Systems Administrator II

Well that was the fix, I screwed up merging that into my unattend.xml.

I was missing the </FirstLogonCommands>  .. here is my updated xml:

<?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">
            <FirstLogonCommands>
                <SynchronousCommand wcm:action="add">
                    <Order>1</Order>
                    <CommandLine>REG ADD &quot;HKLM\System\CurrentControlSet\Control\Network\NewNetworkWindowOff&quot; /F</CommandLine>
                    <Description>No New Network Block</Description>
                    <RequiresUserInput>true</RequiresUserInput>
                </SynchronousCommand>
            </FirstLogonCommands>
            <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://wnsccm.ad.ppsnet/e$/OSImages/WIN_10_64_EDUCATION/sources/install.wim#Windows 10 Education" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>

The system did not prompt for network discovery!

Thanks again!!!!!!!!

Portland Public Schools / Systems Administrator II

Thursday, August 18, 2016 11:47 PM

Just a quick look, perhaps this can be set via GPO. See if disabling the "Preventd the computer from joining a homegroup" prevents this prompt on first logon.

Computer Configuration/Administrative Templates/Windows Components/HomeGroup/Prevent the computer from joining a homegroup

Domain GPOs have no effect during OSD.

Jason | http://blog.configmgrftw.com | @jasonsandys

That is correct. Post OSD, when domain join occurs, it does.

Friday, August 19, 2016 1:29 AM

Domain join does not happen post OSD so that's not correct either.

Jason | http://blog.configmgrftw.com | @jasonsandys