Discussion Locked

Win98 and AD

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
If I upgrade my NT 4.0 PDC to be my Win2k DC, do I have to have all my Win98 users using the new AD Client to connect to a Win2k member server? Or can I gradually migrate them while they are using the standard client for Microsoft Networks? I know they won't have all the functionality that AD provides, but will they be able to use their current log-in scripts and connect to the shares?

5 replies

by mike.lee

All of the Win98 clients will not have any of the functionality with regard to AD, but logon will be maintained, mapping drives, ect... The only thing to look out for is the naming conventions. In AD you can specify the server name (server01)only but for the 95, 98, NT clients you must specify the domains fully qualified address (sub.home.net). This might cause minor problems with e-mail(depending on the logical location and accesses of your e-mail server).A gradual migration is possible and the better way to do it. Another thing to lookout for is legacy systems. Don't select the setting for conversion to Native, use mixed mode, that way all of your BDC's can comunicate with the PDC and other domain controllers.

by dc1

One of the bigest benefits with he AD client is it allows the down-level client to communicate with the closest domain controller to it for authentication instead of possibly going across a WAN link for the PDC emulator when a DC is on the same LAN.You login scripts will work fine and as long as they have a qualified login ID the shares will work also.

This discussion is closed to new replies.