Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Symantec System Center - move/remove & transfer duties

Created: 31 Jan 2012 | 7 comments

Working with a customer who has Business Version 10.1 AV running on his Windows 2000 network.  It is managed by System Center from an old Windows 2000 server which is about to be retired.  System center is already installed and funtioning on a newer Windows 2003 server, but seems to be secondary to the setup on the older server.

What do we have to do to get all of the functionality moved off of the old server and transferred to the new server before we retire it?

Thanks.......GK

Comments 7 CommentsJump to latest comment

Grizzlyking's picture

Pete...Thanks, but I'm not sure I either made myself clear or understood your response.  We already have a second Version 10 System Center running on a different computer and it sees the Server Group, sub groups and computers within each subgroup.  There is only one Server Group and now only two computers running the System Center.

What we want to do is remove from service the primary/original System Center which was used to create/define the Server Group, its subgroups and manage the clients (pushing clients and policies, etc).  We wish to transfer to the new System Center running on the new computer all of the functionality which had been associated with the old System Center computer.  Which I assume also means the files and folders which are used to push clients to computers, set policy and manage updates.

We have to retire the older computer as it is beginning to show signs of failure.

I hope this additional information clarifies our situation. Thanks...GK

Mohankumar's picture

Hi,

Try below steps once:

1.Backup the following folders of the old SEPM or SAV

 

2.break the Replication with any other site

3.Install the additional SEPM to the existing Database

4.Uninstall the old SEPM or SAV

5.Enable the Replication to the new SEPM

6.adjust the Server Managment Lists that are custom.

If it not works try the below steps:

1.Get one new server and install the SEPM 12.1 RU1

2.Creat the same groups that we have in the old server.

3.Once installation complete move all client from old server to the new server with same groups.

 

 

 

 

Grizzlyking's picture

Mohankumar....Thanks for your reply.  I'm having a bit of a problem following and understanding your first three steps.  Can you provide some more details?  You mentioned "folders" in step 1 but didn't detail them.  How does one "break replication"?  How does one add an additional System Center to the database?

Sorry for the "newbie" type questions, but this is the first time I've run into this situation.....GK

ps....Will the Version 12 System Manager manage version 10 clients?..

MichaelD50's picture

Just to be clear, the best that you will get out of a SSC to SEPM migration are custom client groups and settings for those custom client groups. The clients don't migrate over.

Depending on details you haven't provided, I would simply approach your move to 12.1 RU1 as a "fresh start".

SAV 10 clients can not be managed by a 12.1 RU1 SEPM.

There is support for W2K, but not to host SEPM; you will be able to install a SEP 11.0.7000 client which can be managed by a 12.1 RU1 SEPM.

MJD

Grizzlyking's picture

MichaelD50...Thanks for the reply.  The client has no desire to move from Version 10 to SEP versions 11 or 12.  He just wants to move the System Manager (version 10.1) from the old Window 2000 server to a new Windows 2003 server so he can retire the old Windows 2000 server.

I have tried to install the System Manager (ver 10.1) on the new server, but it seems to be flawed.  When I open up the System manager and server group on the Windows 2003 Server, all the clients are marked "Disabled - Time out of sync" ( or something like that).

Old Windows 2000 server is working fine, but the client has worries that it is starting to fail.

What other details do you need to help with this?.....GK