http://social.technet.microsoft.com/wiki/contents/articles/4268.fim-reference-migrate-from-miis-or-ilm-to-fim-2010.aspx
I am planning migration procedure from MIIS(SP1) to FIM2010 for galsync.
I think there is two way.
#1. use SQL2000 DB restore to SQL2008x64
#2. do not use DB restore and import mailbox data to empty FIM DB and import and join existing contact object by join rule.
In our migration scenario , we would like to avoid recreation of existing contact objects as possible because to avoid NDR and reduce tasks related to contact object recreation.
As far as I see the above link, #2 looks preferable because our environment is MIIS(SP1) and SQL2000(SP1) and #1 plan need to upgrade to MIIS(SP2) and SQL2000(SP4).
We have already FIM2010 in our domain where MIIS exists.
I think we can import server configuration xml or each MA's setting xml of current MIIS to existing FIM.
Question 1. If we only define import attribute flow from AD mailbox to Metaverse person object for each MAs (delete import flow of contact and all others import and export flows) in FIM2010, and import stage only of each MA and full sync and never run any export(delete export run profile) , is thera any negative impact on current MIIS and AD environment ?
After mailbox import and sync to FIM2010, I am thinking of making import attribute flow from existing AD contacts to FIM2010 Metaverse person object for each MAs with join rule by legacyExchangeDN value. ( I think in current MIIS setting, MIIS collects legacyExchangeDN of contact to MIIS metaverse person object's legacyExchangeDN(multi-value) and export collected legacyExchangeDNs to source mailbox's proxyaddressses as X500 address.(some MA are not but I think we can change it in that way, and current MIIS import flow from AD mailbox to metevse person object of each MAs include import flow from AD mailbox X500 proxyaddresses to metevse person object legacyExcangeDN by rule extension. FIM metaverse has legacyExchangeDN value of existing contact object by this rule in previous mailbox import step and I think contact object is joinable by legacyExchangeDN value if we recompile current MIIS rule extenstion for FIM and put those DLLs to FIM extension folder).
Question 2. If this contact object join fail, is it possible to recover by unchecking source synchronization OU which contacts are placed(say OU1) and targer OU(OU1) which contacts are created in each MA's setting, or make new Empty OU(say OU2) and select OU2 for source and target OU in stead of OU1 without no negative impact to current MIIS and AD environment ? I thought if we uncheck OU1 and import and sync contact object again, I guessed Connector Space object of contact object will be deleted and there is no negative impact if we do not run any export to ADs.
Does this procedure make sense or how could we improve this migration procedure ?
I am making test environment of this MIIS to FIM migration and will test that migration procedure in test environment at first.
I am planning migration procedure from MIIS(SP1) to FIM2010 for galsync.
I think there is two way.
#1. use SQL2000 DB restore to SQL2008x64
#2. do not use DB restore and import mailbox data to empty FIM DB and import and join existing contact object by join rule.
In our migration scenario , we would like to avoid recreation of existing contact objects as possible because to avoid NDR and reduce tasks related to contact object recreation.
As far as I see the above link, #2 looks preferable because our environment is MIIS(SP1) and SQL2000(SP1) and #1 plan need to upgrade to MIIS(SP2) and SQL2000(SP4).
We have already FIM2010 in our domain where MIIS exists.
I think we can import server configuration xml or each MA's setting xml of current MIIS to existing FIM.
Question 1. If we only define import attribute flow from AD mailbox to Metaverse person object for each MAs (delete import flow of contact and all others import and export flows) in FIM2010, and import stage only of each MA and full sync and never run any export(delete export run profile) , is thera any negative impact on current MIIS and AD environment ?
After mailbox import and sync to FIM2010, I am thinking of making import attribute flow from existing AD contacts to FIM2010 Metaverse person object for each MAs with join rule by legacyExchangeDN value. ( I think in current MIIS setting, MIIS collects legacyExchangeDN of contact to MIIS metaverse person object's legacyExchangeDN(multi-value) and export collected legacyExchangeDNs to source mailbox's proxyaddressses as X500 address.(some MA are not but I think we can change it in that way, and current MIIS import flow from AD mailbox to metevse person object of each MAs include import flow from AD mailbox X500 proxyaddresses to metevse person object legacyExcangeDN by rule extension. FIM metaverse has legacyExchangeDN value of existing contact object by this rule in previous mailbox import step and I think contact object is joinable by legacyExchangeDN value if we recompile current MIIS rule extenstion for FIM and put those DLLs to FIM extension folder).
Question 2. If this contact object join fail, is it possible to recover by unchecking source synchronization OU which contacts are placed(say OU1) and targer OU(OU1) which contacts are created in each MA's setting, or make new Empty OU(say OU2) and select OU2 for source and target OU in stead of OU1 without no negative impact to current MIIS and AD environment ? I thought if we uncheck OU1 and import and sync contact object again, I guessed Connector Space object of contact object will be deleted and there is no negative impact if we do not run any export to ADs.
Does this procedure make sense or how could we improve this migration procedure ?
I am making test environment of this MIIS to FIM migration and will test that migration procedure in test environment at first.