Symantec Management Platform (Notification Server)

 View Only
  • 1.  Migrate NS7 to 7.1

    Posted Sep 22, 2011 02:32 AM

    Hi I migrated NS 7 to NS 7.1 the old NS is still in place on another server, I have backed up the database and pointed the new install to the backup database and ran the migration wizard, all that failed was converting the software and this is due to the software repository now on a different drive.

    I have been into the NS 7 and done the following the issue is all the computers in the new NS still say they are managed by: the NS 7.0 server even those that I have manually installed the NS 7.1 agent onto and appear the correct NS setttings on the client itself but are not do not appear to be updating agents ie - getting a guid etc.

    In the 7.0 console, on the Settings menu, click Agents/Plug-ins > Targeted

    Agent Settings.

    3 On the Targeted Agent Settings page, select the policy that contains the

    agents that you want to redirect to 7.1, and click the Advanced tab.

    4 In the Alternate URL for accessing NS section, specify the URL for the 7.1

    Notification Server as follows:

    Server Name

    Symantec recommends that you use the fully qualified domain name.

    Server Web

    The Server Web address should be in the following format:

    https://<NS_FQDN>:<port>/Altiris/

    5 Click Save changes.

    About the Symantec Management Agent upgrade policies



  • 2.  RE: Migrate NS7 to 7.1

    Posted Sep 22, 2011 02:37 AM

    sorry they are updating the guid on the client but not in the console and keep showing as managed by the old NS7.0 server



  • 3.  RE: Migrate NS7 to 7.1

    Posted Sep 26, 2011 04:35 AM

    we had the same problem as you symantec solved

     the pc on our ns7.1 in Resource Manager show managed by old server

    we solved our problem by this mail from symantec

     

    ---------------- mail from symantec --------------------

    Hello  

    How are you today? Since I could not reach you on the phone, I am now following up with this email.

     

    I have some good news for you today, I believe. As mentioned before, we could reproduce this issue in house and we have now managed to resolve it here by running a SQL command against our CMDB.

     

    Therefore I would like to recommend the following steps for you:

    1) Use SQL to back up your CMDB. This is best practice anytime you use SQL commands to access any database directly.

    2) In the SQL Management Studio, run the following SQL script:

         update Item
         set name='new server name'
         where Description like 'The owner notification server source item for'

    Please note you will have to enter your own values in lines 2 and 3 of this script to have it match your own environment.

     

    The machines should now show up with the new server name in resource manager.

    -----------------------------