3 Replies Latest reply on Jul 2, 2010 5:18 AM by thertkorn

    Umzug Centennial auf neuen Server

    chris24 Rookie
      Hallo,

      bedingt durch einen Domainumzug wurde Cenntenial auf neuer Hardware installiert. Nun sind die Clients dran. Wie bekomme ich die Clients an den neuen Server ? Muss der "alte" Agent deinstalliert werden oder kann man
      die csetup.exe einfach vom neuen Server auf dem Client installieren lassen und gut ?

      Vielen Dank für kurzes Feedback.

      chris
        • 1. Re: Umzug Centennial auf neuen Server
          thertkorn Expert
          HAllo,

          dazu gibt es 3 KB Artikel von centennial.

          HOWTO: How do I move my Discovery server software to a new server machine?
          VERSIONS AFFECTED

          Discovery 2005, 2005SP1, 2006, 2006FP1, 2007, 2007 International

          DESCRIPTION

          The Discovery server is to be migrated to new hardware.  At the same time the repository data may or may not be migrated to a new SQL server.

          RESOLUTION

          Migrating to the new server will require the installer to have the SA account information for both the old server and the new one.  The process should not be performed in a Remote Desktop session.

          To migrate the Discovery server to a new machine do the following:

          1) Check the Discovery version in the Control Center by selecting Help and then About.  Verify that an original, non-upgrade CD is available to install the same version of Discovery later in the process.  If such a CD is not available contact your Discovery reseller to obtain one.  Upgrade version downloads are available from the Centennial support sit but should not be used for fresh installations.  They are only suitable for upgrading existing installs.

          2) If the new server will not have the same name or IP address as the old server the clients must be configured to connect to the new server before the old server is taken down.  If the new server will have the same name and IP address as the old server this step may be skipped.

          For a secure installation:

          A) Edit C:\Program Files\Centennial\Discovery\ClientFiles\xferwan.ini so that the addresses in the ServerURL1 and HTTPsvcURL1 are correct for the new server.  If using a computer name instead of an IP address use a name format that will resolve correctly for all clients.  Save the file.

          B) In the Discovery Control Center select Tools and then Update All Secure Clients.

          This process requires the client agents to check in with the server for updated settings, download the new settings, and then apply the new settings.  By default this occurs every 30 minutes.  Allow sufficient time for all of agents to connect to the server and obtain these changes before proceeding.  Client agents that are not updated at this time will need to be redeployed before they can communicate with the new server.

          For a non secure installation the clients will have to be redeployed once the new server is established.  This would be an excellent time to consider upgrading to a secure installation as agents will have to be deployed in any case.  Upgrading to a secure installation not only enhances the security of Discovery communications but it will allow many types of configuration changes without requiring a full client agent redeployment in the future.

          3) Launch the Services management tool and stop the CentennialServerAgent service.

          4) Make a backup of the full C:\Program Files\Centennial\Discovery folder and store it somewhere accessible to the new server.

          5) Launch the Discovery Control Center.

          6) Backup the Discovery repository by selecting File and Backup Repository.  Be certain to save the database in a location accessible to the new server.

          7) Uninstall the Discovery server software from Add or Remove Programs.

          8) Using SQL management tools, verify that the Discovery database and Discovery users have been removed.

          9) Using the full install CD, install Discovery on the new server.  When prompted for the database location you may choose the same SQL server that was used previously or any SQL server accessible to the new Discovery server.  Use the SA account to connect to the SQL Server.  Do not use SQL management tools to create the Discovery accounts before running the installer; let the installer create them.

          10) Launch the Discovery Control Center.

          11) Restore the database backup made in step 6 by selecting File, Restore Repository, and browsing to the backup file.  When the repository is successfully restored close the Control Center.

          12) Now it is possible to restore certain important files from the backup of the Discovery installation folder made in step 4.  Restore the following files to the C:\Program Files\Centennial\Discovery folder:

               runmenu.dat
               \ClientFiles\userinp.dat
               \ClientFiles\kc-pub.pem
               \ClientFiles\client.xml
               \ClientFiles\csetup.ini
               \Control\kc-priv.pem

          13) Launch the setup program on the CD a second time and choose the Repair option.  This will sign the client files that were restored in step 11 so that client agents can be deployed in the future.

          14) Launch the Services management tool and restart the CentennialServerAgent service.

          15) Copy any .RP1 or .RP2 files from the \Discovery\Messages folder in the backup to the C:\Program Files\Centennial\Discovery\Messages folder.  Do not copy in the INFO.RP0

          16) If the environment was non-secure environment in step 2, it is now possible to deploy
          new client agents.
          • 2. Re: Umzug Centennial auf neuen Server
            thertkorn Expert
            HOWTO: How to move Discovery data to a new SQL server or SQL instance?
            VERSIONS AFFECTED

            Discovery 2005, 2005SP1, 2006, 2006FP1, 2007, 2007 International, 8.0, 9.0


            DESCRIPTION

            Discovery server services will remain on the same server but the data repository will be moved to a new SQL server or SQL instance.

            RESOLUTION

            Migrating to the new server will require use of SA account information for both the old server and the new one.  The process should not be performed in a Remote Desktop session.

            To migrate the Discovery database to a new SQL server or instance do the following:

            1) Check the Discovery version in the Control Center by selecting Help and then About.  Verify that an original, non-upgrade CD is available to install the same version of Discovery later in the process.  If you do not have an original CD contact your reseller to obtain one.  Upgrade version downloads are available from the Centennial support site but should not be used for fresh installations.  They are only suitable for upgrading existing installs.

            2) Launch the Services management tool and stop the CentennialServerAgent and IIS Admin services.


            3) Make a backup of the full Discovery installation folder.  By default this is C:\Program Files\Centennial\Discovery, C:\Program Files\Frontrange Centennial\Discovery, or C:\Program Files\FrontRange Solutions\Discovery depending on the version of the software you're using.


            4) Launch the Discovery Control Center.

            5) Backup the Discovery repository by selecting File>Backup Repository.  Note the location of the database backup so it can be found later.

            6) Uninstall the Discovery server software from Add or Remove Programs.

            7) Using Enterprise Manager or SQL Management Studio verify that the Discovery database and the four SQL users Discovery, DiscoveryAdmin, DiscoveryWeb, and DiscoveryRO have been removed from the old SQL instance.

            8) Using the full install CD, reinstall Discovery.  When prompted for the database location choose the new server or instance.  Use the SA account to connect to the SQL Server.  Do not use SQL management tools to create the Discovery accounts before running the installer; let the installer create them.

            9) Launch the Services management tool and stop the CentennialServerAgent and IIS Admin services.

            10) Launch the Discovery Control Center.

            11) Restore the database backup made in step 5 by selecting File>Restore Repository and browsing to the backup file.  When the repository is successfully restored close the Control Center.

            12) Now that the repository is restored important files from the backup of the Discovery installation folder made in step 3 can be restored.  Restore the following files to the \Discovery folder on the freshly installed server:

                 RUNMENU.DAT
                 \ClientFiles\USERINP.DAT
                 \ClientFiles\KC-PUB.PEM
                 \ClientFiles\CLIENT.XML
                 \ClientFiles\CSETUP.INI
                 \Control\KC-PRIV.PEM

            In the \Messages folder restore all backed up files other than INFO.RP0 and any files with file extensions beginning with letter F.  The INFO.RP0 should never be modified by hand unless directed by support and the files with extensions beginning with letter F are failed client messages so ther is no reason to restore them.


            13) Launch the setup program on the CD a second time and choose the Repair option.  This will sign the client files that were restored in step 12 so that client agents can be deployed in the future.

            14) Launch the Services management tool and restart the CentennialServerAgent  and IIS Admin services.

            Would you like to... Print this page
            Email this page
            Post a comment
            Subscribe me
            Add to favorites
            Remove Highlighting
            Edit this Question
            User Opinions ( )How would you rate this answer? Helpful
            Not helpful
            Help us improve. Why was this unhelpful? Thank you for rating this answer. Related Questions
            •HOWTO: Moving a Discovery Server
            Attachments
            No attachments were found.
            • 3. Re: Umzug Centennial auf neuen Server
              thertkorn Expert
              Anbei noch ein älteres PDF was aber auch noch für Disco 9 anwendbar ist.
              Hat sich nicht soviel in der Architektur geaendert.
              Oder Siehe oben die Anleitung die direkt aus der KB kopiert wurde.