%SCRIPTROOT% = deploymentshare\scripts folder. That's where is being called.
One thing that has got me in the past is not using caps on the values required by ZTIbackup. you can certainly try that. I would suggest you turn on monitoring and set the logging to your server share, it helps tremendously in troubleshooting. On Fri, Jan 10, 2014 at 4:56 AM, Kevin Johnston < [email protected]> wrote: > Sorry for the spamming… > > > > I do not seem to have the ZTIBackup.wsf file anywhere on the local drive > of the machine. I assume it is needed to start the capture of the .WIM as > the last task sequence is cscript.exe "%SCRIPTROOT%\ZTIBackup.wsf" > > > > It is not in the MININT\Scripts nor is it in _SMSTaskSequence\Scripts > > > > Surely this should have been copied down during the deployment. Could I > not just add this to the folder and it should run? > > > > Kevin > > > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Kevin Johnston > *Sent:* Thursday, January 09, 2014 9:56 PM > *To:* '[email protected]' > > *Subject:* [MDT-OSD] RE: Connection Issue to deployment share > > > > So a quick update… I got a bit farther. It now does the reboot after > applying sysprep, and when it reboots it is supposed to start the capture, > but it doesn’t it just comes back up to the desktop and then after 5 ish > minutes I get the same connection error to the share. > > > > I got passed the first error by changing the install Task Sequence under > the Install Phase from > > > > “select the location where you want to apply this operating system” - > logical drive letter stored in variable > > To > > Specific disk and partition > > > > This got me by the first connection error, rebooted and then failed to > connect again to start the WIM creation. > > > > Still not sure what the issue is. > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Kevin Johnston > *Sent:* Thursday, January 09, 2014 8:42 AM > *To:* [email protected] > *Subject:* [MDT-OSD] RE: Connection Issue to deployment share > > > > Here is a screenshot: > > > > > > We really don’t do software deployments using MDT, we use this just as a > glorified image deployment solution. Nothing fancy. This TS just installs > Windows on the VM, then pauses then captures. > > > > And yes I do get a network IP address. I use Bridged-network for the > VMWare network setting. > > > > I can browse to the actual folder using the same user name and password in > my bootstrap.ini and it connects. > > > > Thanks, > > > > Kevin > > > > > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Michael Niehaus > *Sent:* Thursday, January 09, 2014 1:02 AM > *To:* [email protected] > *Subject:* [MDT-OSD] RE: Connection Issue to deployment share > > > > Where did you place the LTISuspend step? Does the machine have an IP > address before you resume the task sequence? > > > > Thanks, > > -Michael > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Kevin Johnston > *Sent:* Wednesday, January 8, 2014 8:25 PM > *To:* '[email protected]' > *Subject:* [MDT-OSD] Connection Issue to deployment share > > > > Okay I have an issue that has been a thorn in my side ever since I > upgraded my MDT server from 2010 U1 to 2012 U1. > > > > The existing Windows 7 images work fine, and My capture task works fine. > So I decided I would build a brand new image, so I use VMware and have a > task that does the “install Windows 7 then adds a Pause sequence” This is > pretty much just like my old task I have used in the past. > > > > So in VMWare I have the OS installed, and I setup my software, etc… then I > click on the pause sequence (LTISuspend) and then I get an error > > > > A connection to the deployment share could not be made. Connection OK. > Possible cause : invalid credentials. > > > > I have triple checked that the permissions are right, and the folder has > the same rights, etc.. So I figured maybe it is something new with 2012. > > > > So I created a whole new share, set it up with vmdrivers, the OS, etc.. > and did all the same steps and I still get the same error. > > > > It usually reboots and then starts the capture task, but it gives me this > error before the VM restarts. > > > > I have read some people used the IP address and it worked, so I did that > and still nothing. > > > > I have looked at the BDD.log and the LitTouch.log files located in the > C:\MININT\SMSOSD\OSDLOGS and I don’t see anything except the error.. > > > > Is there anything I can try to get this to work? > > > > Thanks, > > > > Kevin Johnston > > >
<<image001.png>>
