Video Screencast Help

SEP Client in wrong group

Created: 07 Nov 2012 • Updated: 09 Nov 2012 | 4 comments
Sepp105's picture

Environment:

- SEP 11

- Changed IPs of SEPM and Database-Server

- Migration done successfully, all clients work correctly

Problem:

- Only the SEP-Client on the SEPM-Server has the wrong group under "Troubleshooting" and therefore has no connection to the SEPM-Server (himself). Hostname is correct though.

Steps taken:

- Reinstalled, updated Sylink.xml.

Solution:

- Create a new temporary group in SEPM for this client. Export new sylink.xml for this group. Connect the client with sylinkdrop.exe. After client is green and updated, move it to the desired group and delete the temporary group again.

Comments 4 CommentsJump to latest comment

.Brian's picture

When creating a package, check the following:

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

Mithun Sanghavi's picture

Hello,

The SEP clients contact the SEPM using the IP address. So, as long as your client machines are able to contact the new server on the installation port and IP address of the server, the migration should be fine.

You’ll be happy to know this is fairly easy to accomplish. 

The SEP clients find the management server by looking in management server list they are configured to use.  By default when you install the SEP Manager it creates a default management server list that contains the IP address of the manager and it's name.  If you just change the address of the server SEPM will update this list but don’t just run and change it. 

You can create your own management server list and have the clients use it instead.  If you were to create a new Management server list with only the name of the management server it would force the clients to resolve the IP address of the management server from dns or NetBIOS and all should be well as long as you change DNS when you change the IP on the server. 

Another idea would be to create a new Management Server List with the IP address and name just like the default list but then add the new IP address that you will be changing the server to.  This way the clients will first try the old address, the new address, and then the name.

After you create the management server list under policies -> Policy Components you need to tell the clients to use the new list.  For this under the clients section select the group containing the clients and select communication settings under the policy tab at the top.  Select your management server list from the drop down.   It’s much easier then it sounds. 

Let me know if you need any other info. 

Reference: https://www-secure.symantec.com/connect/forums/recommended-procedure-sepm-manager-ip-address-change

VIDEO:Changing SEPM Server Name and IP address

http://www.symantec.com/connect/videos/changing-sepm-server-name-and-ip-address

Hope that helps!!

Mithun Sanghavi
Senior Consultant
MIM | MCSA | MCTS | STS | SSE | SSE+ | ITIL v3

Don't forget to mark your thread as 'SOLVED' with the answer that best helped you.

Ashish-Sharma's picture

HI,

Changing the IP address of the SEPM server may affect two things.

1) Client-Server communication.

2) Replication between two SEP Managers (if applicable).

 

If you have only one SEP Manager in your network, follow

http://www.symantec.com/docs/TECH98430

 

If you have more than one SEP Manager in your network and If you have replication configured on the SEPM Manager in which you need to change the IP address, follow

http://www.symantec.com/docs/TECH96090

 

Check this thread

https://www-secure.symantec.com/connect/forums/how-change-ip-address-sepm

Thanks In Advance

Ashish Sharma

 

 

SameerU's picture

Hi

Please upgrade to SEP 12.1 RU1 MP1

Regards