Re: Help : Sr. Developer (IT Newbie) removes logon process from st
From: shawnk (shawnk_at_discussions.microsoft.com)
Date: 03/19/05
- Next message: Tony Marziano: "RE: Retaining local profiles when migrating from NT4"
- Previous message: Billy Guthrie: "Re: Can't view website I host"
- In reply to: Steven L Umbach: "Re: Help : Sr. Developer (IT Newbie) removes logon process from startu"
- Next in thread: shawnk: "Re: Help : Sr. Developer (IT Newbie) removes logon process from st"
- Reply: shawnk: "Re: Help : Sr. Developer (IT Newbie) removes logon process from st"
- Reply: Steven L Umbach: "Re: Help : Sr. Developer (IT Newbie) removes logon process from st"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 19 Mar 2005 10:17:12 -0800
Thanks to TheTaiTech and Steven I have been able to;
(1) Sysinternals psexec - Get a DOS command prompt on remote machine.
(2) Sysinternals autorunsc - Get a listing of the startup configuration
(3) MS regedit - Use regedit to verify the startup configuration registry
key values
In the key below we can see I've disabled 3 important services.
Does anyone know for sure how to re-enable them?
I want to;
(1) remove the 'rdpclip.exe' value completely
(2) remove the 'shell=explorer' entry completely
(3) remove the 'Userinit=C...' entry completey
I can delete these but I want to 'tread carefully' and make sure
this is the right thing to do. The server works just fine except
that I can not get back in because of these registry keys.
I want to make sure that if remove them I won't bring the system
down or something.
Any help is appreciated and thanks again to TheTaiTech and Steven.
The keys (listed by Sysinternals autorunsc via Sysinternals psexec) are
given below.
HKLM\System\CurrentControlSet\Control\Terminal
Server\Wds\rdpwd\AutorunsDisabled\StartupPrograms
[DISABLED] rdpclip
RDP Clip Monitor
Microsoft Corporation
c:\windows\system32\rdpclip.exe
- This key has the value "rdpclip" in it
HKLM\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Winlogon\AutorunsDisabled\Userinit
[DISABLED] C:\WINDOWS\system32\userinit.exe
Userinit Logon Application
Microsoft Corporation
c:\windows\system32\userinit.exe
- This key has the value : Shell=Explorer.exe
HKLM\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Winlogon\AutorunsDisabled\Shell
[DISABLED] Explorer.exe
Windows Explorer
Microsoft Corporation
c:\windows\explorer.exe
- This key has the value : Userinit=C:\Windows\system32\userint.exe
"Steven L Umbach" wrote:
> If you can connect to it from another computer via Computer Management -
> other computer look in Event Viewer to see if you can find ant error
> messages to see what the problem may be. Since you do have access to the
> command prompt use the command net start to see what services are running.
> He may have disabled a necessary service. You can compare the results to
> another like configured computer to see what services that are not started.
> Another possibility is to use secedit to reset the computers security
> settings back to default defined settings as per the link below. You can
> append the /areas command if you want to reset only certain parts of
> security settings such as services. The free tool psexec from SysInternals
> can also be used to manage a remote computers command prompt in most cases
> if smb connectivity exists between the computers. An in place upgrade of the
> operating system may be another option though there is no guarantee if will
> fix your problem and if you do it you will need to first install your
> service pack and then all critical updates after the upgrade install. ---
> Steve
>
> http://support.microsoft.com/default.aspx?scid=kb;EN-US;313222
> http://www.sysinternals.com/ntw2k/freeware/psexec.shtml --- Psexec
> http://support.microsoft.com/default.aspx?scid=kb;en-us;Q292175 -- in place
> upgrade of W2K. Should be very similar procedure for Windows 2003
>
> "shawnk" <shawnk@discussions.microsoft.com> wrote in message
> news:CCD896D4-0315-46E6-A56A-1760DBDD52E5@microsoft.com...
> > In an attempt to fix a problem one of our Sr. Developer's used a startup
> > manager application on Win 2003 server to temporarily remove some
> > applications from the start up process.
> >
> > Unfortunately it appears they also disabled the logon process for the
> > server.
> >
> > The result is that when you logon to the system (at the machine) you get
> > in
> > and then the system logs you right out again.
> >
> > No remote terminal services are enabled.
> >
> > The only way we can 'get back in' is using the Win 2003 Server CD in a
> > very
> > limited diagnostic mode (Dos prompt).
> >
> > Is there an easy way to enable the Remote Desktop service manually or by
> > command line?
> >
> > We have to use a console 'dos' prompt to work from.
> >
> > Thanks for any help.
> >
>
>
>
- Next message: Tony Marziano: "RE: Retaining local profiles when migrating from NT4"
- Previous message: Billy Guthrie: "Re: Can't view website I host"
- In reply to: Steven L Umbach: "Re: Help : Sr. Developer (IT Newbie) removes logon process from startu"
- Next in thread: shawnk: "Re: Help : Sr. Developer (IT Newbie) removes logon process from st"
- Reply: shawnk: "Re: Help : Sr. Developer (IT Newbie) removes logon process from st"
- Reply: Steven L Umbach: "Re: Help : Sr. Developer (IT Newbie) removes logon process from st"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|