Enable RDP Remotely via RPC/Remote Registry

Posted by & filed under Server Admin.

Two good methods for enabling rdp:

You enable remote desktop over the network via regedit if you have administrator rights to the remote machine:
1.Run Regedit
2.Select File –> Connect Network registry
3.Enter the name of the remote computer and select Check Name
4.At the bottom of the registry tree you will see 2 Hives appear Hkey_Local_Machine and
Hkey_Users (under the remote computer’s name)
5.Goto hklm\system\currentcontrolset\control\terminal server\FdenyTSConnections=1
6.Change the FdenyTSConnections to 0
7.Attempt to Re-Login

Or with psexec magic:

psexec \\remotecomputername netsh firewall set service remoteadmin enable
psexec \\remotecomputername netsh firewall set service remotedesktop enable

Fixing MS FTP Service from needing the domain prefix for user logins

Posted by & filed under Windows.

The MS FTP server by default requires a domain name prefixed on the username. We don’t want this for our FTP users:

1. Change to the %Systemroot%\Inetpub\Adminscripts directory.
2. Type the following:
Adsutil Set MSFTPSVC/DefaultLogonDomain “Domain Name”
Make sure when you type in the Domain Name that it is enclosed in quotation marks.
3. Stop and restart the FTP Service.

This applies to IIS 4 thru IIS7. FOr IIS7 I copied the adsutil.vbs form the inetpub/adminscripts folder on a IIS6 box.

Debugging STOP Errors / Reading Crash Dumps

Posted by & filed under Server Admin.

1. Configure for a large dump model — A complete memory dump, which is written to the %SystemRoot%\Memory.dmp folder.

The paging file on the boot volume must be large enough to hold all of the physical RAM plus 1 MB.

The default type of memory dump is the small memory dump. To change or view the settings for the type of memory dump, follow these steps:
1. Click Start, and then click Control Panel.
2. In Control Panel, double-click System, and then click the Advanced tab.
3. Click Settings in the Startup and Recovery area.
4. View or change the type of memory dump under Write debugging information.

2. Download and install the debugging tools for Windows 32-bit: www.microsoft.com/whdc/devtools/ … llx86.mspx

3. Download and install, (Important: install to the folder C:\Symbols), the Appropriate Symbol package: www.microsoft.com/whdc/DevTools/ … olpkg.mspx

4. To make life easier, download and install DebugWiz: windowsbbs.com/debugwiz.zip
Install this to C:\Windows so that it can be found in your Path.

Now the next time your computer shows a BSOD:

For non-BSOD crashes, the program crash dump is probably located in C:\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson\user.dmp

For BSOD events, “Blue Screens of Death”: the dump file will be found at c:\MEMORY.DMP ; or (for Mini-dumps) in C:\WINDOWS\Minidump\

* Find your copy of DebugWiz.exe and run it.
* Select a dump using the tool and ‘generate log’
* Open the file c:\debuglog.txt in notepad

You can paste the log back to the Forum.

Additional Reading:

See the 3-Part discussion by Ken Schaefer on 0x0A errors due to driver issues. The methods apply to any driver-related BSOD event. The discussion shows how to use the Windows debugger, as well as driver utilities such as Driver Verifier and the use of Special Pools.

www.adopenstatic.com/cs/blogs/ke … art-1.aspx

www.adopenstatic.com/cs/blogs/ke … art-2.aspx

www.adopenstatic.com/cs/blogs/ke … /1005.aspx