Management server gone need to replace
Created: 21 Nov 2011 | 17 comments
My SEP management server crashed. 2 bad drives at the same time so my RAID array failed. Long story short I am rebuilding the server using the same name and IP address.
What is the best way to re-install the SEP management console? I am running version 11.0.6100.645
Thanks in advance for any assistance you can provide.
Discussion Filed Under:
Comments
I'm guessing you do not have
I'm guessing you do not have any backup's. In that case there's only one way,
Re-install SEPM and then use the sylink replacer to replace sylinks on the clients and bring them back.
Do you have anything as
Do you have anything as backup ? DB, Private key etc ?
If not just rebuild new SEPM (install new SEPM)
Add the old Domain Name..you can find the domain name from syliink file of any client.
Check the disaster recovery doc.
http://www.symantec.com/business/support/index?page=content&id=TECH102333
VMWARE-- SEP 12.1 vs McAfee vs Trend Micro
Hello, Please refer to the
Hello,
Please refer to the below link,
Overview of how to move the Symantec Endpoint Protection Manager from one machine to another
http://www.symantec.com/business/support/index?page=content&id=TECH148555&actp=search&viewlocale=en_US&searchid=1321908152269
No DB backup, no private key
No DB backup, no private key export. I know I suck.
Re-install SEPM and then use
Re-install SEPM and then use the sylink replacer to replace sylinks on the clients and bring them back.
I am going to name the server
I am going to name the server exactly the same and the IP address is going to be the same. Will the clients just start seeing the "new" server or do I need replace the sylink on all the clients.
Follow
Follow this:-
http://www.symantec.com/business/support/index?page=content&id=TECH104389&actp=search&viewlocale=en_US&searchid=1321910003995
B) Disaster Recovery method
The old server died. I can't
The old server died. I can't logon to it, it doesn't exist anymore.
To restore client
To restore client communications without a database backup
Note: The computers appear in the Temporary group.
Get the domain Id from a sylink.xml from any one of the clients that was communicating earlier, with the old SEPM.
Disaster Recovery says
To backup the database but it doesn't give instructions on how to backup the DB. Is there a tech article somewhere I am not seeing? I am not using SQL Express for the DB, I chose to let Symantec setup the DB.
Thanks.
Please check following
Please check following article it might help you.
Title: 'How do I move Symantec Endpoint Protection Manager from one server to another with a different IP address and host name?'
Document ID: TECH104389
http://www.symantec.com/business/support/index?page=content&id=TECH104389
Arpit Badwaik
Symantec Technical Support Analyst, SEP
MCITP
Don't forget to mark your thread as 'SOLVED' with the answer that best helped you
amantica Just follow the
amantica
Just follow the instructions that I have asked you to follow for the Domain Id thing and that should bring your client communication back.
I have done that and so far
I have done that and so far no luck. I used the sylink from my pc, added the domain ID back as you posted and no communication yet.
Also, when I start the SEPM Console it says "Unable to communicate with the reporting component"
What database are you
What database are you using?
When you browse through IIS > Reporting does it gives you the blue login page to the SEPM?
Did you try to establish ODBC connectivity?
Can you collect the sylink logs from one of the client which is not connecting to the SEPM and post it over here?
I have the sylink log but I'm
I have the sylink log but I'm not sure how much of it I should post. What exactly are you looking for?
You need to fix the Unable to
You need to fix the Unable to connect to report component..hope you are not installing SEPM on XP OS.
Check this document
http://www.symantec.com/business/support/index?page=content&id=TECH104777
VMWARE-- SEP 12.1 vs McAfee vs Trend Micro
Installing on Server 2003 R2
Installing on Server 2003 R2 SP2. Tried that tech doc already, will follow again. Maybe I missed something.
Would you like to reply?
Login or Register to post your comment.