1. Hi,
   
   I have Dell PowerEdge Rack Server R510 that have Dell PERC S300 RAID Adapter which is configured to RAID 1. The server runs Windows Server 2008 R2. Currently the OS corrupted I cannot do backup anymore using Windows Backup, I cannot remove or add server roles, I cannot install updates and some application software fail to accessed from domain users. Also I cannot edit DNS and DHCP information.
   
   I tried to perform in place upgrade to Windows Server 2012 R2 but it keep showing Setup is restarting for three days now. So I have come to a decision to install Windows Server 2012 R2 on top of the existing one Windows Server 2008 R2.
   
   The server has two shared Printers & one shared Scanner, File Server, AD DC, DNS, DHCP, and two Access Points. It serves more than 20 PCs mostly in wireless connectivity.
   
   My Questions are:
   
   1.Will I be able to access the RAID Drives from Windows Server 2012 R2 after installing it on top of Windows Server 2008 R2 without need a of reconfiguring the RAID Adapter?
   
   2.On top accessing the RAID Drives, will my data be safe after the process that I won't lose them?
   
   3.How will I be able to transfer DNS, DHCP, AD DC roles records from Windows Server 2008 R2 to Windows Server 2012 R2 after the installation is successful?
   
   4.With the new OS Server 2012 R2, will the client PCs pick Server 2012 R2 automatically or I'll be required to rejoin them to the domain.
   
   5.What is the best way if I'm wrong with my decision?
   
   Thank You!

We were trying to install both NDES and CES on our existing enterprise CA server.

However, during the step to specify the service account, after selecting the account to use, it prompted error "The implementation is not capable of performing the request" Any idea how we can fix this issue?

The service account used is already in local admin group, the user account that we used to run the setup has also been added as member of Enterprise Admins group before starting the setup.

My WDS MDT PXE boot process was working fine until I installed the latest versions a couple of days ago of Windows 10 Deployment Kit and ADK WinPE for Windows 10. I've seen a possible fix (see below)

1.Open WDS

2.Right-click your server in the left pane and open properties.

3.Open tab “TFTP” and change the maximum block size to eg 1024.

4.Restart your WDS server.

The trouble is there is no TFTP tab in the properties of my WDS? Any ideas?

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 everyone, hope you can help me.

I have a Windows Server 2019 with WDS role

It was working perfectly with many virtual and physical machines for Windows deployment.

Suddenly without changing anything it stopped working and now machines (virtual or physical) get stuck at the start of the loading bar and then display this error:

Status: 0xc0000001

Info: A required device isn't connected or can't be accessed. 

I've already tried reinstalling WDS role and shared file



Hello,

I'm having some Problems with the WDS. I have installed in a windows server 2016 /1607 (OS Build 14393.3204).

When i configure WDS it always says "The service did not respond to the start or control request in a timely fashion". no matter what I do.  I dont have a DHCP in the same server, it only has the WDS.

I checked the event viewer to research more information about it and i get these events:

- Event ID :768

An error occurred while trying to initialize the Auto Add Policy. 
 
 Error Information: 0x6FC 

- Event ID :261

An error occurred while trying to initialize provider WDSDCPXE loaded from C:\Windows\system32\wdsdcpxe.dll. If the provider is marked as critical, the Windows Deployment Services server will  shut down. 
 
 Error Information: 0x6FC 

- Event ID :264

An error occurred while trying to initialize provider WDSDCPXE. Because the provider  is not marked as critical, the Windows Deployment Services server will continue to run. 
 
 Error Information: 0x6FC 

- Event ID :268

All registered providers failed to initialize. Review the Event Log for specific  error messages for each provider. Windows Deployment Services will  shut down.

- Event ID :513

An error occurred while trying to initialize provider WDSPXE from C:\Windows\system32\wdspxe.dll. Windows Deployment Services server will be shutdown.
 
 Error Information: 0xC107010C 

- Event ID :257

An error occurred while trying to start the Windows Deployment Services server. 
 
 Error Information: 0xC107010C 

- Event ID :7024

The Windows Deployment Services Server service terminated with the following service-specific error: 
%%3238461708.

I tried a lot of workaround and i still cant fix the problem. I just discovered that if I get the server out of the domain and I rejoin, the moment that starts the services are working fine, but in a matter of time (15-20 minutes) they dont work again. and even if I try installing a OS when the servces are "working" still dosn't work.

I ran out of ideas. Any sugestions?

We have a 2016 KMS host. It's publishing a Office 2016 KSM key. It works fione and Offoce 2016 cluents can obtain their Office license.

But after I purchased more Office license in another contract, we needed to add a second Office 2016 on the same KMS host. But when I add the second Office 2016 KMS key, the KMS host lose the first OFfice 2016 KMs key. It only accepts one KMS key for the same product+version.

If now we add once the fisrt Office 106 KMs key, one more time it loses the other Office 2016 KMs key.

We need to publish all our Office 106 keys but we cannot. I don't know how to proceed in this case.

anyone getting pxe-e16: no offer received for uefi client computers?

start pxe over ipv4

station ip address is xxx.xxx.xxx.xx

pxe-e16: no offer received

start pxe over ipv6

using same computer and change to bootmode to legacy but it has no problem boot to pxe.

dhcp is distributed by router with ip helper-address [ip address of sccm dp]. wds service is installed is sccm dp.

both router, sccm dp, pxe boot client are in the same network segement.

tried below 2 methods but it doesn't help.

1. disable NetBIOS over tcp/ip

2. reinstall wds to standalone mode

HI EVERY BODY

I HAVE WDS SERVER 2012 IT WORK WELL BUT

WHEN I ADD INSTALL IMAGE RELATED TO WINDOWS 8 (FROM ISO OR FROM DVD  OR FROM SYSPREP )

SOTPP IN WORK  AND GIVE TAHT ERROR

"The service did not respond to the start or control request in timely fashion"

IF I ADD INSTALL IMAGE RELATED TO WINDOWS 7 (FROM ISO OR FROM DVD  OR FROM SYSPREP )  WORK WITH NO ERROR  

Dear Team,

I m trying to perform authoritative restore for one OU . but its not Woking
after replication restore object getting deleted.
Please find below step

1. Booting system in DSRM.
2. login with DSRM credential
3. Disabling AD services
4.Restoring system state using wbladmin
5. Performing authoritative restore command
    restore subtree "ou=***,DC=***,DC=***"
After restore rebooting AD in normal mode.

..But post replication restored OU gets deleted

Thanks,

Ritesh

R!t@$#

I HAVE WDS SERVER 2012R2 ONTHER MACHINE WINDOWS 8.1 

I MAKE SYSPREP FOR WINDOWS 8.1 AND WHEN I WANT TO UPLOAD THAT WIM FILE TO WDS SERVER I GET THE DATA IS INVALID

Hello,

I have a problem with my sysprep i have this error

Do you have a idea to solve my problem ?

I HAVE TWO  HYPER-V MACHINE (SERVER 2012 R2    - WINDOWS 8.1)

INSTALL WDS ON SERVER 2012 AND MAKE CONFIGURE THE WDS SERVER DONE NO PROBLEM

IN WINDOWS 8.1 MACHINE I MADE SYSPREP AND TURN OFF THAT MACHINE

WHEN I WANT TO UPLOADE THE IMAGE TO SERVER GET THE FOLLOWING ERROR 

THE POERATION COMPLETD WITHE ERROR

TH DATA IS INVALID

Does anyone have step by step process moving IIS 8.5 INETPUB directory to Another Drive? Running Windows Server 2012 R2.

Thanks.

Добрый день.

Реализован falover cluster и две ноды SQL , вот такая ошибка, не пойму куда и кому нужно дать права ? на контейнер или куда ? :

The computer object associated with the cluster network name resource 'AlwaysOnDb_ListenerDb' could not be updated in domain 'domain.local' during the 

Password change operation.

The text for the associated error code is: The specified network password is not correct.


The cluster identity 'DBCLUSTER$' may lack permissions required to update the object. Please work with your domain administrator to ensure that the cluster identity can update computer objects in the domain.