KBConsider the following scenario:

1. You deploy many updates to a Microsoft System Center Configuration Manager 2007 Service Pack 2 (SP2) client.

2. You perform an operation that generates the WM_TIMECHANGE message from the client computer. For example, you perform one of the following operations:

- You change the system time.
- You resume a computer from sleep.
- You resume a computer from hibernation.

In this scenario, the computer runs slowly for some time. Additionally, the CPU usage is high, and the computer processes a heavy workload of disk I/O.

For all the details, including the cause and hotfix, see the following new Knowledge Base article:

KB2309968- Slow performance after you change the system time or resume the computer from sleep or hibernation on a System Center Configuration Manager 2007 SP2 client

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

clip_image001 clip_image002