I have DownLoaded Windows 2016 Tech Preview Files.  I am surprised that they Exceed a Standard DVD.

That being said, does anyone have any tips on how to get the DVD to Boot after making a Dual Layer DVD ISO?

Is there an Alternative for this process on a USB?

Any and all ideas would be appreciated.

Thanks in advance.

John

JP

Hi,

So I have been having a bit of trouble removing domain admin rights from my local deployment staff that use Windows Deployment Services.  

I gave their domain accounts the right to make computer accounts and change computer properties, I also gave them full admin rights on the WDS machine and also over the AD Object.   I even tried modifying the registry for the PXE devices user from the default setting of Domain Admin.

But they keep getting permission errors when trying to modify pre-authorized devices or authorize any pending devices.

I keep reading that I need to delegate them full control over the SCP object under the WDS server object, but it is not there (no Remote Install Tab either)  

I checked adsiedit as well as view > advanced features & show AD objects as containers.  

There is a Technet article that says I should restart the WDSService as it is meant to create the SCP object when the service starts and continues by making sure the server can access the domain controllers (which it can).

All of my WDS servers are VM's running in a vSphere environment.  When the user is a domain admin, there is no problem.  

If there something different with 2012 R2?  Or is it that they are running on VM's?  I can't imaging that being an issue though as it works perfectly except for the SCP issue.

Hi!

I've a image for my 2012 r2 RDS desktop session hosts. Im using MDT 2013 and Applications to install the applications on deployment with a varity of "silent install" commands, this works fine but a thing come to my mind, since this is a terminal server you usually install apps with "Admin install remote desktop". We are just in a test period now and i cant say i have got any troubble with my setup, but a tought it would be better to install it the right way.

I think i have a solution that goes like this. Insted of typing the silent commands in MDT, why not refer do a cmd file insted what includes this lines:

chang user /install

"silent command"

Change user /execute

And do the same for every app, would that work?

Best regards

Lars-Göran

I've found lots and lots of posts & discussion on KMS activation and troubleshooting. All of them come down to:

• making sure the client can reach the KMS server
• The KMS server has been activated with a valid KMS key
• The minimum activation request count for the type of activation requested is met.

The key challenge that most people have (based on the number of posts I've found) seems to be that last item: making sure the minimum request count is maintained.

Every solution has to do with making sure unique CMIDs (Client Machine IDs) exist on the machines making requests; the CMID is supposed to be the unique identifier for activation.

Unfortunately, I can prove in a lab environment that this is not true; some other factor is also at play. Here is the procedure to reproduce the failure:

1. Provision a domain controller in an isolated forest on an isolated network (so that you don't get noise or accidental client activation from any other KMS servers)
2. Provision a KMS server as a domain member in the isolated forest. Install the KMS key (slmgr.vbs /ipk {kms key}) and activate it.
3. Provision a VM (any hypervisor will do) as a test client machine (server or workstation) as a domain member on the isolated domain with a generic KMS client key and OS that should successfully activate on your KMS server. Take a snapshot of the VM so you can revert back to the original state before the "rearm counter" is reduced (Vista/Windows7 and Server 2008/2008R2 only allow 3 rearms, so reverting is faster than re-provisioning).
4. Attempt to activate the test machine; it will fail due to insufficient unique cached requests. This is expected because we've just started to initialize the KMS server.
5. Run "slmgr.vbs /rearm"; restart as requested.
6. Log in to the test system. Check the event viewer for IDs 12288 and 12289; if you don't see activation attempts, manually attempt to activate using "slmgr.vbs /ato".
7. On the KMS server, check the status of the unique client cache using "slmgr.vbs /dli"; the count should be at 1 or possibly 2, depending on whether the pre-rearm CMID was captured as a unique ID.
8. Repeat steps 5 & 6, checking the KMS server count after each restart. If you run out of rearms, revert the VM and repeat.
9. Note the CMID logged on the KMS server to be certain a unique ID was generated with each rearm.

In repeated testing, I've had no luck with getting the count to properly increase based on the simple use of /rearm, although I can clearly see the unique CMIDs being logged on the KMS. What's up with this? What else must be "uniqueified" to get KMS to acknowledge the new client?

I am trying to capture a Windows 8.1 Enterprise (with Update) x64 installation using WDS, but the Capture Image fails to load. I used the boot.wim from the Windows Server 2012 R2 (with Update) ISO to create a boot image in WDS and then a capture image from it. After I press F12 and the progress bar finishes the following message appears:

This only happens when I boot the capture image - the original boot image that I imported in WDS boots normally. I also tried with the Windows 8.1 (with Update) boot.wim, but the issue reoccurs. This is a Hyper-V VM on Windows Server 2012. Is this a problem with the recent update?

WDS 2008R2 I can deloy images but I do have a error to fix.

<WillWipeDisk>true</WillWipeDisk> is not actually wiping the disk.  I have several machines that have issues and need to be reimaged but WDS is not wiping the disk.  No errors are given and the only way I know is that same files/problems are still there.  It is overlaying and not wiping the disk.

Can anyone point me in the right direction?

<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
    <settings pass="offlineServicing">
        <component name="Microsoft-Windows-LUA-Settings" 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">
            <EnableLUA>false</EnableLUA>
        </component>
    </settings>
    <settings pass="windowsPE">
        <component name="Microsoft-Windows-International-Core-WinPE" 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">
            <SetupUILanguage>
                <UILanguage>en-US</UILanguage>
            </SetupUILanguage>
            <InputLocale>en-US</InputLocale>
            <LayeredDriver>1</LayeredDriver>
            <SystemLocale>en-US</SystemLocale>
            <UILanguage>en-US</UILanguage>
            <UILanguageFallback>en-US</UILanguageFallback>
            <UserLocale>en-US</UserLocale>
        </component>
        <component name="Microsoft-Windows-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">
            <ComplianceCheck>
                <DisplayReport>OnError</DisplayReport>
            </ComplianceCheck>
            <DiskConfiguration>
                <WillShowUI>OnError</WillShowUI>
                <Disk wcm:action="add">
                    <CreatePartitions>
                        <CreatePartition wcm:action="add">
                            <Order>1</Order>
                            <Extend>true</Extend>
                            <Type>Primary</Type>
                        </CreatePartition>
                    </CreatePartitions>
                    <ModifyPartitions>
                        <ModifyPartition wcm:action="add">
                            <Active>true</Active>
                            <Extend>false</Extend>
                            <Format>NTFS</Format>
                            <Label> Windows Operating System Volume</Label>
                            <Letter>C</Letter>
                            <Order>1</Order>
                            <PartitionID>1</PartitionID>
                        </ModifyPartition>
                    </ModifyPartitions>
                    <DiskID>0</DiskID>
                    <WillWipeDisk>true</WillWipeDisk>
                </Disk>
            </DiskConfiguration>
            <WindowsDeploymentServices>
                <Login>
                    <Credentials>
                        <Domain>test.com</Domain>
                        <Username>example</Username>
                        <Password>Password</Password>
                    </Credentials>
                </Login>
                <ImageSelection>
                    <InstallTo>
                        <DiskID>0</DiskID>
                        <PartitionID>1</PartitionID>
                    </InstallTo>
                </ImageSelection>
            </WindowsDeploymentServices>
        </component>
    </settings>
    <cpi:offlineImage cpi:source="wim" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>

my wds server is on network segment 192.168.200.0/24 where there's not dhcp server. in second segment (192.168.0.0/24) is dhcp server, Domain controller and workstations on them have to install win 7. i configured mikrotik dhcp server with option 66 = 192.168.200.28 option 67 = boot\x86\pxeboot.n12. on cisco router that is between 192.168.0.0/24 and 192.168.200.0/24 i set ip helper-addres on interface that is in segment 192.168.0.0/24. on wds is disabled firewall, there's not  antivirus program.

i tested, i installed dhcp server,secondary DC in segment 192.168.200.0/24 i booted workstation in network segment where is wds and process installation is ok. wds works ok.

when i boot workstation over network i receive

pxe-e32: tftp open timeout

where's i made mistake?

Hello!

I'm having some issues with multicasting on a large university network. Our setup is like this:

• WDS role setup on VM with Server 2012 R2
  
• Deployment shares hosted on the same VM - Using MDT 2013 to manage Deployment Shares
  
• VM is on a different VLAN from client computers. - IP Helpers to connect between the VLANs
• Multicast namespace was created successfully.
• All switches between server and client are managed, IGMPv3 compatible, and have snooping enabled3
• MDT Images are custom WIMs, with no setup files

When I run a deployment on any number of clients, I get the message saying "Attempting multicast transfer". The clients show up listed in the WDS Multicast Transmission. Then the clients drop off the server, and begin unicasting. Unicast speeds are excellent. Our 10GB images copy in about 10 mins. But we plan to do 30-40 systems at a time, and I believe that could cause some issues with so many individual sessions running...

I've noticed under our network adapter properties that Microsoft Network Adapter Multiplexor Protocol is unchecked. Not sure if that is related?

I have copied multicast information from the BDD.log file on one of the failed clients. That can be found below.

Any help/advice will be greatly appreciated! Thank you!

<![LOG[LTI applying image \\BRYANTWDS-SERV1\CopyToDrives$\Operating Systems\Windows 7 (x64) - Vers 4\Windows 7 (x64) - 4.0.wim using ImageX]LOG]!><time="14:42:33.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Event 41023 sent: LTI applying image \\BRYANTWDS-SERV1\CopyToDrives$\Operating Systems\Windows 7 (x64) - Vers 4\Windows 7 (x64) - 4.0.wim using ImageX]LOG]!><time="14:42:33.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Property SourcePath is now = \\BRYANTWDS-SERV1\CopyToDrives$\Operating Systems\Windows 7 (x64) - Vers 4]LOG]!><time="14:42:33.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Multicast transfer to directory: C:\MININT\Operating Systems\Windows 7 (x64) - Vers 4]LOG]!><time="14:42:33.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[<Message containing password has been suppressed>]LOG]!><time="14:42:33.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Command has been started (process ID 504)]LOG]!><time="14:42:33.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[ZTI Heartbeat: command has been running for 0 minutes (process ID 504)]LOG]!><time="14:42:34.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Event 41003 sent: ZTI Heartbeat: command has been running for 0 minutes (process ID 504)]LOG]!><time="14:42:34.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[  Console >
]LOG]!><time="14:42:34.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[  Console > Windows Deployment Services Multicast Client [Version 6.3.9600.17237]
]LOG]!><time="14:42:34.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[  Console > Copyright (c) Microsoft Corporation. All rights reserved.
]LOG]!><time="14:42:34.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[  Console >
]LOG]!><time="14:42:34.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[  Console >
]LOG]!><time="14:43:04.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[  Console > Transfer Started.
]LOG]!><time="14:43:04.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[  Console >
]LOG]!><time="14:43:04.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[  Console > Transfer Complete [0x800705B4].
]LOG]!><time="14:43:04.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[  Console >
]LOG]!><time="14:43:04.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[  Console > Operation Failed. [0x800705B4].
]LOG]!><time="14:43:04.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[  Console >
]LOG]!><time="14:43:04.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[  Console > This operation returned because the timeout period expired.
]LOG]!><time="14:43:04.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[  Console >
]LOG]!><time="14:43:04.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[  Console > ]LOG]!><time="14:43:04.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Return code from command = -2147023436]LOG]!><time="14:43:04.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Multicast transfer could not be completed, rc = -2147023436, falling back to using \\BRYANTWDS-SERV1\CopyToDrives$\Operating Systems\Windows 7 (x64) - Vers 4\Windows 7 (x64) - 4.0.wim]LOG]!><time="14:43:04.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">

I am new to image management and am just learning about DISM.  I have a basic question that I hope won't appear stupid.  I need to know exactly what is meant by an Online image?  Is it an image that is in the process of being created?  I think I have a handle on offline images but need to know how an online image works.  Thanks for your patience.

Michael T. Glenn

Michael T. Glenn

I just installed WDS on my virtual machine, the remote deploy is working as I have installed my virtual machine desktop via WDS.

I wanted to try to capture an image from my template computer. I have executed sysprep /generalize on the template computer and Booted the PXE from the template computer and selected the Capture Image I setup on WDS.

However I get this error.

The capture image is from a boot.wim of Windows 8.1 Enterprise 64bit

Any ideas?

For God, and Country.

Hi,

I'm trying to run sysprep in windows 2008 R2 enterprise edition using unattended file. Below is my code.

<?xml version="1.0" encoding="utf-8"?><unattend xmlns="urn:schemas-microsoft-com:unattend"><settings pass="windowsPE"><component name="Microsoft-Windows-International-Core-WinPE" 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"><SetupUILanguage><UILanguage>en-US</UILanguage></SetupUILanguage><UILanguage>en-US</UILanguage><InputLocale>0409:00000409</InputLocale><SystemLocale>en-US</SystemLocale><LayeredDriver>1</LayeredDriver><UserLocale>en-US</UserLocale></component><component name="Microsoft-Windows-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"><UserData><AcceptEula>true</AcceptEula><FullName>Loges</FullName><Organization>Az</Organization></UserData><DiskConfiguration><WillShowUI>OnError</WillShowUI><Disk wcm:action="add"><CreatePartitions><CreatePartition wcm:action="add"><Extend>false</Extend><Order>1</Order><Type>Primary</Type><Size>100</Size></CreatePartition><CreatePartition wcm:action="add"><Extend>true</Extend><Order>2</Order><Type>Primary</Type></CreatePartition></CreatePartitions><ModifyPartitions><ModifyPartition wcm:action="add"><Active>true</Active><Format>NTFS</Format><Order>1</Order><PartitionID>1</PartitionID></ModifyPartition><ModifyPartition wcm:action="add"><Active>false</Active><Format>NTFS</Format><Label>Windows</Label><Letter>C</Letter><Order>2</Order><PartitionID>2</PartitionID></ModifyPartition></ModifyPartitions><DiskID>0</DiskID><WillWipeDisk>true</WillWipeDisk></Disk></DiskConfiguration><WindowsDeploymentServices><ImageSelection><InstallTo><DiskID>0</DiskID><PartitionID>2</PartitionID></InstallTo></ImageSelection></WindowsDeploymentServices></component></settings><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></OOBE><UserAccounts><AdministratorPassword><Value>dABlAHMAdABAADEAMgAzAEEAZABtAGkAbgBpAHMAdAByAGEAdABvAHIAUABhAHMAcwB3AG8AcgBkAA==</Value><PlainText>false</PlainText></AdministratorPassword></UserAccounts></component><component name="Microsoft-Windows-International-Core" 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"><InputLocale>en-US</InputLocale><SystemLocale>en-US</SystemLocale><UILanguage>en-US</UILanguage><UserLocale>en-US</UserLocale></component></settings><settings pass="specialize"><component name="Microsoft-Windows-OutOfBoxExperience" 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"><DoNotOpenInitialConfigurationTasksAtLogon>true</DoNotOpenInitialConfigurationTasksAtLogon></component><component name="Microsoft-Windows-ServerManager-SvrMgrNc" 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"><DoNotOpenServerManagerAtLogon>true</DoNotOpenServerManagerAtLogon></component></settings><cpi:offlineImage cpi:source="wim:c:/wsim/install.wim#Windows Server 2008 R2 SERVERENTERPRISE" xmlns:cpi="urn:schemas-microsoft-com:cpi" /></unattend>

During the sysprep, disk configuration is keep on ignoring. I have gone through all the technet forum threads related to this issue and following same instructions but not working.

I created this XML using WSIM tool. Please let me know how to wipe the existing partition during sysprep. I'm trying all the possibilities almost for few weeks. Nothing is worked out :(

Please help me to resolve this issue.

Regards,

Loges

When I go to save a document on Word the system will not allow me to. It says I need permission from the administrator.

I need the same permission to delete photos.

How can I disable the "Administrator"   .....  I am the only one who uses my computer.  

Please explain simply and completely as I am an older guy and not very computer savvy.

Thanks for any assistance.

PS I have windows 10...

I have DHCP and WDS on the same server.

I have only configured option 60 = PXEClient

I have ticked the two boxes in WDS, "don't listen" and "configure DHCP options"

But still I get "ProxyDHCP service did not reply to request on port 4011"

Can some please help I don't want to rebuild my domain controller.

Please move this accordingly if this is not the correct forum for this question.

I have limited experience with Windows Server and I am learning on production servers.  I have been in an environment previously where we had a WSUS server set up on our network and periodically the administrator would go in and review available updates and push them to clients periodically.  If I am not mistaken, this also made the installation of OS and updates to the newly installed OS much easier and quicker and was less taxing on network traffic.

If I understand what I am reading correctly, the same server can be used to use the network to install OS images to new computers and computers that are being wiped and repurposed.

I am looking for information on how to set this up, what kind of resources are required, and how to go about planning set up of WSUS for my company.  Any direction would be helpful.

Thank in advance.

Hi I am tyring to configure WDS role service in Windows Server 2012 R2 Version. 

I am able to install the role properly, i am configuring the deployment server, but when i attempt to configure it, at the point when it starts copying files of configuration, the mmc crashes and gives the below error message: 

My Windows server 2012 R2 has the required updates and my network has an active ADDS, DHCP and DNS installed. 

This server also has WSUS and IIS service installed in it. I have also attempted to install WDS in a clean server and the issue is still the same. 

Please advise what should be next step here to successfully configure the WDS service. 

I was able to mount images previously but now I am unable to. 

I have tried multiple mount points, and even installed a new hard drive to mount to and still continue to get error 3.

I get the same error using imagex or dism.

I verified permissions were correct and even went as far as to give everyone full permissions to the entire drive.

I am on Server 2012 R2. Fully updated as of 12-16-2015 at 1:25PM CST. 

Here is my dism log after trying to mount.

Hi

I am deploying a second 2012 Server in a remote office and would like to know whether the Primary DC (also Server 2012) in the head office needs to be visible to the remote office at all times?

I will be joining the new server to the domain via VPN but would then like users to log into the new DC regardless of the VPN being active or not. The VPN should be up 95% of the time.

If this is possible, is there a certain way that the new DC needs to be set up that is different from a standard install and promote to DC?

Thanks in advance

• Browse button do not work in "Windows Deployment Services" console.

  This BUG exist also in  Windows Server 2012 R2.
  The BUG exist in English-US, French, and probably other languages (not related to a language)

  To produce the bug do the following:

  On www.msdn.com download Windows Server Technical Preview 
  

  At command prompt install WDS Server role in StandAlone mode with the folowing command:
  PowerShell  Add-WindowsFeature  WDS   -IncludeManagementTools   -IncludeAllSubfeature

  Initialize the WDS role "IN STAND ALONE MODE" with the folowing command:
  wdsutil /verbose  /progress  /initialize-server  /server:localhost /REMINST:C:\RemoteInstall   /StandAlone

  The bug exist only if WDS is installed in standalone mode !

  To create a "prestaged device" and associate to this device an answer file we need an "answer file".
  To reproduce the BUG  a simple text file can be created with notepad in C:\RemoteInstall\WDSClientUnattend folder with the name PC1.xml. The content of this file is not important to reproduce the BUG.

  Now we will create a local "Prestaged Device" and will try to associate with the already existent answer file that we have created C:\RemoteInstall\WDSClientUnattend\PC1.xml:

  ServerManager, Clic "Tools", select "Windows Deployment Services"

  Click "Servers", Click on the name of your server, Right Click "Prestaged Devices", Select "Add Device",

  ( Do not confuse "Prestages Devices" with "Active Directory Prestaged Devices" because "Active Directory Prestages devices is not available in Stand Alone mode),

  Name: PC1
  DeviceID: 123456123456, Clic "Next"

  On the page "Boot", Clic "Next"

  On the page "Client Unattend", to see the bug click "Browse", Clic "C:", Clic "RemoteInstall", Click "WDSClientUnattend", Clic "PC1.xml"

  You can see that the PC1.xml are NOT added as "Unattend File".

  BROWSE BUTTON FAIL TO ADD THE SELECTED ANSWER FILE ! You can clic Next buton but your selected file ARE NOT ASSOCIATED WITH THE PRESTAGED DEVICE.

  My opinion is: The path to Unattend file must be relative to C:\RemoteInstall and must NOT contain C:\Remoteinstall.

  If you clic on Browse button you will indicate a FULL PATH and this is not accepted because the BUG. Also if you fill manually a FULL PATH next to Unattend File this is not accepted. Only file path relative to C:\Remoteinstall are accepted. This can be very confusing for somebody who do not know this.

  WorkAround:
  Insted of clic on Browse button, you can write the relative path:  "WDSClientUnattend\PC1.xml",
  Clic Next, Click Back, You can see that Unattend File is WDSClientUnattend\PC1.xml and this is right.

  Conclusion: relative path are OK, Full path including C:\RemoteInstall are not accepted. Browse button do not work !