WDS 2012 Image Capture - Stuck at 50% "Capturing Windows image metadata..."

I have tried capturing a few images after running sysprep, and they are getting stuck at 50% completion, never moving past after hours of waiting. "Capturing Windows image metadata...". If I look on the WDS server I see that the file
hasn't been modified since it was actually capturing and moving the progress bar.
Has anyone ever experienced this, or have any ideas of how to troubleshoot?
Thank you!

Hi motenoob,
What system edition and MDT edition you are capturing? If it is Windows8 or 8.1, it seems is the know issue, you can refer the following KB:
Sysprep and Capture task sequence fails when it tries to capture Windows 8 or Windows 8.1 images
https://social.technet.microsoft.com/Forums/en-US/4e28cac0-29e4-4f24-a8f0-30d34d543a76/wds-2012-image-capture-stuck-at-50-capturing-windows-image-metadata?forum=winserversetup
Regards,
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.

Similar Messages

WDS 2012 Black Screen when trying to capture image

I'm currently having an issue trying to capture windows 8.1 Enterprise image using Server 2012 R2 + WDS for deployment.
All the usual steps have been followed, images added from the install media used to set up the initial machine, DHCP configured and PXEBoot works fine for the deployment image (it loads, I get an ip, can access reminst share) but when I boot in the capture
image I get nothing but a black/blank screen.
Initially when I booted in to the capture image I was receiving an 0xC000000F error but by adding the network driver to the capture image it resolved that issue and it gives the blue windows logo and starts loading but then goes black. I've subsequently
tried to add all available drives for this machine from the HP site but made no difference.
WDS server is a hyper-v VM and the box to be capture is physical, both on the same vlan.
Any one experienced this?

I did not find any help with this. I was able to get a native boot.wim and install.wim to work from the installation media (with driver injection - which I must say is way easier in W2K12). However the capture did not and will not work. VERY frustrating!
I wound up doing a WDS basic OS install then I had to manually touch 24 boxes to install the rest of the software (still not quite done after three solid days of work).
Also, I should point out: I am targeting Dell Optiplex 790s. I'm using the PE 5.0 drivers which work fine. i also downloaded the Dell Optiplex 790 driver set and injected those as well, even though they are targeted for Win 7, not Win 8.1.
Interestingly, if I updated the old system bios (A05) to the new (A18) the machine couldn't even contact the WDS server. It was working before at A05 and then completely stopped at A18, requiring me to do a complete full install from installation media.
Way to go Dell! This is why people are switching to Lenovo.
Best,
Bill

SCCM 2012 R2: Build and Capture - Windows 8.1 prompting for network

I have upgraded my SCCM 2012 SP1 (CU2) to SCCM 2012 R2 and I am attempting to Build and Capture Windows 8.1 Enterprise. Everything is perfect except for the OS prompting for a network selection during the process, if I click "next" on that screen
the Capture finishes without incident. The same is true of the Deploy as well...
Is this a bug from my upgrade?
Portland Public Schools / Systems Administrator II

Hi LillonelC
Can you point out how and where to do this?
When capturing with MDT 2013 on VMware I do not see this, naturaly, since the "machine" only has one network adapter.
But when deploying to a Laptop I get the wireless Setup screen...
On beforehand Thank You!
With kind regards
We aren't using MDT but what we did was create a package called Windows 8.1 - Compnents. In it placed a file named "32Bit-Unattend.xml" and 1 named "64Bit-Unattend.xml".
During the capture in the "Apply Operating System Image" I put a check in the box "Use an unattended or Sysprep answer file for a custom installation". The package was Windows 8.1 - Compnents the File name was "32Bit-Unattend.xml".
I did the same for 64-bit and used the 64-bit version.
Here is content of the 32-bit file:
<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="oobeSystem">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<OOBE>
<HideEULAPage>true</HideEULAPage>
<HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
<NetworkLocation>Work</NetworkLocation>
<HideOnlineAccountScreens>true</HideOnlineAccountScreens>
<HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
<HideLocalAccountScreen>true</HideLocalAccountScreen>
</OOBE>
</component>
</settings>
<cpi:offlineImage cpi:source="wim://SERVERNAME/e$/osimages/win_8.1_x86/sources/install.wim#Windows 8.1 Enterprise" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>
Here is the content of the 64-bit file:
<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="oobeSystem">
<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">
<OOBE>
<HideEULAPage>true</HideEULAPage>
<HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
<NetworkLocation>Work</NetworkLocation>
<HideOnlineAccountScreens>true</HideOnlineAccountScreens>
<HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
<HideLocalAccountScreen>true</HideLocalAccountScreen>
</OOBE>
</component>
</settings>
<cpi:offlineImage cpi:source="wim://SERVERNAME/e$/osimages/win_8.1_x64/sources/install.wim#Windows 8.1 Enterprise" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>
If that doesn't help I can try to clarify it a bit further.
PS You won't need to do this for the deploy, only the capture.
Portland Public Schools / Systems Administrator II

MDT 2012 Update 1 - Attempting to capture Windows Thin PC but it keeps looping after reboot.

I have been trying to capture a master image of Windows Thin PC we have prepared using MDT 2012 Update 1 but to no avail. When attempting the capture process using LiteTouch.vbs it syspreps and then reboots as it normally would and then it simply keeps rebooting
over and over in a loop.
I am unsure of how to bypass this and correctly capture Windows Thin PC using MDT 2012 Update 1. If anyone has any advice or feedback they can offer I would greatly appreciate it. Thank you.

Logs suggest that the script is most likely crashing early on.
I suspect that the reason for this is that the deployment share was *updated* from a previous version of MDT, and some files are out of date.
Can you update the share (full update, regenerate from scratch?)
Otherwise we may need to run Litetouch.wsf manually from within WinPE:
When WinPE Boots and you have a mouse, press F8.
Run TaskMgr.exe and verify that wscript.exe is no longer running (wait 2 minutes).
Then run the following command:
"cscript.exe x:\deploy\scripts\litetouch.wsf /debug:true /debugcapture"
That should run the litetouch.wsf script and it should display any errors if found.
Keith Garner - keithga.wordpress.com

Capture Windows 8.1 Image

Hello I am in the process of capturing a Surface Pro Windows 8.1 image. I would like to create a task to capture the image instead of having to create the capture media --> copy it to that computer and have it copy the image file back to
SCCM. Can this be done? Thanks.
Charles

Have a look at something like this:
http://www.windows-noob.com/forums/index.php?/topic/6353-using-system-center-2012-configuration-manager-part-7-build-and-capture-windows-7-x64-sp1/
This will build and capture your machine. In case you really only want to capture simply disable the build part. Also keep in mind that in that case the machine requires a client to push the task sequence to.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

"Unable to capture window image"

if I select a window to be screenshot, I get this error:
Your screen shot can’t be saved.
Unable to capture window image.
(shortcut: cmd-shift-4 and then space)
It seems to be new in Lion. Never had that problem before. And regular screenshots seem to work fine (cmd-shift-3).
Thanks for any help! ~ Kai

Thanks Davide ...
I created com.apple.screencapture.plist with Terminal and restarted the Mac.
The first couple of window screenshots worked on a Chrome browser window (command-shift-4, then space bar). But it did not work on other app's windows (Finder, Carousel).
Then I switched back to Chrome and I didn't work there too anymore. Crazy thing is that now it works on Finder windows. Very very strange.
All this is only true for capturing a whole window content (command-shift-4, then space bar)
~ Kai

Why is the image in my capture window of Premiere Pro 2 is too large.

The image in my capture window of Premiere Pro 2 is too large, however the capture is correct on the time line for editing.
Why is it too large? and how do I correct it?
Thank you for taking the time to read this e-mail and for answering my question.
Yours truly,
Thom Elliott
Photographer

Also, for future reference, PPro2 has a different forum http://forums.adobe.com/community/premiere/premierepro_previous?view=all
For this discussion, what are you editing?
Read Bill Hunt on a file type as WRAPPER http://forums.adobe.com/thread/440037
What is a CODEC... a Primer http://forums.adobe.com/thread/546811
What CODEC is INSIDE that file? http://forums.adobe.com/thread/440037
Report back with the codec details of your file, use the programs below... A screen shot works well to SHOW people what you are doing
http://forums.adobe.com/thread/592070?tstart=30
For PC http://mediainfo.sourceforge.net/en or http://www.headbands.com/gspot/
For Mac http://mediainspector.massanti.com/

WDS Install Image missing HAL details

I have a Win2008 R2 WDS server that has been up and running for quite some time. I have a Windows 7 x86 image that is hosted on that server.
I recently updated the Win7 image, syspreped, and uploaded to my WDS server as a new (v2) image. In the past this has always been quite simple, but for some reason i cannot get the new v2 image to display at the WDS client image selection screen.
The WDS server allowed me to add the new v2 image to my install image group, and says its online and working properly.
The WDS Client will only display the old v1 image and not the newly updated v2 image.
Both images were created on the SAME computer, x86, acpi multiprocessor. I am using the SAME computer to test/deploy the image.
The source of the problem seems to be from the install image missing the HAL details
If i use the WDS console and drill down to my old and new install images, right click and look at the properties this is what i get:
v1 Image: HAL Type ACPIAPIC
v2 Image: HAL Type (ITS F"N BLANK!!!!)
I get the same results looking at the <HAL> </HAL> parmeters using ImageX /info blah.wim
SO, Why the HELL does WDS/Sysprep not recognize my HAL type of my new v2 image???? I have tried 3 different computers to generate/capture the install image and ALL are missing the HAL type.
Anyone have a clue why the WDS/SYSPREP process does not identify the HAL type and leaves me with a blank string - and hence a useless image?
I have previously tried this KB with no change:
"An ACPI APIC UP HAL operating system image cannot be deployed if a Windows 7 boot image or a Windows Server 2008 R2 boot image is used in the deployment process
http://support.microsoft.com/kb/980711"
me

I cant post that online. Its from a secure network. So this is hand typed...
v1 Image that works:
<WIM>
<TOTALBYTES>3465086</TOTALBYTES>
<IMAGE INDEX=1>
<NAME> WINDOWS 7 V1 </NAME>
<DESCRIPTION> THIS IS MY DESCRIPTION </DESCRIPTION>
<WINDOWS>
<ARCH>0</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>18229</SPBUILD>
<SPLEVEL>0</SPLEVEL>
</VERSION>
<SYSTEMROOT>WINDOWS</SYSTEMROOT>
</WINDOWS>
v2 Image that does NOT work:
<WIM>
<TOTALBYTES>3510306</TOTALBYTES>
<IMAGE INDEX=1>
<NAME> WINDOWS 7 V2 </NAME>
<DESCRIPTION> THIS IS MY DESCRIPTION </DESCRIPTION>
<WINDOWS>
<ARCH>0</ARCH>
<PRODUCTNAME> Microsoft Windows Operating System </PRODUCTNAME>
<EDITIONID>PROFESSIONAL</EDITIONID>
<INSTALLATIONTYPE>Client</INSTALLATIONTYPE>
<VERSION>
<MAJOR>6</MAJOR>
<MINOR>1</MINOR>
<BUILD>7601</BUILD>
<SPBUILD>18229</SPBUILD>
<SPLEVEL>0</SPLEVEL>
</VERSION>
<SYSTEMROOT>WINDOWS</SYSTEMROOT>
</WINDOWS>
Notice that the v2 image is missing the following from the xml:
<HAL>acpiapic</HAL>
<PRODUCTTYPE>WinNT</PRODUCTTYPE>
<PRODUCTSUITE>Terminal server</PRODUCTSUITE>
<LANGUAGES>
<LANGUAGE>en-US</LANGUAGE>
<DEFAULT>en-US</DEFAULT>
</LANGUAGES>
Im lost as what to try next. Anyone have any ideas why my new v2 image is missing information from the .wim file?
me

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.

What is the size of capture window for MX440-VTD8X?

I am trying to figure out how best to resize video I have captured with my MX440-VTD8X. For the application I am using (AVISynth) I need to calculate the PAR (Pixel Aspect Ratio), for this I need to know the size of the capture window for my video capture card.
I think that this card uses a Philps SAA-7114H, although I cannot be certain as MSI don't seem to publish this fact anywhere. (I found a few references to the 7114 via Google so that is the best lead I have had so far).
Anyway, even if I knew it used a 7114H that doesn't much help as I can't find any published data that tells me what the capture window (in microseconds) is for this card. The WDM driver might modify the window so how, so I can't just look it up in the datasheet for the 7114H.
I am looking for figures for the capture window for both PAL and NTSC,
could someone please help?
many thanks,
Kevin

To quote from the article I have been using which gives step-by-step instructions on how to calculate to aspect ratio ..
(Pixel Aspect Ratio, Source Aspect Ratio and Target Aspect Ratio)
"To determine your source PAR, you first have to know what the aspect ratio of the capture window of your capture device is. This capture window is fixed, but again it is rarely exactly 4:3. The device always digitizes the same area of your video and resizes it to the size you set in your capture application. The raw captured height is always 480 lines for NTSC and 576 for PAL. The width of the capture window has to be determined. A table with known values (and a more elaborate explanation) can be found in section 5.4. A method for determining this value yourself can be found in chapter 11.
Once you know the capture window width, the Image Aspect Ratio of your device can be calculated as:
PAL IAR = (4 / 3) * ([window width in µs] / 52.0 µs) / (576/576)
NTSC IAR = (4 / 3) * ([window width in µs] / 52.6555 µs) / (480/486) "
The 'window width' is given for some capture cards in the guide, but unfortunately not the MSI one I am using, and the 'window width' does vary from one type of capture card to another.
Without this information I am at a brick wall. There is a method to determine the window by using a PAL DVD player as the source video, playing some test image, the problem is that I only have an NTSC DVD player so I can't use that technique,
this is something that the manufacturer must know, but unfortunately they rarely publish it,
Kevin

Capture window always uses the wrong name-

Hello everyone, I'm having this problem… when I go to capture HDV footage the Capture Window always remembers the name of the LAST clip I captured, when I change it and do all my capturing I find out that all my clips (and with HDV that can be a lot) have still retained the wrong name (in the browser and on my scratch disk). I tried trashing preferences and it works for the first time and goes back to this. Any help would be much appreciated. Thanks!
Also I am using someone else's computer which is a G4 (not my macbook listed below).

xorg.conf:
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 304.64 (buildmeister@swio-display-x86-rhel47-12) Tue Oct 30 12:04:46 PDT 2012
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0"
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
EndSection
Section "Files"
EndSection
Section "InputDevice"
# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection
Section "InputDevice"
# generated from default
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "Monitor"
Identifier "Monitor0"
DisplaySize 360 203
VendorName "Unknown"
ModelName "Unknown"
HorizSync 28.0 - 33.0
VertRefresh 43.0 - 72.0
Option "DPMS"
# Option "UseEdidDpi" "FALSE"
# Option "DPI" "96 x 96"
EndSection
Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
Option "NoLogo" "1"
Option "TripleBuffer" "1"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Depth 24
Modes "1360x768_60.00"
EndSubSection
EndSection

WDS 2012 - Stopped pushing Drivers after disabling a Driver Group

Hi Guys,
i really would appreciate your help on this:
I have a WDS 2012 server which was working fine and pushing drivers ok to windows 7 clients
I have disabled a driver group in order to apply the image on a different hardware and re-enabled after i have finished.
WDS stopped pushing any drivers
Troubleshooting:
Restarted WDS
Deleted the Group and created a new one with a different name, added displaydrivers
Restarted the server just in case but no luck
I do not have any filters on
Could you please help
Thanks
Alex

Hi MJM,
Did you get any event error? Please enable the WDS log, then execute a deploy action, then post the error.
The related KB:
How to enable logging in Windows Deployment Services (WDS) in Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, and in Windows Server 2012
http://support.microsoft.com/kb/936625
I’m glad to be of help to you!
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.

Capture window 'black'?

FCP 5.1.4
Capturing HDV from small Sony Handycam (set to iLink). Never captured from this camera before. Capture window will play tape back and forth ... but there is no image in the window. Just black.
Mmmm. Any ideas? Something to do with the setting in the camera?
All ears,
Ben

possibly the camera settings -
start by choosing the FCP easy setup that corresponds to the format in which you plan to edit.
Now check the setting on the camera - there will an option for downconverting the digital out to DV. If you FCP easy setup is for DV, then downconvert on the camera should be ON, if your easy setup is for HDV, then the downconvert should be OFF.
Hope this helps -
Max Average

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

Is it possible to resize the log and capture window?

Hi,
Using Final cut pro, I would like to make my capture window a bit bigger while capturing. I am capturing footage via my Blackmagic Infinity card and get the input through an HDMI cable. I'm capturing in Apple Pro ress on 720p, 59,59 fps.
For a good overview of what I'm capturing at the moment, I would love to have a bigger capture window. For all I know, FC pro doesn't support the resizing of the log and capture window. Anyone an idea on how to solve this?
Thank you.

In my case, the capture window is adjustable if I am capturing SD (DVCAM) video. I can also use the scopes in this case. (Good if you are recording to disk, or using a laptop for monitoring.)
However, both features (adjustable capture window and scopes) are not available if capturing HD (HDV in my case) video.
Message was edited by: amarasme

WDS 2012 Image Capture - Stuck at 50% "Capturing Windows image metadata..."

Similar Messages

Maybe you are looking for