none
WDS - image capture upload - There is not enough space on the disk

    Question

  • I have passed all the steps of the image capture wizard of the WDS Server 2008 R2...

    In the middle of the process of the uploading the image captured it tells me "There is not enough space on the disk".

    I canceled the process and I can see the xyz.wim file created in the local machine, but no in the WDS server (E:\RemoteInstall).

    Obviously I have sufficient space on both, local machine where I am capturing the image and on the WDS server.

    Also, both disk drives are NTFS without quota allocation.

    Anyone has an idea of how to solve it¿?

    I have read some information in Internet, but with no succesful.

    Thanks in advanced.

     

    Friday, April 29, 2011 5:34 PM

Answers

  • You have to create an small (10GB) partition in the client machine, and then in the wizard you need to specify that you want to create the .wim there.

    It works like a charm.

    Good luck!

    • Marked as answer by Tacheleu Friday, June 17, 2011 12:01 PM
    Friday, June 17, 2011 12:01 PM

All replies

  • Hi guys,

    any idea?

    I am sure that I am not the unique person that am with this issue.

     

    Tuesday, May 03, 2011 2:27 PM
  • Hi,

    Have you tried the steps discussed here?

    Regards,


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
    Wednesday, May 04, 2011 10:39 AM
  • Hi Magon,

     

    yes I have done all this that Zingy (Tuesday, November 14, 2006) describes. But for example he has an error connecting to the WDS server that I have solved, and I am one step ahead.

    In the other hand I am using WDS in WS2008R2 and W7 client.

     

     

    Wednesday, May 04, 2011 1:35 PM
  • Hi,

    There might be conflict with the Server side. I suggest try it again later.

    Regards,


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
    Friday, May 06, 2011 9:37 AM
  • It works if I copy the .wim file (10GB) using a shared directory.

    Therefore, I have uninstalled WDS role and I installed once again. If it will fail again, I will try with another SO what it means will be another WDS capture.

    I have re-re-recheck that all partitions are NTFS.

    More concretly, the host server (hyper-v) has c: and d: partitions, both are ntfs. In d: partition I have 1,8TB free and are stored the .vhd for two VM, the first one has DC, WDS, DNS installed and the second one has DHCP installed. The first one, has also two partitions, c: and d:. Both are NTFS. c: is for SO and d: is exclusively for WDS role. In d: partition WDS role is where WDS stores all configuration for WDS and also the .wim files that are send trough the network.

    When it tells me "There are not enough space on the disk" I think that it is refering to d: partition, but how I said in the first line of the post, using shared directory it works. And also I can discard a switch issue.

    I will continue doing tests.

    • Proposed as answer by Gigi4444 Tuesday, June 14, 2011 7:11 PM
    • Marked as answer by Tacheleu Friday, June 17, 2011 12:00 PM
    • Unmarked as answer by Tacheleu Friday, June 17, 2011 12:00 PM
    Friday, May 06, 2011 12:42 PM
  • I have the exact same problem. Not enought space. I did try to manualy import the wim file created localy in th C: drive in to the WDS with the WDS console. It work but, the image itself after I deploy it. with the same PC,To test the image after I reboot the PC. The image fail and I was not able to repair IT on the PC.

    Any solution?

     


    Tuesday, June 14, 2011 7:16 PM
  • You have to create an small (10GB) partition in the client machine, and then in the wizard you need to specify that you want to create the .wim there.

    It works like a charm.

    Good luck!

    • Marked as answer by Tacheleu Friday, June 17, 2011 12:01 PM
    Friday, June 17, 2011 12:01 PM
  • Hi,

     

    I have the same problem. After capturing until 100% and writing the Metadata I get the error message: "There is not enough space on the disk". 

    The client is running Windows 7 x64 with 500 GB hard drive and only one partition (plus the 100 MB system-reserved partition). The image is 75GB and the wim file is 34 GB (for me it is too little). On the WDS server are 240 GB free space. The marked solution doesn't work for me. 

    I read all the posts here but no solution works. My problem is that I cannot recognize whether the problem is server or client based. Where is not enough space? 

    Does anybody have another suggestion? Until two months the WDS server was working fine and I had no problems with capturing and uploading any image. 

    Kind regards,

    Martin

    Friday, January 20, 2012 10:17 PM
  • We are having the same issue here. W7 x64 sp1, 75GB image Toughbook. We have a 200GB C: drive and a 100GB D: drive. We use the D: drive to capture the image and then the upload happens after that. The WDS server has 350+GB available. Not sure what to look at now. I can capture smaller images (servers, laptops, desktops) with no issues. This one is just bloated so we can bypass a long user synch process. Any ideas would be appreciated.

    Thanks

    Erik

    • Proposed as answer by HunterIT Friday, August 31, 2012 8:44 AM
    • Unproposed as answer by HunterIT Friday, August 31, 2012 8:44 AM
    Monday, March 05, 2012 2:18 PM
  • How big is the image that is being generated? What version of WinPE is your capture images based off of?
    Saturday, March 10, 2012 12:26 AM
  • Has anyone found a resolution to this yet?  I have the same exact problem and have yet to find a solution.  Have more than 100GB of free space on both the Client and Server, so space is definitely not an issue.  I do not have this issue with sysprepping Win XP machines, only using Sysprep on Windows 7.
    Thursday, April 19, 2012 7:41 PM
  • Can you gather the tracing logs from WdsCapture? To do this, perform the following steps:

    Edit the registry in WinPE prior to running WdsCapture.exe to contain the following keys:

    HKLM\Software\Microsoft\Tracing\WDSCAPTURE

    • EnableFileTracing (REG_DWORD) == 1
    • FileTracingMask (REG_DWORD) == 0xffff0000
    • MaxFileSize (REG_DWORD) == 0x01900000
    • FileDirectory (REG_EXPAND_SZ) == %windir%\tracing
  • Then, run WDS capture and grab the tracing logs from x:\windows\tracing and post them here.

Thursday, April 19, 2012 7:58 PM
  • "Can you gather the tracing logs from WdsCapture? To do this, perform the following steps:

    Edit the registry in WinPE prior to running WdsCapture.exe to contain the following keys:

    HKLM\Software\Microsoft\Tracing\WDSCAPTURE

    • EnableFileTracing (REG_DWORD) == 1
    • FileTracingMask (REG_DWORD) == 0xffff0000
    • MaxFileSize (REG_DWORD) == 0x01900000
    • FileDirectory (REG_EXPAND_SZ) == %windir%\tracing

    Then, run WDS capture and grab the tracing logs from x:\windows\tracing and post them here."

    Hi Aaron,

    Just a clarification, do I edit the registry on the client PC, or on the WDS?

    Thanks,

    Dan

    Monday, April 23, 2012 5:54 PM
  • On the client PC, inside of the WinPE image that's running WdsCapture.exe
    Tuesday, April 24, 2012 7:53 PM
  • Hi Aaron,

    There is no "WDSCapture" in either the client machine(machine I want to capture) or the WDS (server I want to capture to).  On the WDS, I only see WdsImge, WDSMGMTY, WDSMMC, WDSSERVER, and WdsTptMgmt under HKLM\Software\Microsoft\Tracing

    On the client machine there are absolutely no references to WDS in the registry.

    Any thoughts?

    Tuesday, May 08, 2012 5:15 PM
  • This Works for  me, i Have the  same  problem,  the directory where i save the image file was too small...

    try to create a New directory where you save all your  image file....

    Saturday, June 02, 2012 4:11 AM
  • I was having the exact same problem, Capture was getting to 33% then failing. After spending a good day trying different variations, I removed the Windows 7 Product Key from my answer file, and removed unattendedjoin component. Ran Sysprep, then began to capture image. Got past 33% and fully captured image.

    Friday, August 31, 2012 8:49 AM
  • The registry keys will not be created by default. You'll need to create them prior to running WdsCapture.exe
    Friday, September 07, 2012 9:29 PM
  • Having the same issue. I will try this

    Thursday, January 09, 2014 3:45 PM