2 replies to this topic

[j0hnx777]

When I run the sysprep and capture my task sequence fails. It says there is not enough space on the disk to capture the image. However, when I start the task sequence, I direct my capture to go on a different disk (40gb) than the deployment share is running on. Does the deployment share automatically want to direct captures to its own drive? Here are the commands I run:

net use * \\JOHNSLAB\DeploymentShare$ /user: ********
cscript \\JOHNSLAB\DeploymentShare$\Scripts\LiteTouch.WSF

Then I get the task sequence.

I choose the sysprep and capture template. It asks me where I would like to save my capture to and I put:
\\JOHNSLAB\Captures$

I add my credentials and finish the execution.

Then it fails and says I don't have enough disk space, but Captures$ is on a different drive that has 40gb of free space.

The reference computer is a basic install of Windows 7 with no extra programs or files added to it. I am simply doing this as a test to further my knowledge of Windows 7 AIK.

Thank you and kind regards,

- John

[steve6375]

Is the volume FAT32 perchance (max filesize 4GB)? Try NTFS.
Can you access JOHNSLABCaptures$
Try mapping a volume letter to it and using the volume letter?

[j0hnx777]

hmm well it is on NTFS and I did access the Captures$ folder. I'm thinking it might be a setting with Deployment Workbench accessing another drive? I'm not sure though. I did map it to a letter and still unable to capture...