Deployment Solution

 View Only
Expand all | Collapse all

RDeploy: There is not enough disk space

Migration User

Migration UserMay 13, 2011 04:03 PM

  • 1.  RDeploy: There is not enough disk space

    Posted May 13, 2011 10:45 AM

    So, I have been able to capture and deploy a basic image. Now when I build a complete win7 image, I get an error when trying to upload it.

    Now, the server I am sending it to has over 1 terabyte of space available so size should not be an issue.

    Rdeploy: there was not enough disk space to store the file.

    Now, this is a win7 image with office 2010 and a host of other software. The amount of space taken up on the drive is about 30Gigs. My guess is that rdeploy uploads with whole file and then compresses it but maybe not.

    Is there a maximum size the image can be?

     

    Altiris 6.9 SP5



  • 2.  RE: RDeploy: There is not enough disk space

    Posted May 13, 2011 10:51 AM

    What file system is the server drive that you are attempting to send it to?  Keep in mind, if it is FAT32 (like a lot of external drives can be pre-formatted to), it does not support files larger than 2GB.

    Usually by default, RDeploy will break the image up into 2GB span files automatically, unless a command line switch changes that behavior.

    Also, check for any quotas that may be set up on the storage share and that the account that WinPE is using to connect to the share has appropriate rights.  If this is a Windows server, a lot of people don't understand that there are two sets of rights that need to be defined, one is on the share itself (usually defaulted to give "Everyone" read only access) and the other is on the folder itself.  I will usually grant everyone full control on the share and then tighten the security on the folder permissions.  This ensure that everyone can right to the share as long as they have permissions on the folder. 

     

    Hope this helps a little.



  • 3.  RE: RDeploy: There is not enough disk space

    Posted May 13, 2011 11:12 AM

    Well our deployment server is ntfs. It is server 2008 R2. it looks like the folder that I am trying to save to has "everyone" set to full access. Admins are also set to full access. Read only box is checked.

    I have admin rights to the server itself.

    My capture task does not have a spot to specify a particular account name, which is normal I think.

    How does rdeploy do compression? Does it pull the whole system, then compress or does it compress as it pulls? I am under the impression that it pulls the whole thing then performs compression.

     



  • 4.  RE: RDeploy: There is not enough disk space

    Posted May 13, 2011 11:16 AM

    Compression generally happens as it is pulling from the source.

    In regards to the account used to connect.  That would be specified when you created your WinPE boot environment.  When you get into WinPE, you might pull up one of the two minimized dos prompts and change to the drive/folder that is mapped for your imaging and see if you can create a folder/file.  Also doing a DIR command might tell you how much space is available to you (in the event that quotas are set up).



  • 5.  RE: RDeploy: There is not enough disk space

    Posted May 13, 2011 11:23 AM

    Is there any other way to check quotas? Is the quota set in altiris?

    I also tried to have rdeploy send the file to completely different server and the error is the same.



  • 6.  RE: RDeploy: There is not enough disk space

    Posted May 13, 2011 11:42 AM

    Quotas are set by the server OS, in your case Windows 2008.

    Can you include a screenshot of your job?  It might shed some light on the situation.



  • 7.  RE: RDeploy: There is not enough disk space

    Posted May 13, 2011 11:43 AM

    I will see if I can screen shot it but I am going to check quotas first to make sure that is not an issue.



  • 8.  RE: RDeploy: There is not enough disk space

    Posted May 13, 2011 11:48 AM

    When I say a screenshot of the job, I mean the job properties, not of the client machine attempting to run it, although that could be interesting as well.



  • 9.  RE: RDeploy: There is not enough disk space

    Posted May 13, 2011 11:52 AM

    I know, I just want to check the quotas first to make sure those are ok.



  • 10.  RE: RDeploy: There is not enough disk space

    Posted May 13, 2011 02:13 PM

    OK, quotas are disabled so no limit from what I can tell.

    I can't get a screen shot since the server is remote for me to access but the settings are this:

    Imaging tool: Rdeploy(*.exe;*.img) (text mode)

    additional parameters: blank

    enter the path and file name:

    Set to folder on deployment server.

    Disable image path validation: unchecked

    sysprep settings: unchecked

    do not boot to production: unchecked

    automation preboot enviroment: default automation.

    Next screen is all default. 

    Success: continue

    default: stop

    the rest is blank

     

    These settings worked for capturing a smaller image before that consisted of just win7 and nothing else.



  • 11.  RE: RDeploy: There is not enough disk space

    Posted May 13, 2011 02:47 PM

    If you are using Windows 7 as a client, there is a utility called "Snipping Tool" works great to get screenshots.  Another way would be to do screen prints to a wordpad document and get the wordpad document to your computer via the network.



  • 12.  RE: RDeploy: There is not enough disk space

    Posted May 13, 2011 04:03 PM
      |   view attached

    Is this what you want? 



  • 13.  RE: RDeploy: There is not enough disk space

    Posted May 13, 2011 05:10 PM

    Well, I think it all comes down to space. I moved the aclient to our older 6.9 ps 3 server with more space and was able to upload it fine. So I am going to expand disk space on my current DS and see what happens.



  • 14.  RE: RDeploy: There is not enough disk space

    Posted May 16, 2011 09:21 AM

    Seems kind of odd that you say you had 1TB of space available at the beginning of this thread.  I would look at how the drives and permissions are set up on the new server vs. the old server.