Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

migrate enterprise domain for EV 2007 SP1

Updated: 21 May 2010 | 5 comments
noble's picture
0 0 Votes
Login to vote

hi all

 

please assist me the problem follow:

i had installed EV 2007 SP1 for Exchange 2003 journaling archiving half years ago.now my company will change enterprise domain,how can i migrate EV server to the new domain.

 

any article,link or information is welcome.

 

thank you a lot

discussion Filed Under:

Comments

Amit Gupta's picture
07
Sep
2008
0 Votes 0
Login to vote

I am not sure if there any single document which narrates the steps for domain migration. However if you used cnames/alias for the ev server rather than FQDN names or actual server names in your EV confiuration, then domain migration should not be a big problem. It seems that you are just doing EV Journaling, which means there are no shortcuts to worry about. As long as the cname remains the same and it is connected to the same SQL database, you should not have any problems in the new environment.

noble's picture
07
Sep
2008
0 Votes 0
Login to vote

thanks for your reply

 

unluckly,when i install EV i set alias name the same as FQDN name.

 

now i try modify the directory server name in vault directory database,it's cannot update table computerentry column sitentryid to new server FQDN name

 

how can i proceed to

Amit Gupta's picture
07
Sep
2008
0 Votes 0
Login to vote

Its still possible to do it by hacking SQL database since you are only doing Journaling. I would strongly recommend to involve support to do that.

MichelZ's picture
11
Oct
2008
0 Votes 0
Login to vote

Have you sorted this out?

 

Cheers

Michel

www.quadrotech-it.com - All your EV Tools | www.techfreak.ch

noble's picture
12
Oct
2008
0 Votes 0
Login to vote

i have not finished this operation yet.

 

symantec sales engineer suggest me follow the KB:http://seer.entsupport.symantec.com/docs/284641.htm,but it's not work.