Sign In with your
Trend Micro Account
Need Help?
Need More Help?

Create a technical support case if you need further support.

Moving OfficeScan (OSCE) from one local disk to another

    • Updated:
    • 2 Dec 2016
    • Product/Version:
    • OfficeScan 10.6
    • OfficeScan 11.0
    • OfficeScan XG.All
    • Platform:
    • Windows 2000 Advanced Server
    • Windows 2000 Professional
    • Windows 2000 Server
    • Windows 2003 Enterprise Server
    • Windows 2003 Standard Server Edition
    • Windows 2008 Standard Server Edition
    • Windows 7 32-bit
    • Windows Vista 32-bit
    • Windows XP Professional
Summary

When reaching low disk space on the default C: drive, move the OfficeScan server to a different local disk.

Details
Public

To transfer the OfficeScan server:

  1. Take note of the following:
    • Current patch, hot fix, or build number of the OfficeScan server
    • Connection settings within the OfficeScan console, server name, and port number
    • Client_LocalServer_Port from the ofcscan.ini file or web console
  2. Stop the OfficeScan Master Service.
  3. Back up the following:
    • HTTPDB folder
    • ofcscan.ini file
    • Private\ofcserver.ini
    • Web
    • Web_OSCE
     
    Back up the certificate export in a different location. For example: CertificateManager.exe -b strongpassword D:\Test\TrendMicro.zip.
  4. If the client is using the Firewall module, back up the pccsrv\private\PFW folder as well.
  5. Uninstall the existing OfficeScan server.
  6. Install the OfficeScan server on the new drive location.
  7. Keep the same directory tree structure but with new drive letter and use the same server/client port information collected in Step 1.
    For example: E:\Program Files\Trend Micro\OfficeScan
  8. Install the same patch, hot fix, or build number as the original OfficeScan.
  9. Edit the ofcscan.ini and Private\ofcserver.ini file backed up from the original OfficeScan server.
  10. Look for the following sections and modify all references to the old local disk to reflect new drive lettering:
    • [INI_DBFILE_SECTION]
    • [INI_VIRUSLOG_SECTION]
    • [FILE_PATH_SECTION]

    See below for examples:

    [INI_DBFILE_SECTION]
    DB_TYPE = 1
    DB_PATH =E:\Program Files\Trend Micro\OfficeScan\PCCSRV\httpdb
    DB_IDLE_PERIOD = 10
    DB_PACK_PERIOD = 1440
    DB_EXCLUSIVE_OPEN = 1
    DB_MEM_OPT_MAX = 10240
    CIData=E:\Program Files\Trend Micro\OfficeScan\PCCSRV\httpdb\dBCIData.dbf
    CEData=E:\Program Files\Trend Micro\OfficeScan\PCCSRV\httpdb\dBCEData.dbf
    CXData=E:\Program Files\Trend Micro\OfficeScan\PCCSRV\httpdb\dbCXData.dbf
    NTData=E:\Program Files\Trend Micro\OfficeScan\PCCSRV\httpdb\dbNTData.dbf
    MSLog=E:\Program Files\Trend Micro\OfficeScan\PCCSRV\httpdb\dBMSLog.dbf
    PSLog=E:\Program Files\Trend Micro\OfficeScan\PCCSRV\httpdb\dBPSLog.dbf
    RTLog=E:\Program Files\Trend Micro\OfficeScan\PCCSRV\httpdb\dBRTLog.dbf
    SNLog=E:\Program Files\Trend Micro\OfficeScan\PCCSRV\httpdb\dBSNLog.dbf
    MSCfg=E:\Program Files\Trend Micro\OfficeScan\PCCSRV\httpdb\dBMSCfg.dbf
    RTCfg=E:\Program Files\Trend Micro\OfficeScan\PCCSRV\httpdb\dBRTCfg.dbf
    PSCfg=E:\Program Files\Trend Micro\OfficeScan\PCCSRV\httpdb\dBPSCfg.dbf
    SNCfg=E:\Program Files\Trend Micro\OfficeScan\PCCSRV\httpdb\dBSNCfg.dbf
    EFCfg=E:\Program Files\Trend Micro\OfficeScan\PCCSRV\httpdb\dBEFCfg.dbf
    TempDB=E:\Program Files\Trend Micro\OfficeScan\PCCSRV\httpdb\dbtemp.dbf
    VCLog=

    [INI_VIRUSLOG_SECTION]
    LatestLog=E:\Program Files\Trend Micro\OfficeScan\PCCSRV\web\service\LatestLog.dat

    [FILE_PATH_SECTION]
    VIRUS_PATTERN=E:\Program Files\Trend Micro\OfficeScan\PCCSRV\lpt$vpn.259

  11. Save and close the file.
  12. Stop the OfficeScan Master Service.
  13. Open the IIS Manager and stop the OfficeScan web service.
  14. Replace the following with the back up files:
    • HTTPDB
    • ofcscan.ini
    • ofcserver.ini
  15. If the client is using the firewall module, replace the existing pccsrv\private\PFW folder with the backed up one.
  16. Start the OfficeScan Master Service.
  17. Log on to the console and verify if everything has been migrated:
    1. Check that the clients are reporting in OK.
    2. Check that the server is able to download updates from AU.
    3. Check that all client privileges settings are correct.
    4. Verify that all the information displayed in the console are correct.
Premium
Internal
Rating:
Category:
Migrate
Solution Id:
1037622
Feedback
Did this article help you?

Thank you for your feedback!

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.

If you need additional help, you may try to contact the support team. Contact Support


To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.


Need More Help?

Create a technical support case if you need further support.