Hi,

I hope someone can resolve the issue as I am setting up Windows Deployment Server for the first time on Windows Server 2019 WDS works as a standalone with no issues at work. When I integrate it with AD DS it stop working :(

I have read about DHCP options and tried the solutions but nothing is working. The network is all on the same ip range and subnet, the dhcp server is on a different machine to the wds. Can anyone proved my a solution to the problem any help would be much appreciated

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 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?

Hello,

We are currently in the testing phase of setting up WDS in our organization and are running into a few small problems.  Right now we have WDS on Server 2016 on a separate VLAN and this server also hosts the DHCP for that VLAN.  It can still talk to the other servers and most importantly talk to our AD domain.

The problem I am running into is that on Windows 10 we seem to be unable to properly join a domain unattended.  We created a service account for the purpose and it works just fine on Windows 7 unattended installs.  It also works properly to connect to the WDS to get the list of images available.  What happens is after the first boot when it's prepping for the OOBE the machine will reboot and then say "Why did my PC restart?".  If we click OK then it will set it up properly on the next boot.  This can't be right.  I've also noticed that the checkboxes for joining a domain or not joining one in WDS properties appear to do nothing.  Ideally, I'd like to have it just setup the Administrator account silently the autologon to the service account so we can install our AV and any custom per-user software as a final step.  We have a group policy in effect that renames the Administrator account to something else and sets a password only we know and locks out the account on that machine.  Right now, it sets up an WDSAdmin account and autologon to this so we have to join the domain as a final step and rename the machine.  On reboot we logon to a domain admin account and remove the WDSAdmin account.

Another problem we are having is that during approval process we set a machine name and this does not seem to get passed over to Windows.  I thought this would do this and I would like it to do so.

We have two unattended files.  One is pointed to the image itself which does specialize and oobe pass.  During approval, we have an unattended for WinPE for picking an image and disk setup.  It also mirrors the specialize pass.  I am not sure if that is necessary, but I've seen that done as examples elsewhere.

Here is our install XML we pick during the approval process:

<?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><WillShowUI>OnError</WillShowUI><UILanguage>en-US</UILanguage></SetupUILanguage><InputLocale>en-US</InputLocale><SystemLocale>en-US</SystemLocale><UILanguage>en-US</UILanguage><UILanguageFallback>en-US</UILanguageFallback><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"><WindowsDeploymentServices><Login><Credentials><Domain>XXX</Domain><Password>XXX</Password><Username>XXX</Username></Credentials></Login><ImageSelection><InstallImage><ImageGroup>Win_10_Pro_VLK</ImageGroup><ImageName>Win_10_Pro_VLK_VMWare_Unattend</ImageName><Filename>Win_10_Pro_VLK_VMWare_Unattend-(2).wim</Filename></InstallImage><InstallTo><DiskID>0</DiskID><PartitionID>4</PartitionID></InstallTo></ImageSelection></WindowsDeploymentServices><DiskConfiguration><Disk wcm:action="add"><CreatePartitions><CreatePartition wcm:action="add"><Order>1</Order><Size>500</Size><Type>Primary</Type><Extend>false</Extend></CreatePartition><CreatePartition wcm:action="add"><Order>2</Order><Type>EFI</Type><Extend>false</Extend><Size>100</Size></CreatePartition><CreatePartition wcm:action="add"><Order>3</Order><Extend>false</Extend><Size>16</Size><Type>MSR</Type></CreatePartition><CreatePartition wcm:action="add"><Order>4</Order><Extend>true</Extend><Type>Primary</Type></CreatePartition></CreatePartitions><ModifyPartitions><ModifyPartition wcm:action="add"><Active>false</Active><Format>NTFS</Format><Label>Recovery</Label><Order>1</Order><PartitionID>1</PartitionID><TypeID>DE94BBA4-06D1-4D40-A16A-BFD50179D6AC</TypeID></ModifyPartition><ModifyPartition wcm:action="add"><Order>4</Order><Label>Windows</Label><Format>NTFS</Format><Letter>C</Letter><PartitionID>4</PartitionID></ModifyPartition><ModifyPartition wcm:action="add"><Order>3</Order><PartitionID>3</PartitionID></ModifyPartition><ModifyPartition wcm:action="add"><Order>2</Order><Format>FAT32</Format><Label>System</Label><PartitionID>2</PartitionID></ModifyPartition></ModifyPartitions><DiskID>0</DiskID><WillWipeDisk>true</WillWipeDisk></Disk><WillShowUI>OnError</WillShowUI></DiskConfiguration><UserData><ProductKey><Key>XXX</Key><WillShowUI>OnError</WillShowUI></ProductKey><AcceptEula>true</AcceptEula><FullName>XXX</FullName><Organization>XXX</Organization></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"><ProductKey>XXX</ProductKey><SignInMode>1</SignInMode><DoNotCleanTaskBar>false</DoNotCleanTaskBar><TimeZone>Eastern Standard Time</TimeZone></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><UILanguageFallback>en-US</UILanguageFallback><UserLocale>en-US</UserLocale></component></settings><cpi:offlineImage cpi:source="wim:d:/sources/install.wim#Windows 10 Pro" xmlns:cpi="urn:schemas-microsoft-com:cpi" /></unattend>

Here is our XML we add to the image in the properties:

<?xml version="1.0" encoding="utf-8"?><unattend xmlns="urn:schemas-microsoft-com:unattend"><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"><DesktopOptimization><GoToDesktopOnSignIn>true</GoToDesktopOnSignIn><ShowWindowsStoreAppsOnTaskbar>false</ShowWindowsStoreAppsOnTaskbar></DesktopOptimization><ProductKey>XXX</ProductKey><SignInMode>1</SignInMode><DoNotCleanTaskBar>false</DoNotCleanTaskBar><TimeZone>Eastern Standard Time</TimeZone><ComputerName>WDSLab</ComputerName></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"><DesktopOptimization><GoToDesktopOnSignIn>true</GoToDesktopOnSignIn><ShowWindowsStoreAppsOnTaskbar>false</ShowWindowsStoreAppsOnTaskbar></DesktopOptimization><UserAccounts><LocalAccounts><LocalAccount wcm:action="add"><Password><Value>XXX</Value><PlainText>false</PlainText></Password><Description>Local Administrator Account</Description><DisplayName>WDSAdmin</DisplayName><Group>Administrators</Group><Name>WDSAdmin</Name></LocalAccount></LocalAccounts></UserAccounts><OOBE><HideEULAPage>true</HideEULAPage><HideLocalAccountScreen>true</HideLocalAccountScreen><HideOEMRegistrationScreen>true</HideOEMRegistrationScreen><HideOnlineAccountScreens>true</HideOnlineAccountScreens><HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE><ProtectYourPC>3</ProtectYourPC></OOBE><DoNotCleanTaskBar>false</DoNotCleanTaskBar><SignInMode>1</SignInMode><TimeZone>Eastern Standard Time</TimeZone><AutoLogon><Password><Value>XXX</Value><PlainText>false</PlainText></Password><Enabled>true</Enabled><Username>WDSAdmin</Username><LogonCount>1</LogonCount></AutoLogon></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><UILanguage>en-US</UILanguage><UILanguageFallback>en-US</UILanguageFallback><UserLocale>en-US</UserLocale><SystemLocale>en-US</SystemLocale></component></settings><cpi:offlineImage cpi:source="wim:c:/users/franks/desktop/win10_aik/sources/install.wim#Windows 10 Pro" xmlns:cpi="urn:schemas-microsoft-com:cpi" /></unattend>

Hi,

Bear with me if this is question should be on Google forum instead of Microsoft forum.

https://docs.microsoft.com/en-us/microsoftsearch/set-default-homepage#:~:text=Navigate%20to%20%3CComputer%2FUser%20Configuration,and%20set%20it%20to%20Enabled.

According to above MS document, Google Chrome home page can set via additional Group Policies. Is it ONLY true for domain joined devices? Because on workgroup, I am failed to set the customization.

Another reading (non-Microsoft) describes the same procedure, but can we make it via Local Group Policy for non-domain joined devices.

I'm currently having an issue trying to capture windows 8.1 Enterprise image using Server 2012 R2 + WDS for deployment.

All the usual steps have been followed, images added from the install media used to set up the initial machine, DHCP configured and PXEBoot works fine for the deployment image (it loads, I get an ip, can access reminst share) but when I boot in the capture image I get nothing but a black/blank screen.

Initially when I booted in to the capture image I was receiving an 0xC000000F error but by adding the network driver to the capture image it resolved that issue and it gives the blue windows logo and starts loading but then goes black. I've subsequently tried to add all available drives for this machine from the HP site but made no difference.

WDS server is a hyper-v VM and the box to be capture is physical, both on the same vlan.

Any one experienced this?

I seem to get error 87 when checking the current edition as well.

C:\Windows\system32>dism /online /get-targeteditions

Deployment Image Servicing and Management tool Version: 10.0.14393.3750 Image Version: 10.0.14393.3241 Error: 87

The get-targeteditions option is unknown. For more information, refer to the help by running DISM.exe /?. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

C:\Windows\system32>

C:\Windows\system32>Dism /online /Set-Edition:ServerDatacenter /AcceptEula /ProductKey:MyVerifiedWorkingKeyHERE

Deployment Image Servicing and Management tool Version: 10.0.14393.3750 Image Version: 10.0.14393.3241 Error: 87

The set-edition option is unknown. For more information, refer to the help by running DISM.exe /?. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

C:\Windows\system32>

Looking into the logs and I see this after running the TargetEditions. 

2020-07-07 09:05:39, Info                  DISM   DISM Transmog Provider: PID=13304 TID=13272 Current image session is [ONLINE] - CTransmogManager::GetMode

2020-07-07 09:05:39, Info                  DISM   DISM Transmog Provider: PID=13304 TID=13272 Audit Mode: [No] - CTransmogManager::Initialize

2020-07-07 09:05:39, Error                 DISM   DISM Transmog Provider: PID=13304 TID=13272 GetProductType: Error [0x80070002] retrieving current ProductType value. - CTransmogManager::GetProductType

2020-07-07 09:05:39, Warning               DISM   DISM Provider Store: PID=13304 TID=13272 Failed to call Initialize method on IDismServicingProvider Interface - CDISMProviderStore::Internal_LoadProvider(hr:0x80070002)

2020-07-07 09:05:39, Warning               DISM   DISM Provider Store: PID=13304 TID=13272 Failed to Load the provider: C:\Users\HS1139~1\AppData\Local\Temp\B099C144-E6B0-492F-8E86-484EA966549B\TransmogProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007000 2)

2020-07-07 09:05:39, Info                  DISM   DISM.EXE: Got the collection of providers. Now enumerating them to build the command table. 2020-07-07 09:05:39, Info                 DISM   DISM.EXE: Attempting to add the commands from provider: DISM Log Provider

And this arround the time I try to change the license. 

2020-07-07 09:08:43, Info                  DISM   DISM Transmog Provider: PID=4044 TID=10148 Current image session is [ONLINE] - CTransmogManager::GetMode

2020-07-07 09:08:43, Info                  DISM   DISM Transmog Provider: PID=4044 TID=10148 Audit Mode: [No] - CTransmogManager::Initialize

2020-07-07 09:08:43, Error                 DISM   DISM Transmog Provider: PID=4044 TID=10148 GetProductType: Error [0x80070002] retrieving current ProductType value. - CTransmogManager::GetProductType

2020-07-07 09:08:43, Warning               DISM   DISM Provider Store: PID=4044 TID=10148 Failed to call Initialize method on IDismServicingProvider Interface - CDISMProviderStore::Internal_LoadProvider(hr:0x80070002)

2020-07-07 09:08:43, Warning               DISM   DISM Provider Store: PID=4044 TID=10148 Failed to Load the provider: C:\Users\HS1139~1\AppData\Local\Temp\4E17B1A0-E481-41AE-8E61-FC6A08E1A676\TransmogProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x80070002 )

2020-07-07 09:08:43, Info                  DISM   DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.

2020-07-07 09:08:43, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Log Provider 2020-07-07 09:08:43, Info                 DISM   DISM.EXE: Attempting to add the commands from provider: OSServices

Hi All,

I am trying to provisioning the windows using WDS in the ipv6 environment. Though we have set up the WDS on one of the Windows machine without DHCPv6 as we have already a DHCPv6 server in the same network, we did not see any offer from this WDS machine  while we are trying to lanboot in the UEFI shell.

So I would like to know necessary requirements and configuration details for provisioning the Windows from a WDS in ipv6 environment.

Looking forward to help from you folks.

Thanks,

Harinath

In the past I generated and successfully used answer file autounattend.xml to install Windows Server 2016 (used image en_windows_server_2016_x64_dvd_9718492.iso). Now I generated by help of Windows System Image Manager new answer file (see below) to install Windows Server 2019 (used image en_windows_server_2019_updated_june_2020_x64_dvd_7757177c.iso). Differences between these files are only product key and OS name in ImageInstall/OSImage/InstallFrom/MetaData/Value section (Windows Server 2016 SERVERSTANDARD and Windows Server 2019 SERVERSTANDARD accordingly). But Windows Server 2019 installation fails with the following error:
"Windows installation encountered an unexpected error. Verify that the installation sources are accessible, and restart the installation.
Error code: 0xC0000005"

When I removed InstallFrom section from the answer file, Windows Server 2019 installation completes successfully, but I need to select the OS (Windows Server 2019 Standard or Windows Server 2019 Standard Desktop Experience) in UI manually during installation. Of course, it's not unattended installation in result.

Could you please clarify me what's wrong in my autounattend.xml for Windows Server 2019?

<?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><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"><ImageInstall><OSImage><InstallFrom><MetaData wcm:action="add"><Key>/IMAGE/NAME</Key><Value>Windows Server 2019 SERVERSTANDARD</Value></MetaData></InstallFrom><WillShowUI>OnError</WillShowUI><InstallTo><DiskID>0</DiskID><PartitionID>2</PartitionID></InstallTo><InstallToAvailablePartition>false</InstallToAvailablePartition></OSImage></ImageInstall><UserData><ProductKey><WillShowUI>Never</WillShowUI><Key>*****-*****-*****-*****-*****</Key></ProductKey><AcceptEula>true</AcceptEula></UserData><DiskConfiguration><Disk wcm:action="add"><CreatePartitions><CreatePartition wcm:action="add"><Order>1</Order><Size>500</Size><Type>Primary</Type></CreatePartition><CreatePartition wcm:action="add"><Order>2</Order><Type>Primary</Type><Extend>true</Extend></CreatePartition></CreatePartitions><WillWipeDisk>true</WillWipeDisk><ModifyPartitions><ModifyPartition wcm:action="add"><Order>1</Order><PartitionID>1</PartitionID><Label>Boot</Label><Format>NTFS</Format><Active>true</Active></ModifyPartition><ModifyPartition wcm:action="add"><Order>2</Order><PartitionID>2</PartitionID><Label>System</Label><Format>NTFS</Format></ModifyPartition></ModifyPartitions><DiskID>0</DiskID></Disk></DiskConfiguration></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>MyP@ssw0rd</Value><PlainText>true</PlainText></AdministratorPassword></UserAccounts></component></settings><cpi:offlineImage cpi:source="wim:c:/users/administrator/desktop/win2019/install.wim#Windows Server 2019 SERVERSTANDARD" xmlns:cpi="urn:schemas-microsoft-com:cpi" /></unattend>

Hello,

On MDT 2012, under one of the deployment shares, I am getting the error as below

The details shown are :

Other deployment shares under the same server are fine. The monitoring tab are configured for ports 9803 for event and 9804 for Data.

Any suggestions?

Regards,

Ramu V Ramanan

This “Setup Deployment” Forum will be migrating to a new home on Microsoft Q&A!

We’ve listened to your feedback on how we can enhance the forum experience. Microsoft Q&A allows us to add new functionality and enables easier access to all the technical resources most useful to you, like Microsoft Docs and Microsoft Learn. 

Now until July 26, 2020:

• You can post any new questions on Microsoft Q&A or here.

From July 27, 2019 until August 10, 2020:

• New posts – We invite you to post new questions in the “Setup Deployment” forum’s new home on Microsoft Q&A. The current forum will not allow any new questions.
• Existing posts – Interact here with existing content, answer questions, provide comments, etc.

August 10, 2020 onward:

• This forum will be closed to all new and existing posts and all interactions will be in Microsoft Q&A.

We are excited about moving to Microsoft Q&A and seeing you there.        

Learn More

Please remember to mark the replies as answers if they help.
"Windows 10 Installation, Setup, and Deployment" forum will be migrating to a new home onMicrosoft Q&A (Preview)!
We invite you to post new questions in the "Windows 10 Installation, Setup, and Deployment" forum’s new home on Microsoft Q&A (Preview)!
For more information, please refer to the sticky post.

Hi Team,

I have tried to do the inplace upgrade from Windows 2008 to Windows 2012 R2 standard. OS upgrade failed after completed 75% ( went on hung state ). I just wanted to find the root cause why upgrade got failed to prepare the RCA.

Can some one advise me the process and procedure, related logs to find the root cause.

Thanks & regards

Raj.

Hello everyone,

I'm trying to build a WDS Server (Windows Server 2016) to deploy Windows 10 to client.

I try to setup an unattend.xml file for clients connect to WDS Server without typing username password, but it doens't work.

Here is my unattend.xml

<?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" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><WindowsDeploymentServices><Login><Credentials><Domain>deploy.local</Domain><Password>P@ssw0rd</Password><Username>administrator</Username></Credentials></Login><ImageSelection><InstallImage><Filename>install.wim</Filename><ImageGroup>group1</ImageGroup><ImageName>Windows 10 Pro</ImageName></InstallImage><InstallTo><DiskID>0</DiskID><PartitionID>1</PartitionID></InstallTo></ImageSelection></WindowsDeploymentServices></component></settings><cpi:offlineImage cpi:source="wim:c:/iso/windows10_20_7_2020_downfrommicrosoft/sources/install.wim#Windows 10 Pro" xmlns:cpi="urn:schemas-microsoft-com:cpi" /></unattend>

In WDS Server Properties, tab Client, I enabled checklist "Enable unattened installation" and browse to the unattend.xml.

But it doesn't work. Client still ask credentials to connect to WDS Server. Please anyone help me this problem? Thank you.

I Have an active Directory setup within my office, and I wish to take advantage of Windows Deployment Services to deploy office workstations for our employees.

I have 1 requirement.

The DHCP server is an Mikrotik RouterBoard.

I need to know what options I need to set to allow our clients to PXE boot into WDS.

No one really seems to know what needs to be done.

Since there are options for using a 3rd party DHCP server software, I cant see why this will not work.

Hi experts,

I have reverse proxy in the environment where it has existing server farm pointing to the exchange backend services for OWA and autodiscover. However, I would like to use the same reverse proxy server to translate SFTP port from inbound to outbound. Basically it is something as below:-

1. User request for sftp://public_IP:6782, then it translates to the backend server which is sftp://private_IP:22

Can we configure such a thing in reverse proxy via IIS ARR?

Peter

Hello,

I have tried severely to install new window on my laptop from boot-able usb drive but it keeps on saying "Windows cannot open the required file D:\Sources\Install.wim. Make sure all files required for installation are available and restart the installation. Error Code: 0x800700D". What I do to resolve the problem. Please I need help.

Hi there

Our corporate domain is set up as follows

1) Our Active Directory controllers (we have 2) are both Windows Server 2008 R2 Enterprise.  

2) Our Exchange Server is also Server 2008 R2 Enterprise, and Exchange itself is 2007 v 08.03

3) Our users all use Microsoft Office 2007 Service Pack 3. 

Our company wants to transition to Microsoft Office 365. My team has been tasked with drawing up a project road map. It's not just about buying licences for 365 for our users, we need to upgrade our Domain Controllers and our Exchange first. 

What I am hoping someone here can help with, are the following questions.

1) Do we begin with our Domain Controllers? And if we choose 2012 R2, how long can we expect to have no compatibility issues? Is 2016, or 2019 preferred?

2) Regarding Exchange, my question is the same. What server version, and what Exchange version, do we require in order to have complete compatibility with our migration to 365?

3) Regarding both upgrades above, should we look at software upgrades on the existing servers, or completely new installs on new hardware? 

4) Once our Domain Controllers and Exchange have been upgraded, will our existing 2003 and 2008 Servers (some are SQL servers) still function normally?

5) Are there any hidden dangers that we may be unaware of? 

Many thanks for your assistance everyone.