If a SEPM 12.1 server is disabled then re-enabled a User Interface (UI) error occurs that indicates a "Supported product could not be enabled".
The error message is: The specified tenant differs from the originally configured tenant for this product. Changing tenants may...
"The specified tenant differs from the originally configured tenant for the
When a user registers SEPM for the first time they use the format Default\admin on the username field, and do not have to enter anything in the advanced settings if it's the 'Default' SEPM domain. When a SEPM server is disabled then re-enabled the system will not use the Domain\Username format. The Advanced options must be utilized and the username and domain broken into their components.
Workaround: Determine the SEP Credentials required then Expand the Advanced options area on the SPC Integration page and separate the Domain and Username into their respective fields. See the screen shot following the workaround steps as a reference.
Determine the SEP Credentials
To determine the SEP Domain:
1. Start the SEP Management Console (SEPM). 2. Navigate to Admin, Domains. 3. View the list of Domain names. The standard domain name is: Default
To determine a SEP Administrators username:
1. Start the SEP Management Console (SEPM). 2. Navigate to Admin, Administrators. 3. View the list of Administrative names. The standard username is: admin
The information is case sensitive, so match what you see on the screen with what you input on the integration page.
Integrate the products into SPC
Logon to the SPC 2 Web Console.
Navigate to the Available Supported Products tab. Symantec Protection Center > Admin > Supported Products > Available Supported Products
Select the SEPM Hostname from the drop down.
Type the Administrator username in the correct field without the SEPM Domain.
Type the Administrator password in the correct field.
Click on the Advanced options hyperlink.
Type the SEPM domain in the Tenant field.
Verify all remaining information is correct.
Select the Enable option.
Symantec Corporation has acknowledged that the above-mentioned issue is present in the current version(s) of the product(s) mentioned at the end of this article. Symantec is committed to product quality and satisfied customers.
This issue is currently being considered by Symantec to be addressed in the next major revision of the product. There are no plans to address this issue by way of a patch or hot fix in the current or previous versions of the software at the present time. Please note that Symantec reserves the right to remove any fix from the targeted release if it does not pass quality assurance tests or introduces new risks to overall code stability. Symantec’s plans are subject to change and any action taken by you based on the above information or your reliance upon the above information is made at your own risk.
Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.
Please contact your Symantec Sales representative or the Symantec Sales group for upgrade information including upgrade eligibility to the release containing the resolution for this issue. For information on how to contact Symantec Sales, please refer to the following Web site: