RE: ADMT Profile and Client problems
- From: v-xuwen@xxxxxxxxxxxxxxxxxxxx (Vincent Xu [MSFT])
- Date: Tue, 16 Aug 2005 02:43:54 GMT
Hi Jon,
>From your description I found you are in a mass and in a sweat. If your
issue is urgent, I suggest you contact Microsoft Customer Service and
Support for assistance.To obtain the phone numbers for specific technology
request please take a look at the web site listed below.
http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS
If you are outside the US please see http://support.microsoft.com for
regional support phone numbers.
>From your description, I noticed that your windows 2003 domain still don't
have a DNS server. But AD required a DNS server in domain, so please add
DNS first.Recommend integrate it with AD. (I think you also realize this
problem).
In addition, as you said the the DHCP service also hold at NT side, please
also migrate it to 2003 side as a workaround. To migrate DHCP server,
please refer to following article:
<http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/DepK
it/94bddace-d5ab-4979-8853-491c36f1fa3b.mspx>
Hope it helps.
Best regards,
Vincent Xu
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
--------------------
>>From: "Jon E via WinServerKB.com" <forum@xxxxxxxxxxxxxxx>
>>Subject: ADMT Profile and Client problems
>>Date: Mon, 15 Aug 2005 10:23:27 GMT
>>Message-ID: <52DFD9678B4D8@xxxxxxxxxxxxxxx>
>>X-Original-NNTP-Posting-Host: 81.86.110.138
>>X-Complaints-To: http://www.WinServerKB.com/Uwe/NB/Abuse.aspx
>>Complaints-To: http://www.WinServerKB.com/Uwe/NB/Abuse.aspx
>>Newsgroups: microsoft.public.windows.server.migration
>>NNTP-Posting-Host: mail.advenet.com 216.32.72.34
>>Lines: 1
>>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP09.phx.gbl
>>Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.windows.server.migration:11658
>>X-Tomcat-NG: microsoft.public.windows.server.migration
>>
>>Hi, I really hope someone can shed some light on a problem we've been
having
>>as after a 86 hour week my brain just isn't thinking straight anymore.
>>For the purposes of this post I will refer to the domains as DOMAIN1 (NT)
and
>>DOMAIN2 (Child domain in 2003 Forest)
>>
>>We are in the process of migrating an NT4 domain (DOMAIN1) to 2003 domain
>>(DOMAIN2)
>>
>>All the OU structure, GPO's etc are in place and are replicating happily
>>between the sites etc so we are fairly confident that the problems we are
>>having are DOMAIN1 related.
>>
>>All the usual reg keys (TCPClientSupport etc) have been setup, Domain
admins
>>groups been made members of both domain's Administrators group as per the
>>ADMT white paper.?? Two way trusts are in place with two domains and have
>>been verified.
>>
>>The NT4 Domain currently sends handles the DHCP side of things and the
>>DNS/WINS.
>>
>>Here is what is going wrong:
>>
>>1. Cannot copy the profiles, getting an error stating that it cannot write
>>ntuser.dat to the registry as access is denied but as far as I can tell we
>>have full admin rights on both domains and the client device too.
>>
>>2. When we migrate the client devices it goes through all the motions,
>>despatches the agent and reboots the box.
>>
>>When the user comes to log on it says that DOMAIN2 is unavailable.??I'm
>>pretty certain that this is because it has no visability of the new domain
>>because there are no WINS DNS settings being passed to it relating to the
new
>>domain (if i add details in LMHosts file on client they can log on ok) -
>>Presumably the information for DOMAIN2 must be part of the DHCP settings
that
>>get allocated via DOMAIN1?
>>
>>The even messier problems arise once the user tries to access MS Outlook
2000,
>>all that happens is a dialogue box stating "Outlook cannot start" !
>>
>>ADMT in the lab environment worked perfectly which leads me to believe
that
>>all the problems we are having in live are to do with the legacy DOMAIN1.
>>
>>HELP PLEASE!!
>>
.
- References:
- ADMT Profile and Client problems
- From: Jon E via WinServerKB.com
- ADMT Profile and Client problems
- Prev by Date: RE: Using wrong domain controller
- Next by Date: RE: How to migrate CA to New DC
- Previous by thread: ADMT Profile and Client problems
- Next by thread: How to migrate CA to New DC
- Index(es):
Relevant Pages
|