MIgration of file server, Symantec Enpoint Manager and RDS (2008 R2, 2008 R2 and 2012 (64-bit)

How is your sep setup, does it use SQL as backend?
Backup the seo db.

Install see management on the new VM, restore from backup.
Update the existing step to point the clients to the new server

If you use SQL, you can setup the management and point it to the common SQL server.

Oh, missed, the fileserver can be migrated using dfs-r, do not use the same names/IPs.
If fileserver uses dfs names it would be simpler.
RDS has to be reliable sed RDS 2008 do not transfer to newer versions.

Dfs-replication can be used to sync data from existing location to the new one, the process will keep it in sync as files are added, modified.

..

hi! Arnold,

for the Symantec, I did the replication setup so the setup looks like the previous server, but all the clients are offline. so I need to read further on what to do next

For the file server, I installed Windows admin center on the new server I did not know that there is dfs replication solution as these server migrations are new to me, usually done by my boss. windows admin center last progress was scanning all the shared folders from the old server, but I saw some of the server's shares like D drive, vvol were red and error.

need to read more to know what to do

On the existing to which the clients are reporting, you have to update the GAC file if not mistaken which would direct the client to contact the new manager without the need of redeploying the client install package.

HI! Arnold,

The replication works.

I have shut down the old sepm server.

The new SEPM server in the management list is priority 1, the old sepm server is priority 2.

How do i edit the "online at remote site" to "Online" in the status?

The Windows Admin Center after scanning says the bulk of the shared folders have succeeded.

But got one folder that says "Couldn't inventory some devices".

How do I resolve that?

Or should I go to DFS Replication?

I will try to continue with setup and see what happens next, after all the new server is new.

Usually, you should have both running until the clients transition.
You may have trigger the refresh on the client so that they check in with the new/higher priority ..

The other option is to bring up the ip of the other host but your setup might not make it possible.


Re admin center message, not clear..

Dfs-r once setup, will keep the data synchronized as long as files being added are not reflected as temporary, or have suffixes that are excluded from replication, such as .bak.

You can then publish the shared folder as a dfs share so future transition will not involve any additional steps by users.

Can Windows Admin Center do the transfer but leave out the cutover and is there a sync function for the files between the old and new file server??

The SEPM replication is working and I do have to turn on both old and new SEPMs.

Until one day when all the clients are synced then I can shut down the old SEPM server.

If not mistaken, you can direct the client or a group to refresh config/content at which point the client should get info to connect to the new higher priority manager.

I really have no idea on how I can do that.

I am now trying to install endpoints to the new servers by pushing to client but nothing is working.

hi! Arnold, we have successfully did the migration for the RDS and SEPM Server. now we need to find out why the Windows admin center is unable to copy some of the shared folders to the new server

what is the other method for file server migration? DFS...?

Dfs-replication will copy and maintain the data in sync without a need for downtime if the user references the dfs based share.

ok, I will read up on it and try to execute it.

Open dis management, replication, create a group with the existing server as the reference while the new server as the additional member, make sure to set the folder on the new server where it is ...

Test first with a sample folder.....if you'd prefer.

hi! Arnold, will do, as the new server already have some shared folders copied over under the Windows admin centre.

Hi! Arnold,

I created the replication group as follows

fileserver1 - D:\D and fileserver2 - D:\D

But I do not know why it created a D folder under the D drive.

How do I know if the replication is working?

For the SEPM, how do I tell if the clients are connected to the new SEPM server?

In the sep manager you can see which clients are connected to the management server As connected clients.

If not mistaken, a GAC.ini or something similar is a file can be exported from the new and dropped into a folder for step on the client to retarget it, but since you have both up, on the one you are retiring setting the preference for the new while making sure the new refers to itself as primary......
Allowing time, the clients should auto migrate to the new....

If you also centrally retrieve updates, make sure to retarget that if you have to setup the live administartor as well.

since the Windows admin center failed to transfer some of the shared folders, how can I delete the folders that were successfully transferred over as it seems the dfs replication is doing better but there is insufficient space

Have not used, delete the share on the newserver.ran out of space, meaning when adding the share, you did not specify the location, which drive letter you want the share?

Have not used admin center in such a way.