zeezam Posted February 2, 2011 Share Posted February 2, 2011 I have a reference windows 7 machine that I want to capture. I have made a task sequence (http://www.windowsnetworking.com/articles_tutorials/Deploying-Windows-7-Part11.html).When I run the Scripts\LiteTouch.vbs from commandline I got this message:A connection to deployment share (\\server\deploymentshare$) could not be made. The deployment will not proceed. Link to comment Share on other sites More sharing options...
arwidmark Posted February 2, 2011 Share Posted February 2, 2011 Check the Deployroot value in bootstrap.ini... and also make sure you are using MDT 2010 Update 1 since it has fixes for this particular issue./ Johan Link to comment Share on other sites More sharing options...
zeezam Posted February 3, 2011 Author Share Posted February 3, 2011 Check the Deployroot value in bootstrap.ini... and also make sure you are using MDT 2010 Update 1 since it has fixes for this particular issue./ JohanHere is my bootstrap.ini[Settings]Priority=DefaultProperties=MyCustomProperty[Default]OSInstall=YSkipAppsOnUpgrade=YESSkipCapture=NOSkipAdminPassword=YESSkipProductKey=YESJust installed the MDT update 1 and upgraded the MDT Deployment Share.Now I got script problem when trying to load the LiteTouch.vbs in cmd.It's complain about the login details even do I use domain admin... Link to comment Share on other sites More sharing options...
arwidmark Posted February 3, 2011 Share Posted February 3, 2011 The bootstrap.ini is incorrect, deployroot is missing, should look like something this:[settings]Priority=Default[Default]DeployRoot=\\MDT01\MDTBuildLab$SkipBDDWelcome=YES/ Johan Link to comment Share on other sites More sharing options...
zeezam Posted February 3, 2011 Author Share Posted February 3, 2011 The bootstrap.ini is incorrect, deployroot is missing, should look like something this:[settings]Priority=Default[Default]DeployRoot=\\MDT01\MDTBuildLab$SkipBDDWelcome=YES/ JohanStill, same problem. Unknown username or wrong password. Link to comment Share on other sites More sharing options...
arwidmark Posted February 3, 2011 Share Posted February 3, 2011 You need to update the deployment share to create new boot images (with the updated bootstrap.ini)After booting into WinPE, press F8 to get a command prompt. Review the X:\Deploy\Scripts\bootstrap.ini file and verify that you can do a net use to the same share (the deployroot value) from the command prompt./ Johan Link to comment Share on other sites More sharing options...
zeezam Posted February 3, 2011 Author Share Posted February 3, 2011 You need to update the deployment share to create new boot images (with the updated bootstrap.ini)After booting into WinPE, press F8 to get a command prompt. Review the X:\Deploy\Scripts\bootstrap.ini file and verify that you can do a net use to the same share (the deployroot value) from the command prompt./ JohanDo I have to boot into WinPE? I try to follow this guide; http://www.windowsnetworking.com/articles_tutorials/Deploying-Windows-7-Part11.htmlJust want to run the "LiteTouch.vbs" from windows. Link to comment Share on other sites More sharing options...
arwidmark Posted February 3, 2011 Share Posted February 3, 2011 Ah, you want to a Refresh, that is perfectly valid scenario as well, then you don't use WinPE... my bad, I thought you were doing bare metal deployments...Please zip the new logs and post them (as attachment)/ Johan Link to comment Share on other sites More sharing options...
zeezam Posted February 3, 2011 Author Share Posted February 3, 2011 Ah, you want to a Refresh, that is perfectly valid scenario as well, then you don't use WinPE... my bad, I thought you were doing bare metal deployments...Please zip the new logs and post them (as attachment)/ JohanWhere do get the logs? Link to comment Share on other sites More sharing options...
arwidmark Posted February 3, 2011 Share Posted February 3, 2011 Ah, you want to a Refresh, that is perfectly valid scenario as well, then you don't use WinPE... my bad, I thought you were doing bare metal deployments...Please zip the new logs and post them (as attachment)/ JohanWhere do get the logs?C:\MININT\SMSOSD\OSDLOGS Link to comment Share on other sites More sharing options...
zeezam Posted February 4, 2011 Author Share Posted February 4, 2011 (edited) Attached the logs in a zip.OSDLOGS.zip Edited February 4, 2011 by zeezam Link to comment Share on other sites More sharing options...
arwidmark Posted February 4, 2011 Share Posted February 4, 2011 Attached the logs in a zip.hmm, according to the logs you are trying to run a task sequence that syspreps and captures the machine... You need to select a full standard client task sequence (with an Install Operating System action) to do a computer refresh. If it's an OEM installed machine you are not allowed to run sysprep (against the EULA).Second that you seem to be connecting to the deploymentshare with a different account than you are logged on as, but MDT works around that by using the existing credentials./ Johan Link to comment Share on other sites More sharing options...
zeezam Posted February 4, 2011 Author Share Posted February 4, 2011 Attached the logs in a zip.hmm, according to the logs you are trying to run a task sequence that syspreps and captures the machine... You need to select a full standard client task sequence (with an Install Operating System action) to do a computer refresh. If it's an OEM installed machine you are not allowed to run sysprep (against the EULA).Second that you seem to be connecting to the deploymentshare with a different account than you are logged on as, but MDT works around that by using the existing credentials./ JohanHmm I need to sysprep and capture a OEM machine. Isn't that possible with that method? Link to comment Share on other sites More sharing options...
arwidmark Posted February 4, 2011 Share Posted February 4, 2011 It doesn't really matter if is possible or not... You are simply not allowed to sysprep and capture an OEM machine with any deployment solution, sorry... You are supposed to use a Volume License media. Enterprise deployment is one of the key benefits with the Microsoft Volume Licensing program.From the Microsoft Reimaging.docx document: "Organizations do not have the right to reimage using OEM media. An OEM image can only be preloaded on a PC by the OEM during manufacturing. An image can be individually recovered by the organization (or a service provider they choose) by using the Recovery Media. The OEM recovery media should match the product version originally preinstalled on the system; no other image may be used to restore the system to its original state."/ Johan Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now