Reuse Use Case - Separate Unattended

[bladefirelight]

Reuse Use Case - Separate Unattended

[BladeFireLight]

In what case is having both architecture causing you an issue?

None of my testing has ever shown an bad side effect to having both.

[drstonephd]

I think it's been working, but Microsoft warns about using both in the same file. (See the end of the documentation at the following link.) I do not know how this all works, but it if x86 works for both x86 and amd64, then why bother with defining a section for amd64?

https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-7/dd799255%28v%3dws.10%29

I will try just x86. My attempt to add letters to the extra partitions was ignored. Probably because the drives are offline. I added a section to change the SAN policy that prevents them from coming online, but it was ignored. I used amd64, but the documentation indicated x86. Maybe that's the issue. If the oflineServicing pass is after the windowsPE pass, then perhaps this can't work. I have never tried this before. You're module inspired me to see if I can write a script to built a SQL Server unattended.

<?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="offlineServicing">
    <component name="Microsoft-Windows-PartitionManager" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">
      <SanPolicy>1</SanPolicy>
    </component>
  </settings>
  <settings pass="windowsPE">
    <component name="Microsoft-Windows-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral">
      <DiskConfiguration>
        <Disk wcm:action="add">
          <DiskID>0</DiskID>
          <ModifyPartitions>
            <ModifyPartition wcm:action="add">
              <Order>1</Order>
              <PartitionID>3</PartitionID>
              <Label>OS</Label>
              <Letter>C</Letter>
            </ModifyPartition>
          </ModifyPartitions>
        </Disk>
        <Disk wcm:action="add">
          <DiskID>1</DiskID>
          <ModifyPartitions>
            <ModifyPartition wcm:action="add">
              <Order>1</Order>
              <PartitionID>2</PartitionID>
              <Label>SQL</Label>
              <Letter>G</Letter>
            </ModifyPartition>
          </ModifyPartitions>
        </Disk>
        <Disk wcm:action="add">
          <DiskID>2</DiskID>
          <ModifyPartitions>
            <ModifyPartition wcm:action="add">
              <Order>1</Order>
              <PartitionID>2</PartitionID>
              <Label>BACKUP</Label>
              <Letter>H</Letter>
            </ModifyPartition>
          </ModifyPartitions>
        </Disk>
        <Disk wcm:action="add">
          <DiskID>3</DiskID>
          <ModifyPartitions>
            <ModifyPartition wcm:action="add">
              <Order>1</Order>
              <PartitionID>2</PartitionID>
              <Label>DATA</Label>
              <Letter>I</Letter>
            </ModifyPartition>
          </ModifyPartitions>
        </Disk>
        <Disk wcm:action="add">
          <DiskID>4</DiskID>
          <ModifyPartitions>
            <ModifyPartition wcm:action="add">
              <Order>1</Order>
              <PartitionID>2</PartitionID>
              <Label>LOG</Label>
              <Letter>J</Letter>
            </ModifyPartition>
          </ModifyPartitions>
        </Disk>
        <Disk wcm:action="add">
          <DiskID>5</DiskID>
          <ModifyPartitions>
            <ModifyPartition wcm:action="add">
              <Order>1</Order>
              <PartitionID>2</PartitionID>
              <Label>TEMPDB</Label>
              <Letter>T</Letter>
            </ModifyPartition>
          </ModifyPartitions>
        </Disk>
      </DiskConfiguration>
    </component>
  </settings>
etc.

Also, here is a link to the SAN policy bit.

https://support.microsoft.com/en-us/help/973834/microsoft-hyper-v-server-san-policy-is-set-to-automatically-mount-volu

[drstonephd]

I changed the san policy and disk config components to x86 and they are still ignored. I might end up using Set-Disk and Set-Partition to bring them online and set the label and letter.