Consider the following scenario:
- An operating system is deployed to a client computer in a System Center Configuration Manager 2007 Service Pack 2 (SP2) environment.
- You try to deploy another operating system to the same client within one hour of the previous deployment.
In this scenario, the deployment process fails. On the client side, the computer tries to restart from the local hard disk instead of from the Pre-Boot Execution Environment (PXE) image.
Additionally, the following message may be logged in smspxe.log:
Loaded PXE settings from reg key HKLM\Software\Microsoft\SMS\PXE:
HTTP Port: 80
HTTPS Port: 443
BindPolicy: Exclude <empty>
TRK: <non empty>
Root CA Certs: <empty>
PXE GUID: fab8bfcc-3b15-431a-828d-fbfd184c3813
Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows
To resolve this cache limitation, you must change a registry value on the computer on which the ConfigMgr PXE service point role is installed. To do this, follow these steps:
- Click Start, type regedit in the Start Search box, and then click regedit in the Programs list.
Note If you are prompted for an administrator password or for confirmation, type the password or provide confirmation.
Locate and then select the following registry subkey:
Right-click CacheExpire, and then click Modify.
Configure the cache expire value. For example, set the value to 120 seconds (two minutes). To do this, follow these steps:
- In the Value data box, type 120.
- In the Base area, click decimal.
- Click OK.
- Exit Registry Editor.
Restart the Windows Deployment Services Server service.
- Microsoft System Center Configuration Manager 2007 Service Pack 2