Renaming the machine on which Symantec Endpoint Protection Manager is installed

Article:TECH162062  |  Created: 2011-06-10  |  Updated: 2011-06-30  |  Article URL
Article Type
Technical Solution


You rename the machine on which Symantec Endpoint Protection Manager is installed, but you experience errrors and unexpected behavior afterwards.


The Endpoint Protection Manager service keeps stopping unexpectedly and you see error (Failed To Connect to Server) when using Manager console.

You have an existing Symantec Endpoint Protection Manager (or a Policy Manager for Sygate Enterprise Protection) on the same machine as the Manager's database server. If you change the hostname before upgrading the Manager, the upgrade wizard complains of a schema mismatch.



The cause is, of course, the hostname change.


After changing the hostname, you must re-run the Manager's configuration wizard.

In the case of the upgrade error, the upgrade will complete but you must run the configuration wizard afterwards to register the new hostname.

Supplemental Materials


SEPM Upgrade Wizard complains about schema mismatch if Hostname of SPM 5.1 MR9 system before upgrading it to Amber

SourceError Code

SEPM Service is dying if the hostname of the machine is changed which has both SEPM and SQL Server on the same machine

Article URL

Terms of use for this information are found in Legal Notices