cancel
Showing results for 
Search instead for 
Did you mean: 

Syncinmigrationmode was not performed

Sarah_Seftel1
Level 6
Partner Accredited

Hi all

 

scenario:

company moved  to a new exchange server. but did not configure the new exchange server in the EV and did not used the syncinmigrationmode registry key when they moved mailboxes from the old exchange to the new exchange...

 

now - if they'll update the new exchange server in the EV and sync + provisiong the server - than new EV archives will be created to the users.

 

is there a way to connect the users to their old EV archives and prevent the creation of new EV archives?

 

thanks,

 

Sarah.

1 ACCEPTED SOLUTION

Accepted Solutions

JesusWept3
Level 6
Partner Accredited Certified
You almost answered your own question But synch in migration mode in nearly all companies is best to stick on permanently with a value of 2 When you run the provisiong task next ev will see that the legacymbxdn matches the moved users and will link that mailbox to the old archive, it is possible though without the key then EV can just consider it to be a new mailbox and now you have duplicate archives If you haven't run the prov task yet and think you may end up with duplicate archives then there is every pint in adding he registry key
https://www.linkedin.com/in/alex-allen-turl-07370146

View solution in original post

6 REPLIES 6

GertjanA
Moderator
Moderator
Partner    VIP    Accredited Certified

You should use the SynchInMigrationMode key.

That will work fine.

Please do note the 'h' behind the sync. (i made the same mistake)

 

Gertjan

Regards. Gertjan

Sarah_Seftel1
Level 6
Partner Accredited

smiley noted the H...

 

I want to be sure that I understand correctly...

The exchange mailboxes has already moved to the new exchange server WITHOUT using "Synchinmigrationmode" from the first time.

If I'll configure new synch & provisioning task to the new exchange server it will create new EV archives to the users and ignore the old EV archives.

 

So, I think that using "Synchinmigrationmode" after the mailboxes are moved will be pointless.

Am I right?

 

Sarah.

 

JesusWept3
Level 6
Partner Accredited Certified
You almost answered your own question But synch in migration mode in nearly all companies is best to stick on permanently with a value of 2 When you run the provisiong task next ev will see that the legacymbxdn matches the moved users and will link that mailbox to the old archive, it is possible though without the key then EV can just consider it to be a new mailbox and now you have duplicate archives If you haven't run the prov task yet and think you may end up with duplicate archives then there is every pint in adding he registry key
https://www.linkedin.com/in/alex-allen-turl-07370146

AndrewB
Moderator
Moderator
Partner    VIP    Accredited

are you sure it shouldn't be a value of 1?

HKLM\SOFTWARE\KVS\Enterprise Vault\Agents\SynchInMigrationMode

0 - (Default.) Generate an error in the event viewer log.
1 - Link the new mailbox to the old record.
2 - Create a new record for the new mailbox

http://www.symantec.com/business/support/index?page=content&id=TECH54529

JesusWept3
Level 6
Partner Accredited Certified

crap

sorry yeah, 1!

Good catch :)

https://www.linkedin.com/in/alex-allen-turl-07370146

Sarah_Seftel1
Level 6
Partner Accredited

I thoght of putting the synchinmigrationmode reg value on 1, but was not sure if it will do the jog after mailboxes already moved...

 

will do that,

 

cheers!

 

Sarah.