Search the Community

Hi Guys, When we image PC's, 90% of them are fine but the other 10% come up with this error: I have removed all unattend answer files from the image, but it still comes up with the same error. The machines are identical in terms of hardware and software. Any ideas as it means I have a stack of PC's that refuse to build. I have tried swapping HDD's which used to fix some of them but not anymore. Many thanks

It's been a while since I captured an image and the one I am currently trying to is taking a long time to run through and then comes up with an error "Uploading image to WDS server... There is not enough space on the disk". Most of the info I have found states that there is not enough disk space, but my WDS server has over 500Gb free so I cannot see the issue. Is there something I am missing or a check I can complete?

I am building images for Vista Business and 7 Professional that are bare bones for us to sell to employees. What I am trying to get working is the Microsoft-Windows-Setup, Restart property. When I try changing it to Shutdown and trying imaging, it just goes through and restarts a few times as normal. According to the instructions from Microsoft, it is supposed to shut down after the imaging has completed... Has anyone ever got this working as I want it to act like a Factory Restore so a person buys the pc turns it on and it starts at the welcome screen to ask all the questions... Thanks for any help.

I'm getting 0xC00000001 errors when PXE booting in to MDT on some machines across my estate. Seemingly random across devices with the same hardware as others that are fine. I've tried modifying the TFTP Maximum Block size to 1024 and 512 and have tried enabling and disabling Variable Window Extension, no change. kb4489899 is installed which I realise was where the issue started according to the notes. I'm unable to uninstall it, Windows Server 2019 won't give me the option to, even in safe mode. I've now installed kb4503327 which Microsoft say fixed the issue. It doesn't. Microsoft have recommended to apply kb4503327 and edit the BCD files that WDS uses. I have edited all the BCD files that exist in subfolders contained within E:\RemoteInstall\Boot to include: RamDiskTFTPWindowSize to 4 RamDiskTFTPBlockSize to 1024 I still get the same error on the same machines. Any ideas? I really don't want to nuke everything as the MDT Windows 10 task sequence and image is perfect.

I'm trying to create an answer file for WDS deployment using ADK and it fails at the point of building a catalog file with the error: This application requires version 10.0.22000.1 The version of ADK I have is 10.1.22000.1 I tried an earlier version from the MS download page and it was 10.1.19041.1 and have the error This application requires version 10.0.19041.1 I have the install.wim file imported from an iso for Windows 10 Pro build 19044 (i.e. 21H2 edition). Any ideas? I can't find the version it suggests other than on some random websites which doesn't sun like the ideal starting point for a new windows deployment.

I've finally decided to try to take the plunge to move our WDS implementation from legacy to UEFI. I've done some searching the web and have managed to edit my WDSUnattend.xml to look like this: Never en-gb en-gb en-gb en-gb en-gb domain.com Removed Removed 0 4 3 128 MSR 1 500 Primary 2 100 EFI true 4 Primary NTFS WinRE 1 1 DE94BBA4-06D1-4D40-A16A-BFD50179D6AC FAT32 System 2 2 3 3 NTFS Local Disk C 4 4 0 true OnError For reference, here is my Image unattend.xml: true %MACHINENAME% Multi Academy Trust School true GMT Standard Time XXXX Domain.com Removed Removed Domain.com en-gb en-gb en-gb en-gb true true true true true Work 1 true true Removed false Removed false Local Admin Account Admin Administrators LLT The build works fine and results in a Windows 10 image, with a UEFI BIOS. I have 2 issues, 1 more pressing and the other for when I can get the first issue sorted. Firstly, I cannot get the disk partitioning part of the Windows 10 setup to run unattended. Every time, on PXE boot, it will pop up with the prompt asking me how to partition the disk. Even with those where the disk is already partitioned correctly. Is there anyway I can automate it to install on partition 4 and format the partition before install, silently? Secondly, is there a way I can automate this entire process for when I am moving from a legacy BIOS to UEFI. Currently, I have to manually go into the WinPE, run disk part, clean the disk and then run the PXE setup, once the BIOS has been changed to UEFI. Can I automate this entire process (Obviously, I will still need to change the BIOS manually from legacy to UEFI).

Hi all Deploying Windows 10 1703 using WDS and after the Network Selection screen where cortana speaks to you I am left with a black screen and the cursor. There is HDD activity but nothing seems to happen. Powering the machine off and back on allows the installation to complete/continue. Does anyone have any ideas what the cause could be? This is my Unattend File that is attached to the image with all identifying ifno removed/hidden 1 1 net user administrator /active:yes true (UTC +00:00) Dublin, Edinburgh, Lisbon, London en-gb en-gb en-gb en-gb en-gb en-gb en-gb en-gb true 1 administrator true 1 true true true HIDDEN false HIDDEN false Local Administrators Account Administrator Administrators Administrator HIDDEN false Local Account LOCAL ACCOUNT LOCAL ACCOUNT Administrators COMPANY COMPANY (UTC) Dublin, Edinburgh, Lisbon, London en-gb en-gb en-gb en-gb en-gb Cheers for looking

Hi all, Not much really gets me like this one does but I'm stumped!! I have a right mixed bag of equipment here that I'm moving all over to Windows 8.1 64 bit from the mixed XP/Vista and 7 32bit environment. I'm using WDS on Server 2012 R2 to help me with this, creating an image for each type of machine with all of the correct drivers preloaded into the image. Some of my older kit (Fujitsu Esprimo Desktops, Lenovo ThinkPad 15 Laptops) don't have an EFI BIOS so the install is a standard BIOS 2 partition boot to hard disk install. I name and approve clients, they install no problem and name themselves and join to the domain, so I'm left with a machine that is left that the logon screen ready for my to deploy software via GPO. The newer HP ProBooks and Dell Optiplexs here are EFI compatible, so I've switched the BIOS from legacy to EFI mode and they are working beautifully. I had to write a new WDS-Unattend to deal with the new EFI partition structure but that is all working beautifully. I still name and approve these clients in the same way and they install no problem, but prompt me for a computer name and are not joined to the domain - REALLY ANNOYING! Can anyone shed any light on this? Thanks, David.

As of right now, optional programs during deployment include Microsoft Office 2013, Microsoft Visio 2013 and the Adobe Creative Suite, all of which are fairly sizable installs (especially the creative suite).. I want these programs to be installed as part of the image since they're so significant in size and install time, however if I check all 3, the machine ends up going to sleep mid-install and as such, ends up stuck. Any way to prevent this? The machine is already part of the domain at this stage, so I could look into GPO/GPP, but I wouldn't want the machines to not go to sleep in-general, only during deployment. I want them to have power saving as normal once they're fully imaged/configured. Anyone got a method for this?

Hi all, We have few new Dell's on our site, I have added successfully network, fall sensor drivers to WDS and they deploy fine and are installed after re-image job. I have also decided to update the Intel HD graphic drivers on WDS server (as the previous person left igfxtray.exe + 2 other apps to startup with machines). But new graphic drivers don't install at all, I can do it manually afterwards forcing the unsigned driver to be installed. Also tried drivers from Dell website and 2 different versions from Intel website. Are unsigned drivers an issue or am I missing something else? Being me, instead of disabling the old drivers I have delete them from WDS, so can't go back - as I thought new ones will pick up with no problems. Srv 2008 R2, deploying to W7 x86 machines. Thanks Karol

I've used Windows System Image Manager to generate the XML file below. The issue is that only certain parts of the file seem to be being read, i.e. it will enable the local administrators account but then will not set the password. It is also not managing to join the machine to the domain. If anyone has any ideas whatsoever I'ld really appreciate it. For two days I've been banging my head against the wall now! Thanks, Ed. en-GB en-GB en-GB en-GB en-GB OnError true true Work true true 1 IT Services Authorised User OnError Enable Local Administrator Account 1 cmd /c net user Administrator /active:yes OnError mydomainname.local true OnError %COMPUTERNAME% OnError mysecurepassword false OnError

Hello, I have WDS setup and running on 2008 enterprise 32bit to deploy XP images. The system is working well with my unattend.xml/sysprep.inf and I can deploy captured images with a couple of key presses. Now I need to prestage multiple computers and associate them with their xml file. I use wdsutil to acheive this on my test machine; To prestage using MAC address WDSUtil /Add-Device /Device:computername /ID:00-20-ED-88-15-7B To associate my unattend xml WDSUtil /Set-Device /Device:computername /WDSClientUnattend:WDSClientUnattend\unattendhere.xml That works beautifully for my one test machine, but typing that for every machine in the school is going to be a bit of a bind. We have a list of all the MAC addresses so I just need a more automated way to prestage computers & associcate the XML. Is this the best way to do this? Should I be doing this another way? I have gone so far with WDS and spent a long time getting to grips with it, it will not beat me:confused: Any help greatly appreciated Pete

Hi, I have a problem with my deployment share with Windows Deployment Services on a Windows Server 2008 SP1. This is my "customsettings.ini" [settings] Priority=Default Properties=MyCustomProperty [Default] DeployRoot=\\srv-imagex\DeploymentShare SkipBDDWelcome=YES UserDomain=test.local UserID=install UserPassword=XXX OSInstall=YES UserDataLocation=NONE SkipAppsOnUpgrade=YES SkipCapture=YES SkipAdminPassword=YES SkipProductKey=YES SkipBDDWelcome=YES AdminPassword=XXX SkipDeploymentType=YES DeploymentType=NEWCOMPUTER SkipDomainMembership=YES SkipUserData=YES SkipBuild=NO SkipComputerName=NO ComputerName=TEST-COMPUTER SkipPackageDisplay=NO SkipLocaleSelection=YES UILanguage=en-US UserLocale=fr-CH KeyboardLocale=100c:0000100c SkipTimeZone=YES TimeZoneName=W. Europe Standard Time SkipApplications=NO SkipBitLocker=YES SkipSummary=YES And this is my "bootstrap.ini" [settings] Priority=Default [Default] DeployRoot=\\srv-imagex\DeploymentShare SkipBDDWelcome=YES UserDomain=test.local UserID=install UserPassword=XXX UserLocale=fr-CH KeyboardLocale=100c:0000100c But, when I boot with a new PC on the PXE, I have all time this screen : http://i43.tinypic.com/16ga2py.png But, in my customsettings and my bootstrap, I have give this settings no ? Why I don't see my deployment share I dont't understand. Can you help me ?

I'd set up a WDS test server and test workstations a few months ago and had everything working nicely, including unattend.xml and sysprep.inf configuration files. Last week, I set up a new server and grabbed some computers in need of a standard image. But now I can't get it working!! If I capture an image, I can redeploy it to the same box and reboot successfully to test the image, but If I deploy it to a different computer, as soon as it boots, I get a bluescreen. I think the problem is that I'm not using a standard hardware platform. In my initial testing, I used two identical computers. This time I built the image on an HP, then deployed it to a Dell, which failed. Then I grabbed two Dells, but they were different models. Finally, I found two Dim 170L's but when it failed on that too, I noticed the one 170L's motherboard had been replaced with an Asus instead of the standard Dell one. So, my long winded question is, how much wiggle room is there in deploying images across different models of computer hardware?

Hello all! Im probably going to catch some brown stuff for posting this but im at a loss with WDS really. Anyway, i have read microsofts supposed step by step guide on how to setup WDS, now i have it installed on a server, and i downloaded the AIK which supposedly had the install.wim and boot.wim files (it only had the boot.wim file). Few things im stuck on, do i _need_ to have the install.wim image or can i just create one? how do i actually create an image? i have installed the AIK on my laptop but i dont clearly see how to create an image. I have had a machine boot over the network using the boot.wim file but when it boots i just get a command prompt and nothing else I worked out how to do the sysprep stuff so on that point im ready to run the creation of the image but as ive said above im a bit stuck on where to go from there Im wanting to deploy windows xp over the network using WDS, i have 5 schools that could benefit from this especially if we had images ready to go =-) My apologies for being such a nub, havent had a LOT of time to research this properly and i thought id come ask the people in the know =-)

Our XP deployment image is showing some weird changes once it has been deployed. When I created the sysprep.inf file I made sure all keyboard settings were correct and that it all worked. Now when I deploy to a machine we are seeing that the keyboard mappings are different - that is the @ and " are swapped - we have American layout. Where else could this be changed? Gareth

Hullo, As we evaluate our image (again), I'm interested to know what people image. We have several GPO based MSI installations that I could use but I wonder sometimes whether I am better imaging them. When I build my base image I put on the following: Adobe Flash Player Adobe Air Adobe Authorware player ShockWave Player Reader 9 + Updates There is other stuff that could be sent out via GPO. Adobe CS3 is put on the image due to it being a git to install via GPO. But what about things like Office - we have 2003. It is ready to be deployed via GPO and when we were RIS based this is how it went on. However am I better putting it on the image? Will I be able to update it with Office 2007 over Easter without any issues? So just let me know what you guys put in your images. Everyone? Some things or nothing if it has an MSI. Cheers Gareth

I'm having trouble getting a Compaq 311 netbook to build from our WDS server i've got a feeling that it's a problem with the driver, i've tried all of the usual putting the driver in the right folder even copying it to i386 but it will not connect. This link doesn't look promising but it's old http://www.edugeek.net/forums/windows/5022-ris-asus-a7n266-vm-nforce-onboard-nic.html Can anyone suggest if this is possible with WDS legacy or am I going to have to try WinPE? Thanks.

So after working hard on WDS this week to get it up and running I'm rather chuffed that I've been able to put the time in to get things working. Advice on here has been great. I put all the drivers into the universal XP images and deployed to some test machines. All worked. We have two images - one with CS3 and one without. and then the fun starts...... I've discovered two machines that do not pick up a sound card driver. So using the tool I found the other day to mount and edit images can I just drop the drivers into the c:\driver folder I created? I've used a tool (cannot remember the name) to point the registry at c\drivers so can I assume that whever I drop in there will be picked up by the newly deployed machine? I'll try it tomorrow, but I just wondered if this was the case. Regards, and thanks everyone, Gareth

Might be useful to someone but this page explains how you can edit the registry in a .wim file. Off Campus : Edit the registry on a mounted WIM Gareth

Hey guys i've been having trouble with deploying xp from my server. Whenever i try to connect a machine to the deployer it comes up with something to do with cannot find IP address? Any ideas how to reslove this issue? this error appears once it had already started to load the deployment agent. Thankx Nathan

Hi Guys I have WDS installed on server 2003 and im having an issue with WDS. Its all setup, tested and functioning correctly however: I am trying to image some new netbooks the school purchased just before the holls. These are Eee PC 1001P's. They are the second batch of netbooks we have purchased in the last year. The first set were 1001HA's and imaged and deployed fine via WDS however the second set, whenever i try to capture the image after sysprep WDS reports "the parameter is incorrect" after about 5 seconds after i click next to begin the capture. Anyone have any clue why this error is coming up? THanks

Hi all, am trying to get my Windows 7 deployment sorted and after a week of trying with differnet answer file configs i've hit a brick wall so i'm after some help...answer file is below - can anyone see any major problems with it? i'm using mysysprep2 on it as i want it to ask for a computer name and to also require to input the product key seperatly. everything else i want to be unattened. Last time i used it (before i left today) i got an error with the specialize section and failed to run. Also - how can i set the answer file not to ask for my language? Cheers

Does anyone here store their WDS images on a seperate NAS box which is then mapped to the WDS server? My school will not let me purchase a new hard drive to upgrade the WDS server with more space, but I do have 1Tb NAS box lying around - mostly empty. Cannot remember why I purchased it. I seem to remember we were going to use it for Ghost images but in the end didn't go with Ghost. Now I know we can get the WDS server to look elsewhere for the images, but I wondered if anyone had done this and noticed any major speed decrease or had encountered any problems. Cheers GJE

Hi all, I am a long time lurker who has got a load of great info from this site which I have been able to use in the schools I support. I work for an LA as a technician who along with my team support over 120 schools in our county. I have been playing with deploying Windows 7 from a Server 2008 machine running WDS and MDT2010, I have been able to get the system set up and make changes to the default Windows 7 image which is deployed so that info is pre-filled instead of prompting the user. I have got a lot of experience with using RIS/WDS Legacy to deploy XP machines which is what we currently use in many of the schools our team support. We use PXE boot to call the standard ms osc screens which prompt for username and password, In each OU we want to add machines to, we will have a user which has rights to join a machine to the domain. RIS/WDS is set to respond to all machines and to create a computer account in the same OU as the user, this means when we log on with an authorised user we have the computer account automatically created in the correct place so any GPO is applied from the beginning, also it has the advantage that we dont have to prestage any machines in AD as the machine is created with the correct naming convention and incremented automatically (set by the username e.g. Class1 will give a computer name of Class1-01, Class1-02 etc) The actual install of Windows is achieved by a modified .sif file so we can log on to a new machine and walkaway safe in the knowledge that the machine will do the rest for us. Okay enough background babble, the actual issue I am having is in emulating the RIS way of doing things, we are not open to the idea of manually prestaging machines due to the fact that we have a lot of schools and would need to set it up in each location, also I will be writing the draft procedures for out team to use and want to keep it as simple as possible. I would love to be able to PXE boot the machine, be prompted for the username and password and be able to step away. My understanding is that in RIS the machine will check in AD if the GUID/UUID exists for a computer account and if not creates a new machine record populated with the ID in the correct location. My thinking is that I will need a script to run at the beginning of the task sequence which 1.Prompts for a username 2.Gets the GUID of the machine 3.Makes contact with the AD 4.Checks for the GUID 5(a).If there set the computername and OU settings to be used later, 5(b).If not then create the computer account in the correct place and pass the values for later use. I have looked over the internet and have so far not managed to find anything which achieves the results I need, I guess its because W7 and MDT2010 are both new. I was lucky to find MSFN's Unattended Windows : Unattended Windows Introduction when I wanted to do research for XP but havent been too lucky yet. Over to you guys, I am open to ideas/advice/fully formed scripts which do it for me. Sorry for the length of post but I thought I should give as much info as I could to get started. Thanks in advance Marc