Peter van der Woude

Correct _SMSTSUserStatePath is a variable on its own that has a standard value(s) during the Task Sequence. If _SMSTSUserStatePath is not working for you, then you should create your own location. Just don't forget to create that location! This means you need two steps (instead of one): 1. Set State Store Location – Set Task Sequence Variable --> Example: %OSDStateStorePath% = C:\StateStore. 2. Create State Store Location – Run Command Line --> Example: cmd /c MKDIR %OSDStateStorePath%.

I just made a small post on my blog about Capturing User State with ConfigMgr vNext. Its really straight forward now! Take a look here: http://www.petervanderwoude.nl/post/ConfigMgr-vNext-It-just-gets-easier-and-easier.aspx

If you know your way around in ConfigMgr, then what are you nervous for???

Well... its a pretty straight forward proces... when the OSDStateStorePath is being used it wil be untouched during a disk wipe. For another Hardlink only example take a look here: http://www.petervanderwoude.nl/post/ConfigMgr-2007-USMT-40-and-using-Hard-Links.aspx For another Hardlink and Offline example take a look here: http://www.petervanderwoude.nl/post/Capture-User-Files-and-Settings-Offline-(WinPE)-or-Online-(FullOS)-with-ConfigMgr-2007.aspx

You have to set the State Store Location (OSDStateStorePath).

As far as I know that means something like "network path not found". So make sure that the location/ share exists.

The impact is that they are missing the default collections.... As the information is stored in the DB, I asume that with recreating collections and adding machines to it you 'll be fine. Take a look here for recreating the All Systems collection: http://blogs.msdn.com/b/vinpa/archive/2010/03/17/how-to-restore-the-all-systems-collection.aspx

It has to be in the System container of the AD and it needs full rights at System Management container to be able to write its information in it.

Then you should be fine with a Software Update on the central location and DPs on the remote locations.

Did you check the ccmsetup folder on the client?

As far as I known I say that this isn't a critical error (and happens a lot). Also the installation just continues after it.

It all depends on why you have all those WSUS servers on the remote sites... The SCCM Clients can all look at the same WSUS server (with Software Update Point) as long as its within the same SCCM Site. The SCCM Clients can download the Updates from the Distribution Points (eventually at the remote sites).

Did you check the errormessages?

Just create a Task Sequence Variable that only gets set when _SMSTSInWinPE equals TRUE. Then use this variable to make the Capture (Restore and Partition) -Step start or not. Just keep in mind that by doing it this way you can't use an Offline Capture... Just use the same Task Sequence Variable as mentioned before. The last one is a bit harder to implement in the same Task Sequence... Probebly a HTA as mentioned by Niall is the best way.

If you don't want to copy it locally then the important part of the batchfile that I use is %~dp0, see here: REM ====================================================== REM VARIABLE -1- OSDStateStorePath = %1 REM VARIABLE -2- Architecture = %2 REM ====================================================== REM ====================================================== REM RUN USMTUtils REM ====================================================== echo y| "%~dp0%2\usmtutils.exe" /rd "%1" REM ====================================================== REM EXIT Errorlevel REM ====================================================== EXIT /b %errorlevel%

In Native Mode you need to use multiple certicates. Take a look at this post to see the basic certificates that you need in Native Mode: http://www.petervanderwoude.nl/post/Certificates-for-ConfigMgr-Native-Mode.aspx

SCCM only has an 32bits client. Check the client.msi.log on the client for more information. This log can be found on a 64bit machine in C:\Windows\ccmsetup

I am running a Windows Server 2008 R2 box with Hyper-V and the following specs: Motherboard: Gigabyte GA-P35-DS3R CPU: Intel Core 2 Quad Q6600 2,4GHz Socket 775 Memory: 8Gb Kingston HyperX DDR2 Nic: Onboard + External Disk1: 2x Samsung SpinPoint 320Gb (Mirrored) Disk2: External Western Digital My Book Mirror 1Tb And indeed with me the harddisks are slowing it down too...

Change the Boundaries of the BDP's to fast and protect the BDP's with these Boundaries.

When your Primary DP is protected with a Boudary, which includes your whole AD, means that all clients with look at that DP to download content.

Like this its good, but in a previous post you still had two CHICAGO Boundaries...

As an addon to your question about the boundaries, only add the Boundary of an AD Site to the Primary Site that has to manage the clients. So remove the CHICAGO Boundary for the R01 Site.

Nope, you can just add it to an existing AD.

It does not support a real upgrade like that.... But it is possible to use SCCM in combination with USMT to do a computer-refresh. This would mean capturing the user data, wipe the disk, install W7 and restore user data.

To deploy updates from the Task Sequence with the standard Instal Software Updates -step, you need to integrate WSUS with SCCM. Then you can advertise the Software Updates to the collection that includes you machine.