WDS Not working after rebooting the server

[Uber22]

Hey

 

i have just come to use my wds server and i am getting the below error message when booting into lite image, the only thing i can think of is that the server has been rebooted after updates.

 

[bald_pig]

That's usually a driver issue, with the image missing a driver that's required.

[IrritableTech]

Had a similar issue earlier this week at another school. Windows update caused an issue with the tftp server.

 

In WDS right click and choose properties of your WDS server. Choose the TFTP tab and untick Enable variable Windows Extension. Might work for you.

[Uber22]

yes got the image to load but now its coming up with cant connect to deployment shares :/ bloody windows updates

[houlta]

If you have a look here-

http://www.edugeek.net/forums/o-s-deployment/205678-issue-windows-deployment-services-0xc0000001.html

 

It was due to an update a short while ago, however further updates should fix it, so perhaps check for further updates on the server first?

[Uber22]

i seem to be getting this error now, i know the creds are correct because i can connect to the drive in cmd .

[sted]

stupid as it sounds try another pc. ive had that in the past and ive had to diskpart the affected pc to get it to boot into mdt

[Uber22]

Hi, tested on 4 different machines all the same

[sted]

theres a keyboard command for bringing up cmd in a wds boot. its something like shift ctrl f8 (its some combination like that) try that and running ip config my next guess is that you dont have network drivers for that pcs nic in your boot image

[Uber22]

hi, yes i have an ip and i can connect to the wds via the command

[bald_pig]

1) restart the server again?

2) check that the deployment share hasn't reset in the settings, try changing it to something else, applying the change, then changing it back again.

[Uber22]

so here is some development. i rebooted the sever last night and changed something then i regenerated the image. i will now load the boot strap but then comes up with the error again see below

[houlta]

I would try regenerating new boot images using the update deployment share wizard and then replace your boot images with the new ones.

Thats assuming your customsettings.ini and bootstrap.ini have the correct password in them.

[Uber22]

still havent got anywhere with this, see below my bootstrap settings

 

[settings]Priority=DefaultProperties=MyCustomProperty[Default]OSInstall=YSkipCapture=YESSkipAdminPassword=YESSkipProductKey=YESSkipComputerBackup=YESSkipBitLocker=YES

 

 

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

[settings]Priority=Default[Default]DeployRoot=\\whirlpool\DeploymentShare$UserDomain=mydomainnameUserID=domainname\adminUserPassword=XXXXXXXXXSkipBDDWelcome=YesKeyboardLocale=en-UK

[fordea]

I noticed in your screenshots with the errors that the deployment share server name is different each time. One is \\WSUS\DeploymentShare$ and the other is \\WHIRLPOOL\DeploymentShare$. Do you have two different WDS servers or are these just two A records for the same server? Also, are you using the administrator approval option in WDS and if so are the devices you are testing it with listed under 'Active Directory Prestaged Devices'? I've had instances in the past where I've had to remove them from this list and re-do the administrator approval for them.

[Uber22]

hi there is nothing in the active directory prestaged, the first screen shot was just one off google as i had no phone battery but the name is correct. i might end up doing a rebuild but its a busy time to be doing this

[fordea]

Do the affected computers have a _SMSTaskSequence folder in the C: drive? Sometimes this folder gets left behind if a previous task sequence doesn't complete fully. I think that there could be some files in there that may be causing the issue. One of the previous comments suggested using diskpart to clean the disk which could work. You can get a CMD window up to use diskpart if you press F8 just as the machine is booting into the MDT image.

[Uber22]

sorry i just used a image off google for the picture my server name is correct whirlpool, so the strange thing is that the boot.ini loading screen starts and get to the end of the loading then errors out.

 

- - - Updated - - -

 

The pcs are brand new no os on them.

[fordea]

Have you double checked the NTFS/Share permissions on the DeploymentShare folder? Perhaps the update has changed these for some reason. I believe the service account that you've specified in the bootstrap.ini file needs at least read permissions on the folder

[Uber22]

so in server manager/shares the permissions are full but when checking the folder there are no permissions set see below

 

[fordea]

I can only see the share permissions from your screenshot but if as you say the folder permissions are empty then that's probably whats causing the issue. Make sure your service account specified in the bootstrap.ini has at minimum NTFS read permissions on the DeploymentShare folder

[Uber22]

So I have fixed it

[Uber22]

so after all that i think it was the boot.ini settings. the only differences is that i put a space after the password

 

 

[settings]Priority=Default [Default]DeployRoot=\DomainUserID=XXXXXUserPassword= XXXXXXXX SkipBDDWelcome=YES

 

but i have only tested with domain admin account i need to setup an account with the correct permissions