I have done several searches on the site and come away with several snippets that will no doubt help. However, most posts presume a level of knowledge I don't yet have.
The situation: a client has seen the wisdom of installing a non-Windows file/print server on their network. They have about 18 XP client machines on the LAN. In addition, they have a Windows-NT server that was acquired some years ago to host their financial application. It has also been pressed into service as a file/print server (but it has run out of room for more files). They have also set it up as a PDC.
Our original plan was simply to drop in the SME box as a file/print server and move the various data files and print queues from the old NT machine. However, the client now wants the PDC functionality handled by SME. That way they can treat the old NT machine as just an application server, which simplifies the process of replacing that box in the near future.
My problem is that I don't know enough about Windows side of PDC and network management to plan and execute a conversion.
Since we are dealing with only a couple of dozen client machines, I can go to each and make some changes. But I don't know what changes to make. I know how to turn PDC on in SME - but I don't know how to turn it off on the NT server.
On the NT box I believe there are some nice screens to set up drive mapping for the users - but I don't see anything like that in server-manager. If I go in and change netlogon.bat I expect to get the same drive mappings for all users - but some of these ibays won't be accessible for some users because of group membership differences.
Can anyone point me to a cookbook style how-to? Or failing that, can anyone suggest a course of action that I might follow (and subsequently turn into a how-to for subsequent posting)?
All suggestions gratefully accepted.
John
3 Replies
1452 Views