USMT 3.0.1 and SCCM 2007 SP 1

myITforum.com Community Forum

Home Forums Blogs Live Support chat Search Articles Wiki FAQ Email Lists Register Login My Profile Inbox Address Book My Subscription My Forums

Photo Gallery Member List Search Calendars FAQ Ticket List Log Out

All Forums RSS Feed Subscription:

USMT 3.0.1 and SCCM 2007 SP 1

View related threads: (in this forum | in all forums)

Logged in as: Guest

Printable Version

All Forums >> [Management Products] >> System Center Products >> System Center Configuration Manager >> USMT 3.0.1 and SCCM 2007 SP 1

Page: [1]

Message

<< Older Topic Newer Topic >>

USMT 3.0.1 and SCCM 2007 SP 1 - 10/2/2008 11:14:59 AM

bwoodall

Posts: 50
Score: 0
Joined: 5/6/2008
Status: offline

I have gotten my lab fuctional in that PXE boot and standard advertisements for OS deployments work great. So I moved to the next step and that is capturing the user data and settings. I created a package from the .msi of USMT 3.0.1 which in turn imported 6 different programs. I then deleted all but the Per-system unattended and updated my distrubution points. I created a task (which works fine if your not using USMT) this task fails with an error code 0x00004005 on the client machine.

Does anyone know what could be causing this issue?

Post #: 1

RE: USMT 3.0.1 and SCCM 2007 SP 1 - 10/2/2008 11:56:56 AM

lcpc78

Posts: 84
Score: 0
Joined: 10/4/2007
Status: offline

When you create the package don't create it using the MSI, what that does is create a package to deploy USMT to the clients. What you need to do is install the USMT on your server. Than create a package pointing to the location where you installed the scanstate, loadstate etc. Don't create any programs and than it should work.

(in reply to bwoodall)

Post #: 2

RE: USMT 3.0.1 and SCCM 2007 SP 1 - 10/2/2008 2:19:00 PM

bwoodall

Posts: 50
Score: 0
Joined: 5/6/2008
Status: offline

It didn't error out on the capture and the scanstateprogress.log file states that the settings were captured successfully but the restore failed. The scanstate.log file is nothing but a sea of red and yellow. My storage point is located under the server share where all the other packages are stored so I would think network access shouldn't be an issue. Is there something in particular I need to look at such as another log file?

EDIT:

I found this article linked below so I will give it a try. This article is about storing the data on the client itself but not formating the system.

http://technet.microsoft.com/en-us/library/bb693594(printer).aspx

< Message edited by bwoodall -- 10/2/2008 2:47:26 PM >

(in reply to lcpc78)

Post #: 3

RE: USMT 3.0.1 and SCCM 2007 SP 1 - 10/2/2008 5:18:25 PM

jsandys

Posts: 551
Score: 17
Joined: 3/24/2005
From: San Antonio, TX
Status: offline

lcpc78 is correct. Do not create the USMT package using the msi, this will create a package to install USMT, not use it. You must install USMT somewhere and create the packag from the installed files. It has abolsutely nothing to do with where you're storing the state.

_____________________________

Jason
________________________________________
http://myitforum.com/cs2/blogs/jsandys/default.aspx

(in reply to bwoodall)

Post #: 4

RE: USMT 3.0.1 and SCCM 2007 SP 1 - 10/3/2008 12:15:30 AM

bwoodall

Posts: 50
Score: 0
Joined: 5/6/2008
Status: offline

Well I followed the article to the letter along with editing the task to include the %C:\MyLocalStateStore% and it didn’t work. I then created a folder named MyLocalStateStore on the client and still no success. The OS deployed as expected but didn’t restore the user’s settings.
So here is the deal. I have around 4,000 systems that we have finally got the ok to take local admin rights away from and the ok to redeploy a clean OS plus needed applications to but I would like to save the user’s My documents, Favorites and their PSTs.
Long story short after 5 years we have gotten the ok to “format c:” and run the network as it should be run. I am not asking anyone to spell out the combination. I am just asking for someone to point me in the direction so that the answer can be found. I have read and followed the MS book but I think it assumes that everyone is an expert on SCCM even though this is the first book to come out.
Again any direction is greatly appreciated.
OBTY lcpc78 was correct in not using the msi to build the package. It captured the info and stored it where I specified (to be safe it was stored where my other deployed apps were stored so access shouldn't be and issue) it just was not restored. This was pushing an OS to an in place test system.

(in reply to jsandys)

Post #: 5

RE: USMT 3.0.1 and SCCM 2007 SP 1 - 10/6/2008 12:38:34 PM

callen416

Posts: 40
Score: 0
Joined: 9/21/2005
Status: offline

BWOODALL,

Try a manual run of the scan and restore via 2 batch files. One to capture the settings and one to restore the files. See what develops...

(in reply to bwoodall)

Post #: 6