Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Tuesday, April 15, 2014 6:13 PM
I am pretty new to SCCM, but I recently stood up a Windows 2012 server running SCCM 2012 SP1 CU4. I am currently using it for Endpoint Protection and Windows Updates. I would also like to use it for deploying operating systems with PXE... which is where I am stuck.
So far I have created the boot wim files and I am using the Windows 7 wim file (included with the OS). I have a basic Task Sequence created that simply installs a basic Windows 7 OS. I have been Googling and reading forums all day, but I don't know how to fix this.
My client workstation does successfully boot from PXE. I am able to select my task sequence and the installation starts. However, it quickly fails at "Running action: Use Toolkit Package" with the following error message: "Task Sequence: Deploy Windows 7 has failed with the error code (0x00000001). For more information, contact your system administrator or helpdesk operator."
I looked through the smsts.log file from the client workstation, but I can't figure out what I need to fix. I would appreciate it if someone could please have a look and let me know what I'm missing.
Log file entries:
- (__hrMethodRetVal == ((HRESULT)0L)) || (bFailIfMissing == false), HRESULT=80070002 (E:\qfe\nts\sms\common\inc\ccmxml.h,582) TSManager 4/15/2014 12:03:48 PM 1072 (0x0430)
No condition is associated with the step. TSManager 4/15/2014 12:03:48 PM 1072 (0x0430)
Disable: TSManager 4/15/2014 12:03:48 PM 1072 (0x0430)
Run in attribute: WinPEandFullOS TSManager 4/15/2014 12:03:48 PM 1072 (0x0430)
Timeout: TSManager 4/15/2014 12:03:48 PM 1072 (0x0430)
DefaultVarlist found TSManager 4/15/2014 12:03:48 PM 1072 (0x0430)
Variable name: SMSTSDisableWow64Redirection TSManager 4/15/2014 12:03:48 PM 1072 (0x0430)
Action command line: smsswd.exe /run: cscript.exe "%deployroot%\scripts\ztimovestatestore.wsf" TSManager 4/15/2014 12:03:48 PM 1072 (0x0430)
Adding instruction at 138 TSManager 4/15/2014 12:03:48 PM 1072 (0x0430)
Parsing step node: Copy Logs TSManager 4/15/2014 12:03:48 PM 1072 (0x0430)
Description: TSManager 4/15/2014 12:03:48 PM 1072 (0x0430)
ContinueOnError: TSManager 4/15/2014 12:03:48 PM 1072 (0x0430)
SuccessCodeList: 0 3010 TSManager 4/15/2014 12:03:48 PM 1072 (0x0430) - (__hrMethodRetVal == ((HRESULT)0L)) || (bFailIfMissing == false), HRESULT=80070002 (E:\qfe\nts\sms\common\inc\ccmxml.h,582) TSManager 4/15/2014 12:03:48 PM 1072 (0x0430)
No condition is associated with the step. TSManager 4/15/2014 12:03:48 PM 1072 (0x0430)
Disable: TSManager 4/15/2014 12:03:48 PM 1072 (0x0430)
Run in attribute: WinPEandFullOS TSManager 4/15/2014 12:03:48 PM 1072 (0x0430)
Timeout: TSManager 4/15/2014 12:03:48 PM 1072 (0x0430)
DefaultVarlist found TSManager 4/15/2014 12:03:48 PM 1072 (0x0430)
Variable name: SMSTSDisableWow64Redirection TSManager 4/15/2014 12:03:48 PM 1072 (0x0430)
Action command line: smsswd.exe /run: cscript.exe "%deployroot%\scripts\ztimovestatestore.wsf" TSManager 4/15/2014 12:03:48 PM 1072 (0x0430)
Adding instruction at 138 TSManager 4/15/2014 12:03:48 PM 1072 (0x0430)
Parsing step node: Copy Logs TSManager 4/15/2014 12:03:48 PM 1072 (0x0430)
Description: TSManager 4/15/2014 12:03:48 PM 1072 (0x0430)
ContinueOnError: TSManager 4/15/2014 12:03:48 PM 1072 (0x0430)
SuccessCodeList: 0 3010 TSManager 4/15/2014 12:03:48 PM 1072 (0x0430)
(Sorry I cannot post the entire log file because it is too big.
Thanks in advance!
All replies (8)
Tuesday, April 15, 2014 6:49 PM âś…Answered | 1 vote
<![LOG[Input Error: Can not find script file "D:\SMSTaskSequence\Packages\PDC00001\Scripts\ZTISCCM.wsf".]LOG]!><time="12:04:16.086+300" date="04-15-2014" component="InstallSoftware" context="" type="1" thread="1256" file="runcommandline.cpp:34">
<![LOG[Command line returned 1
That line is interesting for two reasons:
- Usually the 00001 package is a boot image.
- It can't find an MDT script.
My guess now is that you configured the boot image in the Use Toolkit Package as package, instead of the MDT Toolkit package.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude
Tuesday, April 15, 2014 6:26 PM
These log snippets don't seem to be relevant as they don't mention any error code... Please post more relevant pieces and provide some information about your task sequence.
Just a wild guess, did you create a MDT Toolkit package and is that the package used in this step?
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude
Tuesday, April 15, 2014 6:42 PM
These log snippets don't seem to be relevant as they don't mention any error code... Please post more relevant pieces and provide some information about your task sequence.
Just a wild guess, did you create a MDT Toolkit package and is that the package used in this step?
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude
I was just sitting here wondering if it could be a problem with the MDT Toolkit. Yes, I did create the task sequence with MDT. I just created a generic Windows 7 task sequence without MDT and it appears to be working.
Is MDT not the "best practices" way of doing it? Or are there known issues doing it that way??
I just uploaded the entire log to box.com. Here is the link to see it:
https://app.box.com/s/k2oqtg13m67nsdj99sum
Tuesday, April 15, 2014 8:06 PM
Sorry if this is dumb, but what do you mean by "you configured the boot image in the Use Toolkit Package as package"?
Tuesday, April 15, 2014 8:13 PM | 1 vote
Edit the task sequence and navigate to the Use Toolkit Package step. Now check with the Toolkit package which package is configured.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude
Tuesday, April 15, 2014 8:23 PM
Edit the task sequence and navigate to the Use Toolkit Package step. Now check with the Toolkit package which package is configured.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude
Thanks for the instructions.
Yes, when I do that, the Toolkit Package is "Configuration Manager Client Package."
I remember choosing that option when I was going through the Task Sequence setup. There were 2 packages pre-installed (that one and the other one that reads Upgrade).
The option to "Create a new Microsoft Deployment Toolkit Files package" is grayed out because I am using ADK 8.0.
I am somewhat at a stand-off with the version of ADK because I am using SCCM 2012 SP1 (which is not supported by ADK 8.1)
Tuesday, April 15, 2014 8:29 PM
Well, if you want to use that step, you need the MDT Toolkit step... or leave it out if you're not using any other MDT steps.
Also note that if you really want to use that step, you could use a different workstation and install the ConfigMgr console including MDT and the necessary ADK version so you can create the MDT Toolkit package. Creating the package is a console thing and after the package is created it can just be re-used.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude
Tuesday, April 15, 2014 8:32 PM
Thanks for all of your help! I really appreciate it!