nt server GONE, need to migrate domain users to workgroup- how?

  • Thread starter Thread starter jjmerrow
  • Start date Start date
J

jjmerrow

story:

firm has 10 win2k boxes connected to nt server domain. nt box dies and
firm actually GETS RID OF IT. firm asks me to reconnect users in a
workgroup. I'm not a win networking expert.

I've seen messages about more or less orderly methods of migrating
from a domain to a workgroup, but none where the domain controller and
server are GONE.

can anybody offer any pointers?

thanks much,
josh
 
go to each machine and just change them from the domain to your workgroup
name. you will have to login as a local administrator to do it as there
will be no more domain admin for validation. then you will have to create a
new user account since the domain one won't work any more. and you will
have to manually copy the user's profile to the new account on each machine,
or you might just be able to map the new user account to the old profile...
you would have to try that and see how it works. then if your domain server
was also doing dhcp and dns you will have to find a new way to do that,
either assign them manually on each machine or get a router that provides
those services. an don't forget that win2k pro only allows 10 connections
for file or print sharing, so if you think about setting up one of the win2k
boxes as a fake server you may find that you run out of connections.

of course you lose all the advantages of sharing printers and drives and
stuff you might have used the server for.
 
thanks, will try it out
j


David Robbins said:
go to each machine and just change them from the domain to your workgroup
name. you will have to login as a local administrator to do it as there
will be no more domain admin for validation. then you will have to create a
new user account since the domain one won't work any more. and you will
have to manually copy the user's profile to the new account on each machine,
or you might just be able to map the new user account to the old profile...
you would have to try that and see how it works. then if your domain server
was also doing dhcp and dns you will have to find a new way to do that,
either assign them manually on each machine or get a router that provides
those services. an don't forget that win2k pro only allows 10 connections
for file or print sharing, so if you think about setting up one of the win2k
boxes as a fake server you may find that you run out of connections.

of course you lose all the advantages of sharing printers and drives and
stuff you might have used the server for.
Click to expand...

has 10 win2k boxes connected to nt server domain. nt box dies and
 
Back
Top