I have an exe that I can run silently on a pc. It does not run in my TS.

I've added lots of exe's before but I can't get this to work.

There is nothing to extract from it, like an MSI.

The file folder has a setup.exe which works on the pc with /s

The error I get is 1603, which I think I found references no access to the file.

This is for a Realtek Audio driver for a Dell 5750 and I took it right off their site.

Does anyone know what solution would get this to silent install in MDT?
I tried /? and /Help and ?dweunreo (garbage) to get a menu but nothing comes up.
Dell and their "full" CAB files. :/

1.

Open Command prompt 

2.

DISM /online /Get-CurrentEdition

3.

DISM /online /Get-TargetEditions

4.

DISM /online /Set-Edition:serverDatacenter /ProductKey:WMDGN-G9PQG-XVVXX-R3X43-63DFG /AcceptEula


This key is provided by microsoft:

https://docs.microsoft.com/en-us/windows-server/get-started/kmsclientkeys

enjoy!

Hi,

When I try to boot to MDT to image a PC, it only gets as far as the MDT splash screen then goes to the command line, "X:\Windows\System32>". prompt. I think it may have to do with the LiteTouchPE_64 boot image, but I'm not entirely sure. 

Any ideas?

Thanks

I am trying to set up the IP address information for my lab servers within the autounattend.xml file for some lab servers.  I have used the information below in order to try to get this set but for some reason it is not working.  Can someone take a look at the info and tell me what I have wrong within the file?

<?xml version="1.0" encoding="utf-8"?><unattend xmlns="urn:schemas-microsoft-com:unattend"><servicing></servicing><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><InputLocale>en-US</InputLocale><SystemLocale>en-US</SystemLocale><UILanguage>en-US</UILanguage><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"><DiskConfiguration><Disk wcm:action="add"><CreatePartitions><CreatePartition wcm:action="add"><Order>1</Order><Size>350</Size><Type>EFI</Type></CreatePartition><CreatePartition wcm:action="add"><Order>2</Order><Size>128</Size><Type>MSR</Type></CreatePartition><CreatePartition wcm:action="add"><Order>3</Order><Size>92160</Size><Type>Primary</Type></CreatePartition><CreatePartition wcm:action="add"><Order>4</Order><Extend>true</Extend><Type>Primary</Type></CreatePartition></CreatePartitions><ModifyPartitions><ModifyPartition wcm:action="add"><Format>FAT32</Format><Label>Boot</Label><Order>1</Order><PartitionID>1</PartitionID><Active>false</Active></ModifyPartition><ModifyPartition wcm:action="add"><Format>NTFS</Format><Label>OS</Label><Letter>C</Letter><Order>2</Order><PartitionID>3</PartitionID></ModifyPartition><ModifyPartition wcm:action="add"><Format>NTFS</Format><Label>Data</Label><Letter>D</Letter><Order>3</Order><PartitionID>4</PartitionID></ModifyPartition></ModifyPartitions><DiskID>0</DiskID><WillWipeDisk>true</WillWipeDisk></Disk></DiskConfiguration><ImageInstall><OSImage><InstallFrom><MetaData wcm:action="add"><Key>/IMAGE/NAME</Key><Value>Windows Server 2019 SERVERSTANDARDCORE</Value></MetaData></InstallFrom><InstallTo><DiskID>0</DiskID><PartitionID>3</PartitionID></InstallTo></OSImage></ImageInstall><UserData><ProductKey><Key>KMS Product Key</Key></ProductKey><AcceptEula>true</AcceptEula><Organization>Home Lab</Organization><FullName>My Name</FullName></UserData></component></settings><settings pass="specialize"><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"><ComputerName>2019WSUS02</ComputerName><TimeZone>Pacific Standard Time</TimeZone></component><component name="Networking-MPSSVC-Svc" 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"><DomainProfile_EnableFirewall>false</DomainProfile_EnableFirewall><PrivateProfile_EnableFirewall>false</PrivateProfile_EnableFirewall><PublicProfile_EnableFirewall>false</PublicProfile_EnableFirewall></component><component name="Microsoft-Windows-DNS-Client" 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"><Interfaces><Interface wcm:action="add"><DNSServerSearchOrder><IpAddress wcm:action="add" wcm:keyValue="1">10.0.0.1</IpAddress><IpAddress wcm:action="add" wcm:keyValue="2">10.0.0.2</IpAddress></DNSServerSearchOrder><Identifier>Ethernet</Identifier><DisableDynamicUpdate>false</DisableDynamicUpdate><EnableAdapterDomainNameRegistration>true</EnableAdapterDomainNameRegistration></Interface></Interfaces></component><component name="Microsoft-Windows-TCPIP" 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"><Interfaces><Interface wcm:action="add"><Ipv4Settings><DhcpEnabled>false</DhcpEnabled></Ipv4Settings><Identifier>Ethernet</Identifier></Interface></Interfaces></component><component name="Microsoft-Windows-TCPIP" processorArchitecture="wow64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><Interfaces><Interface wcm:action="add"><UnicastIpAddresses><IpAddress wcm:action="add" wcm:keyValue="1">10.0.0.8 /24</IpAddress></UnicastIpAddresses><Identifier>Ethernet</Identifier><Routes><Route wcm:action="add"><Identifier>0</Identifier><NextHopAddress>10.0.0.1</NextHopAddress><Prefix>0.0.0.0</Prefix><Metric>20</Metric></Route></Routes></Interface></Interfaces></component><component name="Microsoft-Windows-UnattendedJoin" 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"><Identification><Credentials><Domain>lab domain name</Domain><Password>AD password</Password><Username>AD username</Username></Credentials><JoinDomain>lab domain name</JoinDomain></Identification></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"><UserAccounts><AdministratorPassword><Value>QgBpAG4AZwB5ADEANgA4AEEAZABtAGkAbgBpAHMAdAByAGEAdABvAHIAUABhAHMAcwB3AG8AcgBkAA==</Value><PlainText>false</PlainText></AdministratorPassword><LocalAccounts><LocalAccount wcm:action="add"><DisplayName>Name</DisplayName><Group>Administrators</Group><Name>username</Name></LocalAccount></LocalAccounts></UserAccounts><OOBE><ProtectYourPC>1</ProtectYourPC><HideEULAPage>true</HideEULAPage></OOBE><TimeZone>Pacific Standard Time</TimeZone><FirstLogonCommands><SynchronousCommand wcm:action="add"><Order>1</Order><CommandLine>cscript //b c:\windows\system32\slmgr.vbs /ipk TNK62-RXVTB-4P47B-2D623-4GF74</CommandLine></SynchronousCommand><SynchronousCommand wcm:action="add"><Order>2</Order><CommandLine>cscript //b c:\windows\system32\slmgr.vbs /ato</CommandLine></SynchronousCommand></FirstLogonCommands></component></settings><cpi:offlineImage cpi:source="wim:d:/temp/sources/install.wim#Windows Server 2019 SERVERSTANDARD" xmlns:cpi="urn:schemas-microsoft-com:cpi" /></unattend>

I have a program installing silently which requires a reboot so it throws an error code 2.

On the Properties tab of the step in my TS, I added a 2 and that's fine.

What is the difference, if any, between adding a code there, or in the Options tab where it asks the same thing?

I see that adding the code on the Properties tab does not update the Options tab, so I'm just curious what the difference is.

In all of the previous, I added the startup/homepage in my unattend and it worked fine.

With 2004, all I get is an ABOUT page. So I attempted to add to my CS.INI,

Home_page=https://www.blahblah and I still get an ABOUT page.

What would be a working method to setting a home page in 2004? I ran out of ideas :/

I followed the MS guide https://docs.microsoft.com/en-us/windows/deployment/deploy-windows-mdt/create-a-windows-10-reference-image to create a reference image. I get all the way to the sys prep stage of the task sequence, the sysprep appears to run like normal, the vm reboots, and then logs me back into the OS and displays "can not find script file c:\ltibootstrap.vbs". Here is a breakdown of each step ... 

1) Boot to optical drive of vm with my mdt build iso attached. Using the x64 iso rather than x86 as mentioned in the guide, because my vm won't boot to the x86 iso.

2) I get to the Windows Deployment Wizard Capture Image part. Everything looks good.

3) The OS installs without error, it logs me into Win10 with Administrator account. At this point it is waiting for me to Resume Task Sequence, because I added the optional suspend action into the task sequence. I can see that all of the software has been installed without error (MSVC 2019x86, MSVC 2019x64, MS Office Business, Google Chrome). *Checked hostname (cherryg-i58sors)

4) Now I resume task sequence, It checks WSUS, Apply WinPE, and reboots the vm. Logs me back into Win10 with Administrator account. At this point the deployment share monitoring is showing the "execute sysprep" stage and I'm seeing this happen on the vm. VM reboots again.

This is where my problem begins. I think at this point it should start capturing the image, but it doesn't. It starts booting me back into Win10 and this time it has a different hostname (cherryg-18g1on1). I can tell before it even lets me into the OS, because WSUS picks up the new name.

And then I get this error "can not find script file "c:\LTIBootstrap.vbs" ... I click OK, it lets me in Win10 with the new hostname. Eventually the MDT Monitoring status shows "Unresponsive". I let the last one go for about 12 hours.

I don't even think the error matters. It shouldn't be sysprepping and then booting back into Win10, right? I feel like it should be capturing the image and finishing out the task sequence, but it seems that it's just booting to Win10 after the sysprep and abandoning the task sequence, which eventually becomes unresponsive in the mdt deployment share monitor.

I have successfully captured my Win10 reference image, but it finished with three warnings. Two of which are "Unable to create WebService class", which I've read was an issue with older versions, but I'm on 6.3.8456.1000. The posts I found about this were from a few years ago. Are those two still safe to ignore?

The other error is "unexcepted return code while re-arming Office 2016, RC = -1073425660". This one I can't seem to find anything on. Is sysprep failing to do something it needs to do?

Using: Microsoft MDT version 8456, with KB 4564442 applied following install of Windows 10 2004 ADK

Good morning,

I have been using a reliable Build and Capture task sequence for some time, and all versions of Windows 10 up to 1909 have been built and captured successfully, without errors, with the task sequence.  This includes a 1909 build and capture after updating the ADK and then KB4564442 applied with deployment share updates and new ISO generated for booting.

However, whenever I am attempting a build and capture with Windows 10 2004, the task sequence gets to execute sysprep, and this fails.

C:\windows\system32\sysprep\panther\setupact.log points towards MicrosoftWindows.Client.CBS as being the culprit, extract from the log file is below:

2020-07-28 09:45:24, Info                  SYSPRP Entering SysprepGeneralizeValidate (Appx) - validating whether all apps are also provisioned.
2020-07-28 09:45:24, Error                 SYSPRP Package MicrosoftWindows.Client.CBS_120.2202.130.0_x64__cw5n1h2txyewy was installed for a user, but not provisioned for all users. This package will not function properly in the sysprep image.
2020-07-28 09:45:24, Error                 SYSPRP Failed to remove apps for the current user: 0x80073cf2.
2020-07-28 09:45:24, Error                 SYSPRP Exit code of RemoveAllApps thread was 0x3cf2.
2020-07-28 09:45:24, Error                 SYSPRP ActionPlatform::LaunchModule: Failure occurred while executing 'SysprepGeneralizeValidate' from C:\Windows\System32\AppxSysprep.dll; dwRet = 0x3cf2
2020-07-28 09:45:24, Error                 SYSPRP SysprepSession::Validate: Error in validating actions from C:\Windows\System32\Sysprep\ActionFiles\Generalize.xml; dwRet = 0x3cf2
2020-07-28 09:45:24, Error                 SYSPRP RunPlatformActions:Failed while validating Sysprep session actions; dwRet = 0x3cf2
2020-07-28 09:45:24, Error      [0x0f0070] SYSPRP RunDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = 0x3cf2
2020-07-28 09:45:24, Error      [0x0f00d8] SYSPRP WinMain:Hit failure while pre-validate sysprep generalize internal providers; hr = 0x80073cf2

Performing a check on getting the information for the Windows Package shows that it is installed, but pending removal, but also that it'a a system level application.

Clearly that's something newly added in 2004, as checking for this in Windows 10 1909 shows nothing, and no errors during sysprep.

Can anyone please suggest how this can be resolved?

It's often a battle between myself and Security unit and/or Server group when it comes to any OS changes and GPO's.

I rebuilt all of my VM's from scratch using 2004 with a suspend. All of that is fine. However, once at 2004 I cannot get updates for 2004. I know it's a Security issue because if I put the pc on a MIFI I get all updates available. I've had this battle with those two units for a while now. If we could get updates on 1809 then I don't know what could be blocking 2004 updates.

Also, if I run a Feature update on 1809, I get 1903 (or maybe 1909, I don't recall). Either or, I don't get updates for 19xx either.

The main message I get says the updates weren't signed correctly. We use Checkpoint as our Security system. I know nothing about that so I can't give them any advice. Their excuse for it being an issue is that 'a pc can go to a multitude of locations to get updates, and we can't open the pc to the entire world.'   But, we're getting 1809 updates.

I guess I'm asking if anyone is aware of what may be a needed change to allow 2004 updates. This is what is holding us back from putting it into production. And come Sept, 1809 is no longer supported.

Hi 

Currently my company wants to implement HA version on server 2016, can I install the cluster and install the software at the cluster partition as a HA version, please advise thank you.

1 x Dell R230 - node 2  

Is there a way to multicast a wim from a fileshare, like \\server2\folder\win10.wim ?

Has anyone had success installing McAfee Endpoint Security Platform with MDT? I keep getting a failure with a return code of 16030. This is a code being returned by McAfee itself. The McAfee site is not helpful it only states "The installation wizard was interrupted before Endpoint Security was installed. Your previous software was uninstalled, but no other changes were made to your system." For that code. BDD.log only states McAfee returned an unexpected return code: 16030.

In my lab, we are admins so most things work for us. But when a new user signs onto a 2004 pc, they do not get
their mapped drives, which GPO pushes at logon. This has worked in 1809 and we are testing out issues in 2004.

We have new users (and non-admin users) who do not get their needed mapped drives that they should at logon.

Is anyone aware of a fix for mapped drives not appearing? Some sites say to disable password protected file sharing, but that
isn't even an option in 2004. SMB1 is enabled by the way.

I am using Windows 10 Professional (64-bit) machine and have deployed ADK for Windows 10.

After trying the copype command, I am getting the below error

Windows PE copype error: The following processor architecture was not found: amd64. Failed !

Can you please guide for the same.

Regards, Swapnil Malpani

I'm "still" trying to get our Security group to allow updates for 2004. For some reason they can't figure out what to open for MS Updates just like we get them for 1809.

Their 'solution' is to build a WSUS. I can do that, and that will work in our office, but once a pc leaves our building, they're still
not going to get updates - Security hasn't figured out opening what. Once the pc leaves, it can no longer contact our static IP that the WSUS has.

In this situation, what would be the best method for updates outside of here? Obviously, the best would be to have the IP range opened to get updates. I keep telling them to configure it the same way we successfully get updates for 1809 but they don't get it. Also, on 1809, running updates takes us to 1903.....and we can't get updates for it or 1909 either.

I'm in need of of help. I'm on the verge of completely rebuilding my deployment server. When I'm running MDT Sysprep and Capture via LiteTouch.vbs, my VM hangs up at the generalize step for a while. It will eventually continue. Once it does continue, it reboots and then get stuck in a boot loop. I read about the UEFI / BIOS detection issue, but this is a UEFI VM. My MDT is the same configuration that I have been using since 1909 and 1903 which all work.

I uninstalled the 1909 ADK / ADK PE and installed the newest 2004 ADK / ADK PE and then this issue began happening. Please help me troubleshoot because I am unsure how to continue.

FAILURE (5616): 15299: Verify BCDBootEx

<![LOG[About to run command: \\COMPUTER\Share$\Tools\X64\BCDBoot.exe E:\windows /l en-gb  ]LOG]!><time="13:07:05.000+000" date="06-30-2020" component="ztiRunCommandHidden" context="" type="1" thread="" file="ztiRunCommandHidden"><![LOG[Command has been started (process ID 2352)]LOG]!><time="13:07:05.000+000" date="06-30-2020" component="ztiRunCommandHidden" context="" type="1" thread="" file="ztiRunCommandHidden"><![LOG[  Console > Failure when attempting to copy boot files.]LOG]!><time="13:07:05.000+000" date="06-30-2020" component="ztiRunCommandHidden" context="" type="1" thread="" file="ztiRunCommandHidden">

 \\COMPUTER\Share$\Tools\X64\BCDBoot.exe E:\windows /l en-gb /v

BFSVC: ServiceBootFiles MuiOnly:n Res:y Fonts:y BootMgrOvw:n BootStatOvw:n DbgTrn:y SuspendBDE:n
BFSVC Error: Failed to get partition name. Status = 0xc0000452
BFSVC Error: Failed to get system partition! Last Error = 0x3bc3
BFSVC Error: ServicingBootFiles failed. Error = 0x3bc3
Failure when attempting to copy boot files.