/build/static/layout/Breadcrumb_cap_w.png

New issues with deploying Windows 10 (1803) since upgrading to 6.1

Hello Everyone,


I have been having issues for a little while since upgrading to 6.1 on my SDA.  When running the script, everything runs fine until I start installing Windows.  From there, I get an error message inside of Windows setup that consists of the following:

Windows cannot locate the disk and partition specified in the unattend answer file's <ImageInstall> setting. Make sure the setting references a valid partition and restart the installation.


I have not changed anything on the SDA before the 6.1 upgrade and was not having the issue.  Below I have the script (I did change all of the information that is pertinent to my company).

Script:

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

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

<unattend xmlns="urn:schemas-microsoft-com:unattend" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

  <settings pass="windowsPE">

    <component name="Microsoft-Windows-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">

      <UseConfigurationSet>true</UseConfigurationSet>

      <UserData>

        <AcceptEula>true</AcceptEula>

        <Organization>Contoso</Organization>

      </UserData>

      <ImageInstall>

        <OSImage>

          <InstallToAvailablePartition>true</InstallToAvailablePartition>

          <InstallFrom>

            <MetaData wcm:action="add">

              <Key>/image/index</Key>

              <Value>5</Value>

            </MetaData>

          </InstallFrom>

        </OSImage>

      </ImageInstall>

    </component>

    <component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">

      <UILanguage>en-us</UILanguage>

      <SetupUILanguage>

        <UILanguage>en-us</UILanguage>

      </SetupUILanguage>

      <InputLocale>en-us</InputLocale>

      <SystemLocale>en-us</SystemLocale>

      <UserLocale>en-us</UserLocale>

    </component>

  </settings>

  <settings pass="specialize">

    <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">

      <RegisteredOrganization>Contoso</RegisteredOrganization>

      <ProductKey>KEY</ProductKey>

      <TimeZone>Central Standard Time</TimeZone>

      <AutoLogon>

        <Enabled>true</Enabled>

        <Username>Admin</Username>

        <Password>

          <PlainText>true</PlainText>

          <Value>12345</Value>

        </Password>

        <LogonCount>4</LogonCount>

      </AutoLogon>

      <ComputerName>*</ComputerName>

    </component>

    <component name="Microsoft-Windows-UnattendedJoin" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">

      <Identification>

        <JoinDomain>contoso.com</JoinDomain>

        <Credentials>

          <Domain>contoso.com</Domain>

          <Username>service</Username>

          <Password>12345</Password>

        </Credentials>

      </Identification>

    </component>

    <component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">

      <RunSynchronous>

        <RunSynchronousCommand wcm:action="add">

          <Path>reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows NT\CurrentVersion\NetworkList\Signatures\FirstNetwork" /v Category /t REG_DWORD /d 00000000 /f</Path>

          <Description>Setting Network Location</Description>

          <Order>1</Order>

          <WillReboot>OnRequest</WillReboot>

        </RunSynchronousCommand>

      </RunSynchronous>

    </component>

  </settings>

  <settings pass="oobeSystem">

    <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">

      <OOBE>

        <HideEULAPage>true</HideEULAPage>

        <NetworkLocation>Work</NetworkLocation>

        <SkipMachineOOBE>false</SkipMachineOOBE>

        <SkipUserOOBE>false</SkipUserOOBE>

        <ProtectYourPC>1</ProtectYourPC>

      </OOBE>

      <UserAccounts>

        <LocalAccounts>

          <LocalAccount wcm:action="add">

            <Name>Admin</Name>

            <Group>Administrators</Group>

            <Password>

              <Value>12345</Value>

              <PlainText>true</PlainText>

            </Password>

          </LocalAccount>

        </LocalAccounts>

      </UserAccounts>

    </component>

    <component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">

      <InputLocale>en-us</InputLocale>

      <SystemLocale>en-us</SystemLocale>

      <UILanguage>en-us</UILanguage>

      <UserLocale>en-us</UserLocale>

    </component>

  </settings>

</unattend>

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Can anyone see the reason why I would be receiving this error?

Thanks!

0 Comments   [ + ] Show comments

Answers (1)

Answer Summary:
Posted by: SMal.tmcc 2 years ago
Red Belt
1

Top Answer

What are your preinstallation tasks?  When it fails did you open a command window and do a diskpart to see if partitions to install to exist on the target computer?


Comments:
  • I have both a task for Creating a Single Partition as well as Formatting C: as NTFS - zgillette 2 years ago
    • Are you sure you are not booting in UEFI Mode?

      Read the KBE footer before launching the Scripted Install, make sure it says Boot Mode: Legacy. - Channeler 2 years ago
      • Legacy boot wasn't disabled. We have to do that with our HP desktops and laptops. I would love to know when it will work with secure boot. - zgillette 2 years ago
      • I am talking about the Boot Mode being used and detected by the KBE itself...

        Are you sure you are not trying to create Legacy Partitions while booting in UEFI Mode or vice-versa?

        See:
        https://imgur.com/a/bDWIVAx

        --In your case, make sure it says Legacy\BIOS-- - Channeler 2 years ago
      • This does sound like an issue I see when I use create single partition on a UEFI scripted install. In terms of secure boot, KACE is waiting on Microsoft to returned the signed bootfile, it was submitted quite some time ago. - cserrins 2 years ago
      • Channeler, Your suggestion seems to have worked for me. We didn't have Legacy enabled in BIOS. I'm hoping that we soon will not have to enable that to get imaging to work. We are all good now! - zgillette 2 years ago
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ