Re: Upgrade NT 4.0 to W2003

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Marin Marinov (mlmarinov_at_askme.ca)
Date: 07/04/04 

Date: Sun, 4 Jul 2004 18:04:38 -0400

In article <25b7101c4605d$ae5222e0$a301280a@phx.gbl>,
anonymous@discussions.microsoft.com says...
> I have completed a inplace upgrade from nt 4.0 to w2003.
> All is working well. The client machines as well as the
> W2003 DC have the old "single Label" domain name in the
> login screen. During the upgrade I renamed the forest and
> domain to a domain.com from the "single label". To get the
> new domain name to appear on the client and DC logon
> screen do I have to remove the machine from the old domain
> and join it to the new domain.com domain? Is there any
> ramifications to profiles, permissions etc. I also still
> have to migrate from Exchange 5.5 in the single label
> domain to a exchange 2003 server in the new domain.com
> domain should I wait until this is complete before joining
> the machines to the new domain.com domain? I still have
> the nt 4.0 running with the new 2003 DC.
>
Hi Maynard,
Clients will always display the NetBIOS name in the logon dialog box and
you can't change that. Windows NT 4.0 domains used just NetBIOS names
and what you did during the upgrade is add the Fully Quallified Domain
Name (FQDN) that is needed in AD for each domain. Since you did an in-
place upgrade you don't need to rejoin the machines - that's one of the
goals of this type of migration anyway ;) Profiles and permissions are
also not relevant in this case. AFAIK you cannot upgrade Exchange 5.5
directly to Exchange 2003 and you need to migrate the mailboxes. You can
look for more information on the Microsoft web site as well as ask in
the Exchange newsgroups:

Exchange Migration and Upgrade Resources
http://www.microsoft.com/exchange/techinfo/interop/default.asp

HTH 

-- 
Cheers,
   Marin Marinov
   MCT, MCSE 2003/2000/NT4.0,
   MCSE:Security 2003/2000, MCP+I
-
This posting is provided "AS IS" with no warranties, and confers no 
rights.
"True knowledge exists in knowing that you know nothing."
Socrates

Relevant Pages

  • RE: [Full-disclosure] Symantec Anti-Virus Corporate Edition: DownloadProduct Upd
    ... That stupid check box has been there since v7.0.0 when Symantec first bought that product from Intel LanDesk. ... You cannot move one client to another server, for example, unless it is physically communicating with the server. ... automatically upgrade itself, due to the vast number of vulnerabilities ... Faculty and Staff machines are on the domain and are in general ...
    (Full-Disclosure)
  • Re: Problem connecting to POP3 and SMTP servers
    ... Are these client still located behind the SBS server? ... > machines through Outlook. ... > exchange account that is installed on my sbs 2003 ...
    (microsoft.public.windows.server.sbs)
  • Re: OWA Automatic Logon doesnt
    ... that would automatically configure the exchange settings. ... trying to access email on 10 different machines between 2 buildings, ... up and maintaining outlook profiles for a constantly changing client base ... I am running Exchange 2003 on a 2003 server, ...
    (microsoft.public.exchange.clients)
  • Re: Problem connecting to POP3 and SMTP servers
    ... >Are these client still located behind the SBS server? ... >> machines through Outlook. ... >> exchange account that is installed on my sbs 2003 ...
    (microsoft.public.windows.server.sbs)
  • Re: domain upgrade path... need comments please
    ... I've told many a client the same ... > server to a 2003 DC. ... > servers will need to get rebooted at least once after the upgrade to ... Do AD first, let things stabilize, then do the Exchange ...
    (microsoft.public.exchange.admin)