Windows 10: MDT Change Unattend.xml In LiteTouchx64.wim

I want to open a cmd.exe at the same time as the LiteTouch.wsf runs. How do I change the unattend.xml in the LiteTouchx64.wim. The following is the complete unattend.xml. BUT it does not work ! As soon as it boots, it reboots itself. Is there anything wrong with the script? Thankyou very much.

<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="windowsPE">
<component name="Microsoft-Windows-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
<Display>
<ColorDepth>32</ColorDepth>
<HorizontalResolution>1024</HorizontalResolution>
<RefreshRate>60</RefreshRate>
<VerticalResolution>768</VerticalResolution>
</Display>
<RunSynchronous>
<RunSynchronousCommand wcm:action="add">
<Description>Sets High Power</Description>
<Order>1</Order>
<Path>powercfg.exe /s 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c</Path>
</RunSynchronousCommand>
<RunSynchronousCommand wcm:action="add">
<Description>Lite Touch PE</Description>
<Order>2</Order>
<Path>wscript.exe X:\Deploy\Scripts\LiteTouch.wsf</Path>
</RunSynchronousCommand>
</RunSynchronous>
</component>
</settings>
</unattend>

:)

 

MDT LiteTouchx64.wim Unattend.xml

I want to open a cmd.exe at the same time as the LiteTouch.wsf runs. The following is the complete unattend.xml. I changed the 'RunSynchronous' to 'RunAsynchronous'. BUT it does not work ! As soon as it boots, it reboots itself. Is there anything wrong with the script? Thankyou very much.



<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="windowsPE">
<component name="Microsoft-Windows-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
<Display>
<ColorDepth>32</ColorDepth>
<HorizontalResolution>1024</HorizontalResolution>
<RefreshRate>60</RefreshRate>
<VerticalResolution>768</VerticalResolution>
</Display>
<RunAsynchronous>
<RunAsynchronousCommand wcm:action="add">
<Description>Lite Touch PE</Description>
<Order>1</Order>
<Path>wscript.exe X:\Deploy\Scripts\LiteTouch.wsf</Path>
</RunAsynchronousCommand>
<RunAsynchronousCommand wcm:action="add">
<Description>Opens CMD.exe</Description>
<Order>2</Order>
<Path>cmd.exe</Path>
</RunAsynchronousCommand>
</RunAsynchronous>
</component>
</settings>
</unattend>

 

Unattend xml File....

hiiii

i would like to install windows via WDS Server. How To Create Unattend .XML File in Server 2012......

Regard

Mohit

 

MDT Multicast

Hello Everyone,

I am new to MDT multicast and was hoping someone can answer my question, I set my MDT server up for multicast and it goes all the way to 99% and I watch it in the WDS console under my deployment share, I can see three clients and when they reach 99% and
I hit refresh the clients disappear which i think means it reached 100% but then on the client side its rolls back to installing operating system and starts the percent count again. Is multicast on MDT work different, does it first download the image to one
computer and once downloaded it distributes that one image to all others . I found an article below that explains how it should work but I am not sure if I am understanding it correctly.

Here is the overall process:

• ClientA starts a multicast session to download Win7SP1x86.wim from the MDT/WDS Server.
• When the broadcast session of Win7SP1x86.wim reaches 25%, ClientB joins the session in progress. ClientB knows that it missed the first ¼ of the Win7SP1x86.wim file, so it starts writing 25% into its local copy of Win7SP1x86.wim.
• When the multicast session reaches 100% of Win7SP1x86.wim, ClientA is done and drops off. However, ClientB is still missing the first ¼ of the file, and stays on the multicast chanel as it restarts (rolls back) to zero.
• Eventually the multicast session of Win7SP1x86.wim reaches the 25% mark where ClientB first joined. ClientB now has 100% of the file and drops off. No clients are connected, and the server stops broadcasting.