Quick Update - Robocopy is STILL copying the files...it is under 1TB for sure but upwards around 800-900 GB. Our biggest software suite generates a TON of files so it is the sheer amount of files I believe. It is on the last huge directory so should pick up after it is complete.

The file server VM has been allowed 8GB (and dynamic) memory it is hovering around 90% right now:

The biggest culprit is Symantec Endpoint, using about 214MB and it's SQL Anywhere Embedded Database about 134MB. That is actually normal and what it shows on the current server. Then there is other processes with negligible memory use. So, could it be from the file copying? I don't see how what I show to add up to 7GB of memory use.

@garak0410 said:

@IRJ said:

Did anyone mention DFS to you Garak?

During your transition period you could use DFS Replication to keep shares synced up between the two servers.

http://www.windowsnetworking.com/articles-tutorials/windows-2003/Configuring-Using-DFS-Replication.html

Yes...it has been mentioned but my list has been too full to think of anything else...I'm a solo IT shop, so I am still handling workstation issues, office equipment issues, cell phones, software coding issues...juggling!

That said...I am checking it out now...I may work late tonight...tomorrow is my official move to new servers evening...

@IRJ said:

Did anyone mention DFS to you Garak?

During your transition period you could use DFS Replication to keep shares synced up between the two servers.

http://www.windowsnetworking.com/articles-tutorials/windows-2003/Configuring-Using-DFS-Replication.html

Yes...it has been mentioned but my list has been too full to think of anything else...I'm a solo IT shop, so I am still handling workstation issues, office equipment issues, cell phones, software coding issues...juggling!

I know a lot of you have other suggestions beyond login scripts but I am sticking with them for now...but running into a drive mapping problem...

Question - Our main File Server Drive has a folder called ALL and then under that, various folders like Accounting, Purchasing, etc..

On the current server, you can map directly to one of those folders rather than having to do \server\All\Accounting

I am sure this is something I need to set at the root of the drive but cannot recall. Any suggestions?

This Robocopy command is working for me:

robocopy /mir /sec /copyall \oldserver\d$\ \newserver\e$\

I am running it now and it is working.

Question, if I run this again later, by default, will it only copy changed/new files from source?

@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.

@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...

@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.

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.

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-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.

@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.

@garak0410 said:

@scottalanmiller said:

@garak0410 said:

Getting a lot of these on the same file...is there a flag to skip this error or go to the next file? It will not proceed:

Access is denied.
Waiting 30 seconds... Retrying...

It should skip after a few attempts. Do you have a lot of things open? Ideally you want everything turned off.

Not at the moment...this is a sbscolsole.msc file and it tried at least 10 times before I canceled it...never moved off of it...

This file and it's directory (called Admin) should not be open...I'd like to skip it but continue with copyall if I can.

@scottalanmiller said:

@garak0410 said:

Getting a lot of these on the same file...is there a flag to skip this error or go to the next file? It will not proceed:

Access is denied.
Waiting 30 seconds... Retrying...

It should skip after a few attempts. Do you have a lot of things open? Ideally you want everything turned off.

Not at the moment...this is a sbscolsole.msc file and it tried at least 10 times before I canceled it...never moved off of it...

I am having frustrating problems moving SEPM Small Business Edition from our (soon to be) old server to my new one.

I've studied and attempted to follow the steps (solution B) here and it just doesn't seem very clear:
http://www.symantec.com/business/support/index?page=content&id=TECH183666

For example, when it says: Install the same version of the SEPM you have now on the new machine (1). Use the procedures described in the Disaster Recovery in order to restore the database that you backed up from the old server, as well as the configuration files.

I've installed the same version but it says use the procedures described in the Disaster Recovery. SO I do and it says this:

Reinstall Symantec Endpoint Protection Manager using a disaster recovery file (gathered in Step 2 above). When the Management Server Configuration Wizard runs, choose "Custom configuration" and "Use a recovery file".

I understand what it says here but I never get the option to choose Custom Configuration and Use Recovery File.

It also says to go to on the original server: 3.Click Policies > Policy Components > Management Server Lists > Add Management Server List

I have no such options in my existing SEP.

So, I am a little confused as to what I need to do here. In addition, I thought I handled this part (it found a recovery file from our current server that I manually copied to the new one) and I tried to restore database (again, copied the backup DB to the new server) and restore says it cannot connect to the database and it never asks me to point to it.

Suggestions are really needed as I want to get this step done.

Thanks!

Getting a lot of these on the same file...is there a flag to skip this error or go to the next file? It will not proceed:

Access is denied.
Waiting 30 seconds... Retrying...

@scottalanmiller said:

/sec applies security, /secfix attempts to fix it. Pretty sure that they cannot be mixed.

Thanks dude...copying now.

I am doing a copy now to test some login scripts before Friday. I'll run a fresh one on Friday evening. Getting closer...got another problem I'll make in another post...Anti-Virus migration isn't going "by the book."

@scottalanmiller said:

Why are using /sec and /secfix ? One or the other.

Because it was suggested earlier in this thread...LOL

@scottalanmiller said:

@garak0410 /secfix needs more info. Add /copyall

http://technet.microsoft.com/en-us/library/cc733145.aspx

I added it and it still doesn't like secfix...maybe my syntax is still bad:

robocopy /mir /sec /secfix /copyall "\oldserver\d$" "\newserver\e$"

and the double \ is in there, just now showing up in the post...

@NetworkNerd said:

@garak0410 said:

Most people have said just ROBOCOPY the files from the old file server (in this case, SBS 2003) to the new one (2012 R2 Virtual Machine) and it will keep the permissions intact and echo the different server name...correct?

Something like this should suffice: robocopy /mir /sec /secfix "source" "destination"

Question...I want to just copy everything over from d$ on oldserver and copy to e$ on newserver. What's the best syntax for that? I am getting

ERROR : Invalid Parameter #3 : "/secfix"

Currently when trying this...