RE: decommissioning the old domain after inter-forest migration



Hi,

As you read in the TechNet article, we recommend you run Security
Translation in replace mode to prevent SID history redundancy. If you no
longer need the old domain, we may suggest you do this. However, if you
don't do this step, also doesn't matter.


Best regards,

Vincent Xu
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

This posting is provided "AS IS" with no warranties, and confers no rights.


--------------------
>>Thread-Topic: decommissioning the old domain after inter-forest migration
>>thread-index: AcYVWYOpVfUNNAbUQFuewKm8hEKA1w==
>>X-WBNR-Posting-Host: 65.213.142.100
>>From: "=?Utf-8?B?RGlwdGk=?=" <Dipti@xxxxxxxxxxxxxxxxxxxxxxxxx>
>>Subject: decommissioning the old domain after inter-forest migration
>>Date: Mon, 9 Jan 2006 12:16:03 -0800
>>Lines: 32
>>Message-ID: <46AC5DE4-25E3-4A72-93F0-6E50E4F01234@xxxxxxxxxxxxx>
>>MIME-Version: 1.0
>>Content-Type: text/plain;
>> charset="Utf-8"
>>Content-Transfer-Encoding: 8bit
>>X-Newsreader: Microsoft CDO for Windows 2000
>>Content-Class: urn:content-classes:message
>>Importance: normal
>>Priority: normal
>>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>>Newsgroups: microsoft.public.windows.server.migration
>>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
>>Xref: TK2MSFTNGXA02.phx.gbl
microsoft.public.windows.server.migration:21954
>>X-Tomcat-NG: microsoft.public.windows.server.migration
>>
>>Hello,
>>
>>Here is my question regarding decommissioning the old domain.
>>
>>Here is the basic info:
>>
>>We used ADMT V3 to migrate users account, computer account, file servers.
>>Every thing seems to be working now. We also migrated exchange server
from
>>source to target domain using exchange migration wizard.
>>
>>During the migration I have choose the following options:
>>
>>1) For user migration, I h chose to enable target accounts -- and disable
>>source account in 60 days.
>>
>>2) For computer migration, I chose to use "Add" mode instead of
"replace"
>>mode.
>>
>>3) We chose to use SID History and Sid filtering.
>>
>>Now that we are almost to the point to decommission our source domain
(old
>>windows 2000 domain), I am wondering what I need to do to accomplish this
>>without getting into problem after decommissioning old domain.
>>
>>In the documentation for " restructuring active Directory domain between
>>forestâ?? I believe it is recommended to run computer migration again in
>>"Replace" mode for the file servers(I need to refresh my memory). Is this
a
>>necessary step? How do you go about decommissioning old domain for good.
>>
>>Thanks.
>>--
>>Dipti
>>

.



Relevant Pages

  • RE: SID History Not working after migration
    ... since it is a duplicate thread. ... SID History Not working after migration ... Do not expire source account ...
    (microsoft.public.windows.server.migration)
  • Re: exchange 5.5 test lab
    ... Is SID history a requirement when migrating NT4.0 accts to a new ... this would be consider as an inter-org migration since an exchange org ... Hope I am not making this too difficult but perhaps my migration path should ... | migration tool NetIQ to migrate all our NT accounts to win2003. ...
    (microsoft.public.exchange.admin)
  • Re: exchange 5.5 test lab
    ... We are in the process of performing an intra-org migration however we have ... environment and requirement there is no need for SID history since all data ... Install and run Exdeploy tools on the new exchange 2003 server ... Exchange Server 5.5 Directory Service and Exchange Server 2003 AD. ...
    (microsoft.public.exchange.admin)
  • Re: SID Hitory Not Working after ADMT 3 Migration
    ... Global Groups which the user was a member of. ... change the NTFS permissions and give their account in the new domain ... Shouldn't their SID history give them ... SID Hitory Not Working after ADMT 3 Migration ...
    (microsoft.public.windows.server.migration)
  • RE: Unable to Migrate SID History
    ... Best regards, ... Microsoft Online Partner Support ... Unable to Migrate SID History ... >>We have confiured the souce domain for SID migration as per the article: ...
    (microsoft.public.windows.server.migration)