Jump to content

Recommended Posts

Posted
I have a clean, newly created MDT deployment share that I just created to capture my W10 reference image that I've built. It's a physical PC, but not a member of my domain. I browse to the share, and run litetouch.vbs to initiate the task. It starts running, I give it a file name and credentials, it runs, reboots and brings me back to the login screen for Windows. It seems to somewhat be stuck in between states. No errors or warnings came up at all, however I see remnants of the TS on the C drive. Never seen anything like this - can anyone help?
Posted

have you modified the task sequence for the capture task at all?

SMS trace is a very handy log reader for troubleshooting MDT problems (part of the logging kit for SCCM which can be install stand along iirc)

Posted

Check your rules and see if you have:

 

DoCapture=YES

ComputerBackupLocation=NETWORK

BackupShare=\\server\DeploymentShare$\Captures

BackupDir=%OSDComputerName%

 

 


Posted
Tried adding the above to the CS.ini file and still did the same thing. The piece of script that your link says to modify doesn't exist.
Posted

Got the PC to complete sysprep portion, however upon reboot and attempt to capture, I get the below error. I tried to re-do the permissions on the share, to no avail. Any other ideas?

 

IMG_0358.jpg

Posted (edited)

I had a similar problem for ages. Are you using "net use" via cmd to connect to your MDT share?

 

1. Open a CMD windows and enter the following

a. Net use * \\MDT1\Deploymentshare$

b. When prompted enter credentials for a user who has Write permissions to the \\MDT1\Deploymentshare$ folder in the format of: domain\user

i. Note: typically this would be a user with Domain Administrative rights

c. When prompted enter the password for the user entered above

 

2. Enter the following to run the Litetouch sequence

a. \\ MDT 1\Deploymentshare$\scripts\litetouch.vbs

 

 

I run this when connecting from the Windows image and you need to make sure what RLI said with the DoCapture=Yes, but I have found that SkipCapture=NO, will also work. Sorry if you already know this.

Edited by Maxamoth
added
Posted
I don't get prompted for credentials if I use the net use command to connect to the deployment share. It connects to the share while in Windows, but after reboot and when it starts to create the WIM is when it crashes out. I did upgrade to build 8443 yesterday when I saw that could potentially cause a problem. I even created the TS on my old share and tried it there - I got the same error at the same point. Is there another way of capturing the WIM or does someone know how I can contact someone at MS and get some support?

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...