Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Left Domain - Now can't log into workgroup

5 views
Skip to first unread message

Big Ray

unread,
Apr 9, 2007, 7:46:02 PM4/9/07
to
Before seeing what users were configured for the local PC, I changed my work
PC from being a domain member to being in a workgroup. I won't have access
to my work's domain controller (network) for weeks. How do I log on to my
local PC? I tried administrator with blank password, but it doesn't work. I
was thinking I'd just be able to ESC at the log on screen and start Windows.
Instead, it appears I need to use a valid user name and password. Please
help. Thanks.

Sand Fly

unread,
Apr 9, 2007, 8:28:00 PM4/9/07
to
Contact your administrators.

One practice is to change the name of the local administrator account as
well as requireing a complex password. If your administrators are unwilling
to provide the username and password for the local admin you may be violating
company policy and can get yourself into hot water.

Bruce Chambers

unread,
Apr 9, 2007, 9:43:56 PM4/9/07
to
"Big Ray" <Big...@discussions.microsoft.com> wrote in message
news:A2876C4B-00F0-4298...@microsoft.com...

By changing the computer from the domain to a workgroup, your son
destroyed the trust between the domain and the machine. In doing so, he's
also rendered your domain login credentials as invalid. You'll need to be
physically connected to the domain network, you'll need to have
administrative privileges to the workstation, and you'll need to have
sufficient privileges on the domain. Then you can add the machine back on
to the domain, after having first deleted the computer's old domain account
(unless you've also renamed the computer).

Take the computer to your company's IT department for repairs.


--
Bruce Chambers

Help us help you:
http://dts-l.org/goodpost.htm
http://www.catb.org/~esr/faqs/smart-questions.html

They that can give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety. -Benjamin Franklin

Many people would rather die than think; in fact, most do. -Bertrand Russell

Shenan Stanley

unread,
Apr 9, 2007, 9:52:51 PM4/9/07
to

Please do not change the subject line of the thread.
It can completely break up a conversation thread with some newsreaders/etc.
In fact - dependent on several factors - it can leave your post floating
alone as a new post.

I have included the OP you were supposedly responding to as well. It is
good practice (in a response) to leave at least some of what you are
replying to - as the newsgroup servers all synchronize at different speeds
and archive in different ways - so that again - you could end up being a
lone post in a sea of responses to someone out there and they have no idea
what you were talking about.

See the thread here:
http://groups.google.com/group/microsoft.public.windowsxp.help_and_support/browse_thread/thread/2fdb166a87a27cac/b0f6a1ac9c3675fd?lnk=st&q=&rnum=2#b0f6a1ac9c3675fd

--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html


Shenan Stanley

unread,
Apr 9, 2007, 9:52:21 PM4/9/07
to

Please do not multi-post. If you feel your post is relevant to more than
one newsgroup - please cross-post instead. It saves you and those who might
be reviewing/answering your posts time and effort and might possibly lead to
a proper answer more quickly for several reasons.

Your other post:
http://groups.google.com/group/microsoft.public.windowsxp.security_admin/browse_thread/thread/d58725d2d7d85f13/83f492409c5ffd67?lnk=st&q=&rnum=1#83f492409c5ffd67

Here's the problem...

Your work system was configured by your IT staff for a reason (no idea what
that was, etc.)

This was done before giving you said system and they probably had you
logging in (obvious as an users with local system administrator privs using
a domain username no less) using cached credentials for a reason. Their
main mistake was giving you local administrative rights. This gave you the
ability to do what you have done. You do not know any local user accounts
(particularly administrative level local accounts) and you went ahead and
disjoined the domain using your cached logon domain account - which became
null and void the moment you decided to reboot after taking said action.

Your choices are:

1) Call your IT staff. Tell them what you have done and see what proper
action you should take.

2) Google for a password hacking application so you can hack the local
administrator password and hope that there was no encrypted files/special
things setup on the system that depending on the fact it was a member of the
domain and that you were using that cached account and then later - when you
can - call your IT staff. Tell them what you have done and see what proper
action you should take.

In general - the only 'valid way' (in the end) out of this is to call your
IT Staff. Tell them what you have done and see what proper action you
should take.

Shenan Stanley

unread,
Apr 9, 2007, 9:55:24 PM4/9/07
to
Big Ray wrote:
> Before seeing what users were configured for the local PC, I
> changed my work PC from being a domain member to being
> in a workgroup. I won't have access to my work's domain
> controller (network) for weeks. How do I log on to my local
> PC? I tried administrator with blank password, but
> it doesn't work. I was thinking I'd just be able to ESC at the
> log on screen and start Windows. Instead, it appears I need
> to use a valid user name and password. Please help. Thanks.

Bruce Chambers wrote:
> By changing the computer from the domain to a workgroup, your son
> destroyed the trust between the domain and the machine. In doing
> so, he's also rendered your domain login credentials as invalid. You'll
> need to be physically connected to the domain network,
> you'll need to have administrative privileges to the workstation,
> and you'll need to have sufficient privileges on the domain. Then
> you can add the machine back on to the domain, after having first
> deleted the computer's old domain account (unless you've also
> renamed the computer).
> Take the computer to your company's IT department for repairs.

Bruce,

Copy --> Paste --> Proofread --> Edit as Necessary --> Post.
;-)

"...your son..." *grin*

0 new messages