WDS Server Service won't start - 'An error occurred trying to start the Windows Deployment Services Server.'

I'm having issues installing starting the WDS server service on Win 2008 R2,  this is happening on multiple (all 2008 R2) systems on this domain so I'm beginning to think it's either AD or network related, in event viewer I get the following error.
'An error occurred trying to start the Windows Deployment Services Server.'
Error Information: 0x0906
EventID : 257 
single domain, single forest, 2008 R2 functional level, both system are virtual plugged into same vswitch on a flat network.
any ideas what might be the issue?  I've never had an issue getting this working on many occasions before today and I've come to many a dead end looking at other articles thus far... 
With WDS tracing enabled I get the following error information:
[4304] 09:22:11: ===>Starting logging of module [WDSServer]
[4304] 09:22:11: [UDPPorts] Policy: 1, Dynamic Port Range: 64001-65000.
[4304] 09:22:11: [RPC] Using Tcp Port 5040 for Rpc Calls.
[4304] 09:22:11: [RPC] Client Impersonation Logging=Disabled
[4304] 09:22:11: [RPC] Host Name: sccm.domain.local
[4304] 09:22:11: [RPC] NTLM/Kerberos Spn: ldap/sccm.domain.local
[4304] 09:22:11: [RPC] Initialized
[3756] 09:22:11: [RPC] Server Started.
[4304] 09:22:11: [BINLSVC][RPC][Ep={5F4FB9F0-C0E3-41C1-AA00-9A7C690AC3A3}] Registered
[4304] 09:22:11: [BINLSVC] Provider Initialized.
[4304] 09:22:11: [WDSDDPS][RPC][Ep={FA0A27E1-C2BA-4B3B-94B2-025E82FFAA6D}] Registered
[4304] 09:22:11: [WDSDDPS][RPC][Ep={011D24AC-CB3A-4739-A339-5D2E1B5306CE}] Registered
[4304] 09:22:11: [51][WDSDDPS] [d:\w7rtm\base\ntsetup\opktools\wds\ddp\server\ddpprovider.cpp:196] Expression: , Win32 Error=0x906
[4304] 09:22:11: [WDSDDPS][RPC][Ep={FA0A27E1-C2BA-4B3B-94B2-025E82FFAA6D}] Closed
[4304] 09:22:11: [WDSDDPS][RPC][Ep={011D24AC-CB3A-4739-A339-5D2E1B5306CE}] Closed
[4304] 09:22:11: [d:\w7rtm\base\ntsetup\opktools\wds\wdssrv\server\src\wdsprovider.cpp:144] Expression: , Win32 Error=0x906
[4304] 09:22:11: [WDSDDPS] Initialization Failed (rc=2310)
[4304] 09:22:11: [d:\w7rtm\base\ntsetup\opktools\wds\wdssrv\server\src\wdsprovhdl.cpp:172] Expression: , Win32 Error=0x906
[4304] 09:22:11: [WDSDDPS] Deleted.
[4304] 09:22:11: [d:\w7rtm\base\ntsetup\opktools\wds\wdssrv\server\src\wdsservice.cpp:178] Expression: , Win32 Error=0x906
[4304] 09:22:11: [Udp] Listen Shutdown.
[3756] 09:22:11: [RPC] Server terminated (rc=0)
[4304] 09:22:11: [RPC] Listen Stopped.
[4304] 09:22:11: [BINLSVC] Shutting down
[4304] 09:22:11: [BINLSVC][RPC][Ep={5F4FB9F0-C0E3-41C1-AA00-9A7C690AC3A3}] Closed
[4304] 09:22:11: [BINLSVC] Deleted.

It seems I've found out the solution myself,  the issue seems to be caused when DHCP and WDS are on the same server, The installation must identify this during the first installation of WDS but not on subsequent installations, the method to
get it working again is:
1.      
Install WDS Role (using defaults)
2.      
Make the following registry change:
HKLM\SYSTEM\CurrentControlSet\services\WDSServer\Providers\WDSPXE\UseDhcpPorts  =  0
3.      
Run the following command line to initialize Windows Deployment Services:
wdsutil /initialize-server /reminst:D:\RemoteInstall
4.      
Run the following command to enable the DHCP port registry setting
wdsutil /Set-Server /UseDHCPPorts:No /DHCPOption60:Yes

Similar Messages

  • PXE-E61 Meadia test failure error occurred during installing OS form windows deployment service?

    Hi,
         I have installed WDS service in my dell server windows 2008 server R2. I am using WDS server and Dhcp server in different machine.I have received error "PXE:E-61 Media test failure check cable ", when I trying to install
    OS from my WDS server. But I have created a one partition in VMware and successfully installed windows 2008 R2 server from Windows deployment service.  But when I am trying to install the OS in another dell server from WDS, I have received this error.
    Any help?

    Hi,
    For PXE boot, we need the client boot from network. Check your boot option in BIOS settings. Meanwhile, we need WDS server and
    DHCP server accessible. If the client locate in a different subnet, IP helper should be configured to point to WDS server and DHCP server.
    If everything is configured correctly, I recommend you contact with the manufacture.
    Hope this helps.

  • An error occurred while trying to start the Windows Deployment Services server

    After rebooting the server, I cannot start the Windows Deployment Services anymore.
    It worked perfectly before the reboot. When starting it manually these errors appear in the event log:
    The Windows Deployment Services Server service terminated with service-specific error 1460 (0x5B4).
    An error occurred while trying to initialize multicast manager. Windows Deployment Services server will be shutdown.
    Error Information: 0x5B4
    An error occurred while trying to start the Windows Deployment Services server.
    Error Information: 0x5B4
    This is on server standard beta 3.

    I have removed the server from the WDS, then I have uninstalled the role, rebooted, reinstalled the role.
    When I started the WDS the server was back in there, but when I wanted to start the service I got the message "the windows deployment services configuration is corrupt". I have triggered these commands to reset this:
    Code Snippet
    wdsutil /Verbose /Progress /Uninitialize-Server
    Windows Deployment Services Management Utility [Version 6.0.6001.16510]
    Copyright (C) Microsoft Corporation. All rights reserved.
    Tearing down server...
    == Original server operational mode: Native ==
    -> Resetting setup state
    -> Disabling and resetting Windows Deployment Services services
    -> Removing server BINL SCP
    -> Removing Windows Deployment Services share at \\LH-AJGG6OZWH9Z4.longhorn.offi
    ce\REMINST
    == Final server operational mode: Not Configured ==
    The command completed successfully.
    Then i did this command, but again it failed to start at the end.
    Code Snippet
    C:\Windows\system32>wdsutil /Verbose /Progress /Initialize-Server /REMINST:"c:\R
    emoteInstall"
    Windows Deployment Services Management Utility [Version 6.0.6001.16510]
    Copyright (C) Microsoft Corporation. All rights reserved.
    Setting up server...
    -> Creating Windows Deployment Services installation tree
    ---> Creating Windows Deployment Services installation root at \\LH-AJGG6OZWH9Z4
    .longhorn.office\c$\RemoteInstall
    ---> Creating Windows Deployment Services share at \\LH-AJGG6OZWH9Z4.longhorn.of
    fice\REMINST
    ---> Creating Windows Deployment Services folder \\LH-AJGG6OZWH9Z4.longhorn.offi
    ce\REMINST\Images
    ---> Creating Windows Deployment Services folder \\LH-AJGG6OZWH9Z4.longhorn.offi
    ce\REMINST\Boot
    ---> Creating Windows Deployment Services folder \\LH-AJGG6OZWH9Z4.longhorn.offi
    ce\REMINST\Boot\x86\Images
    ---> Creating Windows Deployment Services folder \\LH-AJGG6OZWH9Z4.longhorn.offi
    ce\REMINST\Boot\ia64\Images
    ---> Creating Windows Deployment Services folder \\LH-AJGG6OZWH9Z4.longhorn.offi
    ce\REMINST\Boot\x64\Images
    ---> Creating Windows Deployment Services folder \\LH-AJGG6OZWH9Z4.longhorn.offi
    ce\REMINST\Boot\Fonts
    ---> Creating Windows Deployment Services folder \\LH-AJGG6OZWH9Z4.longhorn.offi
    ce\REMINST\Tmp
    ---> Creating Windows Deployment Services folder \\LH-AJGG6OZWH9Z4.longhorn.offi
    ce\REMINST\Mgmt
    ---> Creating Windows Deployment Services folder \\LH-AJGG6OZWH9Z4.longhorn.offi
    ce\REMINST\WdsClientUnattend
    ---> Creating Windows Deployment Services folder \\LH-AJGG6OZWH9Z4.longhorn.offi
    ce\REMINST\Templates
    -> Installing Windows Deployment Services files
    ---> Installing system files
    ---> Installing boot files for x86
    ---> Installing boot files for ia64
    ---> Installing boot files for x64
    -> Updating registry
    -> Configuring the TFTPD service
    -> Configuring BINL SCP
    Enabling Windows Deployment Services services...
    Starting Windows Deployment Services services...
    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.
    Anyone have an idea what could be the cause? I found this additional error in the event log, but distributed file system hasn't been installed since the beginning.
    DFS could not access its private data from the Active Directory. Please manually check network connectivity, security access, and/or consistency of DFS information in the Active Directory. This error occurred on root REMINST.

  • Error (2912) An internal error has occurred trying to contact the SCVMM01.dom.local server: NO_PARAM: NO_PARAM.

    
    Error (2912)
    An internal error has occurred trying to contact the SCVMM01.dom.local server: NO_PARAM: NO_PARAM.
    WinRM: URL: [http://SCVMM01:5985], Verb: [INVOKE], Method: [GetError], Resource: [http://schemas.microsoft.com/wbem/wsman/1/wmi/root/microsoft/bits/BitsClientJob?JobId={A210B91B-3239-4347-B251-83E1555356A2}]
    Unknown error (0x80072f0d)
    Recommended Action
    Check that WS-Management service is installed and running on server SCVMM01.dom.local. For more information use the command "winrm helpmsg hresult". If SCVMM01.dom.localis a host/library/update server or a PXE server role then ensure that VMM agent is installed and running. Refer to http://support.microsoft.com/kb/2742275 for more details.
    When we want to create a template of a virtual machine, we receive the following error. The environment has the following components and servers:
    * Windows Server 2012 R2 U1 with Hyper-V role enabled
    * High available Virtual Machine Manager 2012 R2 RU2 (two virtual servers on Hyper-V 2012 R2)
    * High available Virtual Machine Manager 2012 R2 Library servers (two virtual servers on Hyper-V 2012 R2)
    There're a few things I've already checked:
    * Self-signed certificates in the Trusted People store --> OK
    * Windows Firewall turn off --> OK
    * Re-added a Hyper-V host to the SCVMM environment
    * Reboot the VMM servers and the library servers
    * Export port usage and conflicts with netstat -a -b --> OK, no conflicts
    * Free disk space on the VMM library servers --> OK
    The job is starts fine, but step 1.2 "Store virtual machine W2012R2TMPL from HV01 to CLSCVMMLIB01" Failed. So it looks like the sysprep fase is going well. When VMM is trying to store the virtual machine in the library, it fails.
    Who is familar with this issue and can help me find a solution for this?
    Thanks in advance!!
    Mark

    Have you installed AppController on the same machine with VMM?

  • LabVIEW 2013: An error occured trying to load the assembly

    Hey all,
    I'm trying to load a .NET 4.5 dll into LabVIEW 2013.
    When I place any of the .NET VIs and try to select the one I'm after it says "An error occured trying to load the assembly" and won't let me load it.
    I also tried importing the dll, but that gave errors too.
    It's defintely a .NET 4.5 dll as the .NET reflector gives me
    [assembly: ComVisible(false)] [assembly: TargetFramework(".NETFramework,Version=v4.5", FrameworkDisplayName=".NET Framework 4.5")] [assembly: SecurityRules(SecurityRuleSet.Level1)] [assembly: SecurityPermission(SecurityAction.RequestMinimum, SkipVerification=true)]
    To try and get around the import issue, I added the following to my LabVIEW.exe.config file
    <?xml version ="1.0"?>
    <configuration>
      <runtime>
        <loadFromRemoteSources enabled="true" />
      </runtime>
    </configuration>
    but it made no difference.
    Any suggestions? All the things I've read so far are for 2010.
    Solved!
    Go to Solution.

    Hornless.Rhino wrote:
    Wart wrote:
    I had the same issue a while back.  Unfortunately mine magically resolved itself, but I made a post with what I'd been reading and got a reply with another suggested link.  It sounds like you've gone down the same road, but I figure every little bit helps:
    http://forums.ni.com/t5/LabVIEW/Error-Loading-NET-Assembly-in-2013/m-p/2521098
    Thanks.
    Hopefully mine will resolve itself too. LV2013 is meant to support the newer stuff without me having to mess about.
    We shall see...
    So far no dice.
    It's really bizarre. It works with sample c# code in visual studio (see link below), but for some reason LabVIEW doesn't like the dll (tried both LV 2012 and 2013).
    Sample code (not mine) is available at http://elbruno.com/2013/12/01/kinectone-hello-world-with-kinectsdk-v2-body-count/

  • An error occurred trying to load the NTX Terminal.

    Hello,
    I have to do a navigation system with Lego's hardware. My English is not really well and I don't know how to install all the drivers and thinks I need to work with Lego mindstorms and Labwieu 8.5.
    I have in my computer (windows vista) Labwieu 8.5 and the tool kit too. But I thinks I need to install more things because I have always warnings when I do any application (like a simple display).
    With more specifications my problem is:
    When I Click: Tools--NTX Modul--NTX Terminal. I have message box like this: An error occurred trying to load the NTX Terminal. 
    If you can help me, I will be really grateful!

    #include "stdafx.h"
    using namespace System;
    extern "C" {
    namespace clrtest {
        public ref class testClass
        public:
             testClass()
             int foo(void)
                return(42);
    Compiling the above minimal c++ code  into a clr dll gives the same cryptic
    "an error occurred trying to load the assembly" when the .net constructor node tries to load it.
    I am far from a .net expert or a c++ one for that matter.
    Anyone know what is missing from the above code?
    Ultimatley I want to write a wrapper for cyusb.lib a static (c++) library for the FX2 USB chip from cypress exposing some of its functionality to labview.
    Cheers
    baldrik

  • Windows could not start the windows deployment services server Error 1067: The Process terminated unexpectedly - Please help

    Hello All
    I am trying to set up a PXE service point on my DP in SCCM 2012 R2
    1) I have enabled the role on the DP
    2) rebooted and verified WDS installed as a role.( I let SCCM enable this role as instructed)
    3) When I tried to start the role from services I get the error below:
    Note: I also followed the troubleshooting steps in this technet article but still it stops at the half way point
    http://support.microsoft.com/kb/2009647/en-us
    Phil Balderos

    Hi,
    Here is a similar post for your reference.
    Windows Deployment Service
    http://www.windows-noob.com/forums/index.php?/topic/3938-windows-deployment-service/
    Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Firefox won't open no error message, tried everything in the help article nothing works. Won't even open in safe mode. help!

    When I click on the firefox icon (windows 7) nothing happens. not even in safe mode. Nothing in the help article works. I've tried uninstalling twice.

    Hi mcclausky, you may need to manually remove a policy setting from the registry. You also should scan for malware that might have created this problem.
    This article lists scanning and cleaning tools other Firefox users have found helpful: [[Troubleshoot Firefox issues caused by malware]].
    To check your Windows registry for policy settings that might affect Firefox or other programs, I suggest consulting a Windows forum or Microsoft's forums. For example:
    * http://windowssecrets.com/forums/
    * [http://answers.microsoft.com/en-us/windows/forum/windows_8-system/this-operation-has-been-cancelled-due-to/9677848e-072d-4206-87f4-9da9284d6151 This operation has been cancelled due to restrictions in effect on this computer. Please contact your system administrator. - Microsoft Community]
    * [http://answers.microsoft.com/en-us/windows/forum/windows_xp-security/restrictions-this-operation-has-been-cancelled-due/8af1d0cd-8fbd-4223-9396-86d7497bb275 Restrictions. This operation has been cancelled due to to restrictions in effect on this computer.Please contact your system administrator. - Microsoft Community]

  • Windows Deployment Services "the specified image file is either invalid or corrupted"

    I'm trying to add images to a virtual server running WS08 R2 but the only type of images that get accepted are the vista x86, nothing else works,
    I tried the following image files:
    windows server 2008 R2
    windows server 2008 x64
    windows 7 x64
    windows 7 x86
    windows vista x64
    and always the same error: "the specified image file is either invalid or corrupted"
    the machine configuration is as follows:
    Virtual machine on Hyper-V 2 (host is WS08 R2 Enterprise)
    2048 MB RAM
    25 GB free diskspace
    running these roles:
    AD
    DNS
    DHCP
    WDS
    hope someone can help

    Was a solution for this ever found?  I am experiencing the same issue with the following setup:
    I am having an issue with a virtualized Windows Server 2008 R2 Enterprise blue-screening any time I try and add an install image through the Windows Deployment Services mode.
    Server:
    Lenovo TD200x – 3822-43U
    Dual Intel Xeon E5530 CPU’s                                                                                                                                                                                               
    Installed Memory: 28.0 GB
    Two raid arrays.
                    Array 1 – 500 GB Mirror – hosting Windows 2008
    R2 Enterprise running Hyper-V
                    Array 2 – 1 TB RAID 10 – hosting Virtual Machines
    and Virtual Hard Disks
    We have the latest firmware update installed on this physical machine
    Our physical server is the Lenovo TD200x machine.  On it, we are running Windows Server 2008 R2 Enterprise
    Within Hyper-V, I am running a Windows Server 2008 R2 Enterprise domain.
    Virtual Server 1 is a domain controller running Windows Server 2008 R2.  It is configured with roles of: Active Directory Domain Services, DNS,
    and DHCP.
    Virtual Server 2 is a member server running Windows Server 2008 R2.  It is configured with the role of: Windows Deployment Services.
    The error is occurring on Virtual Server 2.  After everything is installed on this server, and it is setup as a domain member and has the Windows
    Deployment services role added, I go through and ad a Windows 7 boot image within Windows Deployment Services with no problem.  When I go through and try to add a Windows 7 install image, however, during the creation of that install image, the Virtual
    Server 2 pops up an error that reads:
    Error occurred while trying to execute command.
    Error Code: 0x80070002
    After this, the system will immediately blue-screen and reboot with a STOP 0x000000F4 Error
    I have tried using various Windows 7 DVD’s and even using the Windows 7 ISO file, mounting it as a drive.  All with the same results. 
    I have erased the virtual server and recreated it with the same results.  I have removed the entire domain and recreated both servers with the same results.
    I have setup the physical box as a Windows Server 2008 R2 domain controller and added the Windows Deployment Services role and did NOT have any problems
    going about it in that manner.  Therefore, the issue lies within running this in a Virtualized server within Hyper-V.

  • Windows Deployment Services will not start

    After advertising a image to my remote client computer I receive this error:
    PXE-T01: the specified file was not found
    PXE-E3B: TFTP error - file not found
    PXE-M0F: Exiting Broadcom PXE ROM
    I logged into the server and noticed the "windows deployment service" is not running. I tried to start the service and it failed to start. I then checked the "Site System Status" log and noticed there was a "Critical" message for the PXE service point role,
    and a "warning" message for the management point role.
    On 8/16/10 for the PXE service point role I see this critical error: PXE Control Manager detected PXE service point is not responding to pxe requests. The error is 16389. Possible cause: pxe service point is not started or not responding.
    I would greatly appreciate any assistance.
    Thank you

    Thank you everyone for your patience and assistance. I have resolved the issue after double, and tripple checking everything. The problem was that the boot images (x64, and x86) were not pointed to SMSPXEIMAGES$ distribution which is the server share. I
    pointed it to the Server only. After pointing to both the share, and the server all works fine.
    So the initial issue with the deployment service not starting was to uninstall WDS, and the PXE option in SCCM. During the troubleshooting I accidently deleted the SMSPXEIMAGES$ distribution point from the boot image which caused another issue after resolving
    the windows deployment problem.
    Hope this helps the next person that has this issue.
    The solution exists already in the link that I gave you, see the point N°5 :)
    http://blogs.technet.com/b/smsandmom/archive/2008/09/17/configmgr-2007-troubleshooting-pxe-service-point-issues-and-wds-service-not-starting.aspx

  • Can't start "Windows Deployment Services" Service

    I have a Windows 2003 Server that has WDS SP1 installed.  The Windows
    Deployment Services Server Service isn't started and when I try to
    start it I get a message that says:
    Windows could not start the Widows Deployment Services Server on Local
    Computer.  For more information, review the System Event Log.  If this
    is a non-Microsoft service, contact the service vendor, and refer to
    server-specific error code 2310.
    Event viewer lists Event ID 257 and this:
    An error occurred while trying to start the Windows Deployment Services
    server.
     Error Information: 0x906
      When I go to the actual WDS application, my server isn't listed.  If
    I try and add it, I get a message that says "The Windows Deployment
    Services configuration is corrupt.  Would you like to add it anyway?"
    If I say yes, the server is added, but it has a red x through it.
    I thought about removing WDS and then re-installing it, but it listed a
    number of programs that might fail if I did that.
    What should I do?

    Thanks, my problem was exactly that:
    ..................The error you are receiving generally indicates that you have a networking configuration problem on your server that
    is causing the domain to be unreachable...............
    They exchanged the Firewall and forgot to unlock the doors. After review and release back to work.
    Thank you.________________
    Moura

  • Make WDS Service account approve pending devices in WINDOWS DEPLOYMENT SERVICES

    Hi Technet and all other people reading this.
    I am at the moment trying to get a Service account(WDSService) to approve pending devices in Windoes Deployment Services on a WDS server.
    I have created a domain called LALALA.dk on a server(DNS is included in the domain), and installed windows deployment services on another server. The Deployment service is setup to prestage devices, and therefore devices needs to be approved before it can
    be deployed.
    My problem is that at the moment, we are using Domain Admin accounts to do the approving and i wish to change that to a service account, made specially for this job which ofc. should have minimum right. Because i have a very hard time understanding
    why i NEED to grant domain admin rights or local admin rights to a person just so that he can approve pending devices. There has to be a way to use a service account to do the job.
    I have done some research and found out that local admin, domain admins and enterprise admins are the only onces that have the permission to approve pending devices, and that a problem for me, when i want a service account to do it for me(Not automatically)
    but a service account that can name and approve devices manually.
    Here is what i have allready tried.
    1. making WDSService run the Windows Deployment Services (service), but this didnt work because it lacks the permissions needed.
    2. I have given the read+write permissions on the remoteinstall folder, even tried with full control.
    3. Delegate control on the OU in active directory, to create computer object, with full write permissions. I also tried with full control. I added both WDSServer$ and the service account(WDSService) on the OU. Still nothing.
    4. I then downloaded subinacl tool, and granted WDSService account permission to start, stop the service, even tried with full control on the Windows Deployment Service(WDSServer as server_name). I get error 1297 something with priviledge missing from the
    service account to perform the actions. So still nothing. Which is really weird when i ran a command i cant remember now, where i could see that the service account had full permission granted to the service, and still was'nt able to start the service.
    5. I then tried to create a script using WDSUTIL, but was not able to grant the service account permissions to perform the action of approving pending devices. And i dont want to use a script everytime i need to approve a device.
    6. Since the local system account is running the Windows Deployment Service , my thought was to join the WDSService account to the built-in NT AUTHORITY/local system or NT AUTHORITY/local service, this seems impossible from what i experienced, unless you
    are super powershell geek i quess you can, so this option didnt get me anywhere as well.
    6. I then created a gpo granting wdsservice account the "log on as a service" policy on the Windows deployment service Server, still nothing works as attended. I still get error 1297.
    7.I tried copying the registry keys (WDSSERVER) from the HKEY_LOCAL_MACHINE hive on the WDS Server, and imported it into my Domain's registry, but could'nt find the service i wanted to grant permissions to in the group policy settings (computer configuration/policies/windows
    settings/security settings/System Services) I then created a registry entry with group policy (computer configuration/policies/windows settings/security settings/registry) to point to (local machine/system/controlset001/services/WDSServer) and granting
    WDSService account full control and deployed the policy to the Deployment server. Nothing happend and i still cant approve pending devices with my service account.
    from my understanding service account where created to maintain small certain tasks or actions with limited permissions, so if comprimised they could only do very little damage, and so that this account can be setup to perform the tasks without any administation
    of the account. So my question is, is it even possible to achieve what i want = granting a service account the permission to perform the action of approving pending devices on a Windows Deployment Server, and if so how ? 
    I am so confused over this and I am really reaching the limits of my understanding of this.
    Help is very much appreciated.
    Henrik Larsen

    Hi ZeR1X,
    The Require Administrator approval is for unknown computers.
    The similar thread:
    WDS - Request administrator approval not working
    https://social.technet.microsoft.com/Forums/windowsserver/en-US/b9088be7-7afe-4e2b-b5fb-4554a92c4a2a/wds-request-administrator-approval-not-working
    More information:
    Windows Deployment Service fails to start with error information of 0x5
    http://support.microsoft.com/kb/2009647
    WDS 3.01 Troubleshooting Guide
    http://technet.microsoft.com/en-us/library/cc754828(v=ws.10).aspx
    I’m glad to be of help to you!
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • Windows Deployment Service Failed to Start

    Hi,
    I am trying to test the deplyment of Windows Vista RC1 using Windows Deployment Services (WDS). I have Installed WDS using WAIK on Windows Server 2003 Sp1. Installation completed Successfully, however i am not able to start the service of WDS. Following errors are logged in event logs:
    Event ID: 257 Source: WDSServer
    Description: An error occurred while trying to start the Windows Deployment Services server. Error Information: 0x54B
    Event ID: 513 Source: WDSServer
    Description: An error occurred while trying to initialize provider BINLSVC from C:\WINDOWS\system32\binlsvc.dll. Windows Deployment Services server will be shutdown.Error Information: 0x54B
    Any help would be greatly appreciated.
    Thanks in advance....
    Vineet Arora

    I am having a similar issue with WDS.  Here is how my server is configured:
    1. The server was initially a RIS Server, it was confiured with Windows Server 2003 SP1.
    2. RIS was then removed, and Server 2003 SP2 was installed.
    3. I then installed WDS (Obviously native mode now)
    4. Configured the WDS Settings for PXE etc.
    5. The WDS Server Service however just refuses to start, these are the messages in the Event viewer:
    Application:
    Source:WDSServer
    Category: WDSServer
    Type: Error
    Event ID:257
    An error occurred while trying to start the Windows Deployment Services server.
    Error Information: 0x32
    System:
    Source: Service Control Manager
    Category: None
    Type: Error
    Event ID:7024
    The Windows Deployment Services (WDS) Server service terminated with service-specific error 50 (0x32).
    Any ideas?
    Laila*

  • "An error occurred when communicating with the server. Check connectivity with your administrator to determine whether further action is necessary", then attempt to approve TimeSheet.

    Kind day, colleague.
    It was required to organize a statement chain for TimeSheet of employees, as we realized. Everything is good, but at linear managers in PSW opportunity to execute Approve when viewing TimeSheet of the employee remained, and in attempt to approve TimeSheet there
    is a mistake.
    500 Internal Server Error
    "An error occurred when communicating with the server.  Check connectivity with your administrator to determine whether further action is necessary. "
    Accept, is carried out as it is necessary.
    It is a bug or we not correctly realized approval chain?

     issue is  related to the user booking time against a task that was past the finish/end date listed in the Project Schedule.
    To resolve the user needs to submit their time on a valid task that is still within the current reporting timeframe, or have the Project Manager
    update the task in questions so that the finish/end dates are at or beyond the submission period and then republish the project. After that, the user should be able to go in and submit their timesheet with success.
    http://patrickdrews.com/2012/09/project-server-2010-timesheet-submission-produces-an-error-occurred-while-communicating-with-the-server/
    kirtesh

  • Windows Deployment Services Unable to PXE boot clients PXE-E53: No Boot Filename Received

    Hi
    I'm trying to configure WDS/MDT to deploy Windows 8.1. I've captured an image and I'm ready to deploy the image to a workstation, as per the above title when I attempt to PXE boot a test workstation it just times out with the following error message PXE-E52:No
    Boot Filename Recieved. I've tried a few tweaks to get it working however no such luck.
    The setup is as follows it's a virtual Windows 2012 R2 machine, just a fresh member server with microsoft deployment toolkit installed and WDS role installed with the nesscary framework features installed.
    I've tried tweaking the properties of most of the settings within the server settings in WDS with no such luck.
    I'm a novice at WDS but from what I've read I shouldn't need configure that much in the first place to get it working.
    I'm willing to bet it will be something I've overlooked so I need a 2nd opinon, could anyone provide any troubleshooting tips. If you require anymore information please let me know.
    Cheers   

    Hi Joel,
    This error may caused by the WDS server is not pushing the images because PXE Clients are not able to download or communicate with the TFTP server.
    The image can’t be download generally caused by the the Vlan is not enabled IP helper/DHCP relay agent configured on it, all DHCP broadcasts on UDP port 67 by client computers
    should be forwarded directly to both the DHCP server and the Windows Deployment Services PXE server.
    The related KB:
    PXE clients computers do not start when you configure the Dynamic Host Configuration Protocol server to use options 60, 66, 67
    http://support.microsoft.com/kb/259670
    The similar thread:
    PXE-E53: No boot filename received
    http://social.technet.microsoft.com/Forums/systemcenter/en-US/8de3bd6a-f8ec-41d9-ae0f-5b2fdb9e5831/pxee53-no-boot-filename-recieved?forum=configmgrosd
    WDSServer (Windows Deployment Server) Fails to Start
    http://social.microsoft.com/Forums/en-US/d96b0b86-f2b0-49a5-8946-19ab515f23e6/wdsserver-windows-deployment-server-fails-to-start?forum=windowshpcitpros
    I’m glad to be of help to you!
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

Maybe you are looking for