Intel,Altiris Group

When SEP R2 is released, I've installed the console at site A and it manages the clients there. Right now I've installed SEP R4 at another location (Site B) and it manages the clients at site B. Both sites are linked via WAN.

I wish to transfer the clients at site A to site B, and convert the console at site A to a LiveUpdate server instead, so that clients at site A can still get definition updates from site A, while their database resides at site B. Is it possible without uninstalling from the client PC at site A? If so, how to do so? 

I also need clients at site A to be upgraded to SEP R4 since site B is already in R4.

Hi,

I have already some ideas to help you but I have to double check them with the product documentation. I think the replication could help you but I have to check some details.
Anyway I suggest to begin the migration of site A, manager and clients, to the MR4, therefore it will be synchronized with the site B and further operations will be possible.
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008121712452848

Just to prevent possible common mistakes: don't add a replication partner from the console of the manager. A lot of people used this option to add a new replication partner, but it is not intended for new partners in fact now, in the latest releases, you can read "add an existing partner..." that is intented to restore a broken replication.

Hi Giuseppe

I'll try the migration of site A manager and clients to SEP R4, as you suggest, and will update this post.

btw, after doing the migration at site A, how do I move the database to site B manager? Use 'add an existing partner...' as you mentioned? How to do that? Do I still still need to keep the database at site A?

You would  need to reconfigure   the  site  B as a  replication partner  of  site  A, using  Mgt. server  reconfiguration  wizard, and  overtie the  database  at  site B(You will lose  all the  clients  at  site  B). Then you can reestablish communication between clients  at  site  B, and site  B sepm, using  Sylink replacer.
Then you can use  MSL, to have  all your  clients report  to site  B. Then you can uninstall site  A.

But, first, you need to ensure that  both site  A , and  site  B, are  at  Mr4.

Vishal.

I've tried upgrade the console at site A, and migrate clients at site A by following this link:   http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008121712452848   (under 'To migrate client software' near to the bottom of the page) last week. After a week, I check on the status on the console, and notice that only abt 8 out of 80+ clients are having R4, the rest are still in R2. Why is it so? Must I do a force restart of all the client PC?

Vnner, regarding your suggestion using the Mgt. server reconfiguration, you mention the client database at B will be gone, and can reestablish them using Sylink replacer. Is it safe? Will I be losing part of existing B client database even after using Sylink replacer?

Once you insta ll SEPM on site B or Install it as a replication partner the database will be overwritten by the new one.
But you will loose all your policies,settings and configuration changes made, You will also loose all your clients in site B.
To bring back the clients you can use Sylink Replacer but for everything else you will have to configure it again.
You cannot restore a previous backup of site B after replication as it will break replication.