Re: NT->W2K3 User Migration Question

From: Keith Caravelli (keith_at_caravelli.com)
Date: 03/24/05 

Date: 23 Mar 2005 20:55:20 -0800

How exactly is this done. I have looke throught google and MS and it
is escaping me.

I have a problem trying to figure out the status of my NT 4 to Win2003
upgrade.
1) I have upgraded an Old NT4 PDC and demoted our PDC to a BDC.
The upgrade seemed to work fine.
Our old NT domain name of "asko" is still used for logon by all
clients.
The NT upgrade had NT4Emulator key put in before upgrade.
It now is a Win2003 DC with AD and DNS.

2) I then took a new server with OEM Win2003 that was a test DC with AD
and demoted it while offline and brought it back up with DC promo using
the NeutralizeNT4Emulator key BUT NOT THE NT4EMULTOR KEY. Just the one
key.
Now the new Win2k3 DC has AD, DNS and WINS and almost all seems to be
working fine.
3) I keep getting the message Error 5917:
  "This computer was not able to set up a secure session with a domain
controller in domain ASKOMAIN due to the following:
There are currently no logon servers available to service the logon
request."

 This does not seem to be causing any problems, however. I seem to
replicating DNS and AD and Wins correctly but I need to know if it is
safe to move forward and start letting users logon here.

4) These Domains in AD are called "askomain.corp" the old netbios NT4
domain is called "asko" The users see both domains choices when logging
in. I would like to get rid of one.
5) I am sitting on an XP Pro system writing this memo from my office at
home.
This pc has been joined and it has used both NeutralizeNT4Emulator and
not used it. It is connected via software VPN (Netscreen) to the
client site.

So just how on earth do I know if users are logged in. When I go to
Users and Computers, I see everyone there, but the Upgraded DC acting
as the PDC is replicating everything and I have one BDC in the loop as
well.

Any thoughts on knowing if the error 5719 is a problem.
Any thoughts on knowing if we are ready or are we acutally already
there.
I tried adding the NT4Emulator to the Second Win2k3 DC last night and
the Win2k and XP Pro PCs could not find the Asko domain when trying to
logon this morning. This has me worried. I took out the NT4Emulator
from the New Wn2k3 server that has the NeutralizeNT4Emulator already in
it and everyone was fine.

One last thing: The DNS suffix in the original PDC upgraded to Win2k3
says "asko" the old NT netbios domain name. The new Win2k3 server
which was dcpromod is blank.

Bob Qin [MSFT] wrote:
> Hello,
>
> Thanks for your posting here.
>
> Can you use the two user accounts to logon Windows 2003 domain
> successfully? If you can find the two user accounts in Windows 2003
domain,
> then it means that the two users were migrated successfully.
>
> When you logon the clients, you can run "set" command in DOS prompt
and
> check the LOGONSERVER value. In general, Windows 2000 Professional
client
> will use your Windows 2003 DC for authentication. Please make sure
that the
> DNS setting is point to the same one with Windows 2003 DC.
>
> Have a nice day!
>
> Regards,
> Bob Qin
> Product Support Services
> Microsoft Corporation
>
> 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.

Relevant Pages

  • Re: NT to W2K3 Migration
    ... You cannot just promote a member server to AD. ... upgrade your PDC to windows 2000 or 2003, whichever flavor of AD you want to ... Upgrading from Windows NT Server 4.0 ... ensure that you have designed a DNS ...
    (microsoft.public.windows.server.active_directory)
  • Re: Native 2003 mode and NT4 workstations?
    ... Migrating from Windows NT Server 4.0 to Windows Server 2003 ... How to Upgrade from Windows NT Server 4.0 ... ensure that you have designed a DNS ...
    (microsoft.public.windows.server.active_directory)
  • RE: NT4 server and W2K3
    ... The underscore "_" character is not a standard character for domain DNS ... I think that you can upgrade the domain with the existing NetBIOS ... |Subject: RE: NT4 server and W2K3 ... |Windows NT 4.0 server on the network and about six ...
    (microsoft.public.windows.server.migration)
  • Re: Authentication process extremely long...
    ... logging on to Windows XP Pro in a domain environment can take up to ... If I logon using the same user name but on a different computer the ... Check the DNS settings on the workstation. ...
    (microsoft.public.windowsxp.general)
  • Re: Underscore issues...
    ... My problem is I have a Windows NT server running ... I suggest you rename the machine, before you run DCPROMO. ... make sure you use a DNS name with a "." ... After you upgrade, and before you DCPROMO run an ipconfig /all, the primary ...
    (microsoft.public.win2000.dns)
Loading