When using Hard Links for User State Migration, attempting to remove the OSDStateStorePath folder after restoring the users data in a Task Sequence may fail or appear to hang.

Note: This is in reference to the steps listed in this article: http://technet.microsoft.com/en-us/library/ee344267.aspx

The command .\%PROCESSOR_ARCHITECTURE%\usmtutils.exe /rd %OSDStateStorePath% may appear to hang unless you configure a timeout value on the Run Command Line step, and/or it may fail with one of the following errors or warnings depending on how the Task Sequence Advertisement is configured:

SMSTS.log may show one of the following errors or warnings.

Warning: This command is going to delete the following list of path(s).
Please review before continuing...
C:\UserState
Are you sure you want to proceed (Y/N)?

If you do not configure a timeout value, it will hang at this point, however, since you cannot see the prompt for user input you cannot continue.

Or, if you configure a timeout value on the Run Command Line step, you may see this error in the SMSTS.log

This operation returned because the timeout period expired. (Error: 800705B4; Source: Windows)

The amount of detail you see in the log will also depend on how you have configured the Advertisement for the Task Sequence. If the Advertisement is configured to Download content locally when needed by running the task sequence (commonly referred to as Download and run locally) then you will not see as much detail on the command line being run. However, if you select Access content directly from a distribution point when needed by the running task sequence (commonly referred to as Run from DP), then you will get more details on the command line being run, and it may show the prompt "Are you sure you want to proceed (Y/N)?" in the SMSTS.log. If you tried adding the cmd.exe /c echo Y | in front of the command and still try to use the Run from DP option, the command will fail with a Path not found error.

Cause

There are two things we are trying to overcome with this issue when running the USMTUTILS.EXE command from a ConfigMgr 2007 OS Deployment Task Sequence:

1. This command requires user input in order to delete the OSDStateStorePath folder and does not seem to support any command line switches to bypass this prompt.

2. Although we are able to use the echo command to pass the Y for yes to the command line step using cmd.exe /c echo Y | "command", this will only work if the Advertisement is configured to Download content locally when needed by running the task sequence (commonly referred to as Download and run locally). If you select Access content directly from a distribution point when needed by the running task sequence (commonly referred to as Run from DP) this step will fail. This is due to the echo command we are needed to pass, it is a built in command in the command interpreter, cmd.exe, so that is why we must specify the cmd.exe /c in the beginning of the command line, as this is not present in the package on the DP.

Resolution

Note: This will only work if the Advertisement is configured to Download content locally when needed by the running task sequence (commonly referred to as Download and run locally). If you select Access content directly from a distribution point when needed by the running task sequence (commonly referred to as Run from DP) this step will fail.  This is because  the echo command we need  to pass is a built in command in the command interpreter, cmd.exe,  We must specify the cmd.exe /c in the beginning of the command line since this is not present in the package on the DP.

NOTE: Data Loss Warning, do not select Continue on error on the Restore User Files and Settings!  It is also important to not select “Continue on error” on the Options tab, or  “Continue if some files cannot be restored” on the “Properties” tab of the “Restore User Files and Settings” task sequence step, Selecting these options will allow the next task sequence step to delete the User Files and Settings even if they are not successfully restored.

This resolution assumes you have already successfully configured and tested an OS Deployment with ConfigMgr 2007 SP2 using Hard Links with USMT 4.0 . If not, follow the steps to configure the OSDStateStorePath, OSDMigrateAdditionalCaptureOptions, and OSDMigrateAdditionalRestoreOptions variables for using Hard Links with USMT 4.0 in ConfigMgr 2007 SP2:

http://technet.microsoft.com/en-us/library/ee344267.aspx

To add a step that should successfully remove the User State folder after the User Files and Settings are restored, follow these steps:

1. In the Task Sequence Editor, after the Restore User State step, click Add, navigate to General, and then click Run Command Line action. Type the following in the Run Command Line action:

2. Type the following in the Command line field:

cmd.exe /c echo Y | ".\%PROCESSOR_ARCHITECTURE%\usmtutils.exe" /rd "%OSDStateStorePath%"

3. Select the Package check box.

4. In the Select a Package dialog box, browse to the USMT 4.0 package, and then click OK.

Although we are able to use the echo command to pass the Y for yes to the command line step using the command line step:

cmd.exe /c echo Y | ".\%PROCESSOR_ARCHITECTURE%\usmtutils.exe" /rd "%OSDStateStorePath%"

Clifton Hughes | Senior System Center Support Engineer

The App-V Team blog: http://blogs.technet.com/appv/
The WSUS Support Team blog: http://blogs.technet.com/sus/
The SCMDM Support Team blog: http://blogs.technet.com/mdm/
The ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
The SCOM 2007 Support Team blog: http://blogs.technet.com/operationsmgr/
The SCVMM Team blog: http://blogs.technet.com/scvmm/
The MED-V Team blog: http://blogs.technet.com/medv/
The DPM Team blog: http://blogs.technet.com/dpm/
The OOB Support Team blog: http://blogs.technet.com/oob/
The Opalis Team blog: http://blogs.technet.com/opalis
The Service Manager Team blog: http: http://blogs.technet.com/b/servicemanager
The AVIcode Team blog: http: http://blogs.technet.com/b/avicode
The System Center Essentials Team blog: http: http://blogs.technet.com/b/systemcenteressentials

Consider the following scenario:

• You create a deployment package on a Microsoft System Center Configuration Manager 2007 Service Pack 2 (SP2) site server.
• You create a program in the package. The name of the program contains extended ASCII characters.
• You create a task sequence, and you add an Install Software step to the task sequence.
• You select the Install multiple applications option, and you configure the Base variable name setting to include the program that contains extended ASCII characters in the Install Software step.
• You deploy the task sequence to a client computer.

This issue occurs because an incorrect data type is used to handle the program name that contains extended ASCII characters.

For more details and a downloadable hotfix for this issue see the following:

KB2507187 - Program does not run in a task sequence on a System Center Configuration Manager 2007 SP2 client if the program name contains extended ASCII characters

J.C. Hornbeck | System Center Knowledge Engineer

The App-V Team blog: http://blogs.technet.com/appv/
The WSUS Support Team blog: http://blogs.technet.com/sus/
The SCMDM Support Team blog: http://blogs.technet.com/mdm/
The ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
The SCOM 2007 Support Team blog: http://blogs.technet.com/operationsmgr/
The SCVMM Team blog: http://blogs.technet.com/scvmm/
The MED-V Team blog: http://blogs.technet.com/medv/
The DPM Team blog: http://blogs.technet.com/dpm/
The OOB Support Team blog: http://blogs.technet.com/oob/
The Opalis Team blog: http://blogs.technet.com/opalis
The Service Manager Team blog: http: http://blogs.technet.com/b/servicemanager
The AVIcode Team blog: http: http://blogs.technet.com/b/avicode
The System Center Essentials Team blog: http: http://blogs.technet.com/b/systemcenteressentials
The Server App-V Team blog: http: http://blogs.technet.com/b/serverappv

I recently encountered a question from a customer who wanted to be able to set the computer name, and also be able to have their Desktop Technicians select software to be installed during an Operating System Deployment for their upcoming Windows 7 refresh over Windows XP.  I walk you through the basics step by step to do this with a UDI Task Sequence over on the TechNet Wiki:

http://social.technet.microsoft.com/wiki/contents/articles/configmgr-2007-basic-user-driven-installation-task-sequence-step-by-step.aspx

Clifton Hughes | Support Escalation Engineer

The App-V Team blog: http://blogs.technet.com/appv/
The WSUS Support Team blog: http://blogs.technet.com/sus/
The SCMDM Support Team blog: http://blogs.technet.com/mdm/
The ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
The SCOM 2007 Support Team blog: http://blogs.technet.com/operationsmgr/
The SCVMM Team blog: http://blogs.technet.com/scvmm/
The MED-V Team blog: http://blogs.technet.com/medv/
The DPM Team blog: http://blogs.technet.com/dpm/
The OOB Support Team blog: http://blogs.technet.com/oob/
The Opalis Team blog: http://blogs.technet.com/opalis
The Service Manager Team blog: http: http://blogs.technet.com/b/servicemanager
The AVIcode Team blog: http: http://blogs.technet.com/b/avicode
The System Center Essentials Team blog: http: http://blogs.technet.com/b/systemcenteressentials
The Server App-V Team blog: http: http://blogs.technet.com/b/serverappv

I have had a couple of cases recently that involve running a task sequence from the Run Advertised Program (RAP) Control Panel applet which has a large number of software package installation steps (usually over 200).  What happens in these cases is that you will see timeout errors in the cas.log and execmgr.log on the machines in question. These errors resemble an issue where the content is not available on the Distribution Point (DP) but in each case it was reported that the task sequences could be successfully run within WinPE which indicates that this content is actually present on the DPs in question.

If you run into this specific scenario then you can change the UIContentLocationTimeoutInterval variable in the site control file from the default of 120 seconds to a value much greater such as 15-30 minutes.  The UIContentLocationTimeoutInterval variable is a property in the root\ccm\Policy\Machine namespace that has a default value of 120 seconds (2 minutes) but this may not long enough for a task sequence with a large number of software installation steps.  In these cases I have found that if I increase this to a higher value (e.g. 900 seconds or 15 minutes) then the problem no longer occurs when running this from within the RAP. 

To do this complete the following steps to edit the site control file:

1. Stop the smsexec service on the site server
2. Edit the site control file and change the following to a higher value:

PROPERTY <UI Content Location Timeout Interval><REG_DWORD><><120>

3. Restart the smsexec service and make sure you update policy on the client.
4. You can check the value on the local client using wbemtest and connecting to root\sms\policy\machine.

Once complete, the Task Sequence should now complete successfully.

For testing purposes, you can compile the following MOF file on a client to update the actual policy on a single machine. This is optional and serves only to verify that this is in fact the issue you’re encountering:

1. Open wbemtest on the machine you want to test.
2. Open the root\ccm\Policy\Machine namespace.
3. Navigate to ccm_softwareDistributionClientConfig.
4. Select UIcontentLocationTimeoutInterval
5. Select instances.
6. Double click the instances of UIcontentLocationTimeoutInterval.
7. Click Show MOF. 

This should look something like the mof.txt file attached.

8. Edit this file and change the line below to a value such as 900

UIContentLocationTimeoutInterval = 120;

9. Add the following line to the top of the mof file (see the attached file as an example)

#pragma namespace("\\\\.\\root\\ccm\\policy\\machine\\actualconfig")

10. Save this file as a .mof file and move this to the machine that you want to test.
11. Open a CMD prompt and run the following:

Mofcomp.exe mof.mof

12. Check to make sure this value has been changed in WMI using the steps outlined above.

Sample file:

Hope this helps,

Luke Ramsdale | Support Escalation Engineer

The App-V Team blog: http://blogs.technet.com/appv/
The WSUS Support Team blog: http://blogs.technet.com/sus/
The SCMDM Support Team blog: http://blogs.technet.com/mdm/
The ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
The SCOM 2007 Support Team blog: http://blogs.technet.com/operationsmgr/
The SCVMM Team blog: http://blogs.technet.com/scvmm/
The MED-V Team blog: http://blogs.technet.com/medv/
The DPM Team blog: http://blogs.technet.com/dpm/
The OOB Support Team blog: http://blogs.technet.com/oob/
The Opalis Team blog: http://blogs.technet.com/opalis
The Service Manager Team blog: http: http://blogs.technet.com/b/servicemanager
The AVIcode Team blog: http: http://blogs.technet.com/b/avicode
The System Center Essentials Team blog: http: http://blogs.technet.com/b/systemcenteressentials
The Server App-V Team blog: http: http://blogs.technet.com/b/serverappv

We blogged this issue a couple weeks ago but now there’s a hotfix available to resolve the issue:

=====

Consider the following scenario:

• You create a task sequence on a Microsoft System Center Configuration Manager 2007 Service Pack 2 (SP2) site server.
• You add lots of Install Software steps to the task sequence.  For example, you add more than 100 Install Software steps to the task sequence.
• You create an assignment that makes the task sequence mandatory when you advertise the task sequence to a client computer.

In this scenario, the task sequence does not run on the client computer.

Note This issue does not occur if the task sequence is assigned as an optional advertisement.

CAUSE

This issue occurs because the large number of Installing Software steps in the task sequence creates a heavy workload for the location service.
When the location service has a heavy workload, it cannot process all the callbacks for the location requests in a 10-minute window. Therefore, the issue that is mentioned in the "Symptoms" section occurs.

=====

For all the details as well as a download link please see the the following Knowledge Base article:

KB2516517 - Task sequence does not run if it has lots of Install Software steps in System Center Configuration Manager 2007 SP2

J.C. Hornbeck | System Center Knowledge Engineer

The App-V Team blog: http://blogs.technet.com/appv/
The WSUS Support Team blog: http://blogs.technet.com/sus/
The SCMDM Support Team blog: http://blogs.technet.com/mdm/
The ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
The SCOM 2007 Support Team blog: http://blogs.technet.com/operationsmgr/
The SCVMM Team blog: http://blogs.technet.com/scvmm/
The MED-V Team blog: http://blogs.technet.com/medv/
The DPM Team blog: http://blogs.technet.com/dpm/
The OOB Support Team blog: http://blogs.technet.com/oob/
The Opalis Team blog: http://blogs.technet.com/opalis
The Service Manager Team blog: http: http://blogs.technet.com/b/servicemanager
The AVIcode Team blog: http: http://blogs.technet.com/b/avicode
The System Center Essentials Team blog: http: http://blogs.technet.com/b/systemcenteressentials
The Server App-V Team blog: http: http://blogs.technet.com/b/serverappv

After creating the article ConfigMgr 2007 Basic User Driven Installation Task Sequence Step by Step, I wanted to follow up with another article covering the Application Discovery and Mapping features in a UDI Task Sequence. This cool feature allows you to discover the applications installed on your Windows Clients during deployment of Windows 7, and based on mappings you configure, installs Windows 7 with the new versions, or other applications, that you specified in the UDI Wizard Designer. I walk you through how to implement this here on the TechNet Wiki:

http://social.technet.microsoft.com/wiki/contents/articles/configmgr-2007-application-mapping-with-a-user-driven-installation-task-sequence.aspx

Clifton Hughes | Support Escalation Engineer

The App-V Team blog: http://blogs.technet.com/appv/
The WSUS Support Team blog: http://blogs.technet.com/sus/
The SCMDM Support Team blog: http://blogs.technet.com/mdm/
The ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
The SCOM 2007 Support Team blog: http://blogs.technet.com/operationsmgr/
The SCVMM Team blog: http://blogs.technet.com/scvmm/
The MED-V Team blog: http://blogs.technet.com/medv/
The DPM Team blog: http://blogs.technet.com/dpm/
The OOB Support Team blog: http://blogs.technet.com/oob/
The Opalis Team blog: http://blogs.technet.com/opalis
The Service Manager Team blog: http: http://blogs.technet.com/b/servicemanager
The AVIcode Team blog: http: http://blogs.technet.com/b/avicode
The System Center Essentials Team blog: http: http://blogs.technet.com/b/systemcenteressentials
The Server App-V Team blog: http: http://blogs.technet.com/b/serverappv

Here’s another good KB article we published today. If you’re seeing an issue where ConfigMgr fails to find a task sequence then this one is for you:

=====

Symptoms

When trying to start a System Center Configuration Manager 2007 (ConfigMgr 2007) OSD Task Sequence on a client, ConfigMgr 2007 fails to find a Task Sequence to run on the PC.

1. If booting from boot media, the follow message well appear after booting into WinPE:
   There are no task sequences available for this computer.
   Examining the SMSTS.log obtained from X:\Windows\Temp\SMSTSLog will show the following message:
   No assigned task sequence. TSMBootstrap
   Setting wizard error: There are no task sequences available for this computer. TSMBootstrap
   
2. If booting from PXE, the PXE boot screen will show the following message:
   TFTP Download: smsboot\<arch>\abortpxe.com
   PXE Boot aborted. Booting to the next device...
   The SMSPXE.log on the PXE Service Point server will contain the following messages at the time the PXE boot was attempted:
   MAC=<Mac_Address> SMBIOS GUID=<SMBIOS_GUID> > Device found in the database. MacCount=x GuidCount=y smspxe
   ProcessDatabaseReply: No Advertisement found in Db for device smspxe
   

If the PC is Known (either an existing client or prestaged via the Import Computer Information Wizard), it has been verified that the Task Sequence Advertisement is targeted to a Collection that the PC is a member of.

If the PC is Unknown, it has been verified that the Task Sequence Advertisement is targeted to a Collection with the Unknown Computer objects (x64 Unknown Computer and/or x86 Unknown Computer) and that the PC is truly unknown and does not exist in the ConfigMgr database.

Cause

This problem can be caused by more than one PC in the environment having the same SMBIOS GUID. ConfigMgr 2007 refers to the SMSBIOS GUID as System UUID. Similar to a MAC Addresses being unique to a NIC card, the SMBIOS GUIDs should also be unique on each PC. Two PCs should not have the same SMBIOS GUID. The SMBIOS GUID is stored in the PC's BIOS.

The problem occurs because when the ConfigMgr database is queried for available Task Sequence that are advertised to that PC, it does so first by using the PC's SMBIOS GUID. Each record in the ConfigMgr database records the PC's SMBIOS GUID under the attribute System UUID. If it does not match a record with the SMBIOS GUID, it then uses the MAC Address instead.

However, if multiple PCs have the same SMBIOS GUID in the environment, when the query on the SMBIOS GUID is done on the ConfigMgr database, it may find the record for a PC other than the one that the Task Sequence is advertised to. If the Task Sequence is not also advertised to the PC that it found, it will return back that there are no task sequences available for the computer.

Note Do not confuse the SMBIOS GUID with the SMS GUID. They are two separate, different, and distinct items. The SMBIOS GUID is a unique hardware identifier used universally, whereas the SMS GUID is a unique ConfigMgr client ID used exclusively by SMS/ConfigMgr.

To see if the problem exists in the environment, create a query or collection in ConfigMgr based on the suspected duplicate SMBIOS GUID using the System UUID attribute. If more than one PC has the same SMBIOS GUID, then the problem exists.

To obtain the SMBIOS GUID from a PC having the problem, use one of the below methods:

• At a command prompt, run the command:
  wmic
  When the prompt
  wmic:root\cli>
  
  appears, type in the command:
  csproduct get uuid
  The SMBIOS GUID for the PC should be displayed.
  Please note that in scenarios where the PC does not have a bootable OS, the PC can be boot into WinPE via PXE or boot media, and then the above commands run from a command prompt window running in WinPE.
• On most PCs the SMBIOS GUID appears next to GUID: at the PXE boot screen. To pause the PXE boot screen so that the SMBIOS GUID can be copied down, hit the Pause/Break key on the keyboard while at the PXE boot screen. This can be done even if a PXE server does not exist in the environment. However to view the PXE boot screen, PXE booting must be enabled in the BIOS of the PC and either F12 may need to be hit to get to the PXE boot screen or the NIC may need to be temporarily set as the first boot device on the PC.
• For PCs that successfully boots into WinPE from boot media but fails to receive an advertised Task Sequence, the SMBIOS GUID will be displayed in the SMSTS.log next to the line
  Setting SMBIOS GUID =
  
• For PCs that do not successfully boot from PXE, the SMSPXE.log on the server hosting the PXE Service Point can be examined for the PC's SMBIOS GUID. The line that contains this information will be something as follows:
  MAC=<Mac_Address> SMBIOS GUID=<SMBIOS_GUID> > Device found in the database. MacCount=x GuidCount=y
  Note: Ignore the lines in the SMSPXE.log with all Fs for the MAC Address:
  MAC=FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF SMBIOS GUID=<SMBIOS_GUID> > Device not found in the database. smspxe
  These lines are the PXE Service Point performing a self-check on itself by performing a PXE request to itself to make sure the PXE Service Point is up and operational.

To create a query based Collection that finds all PCs with a particular SMBIOS GUID:

1. In the ConfigMgr console, navigate to "Site Database" --> "Computer Management" --> "Collections"
2. Right click on "Collections" and choose "New Collection"
3. On the "General" page of the "New Collection Wizard", give the Collection a name next to the "Name:" textbox and then click on the "Next >" button.
4. On the "Membership Rules" page of the "New Collection Wizard", click on the yellow Query icon.
5. Under the "General" tab of the "Query Rule Properties" window, give the query a name next "Name:" textbox and then click on the "Edit Query Statement..." button.
6. In the "Query Statement Properties" window, click on the "Criteria" tab, and then click on the yellow starburst button.
7. In the "Criterion Properties" window, make sure that the "Criterion Type:" is set to "Simple value" and then click on the "Select..." button.
8. In the "Select Attribute" window:
   • Next to "Attribute class:", select "System Resource"
   • Next to "Alias as:", leave at the default of "<No Alias>".
   • Next to "Attribute:", choose "System UUID"
9. In the "Select Attribute" window, click on the "OK" button.
10. In the "Criterion Properties" window, make sure that the "Operator:" is set to "is equal to".
11. In the "Criterion Properties" window, next to the "Value:" text box, enter in the full SMBIOS GUID obtained from the PC. Make sure to enter all 32 characters and the 4 dashes that are part of the SMBIOS GUID.
12. In the "Criterion Properties" window, click on the "OK" button.
13. In the "Query Statement Properties" window, click on the "OK" button.
14. In the "Query Rule Properties" window, click on the "OK" button.
15. On the "Membership Rules" page of the "New Collection Wizard", click on the "Next >" button.
16. On the "Advertisements" page of the "New Collection Wizard", click on the "Next >" button.
17. On the "Security" page of the "New Collection Wizard", click on the "Next >" button.
18. When the "New Collection Wizard" completes, click on the "Close" button.

The newly created Collection should display all of the PCs affected by the duplicate SMBIOS GUID. Repeat the above steps if more than one set of duplicate SMBIOS GUIDs exist in the environment.

Resolution

Please note that this problem is caused by an OEM vendor not adhering to industry standards. It is not an issue with ConfigMgr.

There are two possible solutions to the problem

1. Obtain a BIOS update or utility from the OEM hardware vendor that fixes the duplicate SMBIOS GUIDs and gives each PC a unique SMBIOS GUID.
2. To work around the problem, use the BannedGUIDsregistry entry of WDS as described in the following TechNet articles:Windows Deployment Services Registry Entries
   http://technet.microsoft.com/en-us/library/cc733103(WS.10).aspx#banned
   How PXE Requests Work
   http://technet.microsoft.com/en-us/library/cc725614(WS.10).aspx#Banned
   The BannedGUIDs registry entry "ignores" any SMBIOS GUIDs that have been entered under the key and instead uses the PC's MAC Address.
   Please note that this solution does not actually fix the root cause of the problem and only works around it. When possible, it is recommended to use Solution #1. However in environments where there may be a large amount of duplicate SMBIOS GUIDs or where a BIOS fix or utility is not currently available from the OEM vendor, the BannedGUIDs registry can be used to work around the issue until the duplicate GUIDs issue can be permanently resolved.

For both solutions, use the methods described in the Cause section to discover what PCs are affected by duplicate SMBIOS GUIDs.

=====

For the most current version of this article please see the following:

2591483: No Assigned Task Sequence when initiating deployments caused by duplicate SMBIOS GUIDs in System Center Configuration Manager 2007

J.C. Hornbeck| System Center Knowledge Engineer

App-V Team blog: http://blogs.technet.com/appv/
AVIcode Team blog: http://blogs.technet.com/b/avicode
ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
DPM Team blog: http://blogs.technet.com/dpm/
MED-V Team blog: http://blogs.technet.com/medv/
OOB Support Team blog: http://blogs.technet.com/oob/
Opalis Team blog: http://blogs.technet.com/opalis
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
OpsMgr Support Team blog: http://blogs.technet.com/operationsmgr/
SCMDM Support Team blog: http://blogs.technet.com/mdm/
SCVMM Team blog: http://blogs.technet.com/scvmm
Server App-V Team blog: http://blogs.technet.com/b/serverappv
Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials
WSUS Support Team blog: http://blogs.technet.com/sus/

Here’s a KB article we published today on ConfigMgr 2007. This one describes a hotfix/update we released that addresses an issue where a Task sequence fails with an "0x80004005" error code in System Center Configuration Manager 2007 SP2:

=====

Consider the following scenario:

• You create a prestaged installation media in System Center Configuration Manager 2007 R3.
• You create a task sequence on a System Center Configuration Manager 2007 Service Pack 2 (SP2) site server.
• You configure the task sequence to use the prestaged installation media to deploy an operating system to a computer.
• The boot image in the prestaged installation media is newer than the assigned boot image in the task sequence.

In this scenario, the newer boot image is not installed and the whole task sequence fails. Additional, the following error code is logged in the Smsts.log file:

Failed to install WinPE. Code(0x80004005)

=====

For the most current version of this article and to download the hotfix that corrects this issue please see the following:

2586709 : Task sequence fails with an "0x80004005" error code in System Center Configuration Manager 2007 SP2 (http://support.microsoft.com/kb/2586709)

J.C. Hornbeck| System Center Knowledge Engineer

App-V Team blog: http://blogs.technet.com/appv/
AVIcode Team blog: http://blogs.technet.com/b/avicode
ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
DPM Team blog: http://blogs.technet.com/dpm/
MED-V Team blog: http://blogs.technet.com/medv/
OOB Support Team blog: http://blogs.technet.com/oob/
Opalis Team blog: http://blogs.technet.com/opalis
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
OpsMgr Support Team blog: http://blogs.technet.com/operationsmgr/
SCMDM Support Team blog: http://blogs.technet.com/mdm/
SCVMM Team blog: http://blogs.technet.com/scvmm
Server App-V Team blog: http://blogs.technet.com/b/serverappv
Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials
WSUS Support Team blog: http://blogs.technet.com/sus/

Here’s another good KB article we published today on ConfigMgr 2007. This one describes an issue you may run into with USMT restores and how to fix it:

=====

Symptoms

When using the prestaged media feature in System Center Configuration Manager 2007 R3 to build new machines, the USMT (User State Migration Tool) restore step fails. The task sequence may still be successful but the user state is never migrated. You may also receive the following information in the smsts.log file:

==============================[ OSDSMPClient.exe ]==============================

OSDSMPClient <date/time> 3832 (0x0EF8)
Command line: "osdsmpclient.exe" /restore OSDSMPClient <date/time> 3832 (0x0EF8)
MigrationID not found in Environment. OSDSMPClient <date/time> 3832 (0x0EF8)
Encryption key not found in Environment. OSDSMPClient <date/time> 3832 (0x0EF8)
SMP not found in Environment. OSDSMPClient <date/time> 3832 (0x0EF8)
Client joined to the <domain> domain. OSDSMPClient <date/time> 3832 (0x0EF8)
Client is a member of the <siteName> site. OSDSMPClient <date/time> 3832 (0x0EF8)
GetAdaptersAddressess entry point is supported. OSDSMPClient <date/time> 3832 (0x0EF8)
DhcpGetOriginalSubnetMask entry point is supported. OSDSMPClient <date/time> 3832 (0x0EF8)
Adapter {E08FC8BE-A9C2-406A-8D1A-E5F87493790F} is DHCP enabled. Checking quarantine status. OSDSMPClient <date/time> 3832 (0x0EF8)
Adapter {E08FC8BE-A9C2-406A-8D1A-E5F87493790F} has 1 IPv4 address(es). OSDSMPClient <date/time> 3832 (0x0EF8)
Loading client certificates. OSDSMPClient <date/time> 3832 (0x0EF8)
this->hCertStore != NULL, HRESULT=80092002 (e:\nts_sms_fre\sms\client\osdeployment\osdsmpclient\smpclient.cpp,880) OSDSMPClient <date/time> 3832 (0x0EF8)
Failed to import the client certificate store (0x80092002) OSDSMPClient <date/time> 3832 (0x0EF8)
m_ClientInfo.init(), HRESULT=80092002 (e:\nts_sms_fre\sms\client\osdeployment\osdsmpclient\smpclient.cpp,1014) OSDSMPClient <date/time> 3832 (0x0EF8)
ClientRequestToMP::DoRequest failed (0x80092002). OSDSMPClient <date/time> 3832 (0x0EF8)
pClientRequestToMP->DoRequest(), HRESULT=80092002 (e:\nts_sms_fre\sms\client\osdeployment\osdsmpclient\smpclient.cpp,2787) OSDSMPClient <date/time> 3832 (0x0EF8)
ExecuteRestoreRequestToMP failed (0x80092002). OSDSMPClient <date/time> 3832 (0x0EF8)
ExecuteRestoreRequestToMP(migInfoFromMP), HRESULT=80092002 (e:\nts_sms_fre\sms\client\osdeployment\osdsmpclient\smpclient.cpp,2899) OSDSMPClient <date/time>3832 (0x0EF8)
ExecuteRestoreRequest failed (0x80092002). OSDSMPClient <date/time> 3832 (0x0EF8)
ExecuteRestoreRequest(), HRESULT=80092002 (e:\nts_sms_fre\sms\client\osdeployment\osdsmpclient\main.cpp,80) OSDSMPClient <date/time> 3832 (0x0EF8)
OSDSMPClient finished: 0x00002002 OSDSMPClient <date/time> 3832 (0x0EF8)
Process completed with exit code 8194 TSManager <date/time>2144 (0x0860)

This is not related to KB article 977203 : User state migration is unsuccessful on an ConfigMgr 2007 SP1 or SP 2 client after you install security update 974571 or Windows 7 SP1 (http://support.microsoft.com/kb/977203). The error code is different and this issue occurs even if 977384 is already installed.

This issue only occurs when you use prestaged media and put the USMT restore step in the same task sequence as the building of the OS. When the USMT restore steps is executed after the OS is built, no problem will occur.

Cause

The 0x80092002 is returned because the client certificate is not created yet. This is considered expected behavior for System Center Configuration Manager 2007 R3. This scenario was not explicitly tested with R3 but will work with Configuration Manager 2012.

Resolution

The workaround is to complete the USMT restore in a separate task sequence.

More Information

977203 User state migration is unsuccessful on an ConfigMgr 2007 SP1 or SP2 client after you install security update 974571 or Windows 7 SP1

=====

For the most current version of this article please see the following:

2648995 : USMT restore fails when using prestaged media in System Center Configuration Manager 2007 R3 (http://support.microsoft.com/kb/2648995)

J.C. Hornbeck| System Center Knowledge Engineer

App-V Team blog: http://blogs.technet.com/appv/
AVIcode Team blog: http://blogs.technet.com/b/avicode
ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
DPM Team blog: http://blogs.technet.com/dpm/
MED-V Team blog: http://blogs.technet.com/medv/
OOB Support Team blog: http://blogs.technet.com/oob/
Opalis Team blog: http://blogs.technet.com/opalis
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
OpsMgr Support Team blog: http://blogs.technet.com/operationsmgr/
SCMDM Support Team blog: http://blogs.technet.com/mdm/
SCVMM Team blog: http://blogs.technet.com/scvmm
Server App-V Team blog: http://blogs.technet.com/b/serverappv
Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials
WSUS Support Team blog: http://blogs.technet.com/sus/

Here’s a new Knowledge Base article we published. This one talks about an issue where a ConfigMgr 2012 Task Sequence fails when using Stand-Alone Media.

=====

Symptoms

Task Sequence execution fails when using stand-alone media (USB flash drive or CD/DVD) in System Center 2012 Configuration Manager. The task sequence will fail to install applications and the SMSTS.log will contain an error similar to the following:

Failed to invoke Execution Manager to Install Software for PackageID='CAS0002C' ProgramID='setup' AdvertID='{00A2B6FB-8E61-47B6-9702-BBDEAD7FBE8A}' hr=0x87d01004

Items in italics above are based on the environment so will not be consistent but the hr code (in bold) will be.

Cause

This occurs because the Software Distribution Agent is not enabled since the client has not yet received policy.

Resolution

To resolve the issue and enable the Software Distribution Agent, add the following Run Command Line step earlier in the Task Sequence, before any Install Package steps:

WMIC /namespace:\\root\ccm\policy\machine\requestedconfig path ccm_SoftwareDistributionClientConfig CREATE ComponentName="Enable SWDist", Enabled="true", LockSettings="TRUE", PolicySource="local", PolicyVersion="1.0", SiteSettingsKey="1" /NOINTERACTIVE

=====

For the most current version of this article please see the following:

2716946 - Task Sequence Fails when using Stand-Alone Media in System Center 2012 Configuration Manager

J.C. Hornbeck| System Center & Security Knowledge Engineer

Get the latest System Center news onFacebookandTwitter:

App-V Team blog: http://blogs.technet.com/appv/
ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
DPM Team blog: http://blogs.technet.com/dpm/
MED-V Team blog: http://blogs.technet.com/medv/
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
Operations Manager Team blog: http://blogs.technet.com/momteam/
SCVMM Team blog: http://blogs.technet.com/scvmm
Server App-V Team blog: http://blogs.technet.com/b/serverappv
Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials
WSUS Support Team blog: http://blogs.technet.com/sus/

The Forefront Server Protection blog: http://blogs.technet.com/b/fss/
The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

From our very own Steve Rachui comes another great System Center tip.  This one covers how to get a Configuration Manager 2007 Task Sequence to rerun:

There are well known methods to force an advertisement to rerun – including several add-on tools available for the SMS or SCCM console.  To date, however, there are not equivalent methods to force a task sequence to rerun.  Part of this may be because task sequences are typically thought of as focused on Operating System Deployment (OSD) and rerunning these types of distributions are not as common as rerunning advertisements.

To continue reading see http://blogs.msdn.com/steverac/archive/2009/11/06/sccm-forcing-a-task-sequence-to-rerun.aspx

J.C. Hornbeck | Manageability Knowledge Engineer

We have a new hotfix for ConfigMgr 1511 that fixes the following issue:

When you use a task sequence to install applications, you experience one of the following symptoms:

• A task sequence tries to reinstall applications that are already installed by using a dynamic variable list if one of the applications is configured to restart the computer. For example, if the third in a list of three applications requires a restart, the task sequence tries to reinstall the first and second applications in the list after the restart.
• A task sequence continues if there’s an application installation failure, even if the Continue on error option is not selected in the task sequence properties. This applies to task sequences that use a dynamic variable list to install applications.

A supported hotfix is available from Microsoft to address this problem. For complete details and a download link, please see the following:

3122677 – Task sequence that uses a dynamic variable list continues if an application installation fails, or it reinstalls applications that are already installed (https://support.microsoft.com/en-us/kb/3122677)

J.C. Hornbeck | Solution Asset PM | Microsoft

Our Blogs

• Configuration Manager: http://blogs.technet.com/configurationmgr/
• Data Protection Manager: http://blogs.technet.com/dpm/
• Orchestrator: http://blogs.technet.com/b/orchestrator/
• Operations Manager: http://blogs.technet.com/momteam/
• Operations Management Suite: https://blogs.technet.microsoft.com/msoms/
• Service Manager: http://blogs.technet.com/b/servicemanager
• Virtual Machine Manager: http://blogs.technet.com/scvmm
• Microsoft Intune: https://blogs.technet.microsoft.com/intunesupport/
• WSUS: http://blogs.technet.com/sus/
• AD and Azure RMS: http://blogs.technet.com/b/rms/
• Application Virtualization: http://blogs.technet.com/appv/
• MED-V: http://blogs.technet.com/medv/
• Application Proxy: http://blogs.technet.com/b/applicationproxyblog/
• Forefront Endpoint Protection: http://blogs.technet.com/b/clientsecurity/
• Forefront Identity Manager: http://blogs.msdn.com/b/ms-identity-support/
• Forefront TMG: http://blogs.technet.com/b/isablog/
• Forefront UAG: http://blogs.technet.com/b/edgeaccessblog/

Hi everyone, I just wanted to post a quick note about a new hotfix we published.

In Microsoft System Center Configuration Manager version 1511, the device management point generates an exception after a mobile client synchronizes a policy that contains Terms and Conditions compliance settings. Additionally, errors messages that resemble the following are logged in the SMS_DM.log file on the device management point:

ProxyEngineHttpHandler.Process Request exception noticed, Id = GUID:{GUID}
Except = System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.ConfigurationManager.Mobile.ProxyEngine.Common.CommonDefinitions.ScheduleToken..ctor(String tokenString)
at Microsoft.ConfigurationManager.Mobile.ProxyEngine.Common.CommonDefinitions.ScheduleData.set_EvaluationSchedule(String_value)

A supported hotfix is available from Microsoft to address this problem. For complete details and a download link, please see the following:

3139572 – Terms and Conditions compliance settings generate errors in System Center Configuration Manager (https://support.microsoft.com/en-us/kb/3139572)

J.C. Hornbeck | Solution Asset PM | Microsoft

Our Blogs

• Configuration Manager: http://blogs.technet.com/configurationmgr/
• Data Protection Manager: http://blogs.technet.com/dpm/
• Orchestrator: http://blogs.technet.com/b/orchestrator/
• Operations Manager: http://blogs.technet.com/momteam/
• Operations Management Suite: https://blogs.technet.microsoft.com/msoms/
• Service Manager: http://blogs.technet.com/b/servicemanager
• Virtual Machine Manager: http://blogs.technet.com/scvmm
• Microsoft Intune: https://blogs.technet.microsoft.com/intunesupport/
• WSUS: http://blogs.technet.com/sus/
• AD and Azure RMS: http://blogs.technet.com/b/rms/
• Application Virtualization: http://blogs.technet.com/appv/
• MED-V: http://blogs.technet.com/medv/
• Application Proxy: http://blogs.technet.com/b/applicationproxyblog/
• Forefront Endpoint Protection: http://blogs.technet.com/b/clientsecurity/
• Forefront Identity Manager: http://blogs.msdn.com/b/ms-identity-support/
• Forefront TMG: http://blogs.technet.com/b/isablog/
• Forefront UAG: http://blogs.technet.com/b/edgeaccessblog/

Hi everyone, I just wanted to let you know about a new hotfix that we released for ConfigMgr 2012 SP2, ConfigMgr 2012 R2 SP1 and ConfigMgr 1511. The hotfix addresses the following problem:

In a Microsoft System Center Configuration Manager environment in which the Microsoft Exchange Server connector is configured for use with Microsoft Exchange Server 2013, mobile devices aren’t listed as expected in the All Mobile Devices node of the administrator console. Additionally, errors that resemble the following are recorded in the EasDisc.log file on the Configuration Manager site server:

ERROR: [MANAGED] Invoking cmdlet Get-Recipient failed. Exception: System.Management.Automation.RemoteException: Cannot bind parameter ‘Filter’ to the target. Exception setting “Filter”: “The value “$true” could not be converted to type System.Boolean….
STATMSG: ID=8817 SEV=W LEV=M SOURCE=”SMS Server” COMP=”SMS_EXCHANGE_CONNECTOR” …
ERROR: [MANAGED] Exception: Cannot bind parameter ‘Filter’ to the target. Exception setting “Filter”: “The value “$true” could not be converted to type System.Boolean.”
ERROR: Failed to check status of discovery thread of managed COM. error = Unknown error 0x80131501

This issue applies to the following versions of System Center Configuration Manager:

• Microsoft System Center Configuration Manager version 1511
• Microsoft System Center 2012 Configuration Manager Service Pack 2
• Microsoft System Center 2012 R2 Configuration Manager Service Pack 1

For complete details as well as a download link and installation instructions, please see the following:

3122637 – FIX: Mobile devices aren’t listed in System Center Configuration Manager (https://support.microsoft.com/en-us/kb/3122637)

J.C. Hornbeck, Solution Asset PM
Microsoft Enterprise Cloud Group

Hi everyone, Cumulative Update 3 (CU3) for System Center 2012 Configuration Manager SP2 and System Center 2012 R2 Configuration Manager SP1 is now available. There are a bunch of fixes in this release so I won’t list them all here, but for the details regarding the problems that were addressed and the functionality that is updated, please see the following:

3135680 – Description of Cumulative Update 3 for System Center 2012 Configuration Manager SP2 and System Center 2012 R2 Configuration Manager SP1 (https://support.microsoft.com/en-us/kb/3135680)

Note that this update applies to both releases: Microsoft System Center 2012 Configuration Manager Service Pack 2 (SP2) and System Center 2012 Configuration Manager R2 Service Pack 1 (SP1).

J.C. Hornbeck, Sr. Solution Asset PM
Microsoft Enterprise Cloud Group

If you’re someone who ever does any work with software updates, either via WSUS or a Configuration Manager Software Update Point (SUP), we have a new guide that I think you’re really going to like.

What does this guide do?

The guide explains the System Center Configuration Manager software update synchronization process from start to finish. Each step in the process is explained, including the various settings that control how update retrieval and synchronization are performed, common problems seen with each step in the process, as well as general troubleshooting tips. The information in this guide applies to System Center 2012 Configuration Manager, System Center 2012 R2 Configuration Manager, and all versions of Configuration Manager in the current branch (e.g. Configuration Manager 1511).

Who is it for?

The guide is for IT professionals who need to understand, implement or troubleshoot Software Update synchronization in System Center Configuration Manager or WSUS when deployed in an enterprise environment.

How does it work?

This guide walks through each step of the process, explaining the settings and configurations required for successful synchronization as well as tests to verify that a particular step is functioning. The guide also shows how the synchronization progression can be tracked via the log files and how to troubleshoot common problems that may be encountered.

Where do I find it?

You can access the guide here.

J.C. Hornbeck, Solution Asset PM
Microsoft Enterprise Cloud Group

The Windows PE boot images that are included with the Windows Assessment and Deployment Kit (ADK) for Windows 10, version 1511, are missing information that’s required in order to configure network adapters during operating system installation. Because of this, when the ADK is used with System Center Configuration Manager, an OSD task sequence that’s based on a Windows PE version 10.0.10586 image cannot initialize during a restart into the Windows PE environment. When this occurs you will also receive the following error message during the “Initializing hardware devices” phase:

Windows PE initialization failed with error code 0x80220014

Another symptom is that the smsts.log file on the target computer will contain entries that resemble the following:

m_pImpl->AddAdapterTcpIpSettings( XMLAnswerFileImpl::WindowsPE, adapterInfo ), HRESULT=80220014
pAnswerFile->AddNetworkAdapter(adapterInfo), HRESULT=80220014
Failed to configure adapter 0
adapterSettings.Configure( pAnswerFile ), HRESULT=80220014
Execution failed with error 80220014

A new hotfix is available to correct this problem. The hotfix as well as the steps necessary to update the Windows Image file (boot.wim) and update the image on Configuration Manager distribution points can be found in the following Knowledge Base article:

3143760 – Windows PE boot images don’t initialize in System Center Configuration Manager (https://support.microsoft.com/en-us/kb/3143760)

J.C. Hornbeck, Solution Asset PM
Microsoft Enterprise Cloud Group

Hi everyone, here’s a quick reminder about .NET Framework and the Configuration Manager build 1511 client that I want to be doubly sure you’re aware of. If you’re running Configuration Manager 1511 or newer, when you go to upgrade or install your clients, Microsoft .NET Framework version 4.5.2 will be installed at the same time if the client is running a version of Microsoft .NET Framework prior to 4.5. This is by design as noted in the documentation here:

Prerequisites for deploying clients to Windows computers in System Center Configuration Manager

You can find it under the section titled Dependencies External to Configuration Manager and Automatically Downloaded During Installation.

On a related note, remember that as of January 12th of 2016, support for Microsoft .NET 4.0, 4.5, and 4.5.1 expired. There will be no new security updates, non-security updates, free or paid assisted support options or online technical content updates. For more information see Microsoft .NET Framework Support Lifecycle Policy FAQ (click on Announcements, then Products Reaching End of Support in the First Half of 2016. You’ll find it under Products Moving to End of Support).

I’m sure you’re probably already aware of this but I wanted to take a minute to point it out just so that there are no surprises when you go to install the new client.

J.C. Hornbeck, Solution Asset PM
Microsoft Enterprise Cloud Group

Here’s a quick note on a new hotfix we released in case you run into the problem. When a service window is created on one site in a System Center Configuration Manager hierarchy, service windows on the other sites in the hierarchy may be deleted. For example, after you create a service window for the Central Administration Site (CAS), a new service window is created for the child primary site, however after a second service window is created, the first service window that you created for CAS may be automatically removed.

A supported hotfix is available from Microsoft Support that addresses this problem. For complete details please see the following:

3142341 – Service windows are deleted in System Center Configuration Manager (https://support.microsoft.com/en-us/kb/3142341)

Note that after you install this hotfix each site can have its own service window, however previously deleted service windows will not be restored.

J.C. Hornbeck, Solution Asset PM
Microsoft Enterprise Cloud Group

If you find that your System Center Configuration Manager 1511 site server can’t connect to your SQL server, check for entries that resemble the following in both the smsexec.log and hman.log files on the site server:

*** [08001][2][Microsoft][SQL Server Native Client 11.0]Named Pipes Provider: Could not open a connection to SQL Server [2].
*** [HYT00][0][Microsoft][SQL Server Native Client 11.0]Login timeout expired
*** [08001][2][Microsoft][SQL Server Native Client 11.0]A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.

This issue usually occurs when the following conditions are true:

• The site server database is configured to communicate using a named instance of SQL server and a custom port.
• The “Service Connection Point” role is installed on the same computer that’s running SQL Server.

If you experience this with ConfigMgr 1511, we have a new hotfix available to correct the problem. For complete details please see the following Knowledge Base article:

3145401 – Service connection point does not connect in System Center Configuration Manager (https://support.microsoft.com/en-us/kb/3145401)

J.C. Hornbeck, Solution Asset PM
Microsoft Enterprise Cloud Group