Discussion Locked

Windows 2000 Clients in an NT4 domain

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hoping anyone can share any problems they ran in to using Win2000 Pro clients in an NT 4 domain.

Any trouble with served applications, permissions, roaming profiles? Especially roaming profiles, where people will be using the same profile on both NT WKS clients and Win2000 Pro clients.

Any URLs that list possible issues would be helpful also.

Thanks.

5 replies

by mckaytech

We've had no issues whatsoever in running W2K Professional clients in an NT4 domain. Where we've had problems is with NT4 clients running W2K Terminal Services in an NT4 domain.

However, we are not doing system policies and are not doing much tolockdown the desktop so that could potentially be a problem area if your environment includes them.

paul

by lorand

We've run into several issues when users migrate between NT and 2k version profiles. If you have an NT Server, and both NT and 2k Workstations, users migrating between NT and 2k will experience increased profile size, and may experince serious logintime increases.

Other issues have included problems with permissions on the local workstation vs. the permissions the user has in the global domain, and some frustratingly hard to trace password shifts. The user will do nothing, but their password will be reset to a random value (As if generated in the Unix passwd environment).

My personal recomendation in this situation would be to try to keep users to one platform as much as possible, but if they must migrate, keep things to a minimum as much as possible.

This discussion is closed to new replies.