Frances [MSFT]
Guest
|
 Posted:
Fri Jan 28, 2005 4:26 pm Post subject:
RE: Migrating Win98 workstations from NT4 to W2K3 |
|
|
Hi Jasper,
Thank you for posting here!
I noticed that you have posted the same question in our newsgroup; please
check my answer to your question, and if you need any further assistance on
this particular issue, please reply to me in that thread so I can follow up
with you.
For your convenience, I have included my reply as follows:
--------------------
Hello Jasper,
Good to hear from you.
According to your post, it seems to be an urgent issue. If this is the
case, it is recommended that you contact Microsoft Product Support Services
(PSS) via telephone so that a dedicated Support Professional can help you
resolve your issue in the most efficient manner possible. Please be
advised that contacting phone support will be a charged call.
To obtain the phone numbers for a 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.
It seems that you now have a NT domain with Exchange 5.5. You want to have
a win2k3 domain with Exchange 2003. All the clients are win98. Is it
correct?
To achieve your goal, you can either upgrade the NT domain to win2k3
domain, or set up a win2k3 domain, and then migrate from NT to win2k3
domain. I recommend that you perform the "not in place" upgrade instead of
migration with ADMT to achieve your goal. Since upgrade provides the
easiest and lowest-risk migration path. Also, if you choose to migrate, you
have to manually restart win98 machines after the computer migration
because the win98 clients don't have RPC service.
Regarding your questions:
Q1. I am aware af the ADMT tool; but what is the proper way to migrate the
Win98 workstations ??
A: ADMT is used to migrate from one domain to another. According to your
description, you do not have a win2k3 domain now. So I recommend that you
do not use ADMT.
I am not sure why do you want to migrate the win98 workstations. The regkey
you offered confused me. What is your real concern? So far, there are no
known issues regarding Exchange with win98 clients. However, many issues
exist regarding win98 clients in win2k3 domain. Because in the win2k3
domain many settings enabled by default will break authentication for Win
9X clients. Please refer to the articles below for information.
834738 Microsoft Windows 9x client computers may not automatically download
and
http://support.microsoft.com/?id=834738
300865 Downlevel clients in a Windows Server 2003-based domain display "No
http://support.microsoft.com/?id=300865,
You should also look at
http://support.microsoft.com/default.aspx?scid=kb;en-us;823659
In addition, I will provide a "not in place" upgrade for your reference.
As a kind reminder, please backup the whole system before you take any
action. Also, it is best if you perform the upgrade process during a
non-business time such as the weekend. :)
Performing a "not in place" upgrade
======================
1.Install NT 4.0 BDC on the new box.
2.Promote the BDC to the PDC, which demotes the PDC to a BDC.
3.Do a full backup of the former PDC and remove it from the network.
4.Upgrade the new PDC to Windows Server 2003. If you want to expand the
boot partition, please refer to the following KB:
325857 How To Expand the Boot Partition During a Windows Server 2003 Upgrade
http://support.microsoft.com/?id=325857
5.Use the Windows Server 2003 Active Directory wizard to turn on the
Active Directory service. The Active Directory service imports the existing
user accounts, groups, and other settings from the PDC.
6.Run your new Windows Server 2003 domain controller with Active Directory
for a test period.
7.If desired you can do a clean installation of Windows Server 2003 on the
former PDC, and bring it online as an Active Directory domain controller.
8.Transfer all Flexible Single-Master Operation (FSMO) roles to the new
Windows Server 2003 domain controller.
9.Verify all directory information has replicated.
10.Demote the first domain controller to a member server, and remove from
the domain.
Regarding the Exchange part, I suggest you post all Exchange-related
question in the following newsgroup since they are the experts in Exchange
and will provide the most accurate information:
microsoft.public.exchange.setup
Hope this helps!
--------------------
Have a nice day!
Best regards,
Frances He
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. |
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in