Disable Software-Distribution:
WMIC /namespace:\rootccmpolicymachinerequestedconfig path ccm_SoftwareDistributionClientConfig CREATE ComponentName=”Disable SWDist”,Enabled=”false”,LockSettings=”TRUE”,PolicySource=”local”,PolicyVersion=”1.0″ ,SiteSettingsKey=”1″ /NOINTERACTIVE

Re-Activate Software-Distribution:
WMIC /namespace:\rootccmpolicymachinerequestedconfig path ccm_SoftwareDistributionClientConfig WHERE ComponentName=”Disable SWDist” delete /NOINTERACTIVE

Trigger Hardware Inventory:
WMIC /namespace:\rootccm path sms_client CALL TriggerSchedule “{00000000-0000-0000-0000-000000000001}” /NOINTERACTIVE

Trigger Software Inventory:
WMIC /namespace:\rootccm path sms_client CALL TriggerSchedule “{00000000-0000-0000-0000-000000000002}” /NOINTERACTIVE

Trigger DataDiscoverRecord (DDR) update:
WMIC /namespace:\rootccm path sms_client CALL TriggerSchedule “{00000000-0000-0000-0000-000000000003}” /NOINTERACTIVE

Force a FULL HW Inventory on next HW-Inv Schedule:
WMIC /namespace:\rootccminvagt path inventoryActionStatus where InventoryActionID=”{00000000-0000-0000-0000-000000000001}” DELETE /NOINTERACTIVE

Repair SMS/SCCM Agent on a remote client:
WMIC /node:%MACHINE% /namespace:\rootccm path sms_client CALL RepairClient

Repair a list (all clients listed in clients.txt) of remote SMS/SCCM Agents:
WMIC /node:@clients.txt /namespace:\rootccm path sms_client CALL RepairClient

Jeff Wettlaufer has put together a short video showing one of the cool new features soon to arrive when R3 is released

OS Deployment enhancements in Configuration Manager 2007 R3

Check it out here > http://blogs.technet.com/systemcenter/archive/2010/01/20/os-deployment-enhancements-in-configuration-manager-2007-r3.aspx

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

The actually workaround before this hotfix came out, was is to uninstall the 974571 hotfix on computers before running USMT task sequence. This workaround works fine but was not sufficient for many customers (The opposite would have been funny ).

Consider the following scenario:

• You install the System Center Configuration Manager 2007 Service Pack 1 (SP1) client or the System Center Configuration Manager 2007 Service Pack 2 (SP2) client.
• You install security update 974571 on this computer.
• A SCCM task sequence runs on this client. This task sequence includes the Capture User State task sequence step and the Restore User State task sequence step.

In this scenario, user state migration fails. At the same time, the following error message is logged in the Ccmexec.log file:

Failed to import the client certificate store (0x80092024) OSDSMPClient

For all the details including a download link to the hotfix see the following new Knowledge Base article:

KB977203 – User state migration fails on a SCCM 2007 SP1 client or on a SCCM 2007 SP2 client after you install security update 974571

Brief Description

SCCM PXE/WDS with Remote DHCP Server

Add the following DHCP Scope Options:

060   PXEClient

066   IP Address of WDS Server

067   bootx86wdsnbp.com

These are required steps if your DHCP Server is on a different subnet than your SCCM/WDS/PXE Server.

Here is a good KB Article on this subject – http://support.microsoft.com/default.aspx/kb/926172 and http://technet.microsoft.com/en-us/library/cc732351.aspx

Well funny thing, after OSD deployment the Found New Hardware Wizard shows up… DOH!

Thinking about drivers like KB888111… and strangely enough one Primary IDE Channel…

Pretty simple solution (Like in BDD / SMS 2003 OSD)

rundll32.exe Syssetup.dll,UpdatePnpDeviceDrivers

Before adding this to your task sequence, just run this command on a system that shows new hardware found. You should see in the task bar, new hardware found and when you look at the Device Manager, you should not see any warnings or errors. Remember, you still need to make sure your proper drivers are available.

Thanks to Brian S. Tucker