ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Moving Symantec Endpoint Small Business To A New Server Problem

    Scheduled Pinned Locked Moved IT Discussion
    15 Posts 5 Posters 2.8k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Bill KindleB
      Bill Kindle
      last edited by

      Moving the management console is a PITA but there are just a few small configuration files that need to be imported to the new management server. I can't find my notes I used to have on this but and that link to the tool is all I have left.

      1 Reply Last reply Reply Quote 0
      • garak0410G
        garak0410 @IRJ
        last edited by

        @IRJ said:

        SEP is bad... really bad.... Use their support. If they cant help you, ditch the product...

        I would agree but we've yet to have an intrusion and it hasn't given me the typical Symantec bloat issues. Plus, we don't review our license until December, so can't afford a new license right now.

        1 Reply Last reply Reply Quote 0
        • garak0410G
          garak0410 @Bill Kindle
          last edited by

          @Bill-Kindle said:

          Get disk 2 (tools) if you are using 12.1, there's a utility called Cleanwipe that will help you a lot with the transition.
          http://www.symantec.com/connect/blogs/latest-symantec-endpoint-protection-released-sep-121ru4#comment-9382691

          OK...let me check this out.

          1 Reply Last reply Reply Quote 0
          • garak0410G
            garak0410
            last edited by garak0410

            They also recommend the Sylink.xml...played around with that before leaving yesterday...no success yet.

            http://www.symantec.com/business/support/index?page=content&id=TECH106288

            Bill KindleB 1 Reply Last reply Reply Quote 1
            • PackMatt73P
              PackMatt73 Vendor
              last edited by

              Getting this in front of our technical folks. Stay tuned...

              1 Reply Last reply Reply Quote 0
              • garak0410G
                garak0410
                last edited by

                I did finally get an email back from Symantec...they said the sylink process is the best:

                If have fewer clients and polices then you can follow the below mentioned steps:

                1. Export the Polices from the existing SEPM.

                2. Install the New SEPM version on the Machine.

                3. Import the Policies.

                4. Create a new test packager and test it with polices that they are working correctly.

                5. Replace the now Sylink.xml on older cleints using sylink replacer.

                6. After few minutes clients will start communicating with the new SEPM and showing online.

                Giving it a shot.

                garak0410G 1 Reply Last reply Reply Quote 1
                • garak0410G
                  garak0410 @garak0410
                  last edited by

                  @garak0410 said:

                  I did finally get an email back from Symantec...they said the sylink process is the best:

                  If have fewer clients and polices then you can follow the below mentioned steps:

                  1. Export the Polices from the existing SEPM.

                  2. Install the New SEPM version on the Machine.

                  3. Import the Policies.

                  4. Create a new test packager and test it with polices that they are working correctly.

                  5. Replace the now Sylink.xml on older cleints using sylink replacer.

                  6. After few minutes clients will start communicating with the new SEPM and showing online.

                  Giving it a shot.

                  The instructions above omit information on entering the new SEPM server into the XML file so I assumed I change it manually...did that...ran the Skylink replacer app on my workstation and I've been waiting 10-15 minutes for my workstation to show up in the SEPM screen and nothing yet. 😞

                  garak0410G 1 Reply Last reply Reply Quote 0
                  • garak0410G
                    garak0410 @garak0410
                    last edited by

                    @garak0410 said:

                    @garak0410 said:

                    I did finally get an email back from Symantec...they said the sylink process is the best:

                    If have fewer clients and polices then you can follow the below mentioned steps:

                    1. Export the Polices from the existing SEPM.

                    2. Install the New SEPM version on the Machine.

                    3. Import the Policies.

                    4. Create a new test packager and test it with polices that they are working correctly.

                    5. Replace the now Sylink.xml on older cleints using sylink replacer.

                    6. After few minutes clients will start communicating with the new SEPM and showing online.

                    Giving it a shot.

                    The instructions above omit information on entering the new SEPM server into the XML file so I assumed I change it manually...did that...ran the Skylink replacer app on my workstation and I've been waiting 10-15 minutes for my workstation to show up in the SEPM screen and nothing yet. 😞

                    OK...I have to export the sylink.xml from the new INSTALL and MANUALLY import it to every workstation and then it will show up on the new SEMP server. They have a "push" for it but they said it doesn't work with the latest SEMP...nice...

                    1 Reply Last reply Reply Quote 0
                    • Bill KindleB
                      Bill Kindle @garak0410
                      last edited by

                      @garak0410 said:

                      They also recommend the Sylink.xml...played around with that before leaving yesterday...no success yet.

                      http://www.symantec.com/business/support/index?page=content&id=TECH106288

                      Sylink. that's it. There's a method where you can update that file and have it point to the new host. I couldn't remember what it was called.

                      garak0410G 1 Reply Last reply Reply Quote 0
                      • garak0410G
                        garak0410 @Bill Kindle
                        last edited by

                        @Bill-Kindle said:

                        @garak0410 said:

                        They also recommend the Sylink.xml...played around with that before leaving yesterday...no success yet.

                        http://www.symantec.com/business/support/index?page=content&id=TECH106288

                        Sylink. that's it. There's a method where you can update that file and have it point to the new host. I couldn't remember what it was called.

                        This is pretty much complete. Just need to transfer my license over and then this is done. 🙂 Thanks for all of the tips.

                        1 Reply Last reply Reply Quote 0
                        • 1 / 1
                        • First post
                          Last post