I think someone was messing with my son's laptop at
college and now he can not logon to WindowsXP Home.
After entering the window's password (blank) an error
screen comes up saying "the local policy of this system
does not permit you to logon interactively". Is there
anything that can be done to correct this.
Thanks

>-----Original Message-----
>I think someone was messing with my son's laptop at
>college and now he can not logon to WindowsXP Home.
>After entering the window's password (blank) an error
>screen comes up saying "the local policy of this system
>does not permit you to logon interactively". Is there
>anything that can be done to correct this.
>Thanks
>.
>

restart PC,then push F8 ,try again!

He can't, the security policy (probably group) is in force preventing any way to
log on interactively. In other words, he's locked out. I'm not sure if he could
get back in using the recovery console, but since the recovery console is it's
own installation, he *might* be able to use it to change the local security
policy to allow him to log on interactively. Some of the MVP's here might know
more as I'm more familiar with W2K/XP pro versions only.

--
Regards,

Durand


<(E-Mail Removed)> wrote in message
news:085c01c3a796$c34e7de0$(E-Mail Removed)...
|
| >-----Original Message-----
| >I think someone was messing with my son's laptop at
| >college and now he can not logon to WindowsXP Home.
| >After entering the window's password (blank) an error
| >screen comes up saying "the local policy of this system
| >does not permit you to logon interactively". Is there
| >anything that can be done to correct this.
| >Thanks
| >.
| >
|
| restart PC,then push F8 ,try again!

Hi Jim,

This is definately a result of a Local Security Policy as the machine is
Windows XP Home and will not be affected by Group Policy. Rebooting the
machine to safe mode should allow access to the Local Security Policy on
the machine. Modify the policy to include the needed user account and
reboot to normal mode. I would recommend the usual.... Antivirus, Firewall
(builtin to XP) and a strong password. In my opinion... firewalls are
paramount in college environments as there is typically an increased amount
of risk present.

Brian Schafer, MCSE, MCSA, CISSP, Security+
(E-Mail Removed)

This posting is provided "AS IS" with no warranties, and confers no rights.


--------------------
> From: "Durand" <(E-Mail Removed)>
> References: <096101c3a791$755fe060$(E-Mail Removed)>
<085c01c3a796$c34e7de0$(E-Mail Removed)>
> Subject: Re: Can not logon to XP
> Date: Tue, 11 Nov 2003 00:56:15 -0500
> Lines: 30
> X-Priority: 3
> X-MSMail-Priority: Normal
> X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
> Message-ID: <#(E-Mail Removed)>
> Newsgroups: microsoft.public.windowsxp.security_admin
> NNTP-Posting-Host: bgp01035329bgs.sothfd01.mi.comcast.net 68.41.249.218
> Path:
cpmsftngxa06.phx.gbl!TK2MSFTNGXA06.phx.gbl!TK2MSFTNGXA05.phx.gbl!TK2MSFTNGP0
8.phx.gbl!tk2msftngp13.phx.gbl
> Xref: cpmsftngxa06.phx.gbl microsoft.public.windowsxp.security_admin:96742
> X-Tomcat-NG: microsoft.public.windowsxp.security_admin
>
> He can't, the security policy (probably group) is in force preventing any
way to
> log on interactively. In other words, he's locked out. I'm not sure if he
could
> get back in using the recovery console, but since the recovery console is
it's
> own installation, he *might* be able to use it to change the local
security
> policy to allow him to log on interactively. Some of the MVP's here might
know
> more as I'm more familiar with W2K/XP pro versions only.
>
> --
> Regards,
>
> Durand
>
>
> <(E-Mail Removed)> wrote in message
> news:085c01c3a796$c34e7de0$(E-Mail Removed)...
> |
> | >-----Original Message-----
> | >I think someone was messing with my son's laptop at
> | >college and now he can not logon to WindowsXP Home.
> | >After entering the window's password (blank) an error
> | >screen comes up saying "the local policy of this system
> | >does not permit you to logon interactively". Is there
> | >anything that can be done to correct this.
> | >Thanks
> | >.
> | >
> |
> | restart PC,then push F8 ,try again!
>
>
>