New forest?
Updated: 14 Nov 2011 | 6 comments
This issue has been solved. See solution.
Hi,
I have a question;
A company which needs to carry all of the domain and exchange environment to new forest and domain.
Enterprise vault mbx archiving and journaling is also running.
All of the exchange mailboxes will carry to new forest exchange with MS ADMT and exchange 2010 prepare-moverequest.ps1.
How can i carry existing EV data and environment to new one?(all of the mbx names will be changed,forest and domnain will changed.)
thanks...
Discussion Filed Under:
Comments
It's probably best to read
It's probably best to read out to your Symantec Partner to assist you with this type of migration
www.quadrotech-it.com - All your EV Tools
How can i carry existing EV
How can i carry existing EV data and environment to new one?(all of the mbx names will be changed,forest and domnain will changed.)
Ref. http://www.symantec.com/docs/HOWTO37779
Regards,
MN
if i understand the post
if i understand the post correctly, i dont think this applies in his situation. he is not building a new EV environment. the question is about taking it out of one domain and joining it to the new one. hense, ADMT, etc.
Andy Becker | Authorized Symantec Consultant | Trace3 | Symantec National Partner | www.trace3.com
my plan is;
please check my steps if you have any additional suggests or plan please inform me;
I have 2 VM machine.
1-rejoin sql and ev server in new domain and forest .
2-change evadmin account with new one and login to evserver.
3-change sql informations;
Open up SQL Enterprise Manager or SQL 2005 Management studio
Open up the EnterpriseVaultDirectory Database
Open up the ArchiveRetrievalTask Table
Check the 'MessageQueue' column to reflect the new server name
Open up the ComputerEntry table
Check 'ComputerName' column to the ALIAS (CNAME) created for the server in the DNS from the old
alias to the new alias name
Check 'ComputerAlternate' column to the NetBIOS name of the new server
Open up the VaultStoreEntry table
Check 'SQLServer' column to be the new SQLServerName
Check StorageArchive to use the new server for the MSMQ name
4-create a new zone and host records that points to old domain
ie: company.local to newcompany.local
question;
old archived items is goes to;
https://oldcompany.local/EnterpriseVault/ViewMessa...
can i redirect these old items with new zone definition and records to ?
https://newcompany.local/EnterpriseVault/ViewMessa...
it resolves and changes new adress or not?
if it is not how can i migrate old dates in same server with new rejoined domain?
thanks...
here the high level overview
here the high level overview of the steps needed:
1. Create a new VSA in the new domain and assign all the required permissions on the Exchange, SQL and existing EV servers.
2. Migrate all EV databases from the SQL server in the old domain to the new SQL server in the new domain (http://www.symantec.com/docs/TECH35744).
3. Replace the old VSA account with the new one in the VAC.
4. Move EV servers to the Newdomain.
If the EV servers are configured by utilizing the FQDN (e.g. EVserver.olddomain.com) and the name resolution for the old domain will not work after the migration to the in the new domain you have the following possibilities:
1. Remove the old A-record for the EVserver.olddomain.com in the DNS and create a Cname DNS alias with the same name EVserver.olddomain.com pointing to the EVserver.newdomain.com. The EVserver.olddomain.com must be resolvable for users even if the olddomain.com domain name will disappear completely. If it’s not possible or does not work for some reason go to the next step.
2. Change the FQDN for EV server manually in the ComputerEntry table. Check if the shortcut policy is configured to use links. If yes, it can be an issue afterwards as the links are usually “hard coded” and contain the old FQDN EVserver.olddomain.com. In Exchange you can rebuild the shortcuts (http://www.symantec.com/docs/TECH47364). Best practice recommendation is to implement EV servers utilizing the short name instead of FQDN (exactly because of such situations with domain renaming or migration).
Cheers and good luck. Look forward to hearing from you how it goes.
Andy Becker | Authorized Symantec Consultant | Trace3 | Symantec National Partner | www.trace3.com
KG, let us know if you need
KG, let us know if you need anything else and it would be great to hear back from you on how it goes.
Andy Becker | Authorized Symantec Consultant | Trace3 | Symantec National Partner | www.trace3.com
Would you like to reply?
Login or Register to post your comment.