bstaud
asked on
Convert Windows 10 PC from Domain to Workgroup
Windows 10 machine with a Domain account xxx.local. Not connected to the xxx.local network anymore. How to move the machine to a Workgroup.
ASKER
To Clarify: If I understand it, netdom removes the Workstation from the domain, up there on the Server running something like Active Domain. The actual question is, on the Workstation, which does no longer have access to the Server, and is at an entirely different location, how do you set the workstation to belong to a local Workgroup?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
So Step 0 of the process above is to verify that there is a local User account with Administrator privileges, or to create such a local user account with Administrator privileges beforehand.
"Step 0". I like that. :)
Right-click on your Windows button in the lower left corner and go to "Computer Management".
From there, go to System Tools > Local Users and Groups > Users
There should be an account on there called "Administrator" and it's probably disabled. If so, enable it. Then, right-click and change the password.
IF YOU HAVE ANY ENCRYPTION ON THAT MACHINE - if it's associated with the Administrator account, you won't be able to decrypt the data once you change the password.
All of this assumes you have Administrator privileges on the machine yourself.
An alternative is to create a new user account with a name you'd rather use. Do that in the Users folder, too. Once that's done, go to the account properties "Member Of" tab and add your account to the local Administrators group.
Right-click on your Windows button in the lower left corner and go to "Computer Management".
From there, go to System Tools > Local Users and Groups > Users
There should be an account on there called "Administrator" and it's probably disabled. If so, enable it. Then, right-click and change the password.
IF YOU HAVE ANY ENCRYPTION ON THAT MACHINE - if it's associated with the Administrator account, you won't be able to decrypt the data once you change the password.
All of this assumes you have Administrator privileges on the machine yourself.
An alternative is to create a new user account with a name you'd rather use. Do that in the Users folder, too. Once that's done, go to the account properties "Member Of" tab and add your account to the local Administrators group.
ASKER
While we are at it, how to handle the other User accounts on the machine, whose login access was managed by the domain which they now cannot see? I guess the question is how/whether to convert those accounts to be local to the machine?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Note: if you aren't confident in how these work, setup a test system and test first.
ASKER
It is all becoming clear(er) now.
One last part: Can different local Users somehow be associated with different Domains or with different Workgroups?
One last part: Can different local Users somehow be associated with different Domains or with different Workgroups?
No.
Workgroups are just logical groupings of computers that aren't associated with each other (from a security standpoint). An Active Directory domain is a logical grouping of computers which each share a common security scope, which is the domain.
It's kind of like having 20 people say "We're accountants" versus 20 people say "We all work for the same CPA firm". The first group are all in accountants... sure. But the second group are all associated with the same organization and are subject to its policies, procedures, etc.
Workgroups are just logical groupings of computers that aren't associated with each other (from a security standpoint). An Active Directory domain is a logical grouping of computers which each share a common security scope, which is the domain.
It's kind of like having 20 people say "We're accountants" versus 20 people say "We all work for the same CPA firm". The first group are all in accountants... sure. But the second group are all associated with the same organization and are subject to its policies, procedures, etc.
Why are you removing the domain?
Keep in mind, you're also mixing your terminology. With Transwiz (the software Lee and I both recommended), you're migrating the PROFILE. The profile is the collection of settings, folders, etc. that are associated with a user account. It is not, however, the account itself.
Your account exists in the domain you were in. You're now creating a new LOCAL account which means it exists ONLY on that computer. You're then taking the profile associated with your old account and associating it with your new account.
Your account exists in the domain you were in. You're now creating a new LOCAL account which means it exists ONLY on that computer. You're then taking the profile associated with your old account and associating it with your new account.
@Lee - I took his question to mean he removed the computer from the domain and now has to force removal.
Correction... I recommended that software on a different post; not this one. Sorry about that. :)
ASKER
Yes Hornsey and Lee both contributed to the enlightenment.
I answered the first question, Lee answered the second.
Open in new window
Or
Open in new window