KB 924034 now unable to login

[Guest Jon]

I am trying to prevent user login scripts from running on a terminal server.

I tried KB 924034 now when I try to log in, even with a domain admin account

the server logs in then logs back out to the login screen. Is there anyway

to at least get to where I can get back into the server to undo that

change!?

 

Jon

[Guest Vera Noest [MVP]]

Re: KB 924034 now unable to login

 

The problem is likely to be an incomplete or wrong path to your

DisableLogonScript.cmd file.

Since you are able to boot the server, you can't use LastKnownGood.

Try this:

Logon to another server or XP workstation with a Domain Admin

account, start regedit on it, and choose File menu - Connect to

remote registry. This will only work if the problematic server

allows remote registry connections. If it does, undo the change to

the registry key which you modified:

 

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion

\Winlogon

 

Double-click the userinit value, change it back to

%systemroot%\system32\userinit.exe

or make sure that the path to your DisableLogonScript.cmd file is

correct.

 

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___

 

"Jon" <nospam@spamsucks.net> wrote on 11 feb 2008 in

microsoft.public.windows.terminal_services:

> I am trying to prevent user login scripts from running on a

> terminal server. I tried KB 924034 now when I try to log in,

> even with a domain admin account the server logs in then logs

> back out to the login screen. Is there anyway to at least get

> to where I can get back into the server to undo that change!?

>

> Jon

[Guest Jon]

Re: KB 924034 now unable to login

 

Ah didnt think about the ability to remote into the registry. That did it,

and I did find a typo in the path.

 

Thanks!!!!!

 

 

"Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote in message

news:Xns9A41F2A31404Averanoesthemutforsse@207.46.248.16...

> The problem is likely to be an incomplete or wrong path to your

> DisableLogonScript.cmd file.

> Since you are able to boot the server, you can't use LastKnownGood.

> Try this:

> Logon to another server or XP workstation with a Domain Admin

> account, start regedit on it, and choose File menu - Connect to

> remote registry. This will only work if the problematic server

> allows remote registry connections. If it does, undo the change to

> the registry key which you modified:

>

> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion

> \Winlogon

>

> Double-click the userinit value, change it back to

> %systemroot%\system32\userinit.exe

> or make sure that the path to your DisableLogonScript.cmd file is

> correct.

>

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

> TS troubleshooting: http://ts.veranoest.net

> ___ please respond in newsgroup, NOT by private email ___

>

> "Jon" <nospam@spamsucks.net> wrote on 11 feb 2008 in

> microsoft.public.windows.terminal_services:

>

>> I am trying to prevent user login scripts from running on a

>> terminal server. I tried KB 924034 now when I try to log in,

>> even with a domain admin account the server logs in then logs

>> back out to the login screen. Is there anyway to at least get

>> to where I can get back into the server to undo that change!?

>>

>> Jon

[Guest Vera Noest [MVP]]

Re: KB 924034 now unable to login

 

Great! Glad that you're back in business again, and thanks for

reporting the results back here, Jon!

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

*----------- Please reply in newsgroup -------------*

 

"Jon" <nospam@spamsucks.net> wrote on 12 feb 2008:

> Ah didnt think about the ability to remote into the registry.

> That did it, and I did find a typo in the path.

>

> Thanks!!!!!

>

>

> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote

> in message

> news:Xns9A41F2A31404Averanoesthemutforsse@207.46.248.16...

>> The problem is likely to be an incomplete or wrong path to your

>> DisableLogonScript.cmd file.

>> Since you are able to boot the server, you can't use

>> LastKnownGood. Try this:

>> Logon to another server or XP workstation with a Domain Admin

>> account, start regedit on it, and choose File menu - Connect to

>> remote registry. This will only work if the problematic server

>> allows remote registry connections. If it does, undo the change

>> to the registry key which you modified:

>>

>> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion

>> \Winlogon

>>

>> Double-click the userinit value, change it back to

>> %systemroot%\system32\userinit.exe

>> or make sure that the path to your DisableLogonScript.cmd file

>> is correct.

>>

>> _________________________________________________________

>> Vera Noest

>> MCSE, CCEA, Microsoft MVP - Terminal Server

>> TS troubleshooting: http://ts.veranoest.net

>> ___ please respond in newsgroup, NOT by private email ___

>>

>> "Jon" <nospam@spamsucks.net> wrote on 11 feb 2008 in

>> microsoft.public.windows.terminal_services:

>>

>>> I am trying to prevent user login scripts from running on a

>>> terminal server. I tried KB 924034 now when I try to log in,

>>> even with a domain admin account the server logs in then logs

>>> back out to the login screen. Is there anyway to at least get

>>> to where I can get back into the server to undo that change!?

>>>

>>> Jon