Re: Global Catalog server error

In news:261E4462-C23B-4F30-8D27-BE866FC9AF15@xxxxxxxxxxxxx,
Fabio <Fabio@xxxxxxxxxxxxxxxxxxxxxxxxx> stated, which I commented on below:
I am running the admt form the source forest not the target forest.
Yes dns is intalled and correctly running on both forests. I have
and external trust between the two. How do you know if the gc is
available in either forest?

Is NetBIOS name resolution in place that the target and source can resolve
each other's NetBIOS names? I assume this is in place, since you were able
to create a trust, but just wanted to verify that.

I would actually run it from the target domain. If it's any help, here's a
reprint of the steps I put together for someone else awhile back:
----------------------------------
From: Aceman
Sent: Fri 1/10/2003 12:05 AM
To: Aceman
Cc:
Subject: ADMT steps, refined with links

Best option is to create a brand new domain in a new pristine forest called
local.domain.com. Or you can make it just domain.com. Not sure why even need
to bother with local as a child domain of domain.com. I would prefer
domain.com, but you will need to follow your company's guidelines they may
have in place.

Then I would use the ADMT tool. Read this about migration. The idea is the
same as W2k to W2k:
Domain Migration Cookbook - Chapter 10 Consolidation of Windows NT 4.0
Resource Domains:
http://www.microsoft.com/technet/prodtechnol/windows2000serv/deploy/cookbook/cookch10.asp

ADMT 2.0 is a nice tool. Available on the .NET beta cdrom. If you don't have
that, download ADMT v1.0 here:
http://www.microsoft.com/windows2000/downloads/tools/admt/default.asp

Steps:
Trust recommended two way between source and target.

ADMTv2 will handle the TCPClientSupport reg settings on target and source
and
the DOMAIN$$$ group on the source.

If using ADMT v1.0, follow these steps to configure the above. It is for NT4
to W2k, but the procedure is the same:
http://support.microsoft.com/default.aspx?scid=KB;en-us;q260871

Then

1. Logged on target, migrate users acccounts (including associated groups).
Include the SIDHistory.
2. Logged on target, migrate group accounts (the ones that the above didn't
get).
3. Logged on source (from target), migrate computer accounts. ADMT will send
out an agent that will install on all client machines that are joined to the
domain. The client machines will automatically be moved to the new domain
and it will preserve the local profiles and move them with the new account
name.
4. Logged on target, run the security translator from ADMT.
5. If going from NT4 to W2k AD, before upgrading, correctly set the Primary
DNS Suffix.

Obviously you may want to test this on your own workstation or a test
workstation so you know what's involved.
Hope it helps.
----------------------------


--
Ace
Innovative IT Concepts, Inc
Willow Grove, PA

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft MVP - Directory Services
Microsoft Certified Trainer

Having difficulty reading or finding responses to your post?
Instead of the website you're using, I suggest to use OEx (Outlook Express
or any other newsreader), and configure a news account, pointing to
news.microsoft.com. This is a direct link to the Microsoft Public
Newsgroups. It is FREE and requires NO ISP's Usenet account. OEx allows you
to easily find, track threads, cross-post, sort by date, poster's name,
watched threads or subject.
It's easy:

How to Configure OEx for Internet News
http://support.microsoft.com/?id=171164

Infinite Diversities in Infinite Combinations
Assimilation Imminent. Resistance is Futile
"Very funny Scotty. Now, beam down my clothes."

The only constant in life is change...


.

Relevant Pages

  • Re: migrating computer account from SBS2000 to WS2003R2 using ADMT
    ... I run ADMT on the target domain I get the access denied error when trying to ... SBS2000 Server to a Windows Server 2003 Standard Edition R2 using ... The machine account migrates fine ... create a two-way trust between the two domains? ...
    (microsoft.public.windows.server.active_directory)
  • Re: Using ADMT
    ... Must I install ADMT in the new DC, creating Trust Relationship and migrate ... Keys include Trust between the source and target (source trusts target ... Agent on source; ADMT on target; you must be admin on both so your ...
    (microsoft.public.windows.server.active_directory)
  • RE: ADMT ver 3: ERR2:7816
    ... 2003 domain to target Windows Server 2003 domain. ... The ADMT box is in target ... groups of target domain are delegated to Admin account of source domain. ...
    (microsoft.public.windows.server.migration)
  • RE: W2k3 to w2k3 Admt
    ... Thanks for posting! ... thought the account of source domain has the ... I would like to suggest you use a SID mapping file with ADMT or SubInACL ... please first reconfirm that you have established the trust ...
    (microsoft.public.windows.server.migration)
  • Re: Distribute to user account objects in specific AD group in SCC
    ... It does NOT work the same way as users in a usergroup. ... Testing the deployment of published apps to targeted user accounts worked at ... computer account collections to download first, ... *could* attempt to leverage the Top Console User, and target "computers ...
    (microsoft.public.sms.admin)