Toolkit Error During Beginning of OSD TS

[BzowK]

Hello All -

Tomorrow morning, I must have a TS ready which will do the following to existing, production XP machines:

1. Back up User Settings / Files (USMT)

2. Clean drive & partition

3. Apply our current Gold Image (Win7 x64)

4. Restore User Settings captured in step 1.

It would be gravy on top to also be able to add other applications during the process automatically. Therefore, I opened up MDT's UDI Wizard and got everything the way I want it. I then saved the 2 files it created as UDIWizard_Config.*, copied them over the exiting ones in my Toolkit folder, and updated my DPs.

I created a new "User Driven Installation Replace Task Sequence" which is only a few general steps, then edited it only to add the 4 environment variables needed by UDI.

The Issue

Every time I run the TS, it errors out soon after selecting which TS I want to use - at the "Use Toolkit Package" step - with Error code3 0x800700A1. I looked through the smsts.log file and see the below errors:

- Failed to save environment to (80070057)

- Failed to save the current environment block. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance. The parameter is incorrect. (Error: 80070057; Source: Windows)

- Failed to persist execution state. Error 0x(80070057)

- Failed to save execution state and environment to local hard disk

The above 4 are repeated 3-4 times followed by the below...

- Failed to resolve the source for SMS PKGID=BBS000EE, hr=0x800700a1 (Toolkit Package)

- Install Software failed to run command line, hr=0x800700a1

- Failed to run the action: Use Toolkit Package. The specified path is invalid. (Error: 800700A1; Source: Windows)

Resolution?

Initial research said it was due to lack of mass storage drivers in my boot image - even though I'm running the TS in new Hyper-V VMs. Still, I added many drivers (hdc class) to my boot image, updated dp, recreated boot ISO for VM, and even recreated TS. Still got same error.

The smsts.log file is attached

I've got to get this done somehow tonight - Help!

smsts.log

[Rocket Man]

What about your network access account does it have rights to where you are backing up the USMT files?

 

Rocket Man

[Rocket Man]

Here is some more info on this.....A direct quote from the guide:

 

""Ok looks like have cracked it. In my advertisement settings I had to change "how clients interact with distribution points to retrieve content from packages reffered by the task sequence"

I have the following set

"Access content directly from a distribtioin point when needed by running the task sequence"

and have ticked

"When no local distribution point is available, use a remote distribution point"

Still doesnt let me know why it wouldnt download and run locally on some systems. Anyway should do the trick

Thanks for help""

 

This can be found here:

 

http://social.technet.microsoft.com/Forums/en-US/configmgrosd/thread/b0f3d672-c9f3-4bb3-9d97-0f958bad2950/

[BzowK]

Yes - Also... here's an update...

 

I decided to start with something new, so did the following...

 

1. Created a standard SCCM task sequence using "Install an existing image package"

2. Set it up to use my Gold Image, general KMS product key, local admin password, & join domain with known good account.

3. At configuration state migration page, selected USMT package and had everything checked - saved to state migration point - not locally, though

4. No applications nor updates installed

5. Edited TS and checked "Migrate domain and workgroup membership" and couple of small things like user & company name

6. Opened a fairly new XP VM and added a couple of icons to the desktop, a folder to the root, and a file inside of it.

7. Deployed and started TS on that Hyper-V VM

 

I was able to run the TS successfully and ended up at Ctrl-Alt-Del. Unfortunatly, NOTHING migrated. None of the shortcuts, folders, profiles - not even the computer hostname. Also looked in Migration Store Role share. Nothing - empty.

 

SMSTS.log only mentioned USMT twice in a search and I don't know which log to really check for.

 

Any ideas? Thanks!

[Ariendg]

We're also experincing big problems with Error 0x800700A1.

It looks like the mass storage driver is working because diskpark can list a disk.

The error is not showing up on most of the older systems. Download content locally is working fine here. The new systems with latest intel storage controller, mostly SSD (and UEFI?) are having this issue.

 

Error 0x800700A1 when using MDT Toolkit and when downloading another bootimage after selecing other TS we get 0x8004005 on these systems.

 

Model: Fujitsu Q920 and running SCCM SP1 (CU2) with MDT 2012 Update 1 enviroment.

 

It looks the same like: http://heineborn.com/tech/sccm-2012-revodrive-and-0x800700a1/

Any new expert comments on this?

[Ariendg]

User did not specify local data drive	TSManager	17-4-2014 9:31:46	1132 (0x046C)
Volume C:\ has 127916363776 bytes of free space	TSManager	17-4-2014 9:31:46	1132 (0x046C)
Volume C:\ is not bootable	TSManager	17-4-2014 9:31:46	1132 (0x046C)
Volume D:\ is not a fixed hard drive	TSManager	17-4-2014 9:31:46	1132 (0x046C)
Volume X:\ is not a fixed hard drive	TSManager	17-4-2014 9:31:46	1132 (0x046C)
TSM root drive = 	TSManager	17-4-2014 9:31:46	1132 (0x046C)
We do not find an available volume to store the local data path	TSManager	17-4-2014 9:31:46	1132 (0x046C)
Set a global environment variable _SMSTSNextInstructionPointer=176	TSManager	17-4-2014 9:31:46	1132 (0x046C)
Set a TS execution environment variable _SMSTSNextInstructionPointer=176	TSManager	17-4-2014 9:31:46	1132 (0x046C)
Set a global environment variable _SMSTSInstructionStackString=175	TSManager	17-4-2014 9:31:46	1132 (0x046C)
Set a TS execution environment variable _SMSTSInstructionStackString=175	TSManager	17-4-2014 9:31:46	1132 (0x046C)
Save the current environment block	TSManager	17-4-2014 9:31:46	1132 (0x046C)
pszPath[0] != L'\0', HRESULT=80070057 (e:\nts_sccm_release\sms\framework\core\ccmcore\path.cpp,60)	TSManager	17-4-2014 9:31:46	1132 (0x046C)
Filesystem::Path::Add(sEnvPath, EnvDataFileName, sEnvPath), HRESULT=80070057 (e:\qfe\nts\sms\framework\tscore\environmentlib.cpp,655)	TSManager	17-4-2014 9:31:46	1132 (0x046C)
Failed to save environment to  (80070057)	TSManager	17-4-2014 9:31:46	1132 (0x046C)
TS::Environment::SharedEnvironment.saveEnvironment(szPath), HRESULT=80070057 (e:\nts_sccm_release\sms\client\tasksequence\executionengine\executionenv.cxx,842)	TSManager	17-4-2014 9:31:46	1132 (0x046C)
Failed to save the current environment block. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.
The parameter is incorrect. (Error: 80070057; Source: Windows)	TSManager	17-4-2014 9:31:46	1132 (0x046C)
SaveEnvironment(), HRESULT=80070057 (e:\nts_sccm_release\sms\client\tasksequence\executionengine\executionenv.cxx,420)	TSManager	17-4-2014 9:31:46	1132 (0x046C)
Failed to persist execution state. Error 0x(80070057)	TSManager	17-4-2014 9:31:46	1132 (0x046C)
Failed to save execution state and environment to local hard disk	TSManager	17-4-2014 9:31:46	1132 (0x046C)

As an addition a part of our smsts.log.

[Iroqouiz]

Whenever I get that error it almost always has something to do with the disk/partition, like it being corrupt. I've only seem it in lab VMs though, so I've always just run diskpart and cleaned disk 0.

[Ariendg]

Unfortunately this is not helping for us. We're doing manual diskpart select disk 0 -> Clean and Format for every deployment in the Initialization phase.

[Peter33]

This is actually a behavior i have seen on uninitialized SSD drives and even SATA drives and brand new Lenovo machines.

What i do is to check if the Computer has a drive wis enough free space on it (500MB) and if not running 2 powershell commands as first Action in the TS.

 

1) initialize-disk command to prepare the disk (throws an error if the disk is already initialized, but who cares)

2) clear-disk command (get rid of encrypted partitions / we do no state migration)

 

... just followed by a regular partitioning step

 

The first 2 steps require the powershell module to be present in your boot Image, but they have the benefit that they will also work if there is no space to save your diskpart config file.

[Ariendg]

These are the things we're already doing with the non-powershell equivalents commands. Diskpart can also initialize the disk.