Hi Everyone,

I have configured the MDT & WDS on Windows Server 2016.

I then captured a reference image of a Windows 10 install (on a laptop) by using the 'Sysprep & Capture' task sequence.

Finally I imaged a laptop using the reference image which I captured earlier.

Whilst WDS appears to have done it's job, and the reference image loaded, I am seeing some very strange Start Menu behaviour!

All of the Apps in the Start Menu have been replaced with 'Blue Arrows', and when I click on one of the shortcuts I see -

Here are some specifics on the versions of software that I am using -

ADK for W10, version 1803
MDT 8450
WDS (on Server 2016), version 10.0.14393.0
WinPE 10.0.14393

If anybody has any advice on how to overcome this issue it will be greatly appreciated.

Kind Regards,

Davo

I currently have a Windows 2008 R2 WDS server.  I built a new 2016 RDS server to replace it.  I exported all my boot images from the old server and imported them into to the new server.  However, when I PXE boot, I only see the 64-bit boot image menu items.  The one 32-bit boot image is a special image used by our workstation support team to do recovery operations for workstations that fail to boot to the OS - they can PXE boot the machine to a recovery console to restore the machine or do maintenance on it.  That one 32-bit image fails to appear in the menu.

Since this works fine on 2008 R2 (I can see both the 64-bit and 32-bit boot images in the menu), I am thinking there must have been some hack I used many years ago to get it to work.  But I cannot remember what I did.

Does anyone know how to get this to work?

Thanks

NK

I have a project to migrate from a Windows 2008 R2 environment to a Windows 2012 environment. My source domain is 2008. I have setup a new 2012 domain and I have a trust between the two. I'm not familiar with the ADMT tool but from my readings it looks like I want to do an INTERforest migration because I don't want to MOVE the current objects from the 2008 domain but rather COPY the objects into the new domain. 

I'm just looking for confirmation from someone/anyone that this is in fact the correct course of action I want to take. And if anyone has any additional 'good to know' information, suggestions or recommendations it would be greatly appreciated.

Thanks.

I get msi error 1640 ERROR_INSTALL_REMOTE_DISALLOWED when I try to install a program as a user and as administrator on a Remote Desktop session server.

EnableAdminTSRemote does not apply for Windows Server 2012.

Have set DisableMSI = 0 , without it the user get error 1625.

Actually the admin user can install, but get that error when trying to uninstall.

Hi Guy's,

I having a problem with a website in a server 2008 R2,

when using the intgrated application pool get the error 500.52 URL Rewrite modul error and also see this error:When put the application pool back to the classic we can open the website.

Any suggestion?

Shahin

Installation of one or more roles, role services, or feature failed. The reference assembly could not be found error: 0x80073701.

DHCP Server

Remote Server Administrative Tools

Role Administrative Tools

DHCP Server Tools

Brand new server 2016 Standard installed yesterday, no anti-virus or Firewall in place yet. Patched and updated. 

Thanks 

Hi Team,

We need to deploy the new servers like a active directory domain server , wsus server and wds server in public cloud like azure or aws.

-Our office branches are presented in India and US.

- We have taken the public cloud services from some X.

-We are planning to deploy the adds server(pdc) in cloud and users will authentication via site 2 site tunnel, will it recommended solution ?. the 200 users need to be authenticated daily to cloud adds server(pdc), what are issues will face if implement like structure and do you have recommended the better solution for this ?

Note :- India users and US location users need to be authenticated to pdc server in cloud.here how much of the bandwidth is recommended for this solution. India location users are 200.  US location users are 100. 

- Will you recommend wsus server install on public cloud ?if we deploy how much of bandwidth is require for 2 sites users getting a patch updates.

-Please confirm wds and  dhcp servers can run in single server ? and will it recommend.?

-Can we install wds server on public cloud from cloud to 2 sites users machine need to rebuild will it is possible and what is bandwidth is require , communication is on site 2 site tunnel.

Please clarify the above quires aspa.

Thanks in advance. 

jsr

Dear all

We're using a Windows Server 2012 R2 (DC of a Domain) and WDS (Windows Deployment Services) to deploy a Windows 8.1 edition with a MAK (Multiple activation key).

Deployment works by PXE booting and deploying the original install.wim (from the .iso) from the WDS Server.

If we try to activate the deployed Windows on the client PC we experience the following:

1. Activation in the GUI ends with error "Windows has detected a change to the system files that is preventing activation."

2. Command line, slmgr /dli ends with "Error: 0xc004d302 on a Computer running Microsoft Windows non-core edition, run slui.exe 0x2a 0xc004d302 to display the error text"

3. Command line slui.exe 0x2a 0xc004d302 ends with the error "The security processor has reported that the trusted data store was rearmed.

Hence we cannot activate Windows.

Our Windows copy and our licenses (MAK key) were purchased thru official channels.

We urgently need this to work.

Any help is much appreciated.

Dominique, Zurich, Switzerland.

Hi,

We are trying to implement SCCM for Internet based client and understand that we have to have Trusted Root CA & PKI

Our AD structure is One forest and multiple sub domain and under sub domains we have all our clients ,users etc.

On Company network or VPN everything is working fine  with SCCM & SCCM clients but for internet based client we need to have Trusted Root CA & PKI on our DC

I have gone through lots of links  and they explain nicely all steps but my concern is, we don't have existing PKI or Trusted root CA configured on our Root DC or sub  domain

if we just implement both PKI + Root Trusted CA will there  any impact to our existing normal machine ,terminal servers or intranet sites or any other things you might know will get affected because of this?

Please suggest 

Regards,

Swapnil

Hi,

I have a new error that I'm not sure how to fix. Hopefully someone can help me.

The PCs on our network must be approved in WDS before deployment and we normally right-click > Approve the machines for deployment; however, that has suddenly stopped working for every machine. We now have to go through the Name and Approve right-click menu option.

Error Message we see says:
Pending Device Error: Windows Deployment Services failed to generate a computer name for the device.

What happened here? Did WDS run out of names? Should I reset something?

Currently I have my Windows Home Server 2003 installed on HP DL380 G3 server... Its all great and WHS 2003 is working great there for about 10 years now... The thing is that i need more space and quieter machine and etc...So i turned to my very powerful HP XW6400 workstation and tried installing WHS 2003 there. The installation starts and few minutes into it it fails with error: "Could not initialize UI subsystem."  Once i OK the error message - it restarts...

Any ideas???

Regards,

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>

Hello,

We are currently trying to setup WDS in our organization.  The WDS is on it's own VLAN with Server 2016 and also hosts the DHCP server.

The problem we are having is that I keep having to pick between x64\wdsnbp.com or x64\wdsmgfw.efi in the DHCP options to get it to boot.  I thought WDS was supposed to set this up automatically when the DHCP server is hosted on the same machine?  We also have to leave "Configure DHCP options to indicated that this is also a PXE server" unchecked or it will not boot.

Are we doing something wrong or is this intended behaviour?  I was under the impression that WDS hosted on the same DHCP server was supposed to automatically choose the proper architecture and boot option.  We are only deploying x64 machines, so it's not a huge deal but it becomes annoying when we forget to change this.

Hi All,

I have an odd issue with WDS that i'm hoping someone can assist with, unfortunately information on this is fairly skim and the articles that do exist don't directly answer the questions so apologies for the length of this. We use PXE Response with admin approval required and previously have not had an issue. However in the last month or so we have had multiple entries of "Domain AdminsX" which we can't explain.

I'll split this up into a few sections so it's easier to answer.

Before we go anywhere:

- WDS 6.3.9600.16384 (Native Mode)

- Server 2012 R2 

- MDT Workbench 6.3.8450.1000

----------------------------------------

1) The MDT server has been configured as a standalone system, and each time a computer is imaged a new "Domain Admins" entry is added under Prestaged Devices (beneath Pending Devices). Can anyone explain what these objects actually mean or how to stop them appearing? 

----------------------------------------

2) I recently received an error stating that "Windows Deployment Services is either stopped or running in legacy mode" when i was trying to approve a device. Turning approval off can address this but doesn't explain why it has never been an issue before. Under Prestaged Devices, there was 99 devices, by deleting an entry (98 at that point) and turning approval back on i was then able to proceed - "The pending device was successfully approved". I tested it again at 99 and received the legacy mode error. 

WDS was re-installed, services restarted etc but this was the only way to get that error to go away.. Is there a limit to approved devices? Ie 99..

----------------------------------------

3) Is there a way to remove all Prestaged Devices via a command as it has to be done one by one (very slow) either in the GUI or by the Remove-WdsClient command. There doesn't appear to be a wildcard command to clear them all. 

----------------------------------------

4) What is the difference between Prestaged Devices and Active Directory Prestaged Devices? If it is a standalone config why do the Domain Admin entries appear there? 

----------------------------------------

Thank you for any assistance, if you require more information please let me know.

Marc 

Hello Expert,

Our system just get hit by an unauthorized access which bring down the HP SAN storage.

What would you do to bring up the storage ASAP 

Here is the background of our system:

• Two HP physical servers with Win 2008R2 running SAP application.  The OS is on local C drive while SAP application is pointing to HP SAN storage.
• Another HP physical server that running Cognos data warehouse with the data pointing HP SAN storage
• All data on SAN storage was less than 1TB of data
• The 3 servers and the SAN are less than 4 years old.
• The servers, network and Cognos was designed and build by outside consultants.
• The SAP application was build and configure by outside developer.
• Teamviewer was used by IT members, users and customer for remote support

Backup status:

• HP 24 tapes library.
• Netgear Ready NAS 2100
• Backup are running everyday to the disk and to the tapes.  
• Backup Tapes will be sent out to the vault every morning.
• Twice a year, an IT administrator performed a system restore the SAP servers from the backup to the test environment and have users tested and validated random program to ensure all figures  are match between live system and restored system.  

Here is the issue:

• An unauthorized access from former IT administrator access the network through Teamviewer and deleted HP SAN configuration.  This deletion put the SAN storage back to factory default setting which clear out all the data on the storage
• He also deleted the backup from the disk.  
• There is no damage to 3 physical OS server.

All the experts out there, please chime in and let me know what would you do to bring the server up and running ASAP at the shortest time?

Will "delete SAN configuration" or "delete backup data from NAS device cause hardware failure?

How to does it take to bring the server up and running again?

hi guys

i deployed a wds server on windows server 2008 R2, i laso have a DC and DNS Server And a DHCP Server on my Other Server,

I Also Use IP Phones In my Office and the problem is exactly here, Option 66 on dhcp server is assigned to ip phone tftp Server and the server is at an other city so i cant change it,

what is your solutions for this Problem????

Hi

I have 2 WDS servers installed on Server 2016, both configured and worked just fine

one bright morning they entered a down state , service is stopped ,  cant start it

i get this:

An error occurred while trying to execute the command.
Error Code: 0x41D
Error Description: The service did not respond to the start or control request in a timely fashion.

im logged in as a domain admin , and nothing changed on my network

any help would do

thank you

Hi all,

I need some help with windows deployment. Basically we want to setup a server connect to a switch and deploy the image to several laptops locally.

For now we only have the image in a USB stick. This USB has a fat image with all the apps and all the task sequence from a MDT server. Is it possible to use this image in a MDT server?

What do we need to setup the server and if we can use the USB we have or we need the wim file?

Apologies if I'm asking basic questions but it's the first time we will be doing this.

Thanks,

Alex

Hey, hope im posting this in the correct forum, I recently setup my wds and mdt and successfuly captured and deployed windows 10 images. I want to know how I can make a users credential tied to a task sequence. For example if theirs a username jsmith and hes in finance and he needs to reimage his laptop all he does is to connects to the internal network and pxe boot his machine to windows deployment wizard, now aside from him clicking on a task sequence to image his machine, how can i make it that a paticular user  group or a department can be tied to a task sequence meaning as soon as the credentials and password is entered the proper task sequence is run. like jsmith enters their credentials and Asanders enters their credentials and that users is in a different department both users get different task sequence that run and install automatically. Excuse my grammer errors english is my second lanaguage. Thank You