Bryan
January 10th 04, 02:35 AM
When you joined the pc to a work group, the username and
password it was asking for was not of the domain, but
rather of an approved user account on the local machine,
ie Administrator. But if it said welcome to XX Workgroup
then it sucessfully left the domain and added to the
workgroup. Any user that was added to the machine that
was part of the domain will not be able to logon as they
need to authenticate through the domain. You should see
a guid as the username (long sting of number and
letters). Most PCs if added to a domain do not usually
have local users added to them, except helpdesk type
accounts. Any local user ie. Administrator should be
able to logon to the machine. How are you able to tell
that the accounts are disabled if you can't logon to the
machine?
Bryan
>-----Original Message-----
>
>I am becoming more aware (and frustrated with) an issue
>with XP Pro when trying to remove it from a domain.
>
>The system in question was physically removed from the
>domain and not able to be 'removed' by an approved
user.
>The system was then moved to a workgroup (without having
a
>local user account set up prior - a key point I am
>learning). As the domain name was removed and the
>workgroup name applied, XP asked for an appropriate
>username and password for the domain it was leaving.
>
>I left the username and password blank, clicked ok, and
a
>few hourglass spins later was welcomed to the workgroup.
>XP then prompted for the obligaroty reboot. No prompts,
>no warnings, and sure as heck no "STOP YOU CANNOT DO
>THIS".
>
>What I am finding now is that the user info is still
there
>in the SAM, but XP is not allowing any login whatsoever.
>The majority of accounts are disabled (or are so corrupt
>that they are read that way) and I'm stuck...
>
>I simply cannot believe this issue has not been more
>common, and/or a fix doesn't exist. Any thoughts?
>
>-R-
>.
>
password it was asking for was not of the domain, but
rather of an approved user account on the local machine,
ie Administrator. But if it said welcome to XX Workgroup
then it sucessfully left the domain and added to the
workgroup. Any user that was added to the machine that
was part of the domain will not be able to logon as they
need to authenticate through the domain. You should see
a guid as the username (long sting of number and
letters). Most PCs if added to a domain do not usually
have local users added to them, except helpdesk type
accounts. Any local user ie. Administrator should be
able to logon to the machine. How are you able to tell
that the accounts are disabled if you can't logon to the
machine?
Bryan
>-----Original Message-----
>
>I am becoming more aware (and frustrated with) an issue
>with XP Pro when trying to remove it from a domain.
>
>The system in question was physically removed from the
>domain and not able to be 'removed' by an approved
user.
>The system was then moved to a workgroup (without having
a
>local user account set up prior - a key point I am
>learning). As the domain name was removed and the
>workgroup name applied, XP asked for an appropriate
>username and password for the domain it was leaving.
>
>I left the username and password blank, clicked ok, and
a
>few hourglass spins later was welcomed to the workgroup.
>XP then prompted for the obligaroty reboot. No prompts,
>no warnings, and sure as heck no "STOP YOU CANNOT DO
>THIS".
>
>What I am finding now is that the user info is still
there
>in the SAM, but XP is not allowing any login whatsoever.
>The majority of accounts are disabled (or are so corrupt
>that they are read that way) and I'm stuck...
>
>I simply cannot believe this issue has not been more
>common, and/or a fix doesn't exist. Any thoughts?
>
>-R-
>.
>