MS OS Patching Images in WDS

Hi All,
Is there a way to apply MS OS patches to client OS images in WDS without deploying the image, applying the patches, and then uploading the image to the WDS server? We have a Windows Server 2008 R2 WDS server and we use WSUS for patch management. I would
like to be able to update our client OS images without deploying them and uploading them back to our WDS server.
Is this possible? Any suggestions?
Thanks,
Adam

Hi,
depending on the OS versions, and the type of update package, you may be able to use DISM Offline Servicing commands.
Here's a detailed article on a specific situation (Configuration Manager), but it includes several links to the topic:
http://blog.configmgrftw.com/kb2522623-and-offline-servicing/
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Similar Messages

So how to specify different answer file for different install images in WDS snap-in?

hello
in WDS snap-in, in properties on server name, on client tab, we can define an answer file for unattended windows installation on WDS clients.
my question is, maybe we have added multiple images in WDS snap-in (win xp image, win 7 , win 2008,...)
now this one answer file applies to all of them ?
so how to specify different answer file for different install images in WDS snap-in?
thanks in advanced

Under the "Client" tab of WDS, you should only use an answer-file with settings relevant for the installation. This would be credentials for the WDS deployment share, international settings used during the setup and possibly also destination drive
details (if you want the installation to take care of partitioning the disk etc). The settings relevant for unattend-files used under "Client" would only be of those in phase 1 (WinPE).
However, if you would like to have specific unattend file for every installation, e.g. Win7, Server 2008, Win 8 etc, you can browse to the image under "Install Images" under the image Groups. There you can select properties for every image and
have a personal unattend-file.
hi Joel
very cool. thanks a lot, that really helped me.
best regards

Getting 100% patched image

Hi Guys,
I am trying to get 100% patched image through build and capture process. I am using below trying to get fully patched image. i have config manager 2012 R2 integrated with MDT 2013
- I have 'install software' steps in TS (multiple times to get all the patches)
- For office 2007 and office viewers, i have downloaded patches and added to update folder with office package.
- I run offline servicing to get any missed out OS and office pacthes
but still once image is deployed, it detects more updates from SUP (specially for office viewers).
Looking for some pointers to get patched image out of build and capture process.
Regards,

Offline servicing will only get OS patches...not Office.
The collection where your OS Deployment TS is targeted should have Updates targeted towards it as well. That way they are applicable while the TS is running. Otherwise the updates won't get applied until after the system is deployed and becomes part of the
regular updates collection. You might already be doing this...it wasn't clear from your post.
Jarvis
Blog:
http://verbalprocessor.com Twitter:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.
The postings on this site are my own and don’t necessarily represent my employer’s positions, strategies or opinions.

Unable to deploy a Windows 8.1 image using WDS name and approve!

Hello,
Hopefully some of you residing Windows 8.1/2012R2 WDS experts are able to answer this question that has been tormenting me for 3 weeks now!
I have been trying to deploy a custom Windows 8.1 image to a test VM using an answer file and WDS for a mostly unattended process (outside of selecting the image to apply).
The image and installation process actually works flawlessly if I let WDS handle all known and unknown clients. The problem comes when I try to "name and approve" the stations. All I do is enter the name and leave everything else blank
and/or at their default settings but it always fails no matter the tweaks I've been trying to apply to the answer file, UnsecureJoin true or false with the credentials and whatnot does not matter. For the sake of simplicity, I'll post the "specialize"
portion of my answer file which worked using UnsecureJoin without name and approve here:
<settings pass="specialize">
<component name="Microsoft-Windows-UnattendedJoin" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Identification>
<UnsecureJoin>true</UnsecureJoin>
</Identification>
</component>
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ComputerName>%MACHINENAME%</ComputerName>
<RegisteredOrganization>Organization</RegisteredOrganization>
<RegisteredOwner>Utilisateur</RegisteredOwner>
</component>
<component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<InputLocale>1009:00001009</InputLocale>
<SystemLocale>en-US</SystemLocale>
<UILanguage>fr-FR</UILanguage>
<UserLocale>en-US</UserLocale>
</component>
</settings>
The error I retrieved from C:\Windows\panther\setuperr.log is: "[DJOIN.EXE] Unattended Join: At least one of JoinWorkgroup/JoinDomain must be specified: 0x57". Thus, I retry with name and approve but by specifying the JoinDomain with the
%MACHINEDOMAIN% value as such:
<Identification>
<UnsecureJoin>true</UnsecureJoin>
<JoinDomain>%MACHINEDOMAIN%</JoinDomain>
</Identification>
This seems weird since WDS should already have this information which is specified in the WDS server properties. Still, I add the requested information and try again which then gives me the following error fetched from C:\Windows\debug\NetSetup.log:
"NetpGetDomainData: Failed to find the domain data: 0x6e"
Anybody else ran into this and know the fix for it?
Also, as an additional note, not sure if it is relevant, but doing only "Approve" will not work at all either as it gives me the following error when I attempt to do so: "The name provided is not a properly formed account name." despite
the fact that I've formatted it to use "CVL%MAC" which should pass by fine.

Hi,
Firstly, I need to confirm how the name setting got passed? Because according to my test, if the device named uncorrectly, it would prompt the error and couldn't go to next step:
As far as I know, the naming standard is different between Device Identity and ADDS server naming policy, the second naming policy should be like: %61username%#
Therefore, please check your PC device name if there is any problem with it. You can also refer to the contents of the link below for more details about Naming Standard:
http://programming4.us/desktop/21662.aspx
Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
For another problem, Unsecure join, according to the contents of the link below. since Vista, shared computer password is a dynamically generated, no need to assign the password manually.
http://technet.microsoft.com/en-us/library/cc730845(v=ws.10).aspx
Roger Lu
TechNet Community Support

WDS & MDT 2012 Integration Questions: Do I need an install image on WDS if I'm multicasting from MDT

I'm running WDS & MDT 2012 on Server 2012 for my deployment solution. I have a few questions about what happens when you integrate WDS & MDT.
Perhaps this is a simple question, but if WDS multicasts the installation image from MDT, do I need to have an image in the installation folder of WDS? I have the "Enable multicasting" box checked whenever I update my deployment share
Also, my server is running X64 architecture, so I have the x64 WAIK installed. but I'm having issues editing the unattend.xml on my server because my images are all X86. Keeping in mind that I already have the X64 WAIK installed, can i install
the X86 WAIK tools on my server?

Sorry, that's two questions you only get one... Just kidding...
FOr MDT, you don't import the images into the WDS console, you just need to add a Multicast namespace.
http://keithga.wordpress.com/2014/04/23/multicasting-with-mdt/
AS for the unattend.xml edit issue, that is known:
http://blogs.technet.com/b/deploymentguys/archive/2009/08/27/windows-7-waik-and-custom-images.aspx
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

Can't add drivers to Server 2012 R2 boot image in WDS

Hi all.
I want to use my "old" Windows Server 2012 (not R2), WDS to deploy new R2 servers but i can't add driver package to the R2 boot image, it comes out with error code: 0xc0000135 no matter what drivers i use.
Without network drivers i can't boot the image on my physical servers, i've tried on a virtual machine where it works just fine.
I can't use the old boot image to install R2, then it comes with error: "Windows could not apply unattend settings during pass [offlineServicing]." when it tries to install it on both virtual and physical servers.
My initial thought is that the WDS server has to be on a R2 server but i can't find anything that proofs that.
Can someone confirm that non R2 WDS is not supported to R2 or does anyone have an idea to a solution?
Thank you in advance.

Okay maybe not a solution but i installed a new WDS server on R2 and then there was no problem adding driver package to to boot image.
So i was able to confirm my theory that it's not supported to deploy R2 from a non-R2 WDS server. If anyone can make it work please let me know but until then i think this is the only way.
If I understand your description of the issue, the problem is that you are trying to update a WinPE 5.0 WIM with a version of the ADK that services WinPE 4.0 images. Installing the new Windows Server 2012 R2 server caused SCCM to use the version of the
ADK that services WinPE 5.0 images. You should be able to deploy them fine from the other server, but you can only service them from the new one. You will not be able to service the older WinPE 4.0 images from the new server either.

WDS Image deployment with updates applied

Hi All,
Is it possible to capture an image which has windows updates included? I am currently building a number of machines for rollout and having to wait for 115 updates to be applied to each.
I have captured a .wim image and is sitting in captured images within install images on the WDS server - I need to add a boot image to show on the machine when network booting, but not sure how to do this.
Any help appreciated.
Cheers
Neil

Yes.. Check this links
http://www.windows-noob.com/forums/index.php?/topic/261-how-can-i-capture-an-image-using-wds/
http://social.technet.microsoft.com/wiki/contents/articles/11680.creating-a-capture-image-in-wds.aspx
Justin Abraham ----------------------------- Knowledge is Power

Add Iso image in the Pxe sever of WDS

Hello sorry for my bad english.
Is there any solution to add an iso image (boot cd like "utltimate boot cd") in the PXE menu of WDS ?
Thanks a lot

You keep saying "startup image" and "discover image" and that is confusing things. There are three image type with WDS:
1. Boot Images - Used to startup the hardware and pull down the
Install Image from WDS and apply the Install Image to the local HD.
2. Install Image - Pulled down to the machine after starting with the
Boot Image and is applied to the HD. The machine reboots and runs from the applied
local Install Image. The Install Image can be a completed installation that is "ready to run" or a "wizard driven" installation which will go through the process of installing Windows on a machine (the way a factory
Windows install disk does).
3. Capture Image - This image is a Boot Image that contains a wizard driven copy of ImageX and is used to create an Install Image from a chosen partition of the local HD on the Master Model Machine. Note, it only captures
a single chosen partition, not the entire drive, and it will only acknowledge OS boot partitions that have had Sysprep run on them. It creates two copies of an Install Image,...one on the WDS Server,...and one on a local destination such as an external USB
HD connected to the source machine during the process.
If you have a custom bootable utility disk of some kind then that would be considered a
Boot Image. So to answer your direct question, as I understand it,...go to the WDS managemant console and tell it you want to import a
Boot Image. Locate and browse to the "boot.wim" file that would be located somewhere on the Boot CD/DVD that you said you already have.
If your bootable CD/DVD is of some other type that does not contain a "boot.wim", then you simply cannot do what you want to do. Boot Images are "special",...when they load they
first create a RAM Drive and then load into, and run from, that RAM Drive. You cannot do that with a Boot Disk Tool that is DOS or Linux based. It must be a Windows Based boot disk with the copy of Windows contained within the "boot.wim" file.
If I knew specifically what this boot disk you have (gotten from a friend or whatever) specifically is, then maybe I could tell you if you have any options.

WDS Capture Image Blank Screen with Cursor

Hey everyone, happy Friday and Happy Sysadmin Day!
Not super happy for myself unfortunately! I'm having a problem with a Capture Image in WDS. I have a Sysprepped Dell 6440 running Windows 7 x64.I've created a Capture Image in WDS from a boot image with drivers injected and without drivers injected, but every time I boot from PXE, it gets to the windows loading screen, and then it just shows a blank screen with a cursor.I'm using Microsoft's OpenLicense ISO as a base for the boot.wimI can't find any solution that works. I've tried mounting and unmounting the WIM, restarting WDS, etc. This is getting really frustrating as I'm so close to having these images ready.The blank screen won't do anything, won't open a cmd with Shift+
F10 or anything. I've also tried booting on a different machine and it does the same thing.Any suggestions are...
This topic first appeared in the Spiceworks Community

HI @Moonrod ,
Welcome to the HP Forums!
It is a super place to find answers and information!
For you to have the best experience in the HP forum I would like to direct your attention to the HP Forums Guide Learn How to Post and More
I grasp you were unable to do a refresh you PC as you received the message that the drive was locked.
Please refer to my post Re: Can't refresh or reset windows 8.1 because drive is locked
Here is a link from the windowsclub.com that may also be informative.
Fix: The drive where Windows is installed is locked.
Best of Luck!
Sparkles1
I work on behalf of HP
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos, Thumbs Up" on the bottom right to say “Thanks” for helping!

WDS Capture Image Failing to Load

Using the instructions posted here:http://social.technet.microsoft.com/wiki/contents/articles/11680.creating-a-capture-image-in-wds.aspx I created a capture image and then injected network drivers into the boot image. When trying to load the capture image
I get the error:
Status: 0x000000f Info: The boot selection failed because a required device is inaccessible.
Does anyone know what might cause this or how to resolve this issue?

Hi,
First test to add/remove any mass storage drivers when capture the image.
Also the error could relate to BCD corrupt. Check BCD entry to see if it is correct. You could try following 3 commands:
a. bcdedit /set {default} device partition=c:
b. bcdedit /set {default} osdevice partition=c:
c. bcdedit /set {bootmgr} device partition=c:
TechNet Subscriber Support in forum |If you have any feedback on our support, please contact [email protected]

Deployment Workbench - how to capture an image after customisation?

I have deployed Vista to a machine using WinPE (Created through Workbench) and chose the option when deploying "Prepare for capture"
I then customised Vista - in this case removing the Fax applications and ran Sysprep with OOBE, Generalise and Shutdown.
In workbench I created a new task sequence 'Standard Client Replace task sequence' which seems to be the right task to capture an image.
When selecting the task when booting the machine with WinPE, it forces me to capture the user data - I cannot select 'Do not save data and settings'
I must be doing something wrong!
What I want to do is:
Deploy Vista
Install some apps manually i.e. not using a task sequence
Capture the image
Deploy to machines
How can I do this using Workbench? Thanks.

Hi,
Thank you for the reply.
I suggest referring to the following article:
Creating a Computer Image
http://technet.microsoft.com/en-us/library/bb977918.aspx
If you select “Capture an image of this reference computer” on the “Specify whether to capture an image” page when running Deployment Wizard, it will sysprep and capture the system for you automatically.
If you would like to
“Install Vista and prepare for capture
Install my own applications WITHOUT using task sequences
Capture the OS”,
I am afraid that you do not need to use MDT (you cannot perform a LTI without running Task Sequences). You can do this by only using WDS.
1.   Install and configure the WDS Server.
2.   Add the default Windows Server 2008 boot image to the WDS Server.
3.   Create Capture Boot Image and add it to boot image in WDS Server.
4. Create a reference computer (install the operating system, applications, and make any other changes)
5. Sysprep.
6. PXE boot the reference computer into capture image on the boot screen and then capture the image (If non-PXE supported, make a discover image to boot)
7. Upload the captured image to WDS server.
8. Clients can PXE boot and install Windows (If non-PXE supported, use a discover image to boot).
Hope it helps.
Tim Quan - MSFT

Using USB dongle with tablet to install from WDS

Is it possible to install an image via WDS to a tablet without an ethernet cable by using a USB>ethernet
dongle?

Hi Brandon Koz,
When you use the Windows system the hardware must compatible with Windows requirement, you can use the Windows Server Catalog to confirm whether your hardware meet the requirement,
the WDS minimum requirement about the WDS you can refer the following KB:
The related KB:
WDS System Requirements
http://technet.microsoft.com/en-us/library/cc731097(v=ws.10).aspx
Windows Server Catalog
http://www.windowsservercatalog.com/
I’m glad to be of help to you!
Alex Lv.
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.

Not able to install sysprepped Windows 8.1 image, an OfflineServicing error appears.

Hello
I have Windows 8.1 Enterprise image failing at the end of the PE phase from a
WDS Server. I´ve searching through every related post but nothing solves the issue. My scenario is similar to this one (http://social.technet.microsoft.com/Forums/en-US/7ce4c49d-e8a4-460a-ae17-240daaf5f50e/deploying-a-win7-image-via-wds-fails-with-offlineservicing-error?forum=w7itproinstall),
but with Windows 8.1 Enterprise instead.
Basically, I have sysprepped Windows 8.1 and capture the image successfully without any problem. Then, I´ve uploaded the image to my WDS without any unattend xml file, but when trying to install it I get the following error message after completing the "Expanding
Windows Files" phase:
“Windows could not apply unattend settings during pass [offlineServicing]”
I´ve used the official image release, plus the only one partition disk is formatted before the installation. Every configuration seems to be set correctly. I wonder if there is any particular issue related to Windows 8.1.
I´ve already done this procedure with many other OS images and I´ve never got this error message.
Furthermore, I also tried to perform the installation with an empty unattend answer file attached to the deployed image, but the error still appears.
I wonder if the Win8.1 image needs a proper configuration of the unattend answer file, specially on the
Pass 2 of OfflineServicing. Unfortunately I don´t know how to configure it. I would like to keep the credentials and partition configuration be set manually.
Thank you for any help you can give me.

Hello, thanks for the replay but I didn't found any relevant log file on the client machine.
Unattend mode is unchecked, and I haven't used DISM at all when creating the image. I haven't also opened nor updated any metroApp (although if this were the case, it would raise an issue on sysprep phase).
X:\Windows\panther directory does not exists; (C: volume is not available at installation phase)
X:\Windows\diagerr.xml doesn't have any relevant information (it defines some AtrributeType tags with a number in a xml format but it has no content on any tag.)
X:\windows\tracing\ folder is empty;
X:\windows\Logs & \Logs\CBS folders are empty;
I've checked all the volume and I couldn't find any relevant log which shows an error on the instalation.
In addition, I tried to look into WDS server, but the Enable Log property that the article refers for Windows Server 2012 (WDS is installed in a Windows Server 2012), is not shown at the
EventViewer - Deployment-Services-Diagnostics section. Plus, I search the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Tracing\WDSMGMT
entry in order to enable it, but it does not exist.
WDS worked and is working without any issue regardless this Windows 8.1 image. I don't think it has a somthing to do with its configuration.
Looking forward to hearing from you.

Capturing an image to use for PXE boot

I'm using Windows Deployment Services in conjunction with Windows Deployment Terminal (Windows Server 2008) to capture an image from one of our workstations to use as a PXE boot image for future computers. I've created the capture image and PXE booted
to that image, which brings up the "Image Capture" wizard. After capturing the image, I created an install image in WDS using the same .wim file. After trying to PXE boot, the workstation yet again brings up the "Image Capture" wizard.
I then right clicked the image under Boot Images (in WDS) and selected "Create Discover Boot Image." A loading window pops up, but always ends with an error saying something to the extent of the image doesn't have WDSClient Binaries. Does anyone
know what this is or how to fix this? Or even if I'm going about it the right way? If anyone has any advice, I'd appreciate it.

Hi,
Yes, you can.
Here are the rough steps:
1.
Install and configure the WDS Server.
2.
Add the Windows 7 boot image to WDS.
3.
Create a Capture Boot Image and add it to Boot Image.
4.
Create a reference Windows 7 computer (install Windows 7, Office and other applications as you like)
5.
Sysprep the Windows 7 computer.
6.
PXE boot the reference Windows 7 computer into capture image on the boot screen and then capture the image.
7.
Upload the captured image to WDS server.
8.
PXE boot clients, choose the captured image to install the system.
Please refer to this link
http://social.technet.microsoft.com/Forums/windowsserver/en-US/be3af7db-b71b-4b14-b166-fef83cde0ac6/deploy-windows-7-from-waik-with-some-application-added?forum=winserversetup
I had the similar problem couple of years back
UMESH DEUJA MCP,MCTS,MCSA,CCNA

Windows 8.1 WDS Installation cannot continue because a required driver could not be installed.

When i try to deploy a custom Windows 8.1 Pro Image Via WDS I get the above error. I have enabled Client side logging and checked WDS logs and install logs on the failed installation (Shift+F10). I don't think the issue is a matter of the drivers that are
included in the boot image. If it were a network card issue i would not be able to get the WINPE on the network and start the install. Second i don't think its a storage driver issue, WINPE has formatted the Drive as one may see in (Shift F10) DISKPART.
If it were a storage driver, it would not see the drive and would not format. I am starting to thing that this may be a Windows 8/8.1 Kernel issue that i have found referenced in other forums.
That Said, I still injected my drivers into WDS then into my boot image, i was unable to do some drivers that were unsigned in WDS so i added them in DISM directly to the images. I forced the unsigned drivers so they could be added. I injected the drivers into
my install and boot image. and still nothing. I then went back and removed, via DISM, all third party drivers from my boot and install image and it's still giving me the error. Help!!!!!!!!!!!!!
I can upload logs if needed.

Hi wkingswt,
In addition, please confirm image file source, prevent capturing yourself or got from faulty image or installation media.
please make sure using right version Windows PE, extract Windows PE from Windows 8.1 installation media.
Check following precautions
First Signed device drivers are a key security feature in Windows. Drivers that are installed on x64-based computers must have a digital signature. If you're adding multiple drivers, you should create separate folders for each driver or driver category.
This makes sure that there are no conflicts when you add drivers that have the same file name.
Also, as a workarround Adding Device Drivers to an Offline Windows Image also is an option.
You could find setup logs from the client computer by referring to following article, and see which driver failed to install.
http://support.microsoft.com/kb/936625/en-us
Regards

MS OS Patching Images in WDS

Similar Messages

Maybe you are looking for