Search the Community

Hi All I'm looking to upgrade our PC's from Windows 10 1803 to Windows 10 1909 using SCCM. This is the first time I've used it to deploy an OS as I've mainly been using it for Endpoint protection and App installations which is working well. I've got to a point where I've created a device collection and added a couple of test PC's in there and they seem to build without any issues but my question is how can I quickly rebuild a pc? I'm coming from using WDS, so it was a just a case of hitting F12 and initialising a network boot and selecting the image I want to install. The way i've sort of got round it is by creating a new Device Collection and deploying the Task sequence to that, and leaving SCCM to refresh the policy to instigate the rebuild. But if i have to rebuild the test pc again it wont as it can see that its sucessfully completed the install. Any advice would be greatly appreciated. Steve

We're trying to deploy our Windows 10 image use PXE boot, however within the last week or so we've begun getting error messages. We think it's traceable back to a power cut we had a couple of weeks ago over the weekend. Our Deployment server is 2012 R2 and we use the deployment workbench to set up the image. We get through the initial stages ok and begin the image deployment on the PC, but during the install we get an error, see attached picture. This process was set up by a recently left network manager and we're at a bit of a loss how to troubleshoot. We've tried finding the logs but have had little success, as we're not 100% where to look. So any advice, experience, ideas will gratefully received and if anyone's had the same issue in the past and can give a step by step guide how to fix, that's an added bonus, and we'll send lots of virtual chocolate as a thank you.

Hi Guys, I've setup WDS many times, this time is the first time I've ever set it up on a network with multiple VLANs and having WDS installed on it's own server, usually I've had it installed on the domain controller. I have it running, it works on multiple VLANs and I've used t to deploy multiple custom images to various Laptops and desktops. My images are x64 UEFI. I have a work bench setup solely for deploying images via WDS. So my Switch and switch port are exactly the same, there's been no network changes and i can still use WDS on other devices successfully. This one PC (Lenovo Thinkcentre Edge72) I've went through BIOS multiple times. I've disabled secure boot and changed the boot time to UEFI Only. I've checked all other settings and nothing else is relevant. I used to get something along the lines of "NBP File too large for memory" Now after fiddling I get "TFTP Error, access violation" I can't seem to get past this for this single machine. Any ideas other than grab a large hammer?

Hi all, I am trying to set up a trolley full of brand new laptops (HP 655) with Windows 7 (the were purchased with Windows 8 installed), and knew the easiest way for me would be to use WDS. This however is not the case as I am totally stuck! The operating system has been installed and updated, and all the necessary software and drivers have been installed. I have sysprep'd the machine ready for capturing the image and there is a capture file ready on the server. Now, when I network boot the computer, from what I have seen before, it should come up with "contacting the server..." etc and then eventually give you a list of either boot or capture files of which I need to select 'capture'... This doesnt happen! I'll hit F12 to Network Boot and it then displays a message "F12 for Network Service Boot", upon hitting F12 the 2nd time it boots straight into Windows 8 setup and following that into Windows Deployment Services to pick an image to boot into. So looks like it automatically selects the first option without giving the chance to change. Has anyone got any ideas of a solution ? I have changed the necessary BIOS settings to be able to network boot, ie. Legacy Support.

Hello, So, I've posted about this before however I'm still having problems with it. Basically, I have MDT set up through WDS for imaging machines. Practically every machine in the network will image with no issues aside from these 'ERGO AS1' machines This is what appears on screen; Intel UNDI, PXE-2.1 (build 082) Copyright (C) 1997-200 Intel Corporation For Realtek RTL8111B/8111C Gigabit Ethernet Controller v2.10 (071105( CLIENT MAC ADDR: 00 90 F5 8C 21 E6 GUID: FFFFFFFF-0C0C-0000-0000-000000000000 PXE-E51: No DHCP or proxyDHCP offers were received. PXE-M0F: Exiting PXE ROM. Why is this? Is there an easy fix? I have to image an entire suite like this and they all have the same issue, if I can't get it to work, I'll have to use the Windows 7 disc! Please help!

Hello! I've been trying to use WDS to capture an image of Windows 7 I have made in Virtual Box on a seperate PC to the server. WDS isn't working because I foolishly only set the Virtual disk to 25Gb. The reason it is a problem, is WDS wants me to save the image to the D: drive before uploading to the WDS server via LAN. I need to know how to do a couple of things to make it work. a) How do I create a virtual drive so that the boot screen picks it up in the virtual machine? Is this possible? I could then save the image to this before it uploads. I just need some extra drive space to do this. b) Is it possible to capture the image from the virtual machine a different way using a different kind of image capture software and then add it to our WDS server for deployment? c) Can I make the virtual disk bigger POST install of Win7, apps etc... or is it set once it's been created in Virtual Box? I hope all this makes sense! Cheers

Hi Guys, I have recently updated the CC4 network too "CC4UPD133" with "CC4DRV087" for the new laptops we have just purchased "Toshiba Satellite Pro R50-B-12U" and when I come to use the name image I get a message on the new laptops saying "RMR: A disk read error occurred Press Ctrl+Alt+Del to restart" has anyone else come across this issue with these laptops? and if so does anyone have a fix?

(I have posted the below under "Enterprise Software" as well - sorry if this is bad practice but the below is relevant in both!) Hello everyone, We currently are having issues with multicasting. We have SCCM 2012 installed and are imaging computers. Our problem is that when multicasting it takes ages to open a session and to download the image WIM file. Also, when PXE booting the computers once we have about 10 computers imaging it takes ages to contact DHCP for an IP address. Also, it will struggle to obtain an IP address when the computer has booted into WinPE - by struggle I mean it sometimes does not get an IP address before it times out and bombs out!. If we keep retrying it will eventually work - imaging is still very slow. When we open Task Manager whilst the computer is downloading the image the network utilisation does not get anywhere above 1.50%!!! Our network consists of Netgear GS724TP and GSM7224 switches. We have a GSM7224 switch as our core switch in the server room. We also have a couple of HP Procurve switches in the server rack that are part of our high availability server virtualisation setup. Our network is flat - no vLANs. All switch links are connected at 1GB. We have checked the switches to the best of our knowledge and they all have IGMP enabled and spanning tree is set to RSTP. I hope the above makes sense - we can only think that the issue is down to some settings on the switches. Thanks in advance! J.Worth.

Hi all, Having a problem getting MDT2010 to find the wireless driver for the Lenovo G550 Laptop. Iv downloaded every driver from the Lenovo site, extracted and included them in the out of box drivers. Iv also got a small add on program that searches the drivers after installation to try and find some it may have missed and it still does not work. I wonder if anyone has got any ideas? or has experienced the same problem. Thanks.

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?

We are currently in the proccess of testing W7 deployment from an XP network for completion over the summer. W7 is great, all working fine, I can sysprep it all and the image's pull's back etc, deployment is also great, much better than ghost. It puts the pc on the doamin and we even got windows and office 2010 to activate automatcily! The only issue im having is naming them on the domain, first I tried having a promt for the name but that broke the trust relationship! I currently have it set to %computername% in the unattend which give's the comptuer the name of account + Number (administartor12 etc). Is ok but means i have to rename them and sometimes if I do an IT suite it gets confused and names 2 the same and then one loose the trust relationship, so we have to remainge a couple! What i really really want is for me to deploy W7 and it take the name of the XP machine! Am i doing something wrong becasuse it seems the same as prestaging to me! Is it possible or is there a better way for me to do this? As its going to give me headache over the summer if not!

Hi Folks, Quick query, hoping someone with experience or knowledge of the current situation could lend a hand/advice with a new setup. One x large building, measuring roughly 30x80m. We are soon to install a wireless system, and to ensure no loss of signal anywhere in the building will be running 4 x WDS enabled wireless access points centrally placed on back wall with high-gain directional antennae (2x per AP) running in series down the back wall point toward the front. My understanding of WDS is limited, all I know is the AP's need to run in Repeater mode rather than Bridging as bridging turns the AP off to client connections and rather acts as a signal repeater. So Repeater mode would need to be enabled. Now the query: 1) When Repeater mode is enabled, do the access points act alone regarding connections and routing, (If a laptop/device is connected via AP2, does AP2 route traffic to and from servers, or does it use a central Access point for all routing?) 2) If a laptop/device is connected via AP1, and moves over to AP4 (AP's support Fast Roam switching) does AP4 with Repeater mode route the signal via server or does it repeat the signal across say AP4 > AP2 > AP1 > Servers and than back again via that route? Cheers for any answers.

Here's the scenario... newly built Server 2003 x64 server with a fresh install of WDS. I need to set this up in mixed mode for the time being so I go to the legacy mode tool to do the initial config. Here's the problem... the server asks for the XP disc which I duly give it and then it decides it wants the Server 2003 x64 installation disc. I put that in and it says it wants a 'win51is' file. This file does not exist and any of my Server installation discs and is nowhere within my Server installation folder. HELP!

Hi, I am just starting planning a new Windows 11 image and start deployment from windows 10. Please can you give me recommendations for the following please? Currently using WDS version 10.0.17763.1 and MDT Windows 11 version education version ect? Microsoft Office version 2024? And any other settings you would recommend? removing apps etc. Thanks in advance

Hi All, Hopefully this is in the right place and someone can offer some assistance for me. I will try to lay this out correctly (newbie on this forum). Have installed WDS on Server 2012 R2. Settings altered... Setup my server as standard, nothing special. Created boot.wim from a copy of a Dell Win 7 disk, copied locally and imported. Created capture image. Imported numerous drivers (which were installed manually and worked on the client (testing client)). Settings changed on the WDS server (it is called ntserver29 for reference). - PXE Response - Respond to all clients...(require administrator approval not ticked) - AD DS - Computer Account Location - Same Domain as WDS server - Boot - as default, require user to press f12. - Client - Joining a Domain - Do not join...ticked. - DHCP - Neither 'do not listen' and 'configure dhcp options' ticked. (DHCP not installed on that server) - TFTP - block size (as default) set to 1298 (have changed the registry file from 0 to 512 as previously instructed on an online guide). Enable the TFTP server to negotiate variable window size requests is ticked. - Network - UDP port policy is set to 'obtain dynamic ports' - Advanced - Domain Controller - Allow WDS to dynamically discover domain servers (ticked). DHCP Authorisation - Authorize this WDS server in DHCP - Multicast - Multicast IP set to obtain IP from DHCP. Transfer Settings set to Keey all multicase clients in a session at the same speed. From the top. Have had issues which seem resolved, will explain further down. * With the above set. Have built Dell desktop machine with Dell windows 7 disc flat. Installed relevant drivers, some updates and google chrome. * Using sysprep and the capture image got as far as saving the wim. Was unable to authenticate to the server as it did not even bring up the account login box, just failed to connect (ISSUE 1). * Chose to test WDS seperate. Copied the image to an external drive. Copied to the RemoteInstall\Images path on the WDS server. This populate the image to the server without involvement from myself. Restarted the server. * When rebooting the desktop, device only shows Windows 7 Setup and Windows 7 Setup Capture (my 2 original boot images) and nothing else (ISSUE 2). Bit stuck from there. WDS didnt work prior to uninstalling a specific update and re-installing a fresh WDS. Any advice would be GREATLY appreciated. I dont lay claim to being knowledgeable about the system, just looking to learn and get this working for the business. Happy to answer questions and will keep checking in. Little more info...(may be irrlevant)... Obtained the details from CMD. Unattend file present: No Status: Enabled ******************************************************************************* -------------------- Boot Images for ia64 -------------------- Image count: 0 ------------------ Image Information: ------------------ There are no images that match the specified criteria. -------------------- Boot Images for arm -------------------- Image count: 0 ------------------ Image Information: ------------------ There are no images that match the specified criteria. =============================================================================== -------- Summary: -------- Total number of boot image stores: 4 Total number of boot images: 3 -------- INSTALL IMAGES =============================================================================== -------------------- Image Group DistributionGroup -------------------- Name: DistributionGroup Security: O:BAG:DUD:(A;OICI;FA;;;BA)(A;OICI;FA;;;SY)(A;;FA;;;BA)(A;OICIIO;GA;;;C O)(A;OICI;0x1200a9;;;BU)(A;CI;LC;;;BU)(A;CI;DC;;;BU) Image format: WIM Image count: 6 ------------------ Image Information: ------------------ Dell Optiplex 3020 Test File name: Dell Optiplex 3020.wim Image name: Dell Optiplex 3020 Test Description: Dell Optiplex 3020 Test Capture ID: Priority: 500000 (Default) Architecture: x86 Image type: Install Image format: WIM Image group: DistributionGroup Size: 12172102562 bytes Partition style: HAL type: acpiapic Creation time: 15 October 2014 19:58:39 Last modified: 15 October 2014 19:58:46 Default language: English (United States) Other languages: Dependent files: \\NTSERVER29.domain.co.uk\REMINST\Images\DistributionGroup\Dell Optiplex 30 20.wim OS version: Microsoft® Windows® Operating System, 6.1.7601 Service pack level: 1 User filter: O:S-1-5-21-1738485378-1525038498-1803697834-16854G:DUD:(A;;FA;;;BA) (A;;FA;;;SY)(A;;FA;;;S-1-5-21-1738485378-1525038498-1803697834-16854)(A;;0x1200a 9;;;BU) Unattend file present: No Status: Enabled Image Filters: ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- Windows 7 HOMEBASIC File name: install-(2).wim Image name: Windows 7 HOMEBASIC Description: Windows 7 HOMEBASIC ID: {587B12B6-D6D9-4F13-8B81-E962AC7078D7} Priority: 500000 (Default) Architecture: x86 Image type: Install Image format: WIM Image group: DistributionGroup Size: 8306998658 bytes Partition style: HAL type: acpiapic Creation time: 14 July 2009 06:24:44 Last modified: 14 October 2014 16:19:18 Default language: English (United States) Other languages: Dependent files: \\NTSERVER29.domain.co.uk\REMINST\Images\DistributionGroup\install-(2).wim \\NTSERVER29.domain.co.uk\REMINST\Images\DistributionGroup\res.rwm OS version: Microsoft® Windows® Operating System, 6.1.7600 Service pack level: 0 User filter: O:BAG:DUD:(A;;FA;;;BA)(A;;FA;;;SY)(A;;FA;;;BA)(A;;0x1200a9;;;BU) Unattend file present: No Status: Enabled Image Filters: ------------------------------------------------------------------------------- =============================================================================== Total number of image filters: 0 ------------------------------------------------------------------------------- ******************************************************************************* Windows 7 HOMEPREMIUM File name: install-(3).wim Image name: Windows 7 HOMEPREMIUM Description: Windows 7 HOMEPREMIUM ID: {150666C9-B2D9-4BA0-873C-3A4B7BF986C3} Priority: 500000 (Default) Architecture: x86 Image type: Install Image format: WIM Image group: DistributionGroup Size: 8747698450 bytes Partition style: HAL type: acpiapic Creation time: 14 July 2009 06:24:44 Last modified: 14 October 2014 16:19:21 Default language: English (United States) Other languages: Dependent files: \\NTSERVER29.domain.co.uk\REMINST\Images\DistributionGroup\install-(3).wim \\NTSERVER29.domain.co.uk\REMINST\Images\DistributionGroup\res.rwm OS version: Microsoft® Windows® Operating System, 6.1.7600 Service pack level: 0 User filter: O:BAG:DUD:(A;;FA;;;BA)(A;;FA;;;SY)(A;;FA;;;BA)(A;;0x1200a9;;;BU) Unattend file present: No Status: Enabled Image Filters: ------------------------------------------------------------------------------- =============================================================================== Total number of image filters: 0 ------------------------------------------------------------------------------- ******************************************************************************* Windows 7 PROFESSIONAL File name: install-(4).wim Image name: Windows 7 PROFESSIONAL Description: Windows 7 PROFESSIONAL ID: {1849C3AE-E2F6-4EC5-9DBD-AD0FD2223185} Priority: 500000 (Default) Architecture: x86 Image type: Install Image format: WIM Image group: DistributionGroup Size: 8627895833 bytes Partition style: HAL type: acpiapic Creation time: 14 July 2009 06:24:44 Last modified: 14 October 2014 16:19:22 Default language: English (United States) Other languages: Dependent files: \\NTSERVER29.domain.co.uk\REMINST\Images\DistributionGroup\install-(4).wim \\NTSERVER29.domain.co.uk\REMINST\Images\DistributionGroup\res.rwm OS version: Microsoft® Windows® Operating System, 6.1.7600 Service pack level: 0 User filter: O:BAG:DUD:(A;;FA;;;BA)(A;;FA;;;SY)(A;;FA;;;BA)(A;;0x1200a9;;;BU) Unattend file present: No Status: Enabled Image Filters: ------------------------------------------------------------------------------- =============================================================================== Total number of image filters: 0 ------------------------------------------------------------------------------- ******************************************************************************* Windows 7 ULTIMATE File name: install-(5).wim Image name: Windows 7 ULTIMATE Description: Windows 7 ULTIMATE ID: {280A4685-155E-4565-B413-D60BB8F105E7} Priority: 500000 (Default) Architecture: x86 Image type: Install Image format: WIM Image group: DistributionGroup Size: 8785899727 bytes Partition style: HAL type: acpiapic Creation time: 14 July 2009 06:24:44 Last modified: 14 October 2014 16:19:24 Default language: English (United States) Other languages: Dependent files: \\NTSERVER29.domain.co.uk\REMINST\Images\DistributionGroup\install-(5).wim \\NTSERVER29.domain.co.uk\REMINST\Images\DistributionGroup\res.rwm OS version: Microsoft® Windows® Operating System, 6.1.7600 Service pack level: 0 User filter: O:BAG:DUD:(A;;FA;;;BA)(A;;FA;;;SY)(A;;FA;;;BA)(A;;0x1200a9;;;BU) Unattend file present: No Status: Enabled Image Filters: ------------------------------------------------------------------------------- =============================================================================== Total number of image filters: 0 ------------------------------------------------------------------------------- ******************************************************************************* Windows 7 STARTER File name: install.wim Image name: Windows 7 STARTER Description: Windows 7 STARTER ID: {1C935F5A-1835-49A3-AE1A-B64910FFF925} Priority: 500000 (Default) Architecture: x86 Image type: Install Image format: WIM Image group: DistributionGroup Size: 8250904871 bytes Partition style: HAL type: acpiapic Creation time: 14 July 2009 06:24:44 Last modified: 14 October 2014 16:19:16 Default language: English (United States) Other languages: Dependent files: \\NTSERVER29.domain.co.uk\REMINST\Images\DistributionGroup\install.wim \\NTSERVER29.domain.co.uk\REMINST\Images\DistributionGroup\res.rwm OS version: Microsoft® Windows® Operating System, 6.1.7600 Service pack level: 0 User filter: O:BAG:DUD:(A;;FA;;;BA)(A;;FA;;;SY)(A;;FA;;;BA)(A;;0x1200a9;;;BU) Unattend file present: No Status: Enabled Image Filters: ------------------------------------------------------------------------------- =============================================================================== Total number of image filters: 0 ------------------------------------------------------------------------------- ******************************************************************************* NON-NATIVE IMAGES =============================================================================== =============================================================================== -------- Summary: -------- Total number of non-wim image groups: 0 Total number of non-wim images: 0 -------- An error occurred while trying to execute the command. Error Code: 0xC10408B3 Error Description: One or more errors occurred while processing the command. Rev iew the error logs for more information. C:\Users\administrator> This is also showing on WDS server, although doesnt seem right as it goes into WDS. Byte count at fault? Many Thanks, hopefully the above makes sense to someone. Mark

I am trying to build a custom page for MDT that will take in some settings from the user and then build the computer name based on those. I already have the DeployWiz_Computername.xml set where it prepopulates the computer name with the serial number of the machine. But I would like to make it a bit easier with an additional page that will build the name for the tech. Our naming standard is: Desktops: Site Initials - Room Number - Last 4 Serial Number (ex. NFHS1258965) Teacher Laptops: Site Initials - Full Serial Number (ex. NFMSCNU02501298) Student Laptops: Site Initials - C - Cart Number - Last 4 Serial Number (ex. CHTTC68547) Once they check what type of computer it is then fill in the required text field depending on that computer type it will then auto generate the computer name for the next screen (DeployWiz_ComputerName.xml) Any help that you can give will be greatly appreciated. I am just starting to dig in deep into WDS/MDT. Also as an FYI we are not using SCCM. Here is a general look of the page I am trying for: [TABLE=width: 500] [TR] [TD]"Radio button" Desktop[/TD] [TD] Room Number "Text Field"[/TD] [/TR] [TR] [TD]"Radio button" Teacher Laptop[/TD] [TD][/TD] [/TR] [TR] [TD]"Radio button" Student Laptop[/TD] [TD] Cart Number "Text Field"[/TD] [/TR] [/TABLE]

I have spent some time this afternoon using DISM to customize Win8 install.wim files and upload them to my WDS server - if its any use to anyone else I have included the procedure below. Download Windows Assessment and Deployment Kit (ADK) for Windows® 8 from Download Windows Assessment and Deployment Kit (ADK) for Windows® 8 from Official Microsoft Download Center (you only need to select Deployment tools during installation for this) Extract the Install.Wim file from your Windows 8 ISO Create a temporary staging folder (in my case this is C:\dism\mount) run the following commands in command prompt cmd as administrator:- dism.exe /Mount-wim /Wimfile:c:\dism\install.wim /index:1 /MountDir:c:\DISM\mount Dism.exe /Image:c:\DISM\mount /Get-Provisionedappxpackages (this gives you a list of the installed metro apps which are installed when a new user is created) Dism.exe /Image:c:\DISM\mount /Remove-Provisionedappxpackage /PackageName:Microsoft...... (and repeat for all of the apps you don't want - I uninstalled all of them) Dism.exe /Unmount-Image /MountDir:c:\DISM\mount /Commit Copy the updated install.wim to your WDS server and deployed it as normal As a side note I also wanted to disable windows store for pupils so I have applied the following GPO Object - User Configuration\Administrative Templates\Windows Components\Store