1

Hi.

I have physical server with 2 Hyper-V on it.

On first, I have DHCP, DNS and of course Domain Controller. Everything is working fine.

on second one I installed WDS, I made some boot images but then a problem ocurred. I can;t start the service, because of: The service did not respond to the start or control request in a timely fashion. And it gives an error: 0xFFFFFE0B (but every single driver is fine).

The WDS machine is of course connected into domain and has a static IP (from same vlan as DC, it’s 10.10.0.1 for DC and 10.10.0.2 for WDS).

I tried check/uncheck that listening at port 60 but no results.

An ideas?

Aha, I’m trying at local administrator, if it’s important, somehow.

Best regards.

2 Spice ups
2

Are you seeing anything in the event log aside from that?

Have you tried clearing all of the drivers and starting the service?

3

Hi,
firstly I got 0x906 error, but i uninitialized and re-initialized WDS from command promopt.

Now anything beside 0xFFFFFE0B I don’t see. I tried restarts etc. but nothing helps.

Maybe that would be tip: At the beginning when I installed WDS for the first time and configured it everything works, but when i added install.wim and boot.wim I think it stopped, or maybe after restart? I’m not sure.

I had few problems with capturing image cause of "File invalid" but at the end I added it, I hope - correctly.

May it have a connection? Maybe adding those files has broken my WDS?

Regards

//I’ve tried now on a domain admin account with ful rights but same result ;/

4

Hmm I think one time I had to login as local admin and just install the role and restart. Then I logged in as a domain admin (or a someone in the local admin group) and then configured the server in order for the service to start. Weird for sure.

5

Verify that DHCP has the correct options enabled for your scope, 60, 66 and 67.

Check the DHCP tab in WDS properties, make sure that you have unchecked the “do not listen on port 67”.

Using a command- wdsutil /set-Server /UseDhcpPorts:No

Restart the WDS service and try again.

If that doesnt work, uninstall WDS reboot and reinstall it.

6

i have no 60 option at my DHCP scope, i dont know why

7

Some fresh info. I reinstalled the WDS role, and

If I configure it (set few options without adding any *.wim neither captuing images) everything is working, well, not working because it’s empty, but I have the green arrow status, and if I restart the WDS server it’s not showing any errors, the service starts normally.

BUT

if I just add some boot.wim I have that error and service can’t start. Might that happen because of that file? Or I have to set up whole WDS to start the server?

I thought that the WDS server should be green and work all the time, even if I would set it not correctly, so fresh PC couldn’t boot from network but WDS server would work with green arrow icon.

Regards

I hope you can understand what I wanted to tell you. :slight_smile:

8

Have you checked the windows System or Application log to see what errors are recorded in regards to your error? That may shed some light on the subject.

9

I fixed it today.

That’s what I’ve done.

As I said, on my physical server I have 2 Hyper-V

First is a Domain Controller 1, and its installed also on physical HDD (form the server)

the second VM is for WDS, and it’s vhdx is on QNAP, connected by iSCSI.

When I tried from WDS machine capture some images and save them also on QNAP connected by iSCSI I got service faults, but today I tried save images on it’s disk and it worked.

Anyway it’s still on QNAP, but I don’t have access to those images from other machines (and I don’t need to), so I’m glad that it’s working.

Sorry for my explanation, I have literally no idea how to explain it properly + my english isn`t that good.

Thanks for everyone for answers :slight_smile: