Moving the Virtual Storage Directory in Prism Patch Manager Server v6.3 and v6.4
|
|
Description |
|
|
In some instances, it may be necessary to move the Storage repository for Prism Patch Manager to a new location with more disk space. The following article provides instructions on performing this action.
Applies To: Prism Patch Manager 6.3 - 6.4 |
INFORMATION
Use the following steps to properly move the storage repository for the Prism Patch Manager Server:
- Stop IIS using the following from a CMD Prompt:
NET STOP HTTP /Y
- Stop the New Boundary Replication Service using the following from a CMD Prompt:
NET STOP "New boundary replication service”
- Create a new directory on the new location for the repository (e.g., D:\PrismPatchManager\, etc.).
- Copy the PatchLink Update Server Storage directory from the existing location (C:\Program Files\New Boundary\Prism Patch Manager Server\Storage by default).
- Open REGEDIT and drill down to HKEY_LOCAL_MACHINE\SOFTWARE\PatchLink.com\Update\ISAPI\.
- Modify the Storage string value to match the new repository location (e.g., D:\Prism Patch Manager Server\Storage).
- Open a CMD Prompt and type the following command to update the database, where SystemConfig_Value matches the new repository location:
- Type OSQL -E and press Enter.
- Type USE PLUS and press Enter.
- Type UPDATE SystemConfig SET SystemConfig_Value = ‘D:\Prism Patch Manager Server\Storage’ WHERE SystemConfig_Name = 'Storage' and press Enter.
- Type GO and press Enter.
- Open Internet Information Services (IIS) Manager and drill down to the New Boundary Prism Patch Manager Server website.
- Right click on UpdateStorage and select Properties.
- Under the Virtual Directory tab, click the Browse... button and select the new repository location.
- Click OK and close Internet Information Services (IIS) Manager.
- Restart IIS executing IISRESET from a CMD Prompt.
- Restart the New boundary replication service using the following from a CMD Prompt:
NET START "New boundary replication service"
Verify Storage Location Configuration
You may confirm the Storage location is configured correctly by deploying the A - Deployment Test and Diagnostic Package from the Prism Patch Manager Server to a test machine. If the test machine does not fail the deployment with a 190D error (download failure), the Storage directory is functioning properly.
Alternatively, perform a DAU by clicking the Detect ASAP button on the PatchLink Update Agent Control Panel and then, once finished, check the Detection Log for a similar entry as shown below, indicating the OS Pack file was able to be found and/or downloaded:
2009/02/09 21:55:20.0113,0,Beginning single pass fingerprint evaluation
2009/02/09 21:55:20.0910,0, Successfully downloaded OS Pack file '/UpdateStorage/OSPacks/Microsoft Windows Server 2003 Enterprise Edition.osp' - last modified = 'Mon, 09 Feb 2009 19:01:36 GMT' ETag = '"d0edaed4e88ac91:ec6"'