MDT/WDS 2012 - Applying the install.wim file concurrently with the multicast download

Hi Folks.
I have a working MDT 2012 setup on Server 2012. Multicasting is all good and my images are deploying smoothly.
Looking though the "What's New" for WDS 2012 it mentions that "You can apply the install.wim file while it is being downloaded"
Does anybody have any idea on how to get this working with MDT? I can't find any info about this new feature anywhere.
PS. Should add that my Windows PE is built from the Windows ADK via MDT and I'm pushing out Win 7.
Cheers
Chris

This is the article I believe you are referring to:
http://technet.microsoft.com/en-us/library/hh974416.aspx
Unfortunately, no data is given (that I can find) about how to enable the functionality.
David Coulter | http://DCtheGeek.blogspot.com |
@DCtheGeek

Similar Messages

MDT / WDS Computers joining the network with correct computer name, but no drivers (including NIC) installed

I'm using WDS and MDT to install the computers in my network.
I recently reinstalled a server 2012R2 with the last available versions of WDS and MDT. Everything works fine except for the fact that none of my computers (different series) is installing the out of the box drivers in windows.
The network connection although is ok during setup because the computers add to the domain with the given computer name.
I'm sure I'm using the correct drivers and in my task sequence I enabled to inject all drivers.
Ideas?

Hi admin0485,
I am not very familiar with MDT, if you used the MDT to install the drivers we can ask in the specific MDT support forum, if you are using WDS to install drivers please recheck
your drivers architecture compatible with your system, we can not use the x64 driver on x86 image.
More information:
Managing and Deploying Driver Packages
http://technet.microsoft.com/en-us/library/dd348456(v=ws.10).aspx
MDT support
forum:
https://social.technet.microsoft.com/Forums/en-US/home?forum=mdt
Thanks for your understanding and support.
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Installing WIM file using USB

Hi,
I want to install captured image using USB. Not sure where I went wrong. here is what I did.
I captured an image(windows 8.1 x64 ) using MDT . I have used the captured image in WDS it works fine. But I wanted to use USB (as the file size is 6GB cant use DVD) to install on remote machines.
Than I converted it to ISO. I followed a step in http://www.ehow.com/how_5750929_convert-wim-file-iso-file.html
Finally I created bootable USB using Rufus (also tried ultraiso). easy ah
But when I boot from the USB it is giving me "windows failed to start"error as if there is no windows file on the USB.
Can anyone please help me.
Thank you very much
Serki

You can use the wim you captured, and create a new task sequence in MDT. You should then be able to create media to a folder, and copy the files to a USB drive. Once booted, the process should be similar to the WDS process you have used, assuming you used
a MDT task sequence for the WDS deployment.
Here is a walkthrough for Windows 8.1.
https://technet.microsoft.com/en-us/windows/dn481547.aspx

Can I install MS file/print with ZEN

I need to install MS FIle/Print on all my client PC's. an I use ZEN to do
this?

Thx for the update Robin.
I'm sure you will save others time.
Robin Witkop-Staub wrote:
> I found a shareware utiltiy and a script to do this.
>
> rem Install and Enable Microsoft File and Print Sharing Service
> c:\temp\migration\snetcfg -l c:\windows\inf\netserv.inf -c s -I MS_Server
>
> rem Run VB Script to Enable File and Print Sharing through Windows Firewall
> firewall.vbs
> Set objFirewall = CreateObject("HNetCfg.FwMgr")
> Set objPolicy = objFirewall.LocalPolicy.CurrentProfile
>
> Set colServices = objPolicy.Services
> Set objService = colServices.Item(0)
> objService.Enabled = TRUE
>
> netsh firewall set service type = fileandprint mode = ENABLE scope = CUSTOM
> address = 192.168.0.0/255.255.0.0
>
> rem Disable the 'Use Simple File Sharing' Option
> rem reg add hklm\system\CurrentControlSet\Control\Lsa /v forceguest /t
> REG_DWORD /d 1 /f
> rem ZEN is doing this command voa a native registry change parameter inside
> ZEN
>
>
> "Robin Witkop-Staub" <[email protected]> wrote in
> message news:Xa%Gg.1493$%[email protected]..
>> I need to install MS FIle/Print on all my client PC's. an I use ZEN to do
>> this?
>>
>>
>>
>
>
Craig Wilson
Novell Product Support Forum Sysop
Master CNE, MCSE 2003, CCN

Can't open DNG files created with Mac CS5 downloader in Mac CS4 Photoshop

I recently installed CS5 on my mac but I kept CS4 installed as well. I notice that I cannot open DNG files created with CS5 in Photoshop CS4. Bridge CS4 shows the files only as icons - no image thumbnails. I am able to open these same files on a Windows version of CS4. Is there some plugin for my mac CS4 that will enable me to access the DNG files created with CS5? Is there a way to use my CS5 downloader when converting my raw files from my camera to DNG files that will make them compatiple with PS and Bridge CS4?

rr3rd wrote:
Is there a way to use my CS5 downloader when converting my raw files from my camera to DNG files that will make them compatiple with PS and Bridge CS4?
Well, yes...but you'll need to modify your DNG Converter prefs to allow for that. You''ll need a recent (ideally current DNG Converter 6.4.1 or above) and click on the DNG Converter preferences and select the correct DNG Converter options. Check DNG Converter 6.4.1 (the current version) and click on "Change Preferences" to be sure select Camera Raw 5.4 and later then make sure CS4 is updated to ACR 5.7 (which is the last version of ACR for CS4) However, the changes made to ACR 6.x really should be adopted since IQ for ACR 6.4.x is a lot better...

SCCM 2012 R2 Client install error - CcmGetOSVersion failed with 0x80070008

Getting this error message, CcmGetOSVersion failed with 0x80070008 and CcmSetup failed with error code 0x80070008. Only thing on this error I can find is Windows Update and removing languages. Only language installed is English. I've pasted
the last part of the ccmsetup.log file. Not sure if more would be needed. I've done a complete uninstall\reinstall attempt. Recompiled MOF files and reregistered DLL files for WMI. Did a repository rebuild of WMI. Nothing has
helped. Not sure what it's checking besides WMI to get the OSversion or what that error code means. This is the only server having this error. Our other 700 servers have installed the client with no issues. OS is Server 2008 SP2, NOT
R2. Any help is greatly appreciated. Thanks.
Detected 6906 MB free disk space on system drive. ccmsetup 6/24/2014 4:01:23 PM 3984 (0x0F90)
Checking Write Filter Status. ccmsetup 6/24/2014 4:01:23 PM 3984 (0x0F90)
This is not a supported write filter device. We are not in a write filter maintenance mode. ccmsetup 6/24/2014 4:01:23 PM 3984 (0x0F90)
SiteCode: MG1 ccmsetup 6/24/2014 4:01:23 PM 3984 (0x0F90)
SiteVersion: 5.00.7958.1000 ccmsetup 6/24/2014 4:01:23 PM 3984 (0x0F90)
Searching for a valid online MP... ccmsetup 6/24/2014 4:01:23 PM 3984 (0x0F90)
Checking the URL 'http://ADCSCCM.xxxx.dom:80/CCM_Client/ccmsetup.cab' ccmsetup 6/24/2014 4:01:23 PM 3984 (0x0F90)
PROPFIND 'http://ADCSCCM.xxxx.dom:80/CCM_Client' ccmsetup 6/24/2014 4:01:23 PM 3984 (0x0F90)
Found a valid online MP 'http://ADCSCCM.xxxx.dom'. ccmsetup 6/24/2014 4:01:24 PM 3984 (0x0F90)
Searching for DP locations from MP(s)... ccmsetup 6/24/2014 4:01:24 PM 3984 (0x0F90)
Current AD forest name is mw.dom, domain name is xxxx.dom LocationServices 6/24/2014 4:01:24 PM 3984 (0x0F90)
Domain joined client is in Intranet LocationServices 6/24/2014 4:01:24 PM 3984 (0x0F90)
Current AD site of machine is London LocationServices 6/24/2014 4:01:24 PM 3984 (0x0F90)
DHCP entry points already initialized. LocationServices 6/24/2014 4:01:24 PM 3984 (0x0F90)
Begin checking Alternate Network Configuration LocationServices 6/24/2014 4:01:24 PM 3984 (0x0F90)
Finished checking Alternate Network Configuration LocationServices 6/24/2014 4:01:24 PM 3984 (0x0F90)
Sending message body '<ContentLocationRequest SchemaVersion="1.00">
<AssignedSite SiteCode="MG1"/>
<ClientPackage/>
<ClientLocationInfo LocationType="SMSPACKAGE" DistributeOnDemand="0" UseProtected="0" AllowCaching="0" BranchDPFlags="0" AllowHTTP="1" AllowSMB="0" AllowMulticast="0" UseInternetDP="0">
<ADSite Name="London"/>
<Forest Name="xxxx"/>
<Domain Name="xxxx.dom"/>
<IPAddresses>
<IPAddress SubnetAddress="172.18.112.0" Address="172.18.112.26"/>
<IPAddress SubnetAddress="172.18.112.0" Address="172.18.112.27"/>
</IPAddresses>
</ClientLocationInfo>
</ContentLocationRequest>
' ccmsetup 6/24/2014 4:01:24 PM 3984 (0x0F90)
Sending message header '<Msg SchemaVersion="1.1"><ID>{C6E08DE7-E3F8-4AEF-971A-FE72D68A21BA}</ID><SourceHost>LONEXCHMB3-V</SourceHost><TargetAddress>mp:[http]MP_LocationManager</TargetAddress><ReplyTo>direct:LONEXCHMB3-V:LS_ReplyLocations</ReplyTo><Priority>3</Priority><Timeout>600</Timeout><ReqVersion>5931</ReqVersion><TargetHost>http://ADCSCCM.xxxx.dom</TargetHost><TargetEndpoint>MP_LocationManager</TargetEndpoint><ReplyMode>Sync</ReplyMode><Protocol>http</Protocol><SentTime>2014-06-24T15:01:24Z</SentTime><Body
Type="ByteRange" Offset="0" Length="1212"/><Hooks><Hook3 Name="zlib-compress"/></Hooks><Payload Type="inline"/></Msg>' ccmsetup 6/24/2014 4:01:24 PM 3984 (0x0F90)
CCM_POST 'http://ADCSCCM.xxxx.dom/ccm_system/request' ccmsetup 6/24/2014 4:01:24 PM 3984 (0x0F90)
Content boundary is '--aAbBcCdDv1234567890VxXyYzZ' ccmsetup 6/24/2014 4:01:24 PM 3984 (0x0F90)
Received header '<Msg SchemaVersion="1.1">
<ID>{C8B36ACA-631C-4FAB-AB16-C84E10A0E558}</ID>
<SourceID>GUID:2C64ED93-54ED-4F2D-A3BE-D3665D1F3A1A</SourceID>
<SourceHost>ADCSCCM</SourceHost>
<TargetAddress>direct:LONEXCHMB3-V:LS_ReplyLocations</TargetAddress>
<ReplyTo>MP_LocationManager</ReplyTo>
<CorrelationID>{00000000-0000-0000-0000-000000000000}</CorrelationID>
<Priority>3</Priority>
<Timeout>600</Timeout>
<ReplyCapabilities><AllowRegistrationReset>direct:ADCSCCM:ClientRegistration</AllowRegistrationReset></ReplyCapabilities><TargetHost>LONEXCHMB3-V</TargetHost><TargetEndpoint>LS_ReplyLocations</TargetEndpoint><ReplyMode>Sync</ReplyMode><Protocol>http</Protocol><SentTime>2014-06-24T15:01:24Z</SentTime><Body
Type="ByteRange" Offset="0" Length="3458"/><Hooks><Hook3 Name="zlib-compress"/><Hook Name="authenticate"><Property Name="Signature">3082018F06092A864886F70D010702A08201803082017C020101310B300906052B0E03021A0500300B06092A864886F70D0107013182015B30820157020101303430203110300E060355040313074144435343434D310C300A06035504031303534D53021074EBF19EB9460F934134D87A82C78424300906052B0E03021A0500300D06092A864886F70D01010105000482010080CC8ADDAD2A1FA5D7986202D7AD27B0C1125ACEE1E4E486D557A7482A309AF74CBC7CB4FC8001C9050E1D77443673290ADE0EFC1B140C805C60F48497DBD8C56B554962BC348C4FC4D315223BFF7200F23CC095D8854129D0852F02472A2F4570D6CF4C8902D39B87EA3BEF77A521881D3A07CC091FBFDB7D7204773BB18F333B9B106AC20E479E714609EC461D074F09B492339928FEE712496B2E8E0660342E7A7ADD575B7320C402E0009816622258D8B49466613734E8780297B32403D18DF6560F2ECB2FF7E820403EA7AC97BCFA2A53D432B37592FD64DA53FB5F03DB715E5326A55172DCF328DD80D110925B30AD2612991B923D92CD3076B26B824E</Property><Property
Name="AuthSenderMachine">ADCSCCM;ADCSCCM.xxxx.dom;</Property><Property Name="MPSiteCode">MG1</Property></Hook></Hooks><Payload Type="inline"/></Msg>' ccmsetup 6/24/2014 4:01:24 PM 3984
(0x0F90)
Received reply body '<ContentLocationReply SchemaVersion="1.00"><ContentInfo PackageFlags="16777216"><ContentHashValues/></ContentInfo><Sites><Site><MPSite SiteCode="MG1" MasterSiteCode="MG1"
SiteLocality="FALLBACK" IISPreferedPort="80" IISSSLPreferedPort="443"/><LocationRecords><LocationRecord><URL Name="AtlantaDataCenter"/><IPSubnets><IPSubnet Address="172.18.200.0"/><IPSubnet
Address=""/></IPSubnets><Metric Value=""/><Version>7958</Version><Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities><ServerRemoteName>ADCSCCM.xxxx.dom</ServerRemoteName><DPType>SERVER</DPType><Windows
Trust="1"/><Locality>FALLBACK</Locality></LocationRecord><LocationRecord><URL Name="RichmondAtlantaLink"/><IPSubnets><IPSubnet Address="172.16.0.0"/><IPSubnet Address=""/></IPSubnets><Metric
Value=""/><Version>7958</Version><Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities><ServerRemoteName>RDCSCCMDP.xxxx.dom</ServerRemoteName><DPType>SERVER</DPType><Windows
Trust="1"/><Locality>FALLBACK</Locality></LocationRecord></LocationRecords></Site></Sites><ClientPackage FullPackageID="MG100003" FullPackageVersion="6" FullPackageHash="03CFD97C8FB5F7E7E9F177FD6D30D6F25ED106E517E69B715695A0E81DB1D9AF"
MinimumClientVersion="5.00.7958.1000" RandomizeMaxDays="1" ProgramEnabled="false" LastModifiedTime="30375547;806889088" SiteVersionMatch="true" SiteVersion="5.00.7958.1000" EnablePeerCache="true"/><RelatedContentIDs/></ContentLocationReply>'
ccmsetup 6/24/2014 4:01:24 PM 3984 (0x0F90)
Found remote location 'http://ADCSCCM.xxxx.dom/SMS_DP_SMSPKG$/MG100003' ccmsetup 6/24/2014 4:01:24 PM 3984 (0x0F90)
Found remote location 'http://RDCSCCMDP.xxxx.dom/SMS_DP_SMSPKG$/MG100003' ccmsetup 6/24/2014 4:01:24 PM 3984 (0x0F90)
Could not find local DP locations from all MPs. Will fallback to MP download. ccmsetup 6/24/2014 4:01:24 PM 3984 (0x0F90)
GET 'http://ADCSCCM.xxxx.dom/CCM_Client/ccmsetup.cab' ccmsetup 6/24/2014 4:01:24 PM 3984 (0x0F90)
C:\Windows\ccmsetup\ccmsetup.cab is Microsoft trusted. ccmsetup 6/24/2014 4:01:25 PM 3984 (0x0F90)
Successfully extracted manifest file C:\Windows\ccmsetup\ccmsetup.xml from file C:\Windows\ccmsetup\ccmsetup.cab. ccmsetup 6/24/2014 4:01:25 PM 3984 (0x0F90)
Loading manifest file: C:\Windows\ccmsetup\ccmsetup.xml ccmsetup 6/24/2014 4:01:25 PM 3984 (0x0F90)
Successfully loaded ccmsetup manifest file. ccmsetup 6/24/2014 4:01:25 PM 3984 (0x0F90)
Checking if manifest version '5.00.7958.1000' is newer than the ccmsetup version '5.0.7958.1000' ccmsetup 6/24/2014 4:01:25 PM 3984 (0x0F90)
Running from temp downloaded folder or manifest is not newer than ccmsetup. ccmsetup 6/24/2014 4:01:25 PM 3984 (0x0F90)
CcmGetOSVersion failed with 0x80070008 ccmsetup 6/24/2014 4:01:25 PM 3984 (0x0F90)
A Fallback Status Point has not been specified. Message with STATEID='301' will not be sent. ccmsetup 6/24/2014 4:01:25 PM 3984 (0x0F90)
Deleted file C:\Windows\ccmsetup\ccmsetup.xml ccmsetup 6/24/2014 4:01:25 PM 3984 (0x0F90)
CcmSetup failed with error code 0x80070008 ccmsetup 6/24/2014 4:01:25 PM 3984 (0x0F90)

Everything seems fine. 7GB of free space, 500 MB of free RAM, 5GB of page file free. I'll reboot the server during our next maintenance window and see if that helps. Was hoping I wouldn't have to reboot but will probably help. Thanks
again.

Cannot instal xorg files - Conflict with another program.

I have a new install and set up my wireless, got pacman working good but there are a couple things that are not working. 1-cannot install powerpill, it just does not find it when i try to download it. 2 when I try to download xorg files it says there is a conflict with another program (not near my comp right now so i dont have the name of the program, i will post it later). I am more worried about getting xorg set up than powerpill. does anyone have any ideas? i am set up for fastest mirror and ran the pacman -Syu to update everything yesterday...

I am trying to install everything under xorg that comes up when you type pacman -S xorg. the error itself says that it conflicts with another program when i try to download it. it says do i want to remove program "x" but does both options still will not download. I will get the full info tonight.

Temporary wim-files for multicast transmissions still needed for WDS installation in Server 2012 R2?

Acording to
https://technet.microsoft.com/en-us/library/dn281955.aspx one of the new features for WDS in Server 2012 R2 for multicast is:
Improved multicast deployment by eliminating the need for making a local copy of the install.wim file. You can apply the install.wim file while it is being downloaded without significant impact to the application process.
However, this doesn't seem to be activated by default and I still get the following error when installing one or more machines using multicast:
"Windows Setup cannot locate a valid hard drive to store temporary installation files." However, once I remove Multicast from this install image, it installs without any problems at all.
I have also noticed that while multicasting, the installation will use the "Copying Windows files" phase, while downloading and copying the install.wim (or whatever name it is) locally on the hard drive first, so this will require lots of space.
So the question is, how do you enable this new feature that should be a part of WDS in Server 2012 R2???

Full version:
Following steps could help enable the feature:
1. Mount the boot image using dism.
e.g.
>dism /mount-wim /wimfile:c:\remoteinstall\boot\x64\images\boot.wim /index:2 /mountdir:c:\mount
2. Create a metadata file if no existing one. The metadata file should be in mountdir from the first step under mountdir\sources. And the file name should be: WdsClientMetadata.txt
3. Add entry to the metadata file: WDS.Client.Multicast.WIM.Streaming.Enabled=true
4. Save changes and unmount the boot image
e.g.
>dism /unmounts-wim /mountdir:c:\mount /commit
Sorry for the late reply, but I had to test this thoroughly since I didn't get it working right away. I tried both the regedit you first mentioned, and later also creating a textfile in the "/index:2 boot.wim", both without any success. I noticed
that creating the sources\WdsClientMetadata.txt with the data "WDS.Client.Multicast.WIM.Streaming.Enabled=true" gives me an error upon booting into WDS as follows (EUFI/IPv6-boot):
Same happens if I boot using IPv4 (an non-UEFI boot), except that there would be a plain IPv4-address instead in the error msg. Just for troubleshooting I tried writing WDS.Client.Multicast.WIM.Streaming.Enabled=false in the file instead, and WDS would throw
me the exact same error message. Once I delete the file sources\WdsClientMetadata.txt from the WDS/Boot image, the client boots ok, both for IPv4/IPv6. Disabling the firewall on the WDS didn't help, so something in the configuration is still missing? I'm getting
to a dead end here, and I suppose you're all out of advice on this one?
Thank you Shaon Shan for your great effort so far.

WDS 2012 R2 - Cannot PXE multiple clients at the same time

Hello All,
This is my first post on here so I apologize if this is the wrong place. I work for a school district and we are implementing WDS 2012 R2. We've been extremely satisfied with the speeds and ease of use through unattend files. However, for
the past month I've been looking for a possible answer to a problem that has plagued us from day one of implementation.
So here's the problem:
I have a stand alone WDS server which is not a domain controller and is not our DHCP server. I have IP helpers and broadcast forwarders setup on the network. As well as option 66 and 67 in DHCP. So far so good right!
Well that's partially right. When we boot one client at a time to the WDS server. Everything works as intended. We can TFTP the necessary files from the WDS server. Everything boots up and we're off and running.
However, if we boot up two or more clients at the same time. The WDS server never responds to the traffic. The clients get their DHCP information. They start the referral and download from the WDS server, but get no response. I'm
really hoping that someone on here would have some insight of something I can try. I've about exhausted my list of peers and contacts. They're all stumped as well and were smart enough to stay with 2008 WDS.
I would prefer to stick with 2012 R2 since it's setup and working for the most part. With only this one hiccup.
Thanks in advance for any guidance!

Hello Daniel,
I appreciate the reply and apologize for taking so long to get back to this. Things have been a little hectic over here.
I have tried everything on this forum and I am still unsuccessful in PXE booting multiple clients at the same time.
Multicast is enabled on the server, and it works for the clients. However, as stated in the original post. I cannot boot multiple machines at the same time. I can start them from the image selection screen around the same time though. So,
that appears to be working fine.

Adding custom WIM files to a bootable thumb drive

Hi, I have setup an WDS 2008 that works fine for deploying and capturing images over my network. I am trying to find a solution to create a bootable thumb, that would contain those custom images captured with WDS. So what I did until I got stuck:
Created a bootable thumb drive from an Windows 7 Pro installation disk, using Se7en Lite. Mounted the custom image in a folder and used "imagex" to append it to the "install.wim" file on the thumb drive. Checked with "imagex /info"
and indeed the custom image showed with index 5 and description "Windows7_x64_patched". Booted a PC off the thumb drive and got to the screen that asks which version of Windows I would like to install. Here, only one option shows up "Professional",
which would be the untouched Windows 7 Pro version. So no Basic, Premium or Patched version would show up, even though I can see them and their indexes with "imagex /info".
Questions:1) Is there an easier/faster way of creating a bootable thumb with multiple custom WIMs?
2) If "imagex /append" is a good solution and I'm on the right track, then what I should do so that the appended image would show as an option when installing off the thumb drive?
Thanks!

Thank you for your reply! So I edited the ei.cfg file (deleted "Professional" from [EditionID]. Now it shows me the four untouched versions "Basic", "Home Premium", "Professional" and "Ultimate" but not the custom one. I can still scroll down one more
row, so there is something without a description available seems. But if i scroll down to the 5th row and press enter, then I get the error: "Windows could not display the image available for installation". Referring to the first question and answer now, if
I replace the original "install.wim" on the thumb with my custom WIM, then I only have one image, as the WIM container would only have my captured image. So what I was asking is there an easier way to stick MORE THAN ONE installation image on the same bootable
device, without using the huge time consuming "imagex /append" command?
Here's a copy of my "imagex /info" on the modified "install.wim" from thumb:
WIM Information:
Path: e:\sources\install.wim
GUID: {65caf905-5e50-4a42-900b-5e14084871e9}
Image Count: 5
Compression: LZX
Part Number: 1/1
Attributes: 0x8
Relative path junction
Available Image Choices:
<WIM>
<TOTALBYTES>5643506813</TOTALBYTES>
<IMAGE INDEX="1">
<DIRCOUNT>13365</DIRCOUNT>
<FILECOUNT>64285</FILECOUNT>
<TOTALBYTES>11710161360</TOTALBYTES>
<CREATIONTIME>
<HIGHPART>0x01CB8936</HIGHPART>
<LOWPART>0x131F339A</LOWPART>
</CREATIONTIME>
<LASTMODIFICATIONTIME>
<HIGHPART>0x01CBF8F0</HIGHPART>
<LOWPART>0x0027D0DC</LOWPART>
</LASTMODIFICATIONTIME>
<WINDOWS>
<ARCH>9</ARCH>
<PRODUCTNAME>Microsoft® Windows® Operating System</PRODUCTNAME>
<EDITIONID>HomeBasic</EDITIONID>
<INSTALLATIONTYPE>Client</INSTALLATIONTYPE>
<HAL>acpiapic</HAL>
<PRODUCTTYPE>WinNT</PRODUCTTYPE>
<PRODUCTSUITE>Terminal Server</PRODUCTSUITE>
<LANGUAGES>
<LANGUAGE>en-US</LANGUAGE>
<DEFAULT>en-US</DEFAULT>
</LANGUAGES>
<VERSION>
<MAJOR>6</MAJOR>
<MINOR>1</MINOR>
<BUILD>7601</BUILD>
<SPBUILD>17514</SPBUILD>
<SPLEVEL>1</SPLEVEL>
</VERSION>
<SYSTEMROOT>WINDOWS</SYSTEMROOT>
</WINDOWS>
<NAME>Windows 7 HOMEBASIC</NAME>
<DESCRIPTION>Windows 7 HOMEBASIC</DESCRIPTION>
<FLAGS>HomeBasic</FLAGS>
<HARDLINKBYTES>4497873056</HARDLINKBYTES>
<DISPLAYNAME>Windows 7 Home Basic</DISPLAYNAME>
<DISPLAYDESCRIPTION>Windows 7 Home Basic</DISPLAYDESCRIPTION>
</IMAGE>
<IMAGE INDEX="2">
<DIRCOUNT>13614</DIRCOUNT>
<FILECOUNT>65339</FILECOUNT>
<TOTALBYTES>12222587449</TOTALBYTES>
<CREATIONTIME>
<HIGHPART>0x01CB8936</HIGHPART>
<LOWPART>0x131F339A</LOWPART>
</CREATIONTIME>
<LASTMODIFICATIONTIME>
<HIGHPART>0x01CBF8F0</HIGHPART>
<LOWPART>0x236D21C7</LOWPART>
</LASTMODIFICATIONTIME>
<WINDOWS>
<ARCH>9</ARCH>
<PRODUCTNAME>Microsoft® Windows® Operating System</PRODUCTNAME>
<EDITIONID>HomePremium</EDITIONID>
<INSTALLATIONTYPE>Client</INSTALLATIONTYPE>
<HAL>acpiapic</HAL>
<PRODUCTTYPE>WinNT</PRODUCTTYPE>
<PRODUCTSUITE>Terminal Server</PRODUCTSUITE>
<LANGUAGES>
<LANGUAGE>en-US</LANGUAGE>
<DEFAULT>en-US</DEFAULT>
</LANGUAGES>
<VERSION>
<MAJOR>6</MAJOR>
<MINOR>1</MINOR>
<BUILD>7601</BUILD>
<SPBUILD>17514</SPBUILD>
<SPLEVEL>1</SPLEVEL>
</VERSION>
<SYSTEMROOT>WINDOWS</SYSTEMROOT>
</WINDOWS>
<NAME>Windows 7 HOMEPREMIUM</NAME>
<DESCRIPTION>Windows 7 HOMEPREMIUM</DESCRIPTION>
<FLAGS>HomePremium</FLAGS>
<HARDLINKBYTES>4912986404</HARDLINKBYTES>
<DISPLAYNAME>Windows 7 Home Premium</DISPLAYNAME>
<DISPLAYDESCRIPTION>Windows 7 Home Premium</DISPLAYDESCRIPTION>
</IMAGE>
<IMAGE INDEX="3">
<DIRCOUNT>13701</DIRCOUNT>
<FILECOUNT>65851</FILECOUNT>
<TOTALBYTES>12122886417</TOTALBYTES>
<CREATIONTIME>
<HIGHPART>0x01CB8936</HIGHPART>
<LOWPART>0x131F339A</LOWPART>
</CREATIONTIME>
<LASTMODIFICATIONTIME>
<HIGHPART>0x01CE98EE</HIGHPART>
<LOWPART>0xCA54650A</LOWPART>
</LASTMODIFICATIONTIME>
<WINDOWS>
<ARCH>9</ARCH>
<PRODUCTNAME>Microsoft® Windows® Operating System</PRODUCTNAME>
<EDITIONID>Professional</EDITIONID>
<INSTALLATIONTYPE>Client</INSTALLATIONTYPE>
<HAL>acpiapic</HAL>
<PRODUCTTYPE>WinNT</PRODUCTTYPE>
<PRODUCTSUITE>Terminal Server</PRODUCTSUITE>
<LANGUAGES>
<LANGUAGE>en-US</LANGUAGE>
<DEFAULT>en-US</DEFAULT>
</LANGUAGES>
<VERSION>
<MAJOR>6</MAJOR>
<MINOR>1</MINOR>
<BUILD>7601</BUILD>
<SPBUILD>17514</SPBUILD>
<SPLEVEL>1</SPLEVEL>
</VERSION>
<SYSTEMROOT>WINDOWS</SYSTEMROOT>
</WINDOWS>
<NAME>Windows 7 PROFESSIONAL</NAME>
<DESCRIPTION>Windows 7 PROFESSIONAL</DESCRIPTION>
<FLAGS>Professional</FLAGS>
<HARDLINKBYTES>4786527097</HARDLINKBYTES>
<DISPLAYNAME>Windows 7 Professional</DISPLAYNAME>
<DISPLAYDESCRIPTION>Windows 7 Professional</DISPLAYDESCRIPTION>
</IMAGE>
<IMAGE INDEX="4">
<DIRCOUNT>13737</DIRCOUNT>
<FILECOUNT>66029</FILECOUNT>
<TOTALBYTES>12285492779</TOTALBYTES>
<CREATIONTIME>
<HIGHPART>0x01CB8936</HIGHPART>
<LOWPART>0x131F339A</LOWPART>
</CREATIONTIME>
<LASTMODIFICATIONTIME>
<HIGHPART>0x01CBF8F0</HIGHPART>
<LOWPART>0x6D7F6938</LOWPART>
</LASTMODIFICATIONTIME>
<WINDOWS>
<ARCH>9</ARCH>
<PRODUCTNAME>Microsoft® Windows® Operating System</PRODUCTNAME>
<EDITIONID>Ultimate</EDITIONID>
<INSTALLATIONTYPE>Client</INSTALLATIONTYPE>
<HAL>acpiapic</HAL>
<PRODUCTTYPE>WinNT</PRODUCTTYPE>
<PRODUCTSUITE>Terminal Server</PRODUCTSUITE>
<LANGUAGES>
<LANGUAGE>en-US</LANGUAGE>
<DEFAULT>en-US</DEFAULT>
</LANGUAGES>
<VERSION>
<MAJOR>6</MAJOR>
<MINOR>1</MINOR>
<BUILD>7601</BUILD>
<SPBUILD>17514</SPBUILD>
<SPLEVEL>1</SPLEVEL>
</VERSION>
<SYSTEMROOT>WINDOWS</SYSTEMROOT>
</WINDOWS>
<NAME>Windows 7 ULTIMATE</NAME>
<DESCRIPTION>Windows 7 ULTIMATE</DESCRIPTION>
<FLAGS>Ultimate</FLAGS>
<HARDLINKBYTES>4947144081</HARDLINKBYTES>
<DISPLAYNAME>Windows 7 Ultimate</DISPLAYNAME>
<DISPLAYDESCRIPTION>Windows 7 Ultimate</DISPLAYDESCRIPTION>
</IMAGE>
<IMAGE INDEX="5">
<DIRCOUNT>16853</DIRCOUNT>
<FILECOUNT>80207</FILECOUNT>
<TOTALBYTES>17942171343</TOTALBYTES>
<HARDLINKBYTES>4936766950</HARDLINKBYTES>
<CREATIONTIME>
<HIGHPART>0x01CE9935</HIGHPART>
<LOWPART>0x5B788A49</LOWPART>
</CREATIONTIME>
<LASTMODIFICATIONTIME>
<HIGHPART>0x01CE9935</HIGHPART>
<LOWPART>0x6D5A05EC</LOWPART>
</LASTMODIFICATIONTIME>
<WINDOWS>
<ARCH>9</ARCH>
<PRODUCTNAME>Microsoft® Windows® Operating System</PRODUCTNAME>
<EDITIONID>Professional</EDITIONID>
<INSTALLATIONTYPE>Client</INSTALLATIONTYPE>
<HAL>acpiapic</HAL>
<PRODUCTTYPE>WinNT</PRODUCTTYPE>
<PRODUCTSUITE>Terminal Server</PRODUCTSUITE>
<LANGUAGES>
<LANGUAGE>en-US</LANGUAGE>
<DEFAULT>en-US</DEFAULT>
</LANGUAGES>
<VERSION>
<MAJOR>6</MAJOR>
<MINOR>1</MINOR>
<BUILD>7601</BUILD>
<SPBUILD>18015</SPBUILD>
<SPLEVEL>1</SPLEVEL>
</VERSION>
<SYSTEMROOT>WINDOWS</SYSTEMROOT>
</WINDOWS>
<NAME>Win7Pro_x64_patched_nod</NAME>
</IMAGE>
</WIM>

Adding patches to an offline .WIM file

Hi guys
I am trying to update my companies Windows Server 2008 R2 x64 install.wim file with some patches I have downloaded from the Microsoft Catalogue.
So a little background, I have taken the install.wim file from the sources directory of our server image which is saved on our deployment server, and I have copied it locally to my PC. I am a domain admin and I am also a local admin on my PC.
I downloaded the latest ADK and ran the Deployment and Imaging Tools Environment tool as an administrator. I mounted the install.wim file to a mount folder with no problems.
When I try to inject a single patch using this command line DISM /image: <mount_directory> /Add-Package /Packagepath: <msu_file> (obviously replacing mount_directory and msu_file with the correct paths) I get the below error.
Image version: 6.17600.16385Processing 1 of 1 – adding package…………(package path details ect)
99.5%
An error occurred applying the Unattend.xml file from the .msu package.
For more information, review the log file.
Error: 0x80070005
Error: 5
Access is denied.
Edited copy of the log file:
2014-11-13 11:02:46, Error                 DISM   DISM Package Manager: PID=9880 Failed processing package changes - CDISMPackageManager::ProcessChanges(hr:0x80070005)
2014-11-13 11:02:46, Error                 DISM   DISM Package Manager: PID=9880 Failed to process package changes in unattend file. - CPackageManagerUnattendHandler::Apply(hr:0x80070005)
2014-11-13 11:02:46, Error                 DISM   DISM Package Manager: PID=9880 Failed to Apply the unattend. - CDISMPackageManager::Apply(hr:0x80070005)
2014-11-13 11:02:46, Error                 DISM   DISM Unattend Manager: PID=9880 d:\w7rtm\base\ntsetup\opktools\dism\providers\unattendprovider\dll\unattendmanager.cpp:400 - CUnattendManager::Apply(hr:0x80070005)
2014-11-13 11:02:46, Error                 DISM   DISM Package Manager: PID=9880 Failed applying the unattend file from the MSU package. - CMsuPackage::ApplyMsuUnattend(hr:0x80070005)
2014-11-13 11:02:46, Error                 DISM   DISM Package Manager: PID=9880 Failed to apply the MSU unattend file to the image. - CMsuPackage::Install(hr:0x80070005)
When looking at the Security tab under properties of the mount folder I can see that the account CREATOR OWNER has no permissions. When I tried to give it full control I get access is denied on the following folders:
C:\mount\program files
C:\mount\program files (x86)
C:\mount\windows
If I check the permissions for my account name, it does have full control of the mount folder.
I am wondering if anyone can help me get rid of this error?
Or even better still as I have 63 patches to inject into this .wim file, can anyone suggest an easier way, as I wouldn’t like to sit here all day doing one patch at a time?
Thanks in advance.
Dave

Hi David Smale,
From your current description and base on my experience, it usually caused by the WIM file corrupt, please try to copy a new Wim file then try to patch again, if it not work,
please post your DISM error log, you can refer the following KB to get the DISM log.
This error also can caused by the Mcafee AV.
DISM.exe generates an Error: 5 or Access Denied when VSE 8.8 Access Protection is enabled
https://kc.mcafee.com/corporate/index?page=content&id=KB76867&locale=zh_CN
I’m glad to be of help to you!
*** This response contains a reference to a third party World Wide Web site. Microsoft is providing this information as a convenience to you. Microsoft does not control
these sites and has not tested any software or information found on these sites; therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. There are inherent dangers in the
use of any software found on the Internet, and Microsoft cautions you to make sure that you completely understand the risk before retrieving any software from the Internet. ***
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.

Variable .wim file (BackupFile) using %TaskSequence% not working for reference image

Hello,
I am trying to make a semi-automated solution for building reference image. The goal is to just select a task sequence and based on only that input create a reference image and store it on the MDT server as a unique named .wim file. I'm doing almost exactly
the same as all the pro's (Johan, Mikael, etc.). What I do is in the CustomSettings.ini I specify BackupFile to be %TaskSequenceID%.wim. My goal with that is to get a .wim file that is called REFWIN81CORENLX64.wim. Instead of that I get %TaskSequenceID%.wim.
I'm banging my head against the wall all day now and I have even build another environment to see if the problem occurs there too. It does..
I'm hoping that someone can tell me what Ido wrong.
Mathijs

Short Answer:
You have programmed a race condition into your system.
Long answer:
MDT will fill out the TaskSequenceID variable during the MDT LiteTouch Wizard.
You put the BackupShare variable in your CS.ini file:
BackupShare=\\MDT02\MDTBuildLab$\%TaskSequenceID%
However, the CS.ini was ALREADY processed *BEFORE* the MDT LiteTouch Wizard. and since TaskSequenceID was set to <BLANK> then Backupshare becomes the value above. ANy attempt to re-parse the cs.ini file will not process BackupShare because ZTIGather.wsf
will only pick up the value the first time.
Instead you should set the BackupShare variable *AFTER* the MDT Litetouch Wizard, if you want to leave it in your CS.ini file, then use Johan's method to re-parse the CS.ini file during the Task Sequence.
http://www.deployvista.com/tabid/36/EntryID/139/language/en-US/Default.aspx
-k
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

An update installed using DISM in install.wim seen as "Not Applicable" by WSUS report instead of "Installed"

Hi all,
To make server's installation faster, I intend to make an updated "install.wim" every 6 months using DISM.
Then, after installation, the Win2012R2 server connect to a WSUS server to get the latests update not included in the install.wim.
As a test, I used DISM to install an update in the install.wim file of Windows 2012R2 sources.
In a new installed Windows server 2012R2, I can see that the KB is installed.
But on the WSUS report of this server, the status of the KB included in the install.wim by DISM displayed as "Not applicable".
Is it because WSUS did not installed it itself ?
Is there a way to display it as "installed" in the report, even if the patch had not been installed by the WSUS server ?
Thanks
ML

But on the WSUS report of this server, the status of the KB included in the install.wim by DISM displayed as "Not applicable".
Very possible, and likely.
It depends on how the detection logic of the update has been written. In some cases, detection logic is based on what an installer does during installation, e.g. create and/or set a registry key or value. This may not happen when injecting an update into
an image using DISM. As a result, the detection logic will not see the necessary flags it's looking for to determine that an update is "Installed" vs "Not Applicable".
You also have to think of this in terms of the baseline image installed on the system. To be true, a baseline image that already has the necessary content is, in fact, "Not Applicable", and has, in fact, not actually been installed to that machine.
Most often you see this in the realm of installing images with slipstreamed service packs.
Consider a scenario with a slipstreamed Win7SP1 baseline. Functionally speaking, all previous updates are contained within that SP1 baseline, but if you inspect the state of the actual updates in WSUS, they will all be listed as Not Applicable. They're not
actually "installed", and they cannot be installed, thus the only viable remaining state is "Not Applicable", which is true -- because they cannot be installed on an SP1-based machine. (Functionally they are superseded, which is also a
contributing factor to the state of "Not Applicable".)
There is no way to display it as "Installed". It's not. This is something that should be documented in the declaration of the baseline image you're using (by patching up the image with DISM once every six months).
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

How to edit WEPOS WIM file?

Hello, I am trying to edit the Install.WIM file on my wePOS disc, as I need to update some drivers and integrate some folders. However DISM does not recognise the Install.wim file as being valid.
I have tried installing Windows vista AIK, win7 AIK and windows 8 AIK.
Please help, thank you.

A little surprised the latest DISM doesn't recognize a WIM file. Are you using WEPOS or POSReady2009?
It has been a while since I looked at a WEPOS disk. Do you see a utility called imagex.exe? If have this older utility, try mounting the WIM file for editing using imagex.exe.
www.annabooks.com / www.seanliming.com / Book Author - Pro Guide to WE8S, Pro Guide to WES 7, Pro Guide to POS for .NET

SCCM 2012: Failed to insert OSD binaries into the WIM file' error when you create a MDT Task Sequence

Hi,
When I try to import the MDT boot image X86, I get the following error:
Started processing.
Creating boot image.
Copying WIM file.
Mounting WIM file.
WIM file mounted.
Setting Windows PE system root.
Set Windows PE system root.
Set Windows PE scratch space.
Adding standard components.
Adding component: winpe-mdac
Adding extra content from: C:\Users\ADMINI~1.afO\AppData\Local\Temp\3\sfup2yp2.0rt
Unmounting WIM.
Copying WIM to the package source directory.
Creating boot image package.
Error while importing Microsoft Deployment Toolkit Task Sequence.
Failed to insert OSD binaries into the WIM file
Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryException: The SMS Provider reported an error. ---> System.Management.ManagementException: Generic failure
   at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
   at System.Management.ManagementObject.Put(PutOptions options)
   at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put(ReportProgress progressReport)
   --- End of inner exception stack trace ---
   at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put(ReportProgress progressReport)
   at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put()
   at Microsoft.BDD.Wizards.SCCM_ImportTaskSequenceTask.DoWork(SmsPageData smspageData, Dictionary`2 data)
Note: previous x86 image was deleted some time ago.
Please advise.
J.
Jan Hoedt

This is the error in smsprov.log
*********** WBEM Missing property TransformAnalysisDate    SMS Provider    16/04/2014 15:11:00    7856 (0x1EB0)
************ WBEM Missing property TransformReadiness    SMS Provider    16/04/2014 15:11:00    7856 (0x1EB0)
Image language ID 1033 and en-US    SMS Provider    16/04/2014 15:11:00    7856 (0x1EB0)
Image language ID 1033 and en-US    SMS Provider    16/04/2014 15:11:10    7856 (0x1EB0)
Image language ID 1033 and en-US    SMS Provider    16/04/2014 15:11:19    7856 (0x1EB0)
ERROR> Error -1073741502 returned to execute the command line: "C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\dism.exe" /Image:"C:\windows\TEMP\BootImages\{8AEF81AB-4B11-4AEF-96D3-E90D84D3DA94}\mount" /Add-Package
/PackagePath:"C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\WinPE_OCs\WinPE-Scripting.cab"    SMS Provider    16/04/2014 15:11:19    7856 (0x1EB0)
Failed to install required components into the boot image C:\windows\TEMP\BootImages\{8AEF81AB-4B11-4AEF-96D3-E90D84D3DA94}\mount    SMS Provider    16/04/2014 15:11:19    7856 (0x1EB0)
*~*~e:\nts_sccm_release\sms\siteserver\sdk_provider\smsprov\sspbootimagepackage.cpp(3766) : Failed to insert OSD binaries into the WIM file~*~*    SMS Provider    16/04/2014 15:11:36    7856 (0x1EB0)
*~*~Failed to insert OSD binaries into the WIM file ~*~*    SMS Provider    16/04/2014 15:11:36    7856 (0x1EB0)
Auditing: User FAC\administrator called an audited method of an instance of class SMS_BootImagePackage.    SMS Provider    16/04/2014 15:11:36    7856 (0x1EB0)
CExtUserContext::LeaveThread : Releasing IWbemContextPtr=9281008    SMS Provider    16/04/2014 15:11:36    7856 (0x1EB0)
Jan Hoedt

MDT/WDS 2012 - Applying the install.wim file concurrently with the multicast download

Similar Messages

Maybe you are looking for