Auto Admin Logon on servers that are domain members

If you want to enable AutoAdminLogon on a Windows 2008 server it’s quite easy, just type “control userpasswords2” in the run as textbox and hit enter. Then a dialog appears that shows a checkbox, which is usually checked, saying that users must enter username and password. If you uncheck this checkbox you will be asked for the password of the current user. Windows stores the password and enables auto logon in the registry. Voila.

This does not work on domain member machines unfortunately. On a server that is part of a domain the checkbox is disabled. To enable the checkbox you have to do this:

In the run as textbox type the following command:

reg add “HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon” /v AutoAdminLogon /t REG_SZ /d “1” /f

This adds a key to the registry and re-enables the checkbox.

You may have to add the name of the domain as well, because by default Windows would use the local user account. In this case run the following command:

reg add “HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon” /v DefaultDomainName /t REG_SZ /d “domain” /f

Replace domain by your actual domain name.

DSMI installation and IIS Management Scripts

While installing DSMI on a Windows 2008 server machine you might get a warning, saying that the installation cannot continue because the IIS Management Console and/or the IIS Management Scripts and Tools roles services are not installed.


Unfortunately the installation is interrupted in this case at its right beginning, since the installation depends on those services on several steps while the installation process, and can’t continue.

IIS service roles in Windows 2008 Server

You can easily add those role services if you open the server manager, expand the Roles branch and click on the Web Server (IIS). In the right pane click on Add role services in the actions pane. In the Add Role Services wizard select IIS Management Console and IIS Management Scripts and Tools and click install.


BTW, we do not need the IIS 6 support. DSMI is fully compatible to IIS 7.

MSI execution in elevated mode

If you still receive the same warning, although you installed those role services, then please check if the installation is running in elevated mode. If not, please do this:

1.) Open a command prompt as administrator

2.) Type msiexec /i <dsmi installation file.msi>  (where <dsmi installation file.msi> is pointing to your installation file)

This enables the installation to access system properties like application pool settings and web sites in IIS.

Have fun!

How to create an SSL binding for a specific port

The other day I needed to create an SSL binding to a specific port where my WCF service was listening. The easiest way to create such a binding is to use netsh commandline tool. You gonna need the following information upfront before you can create such a binding:

  1. The port you want to assign for SSL
  2. The thumbprint of you certificate (just open mmc, add certificates and double click on your certificate. Show the details pane and copy the Thumbprint value to notpad. Remove the whitespaces.
  3. A new GUID (use the VS tool Create new GUID using the registry format)

To add the SSL cert run the following tool from an elevated command shell:

netsh http add sslcert ipport=<PORT> certhash=<cert thumbprint> appid=<GUID>

To remove the SSL cert from a specific port use:

netsh http delete sslcert ipport=<PORT>

Refer to this msdn page if you need more information.

IIS returns 404.3 Not found when requesting a WCF service

Today I had an issue on server of one of our clients. The IIS7 always returned an http 404.3 when I tried to request a WCF service.

The problem was that the handlers were not installed, or not installed correctly by the .Net Framework installer.

Running ServiceModelReg –i from the command prompt fixed the problem by reinstalling the necessary handlers.

The tool can be found in the \windows\Microsoft.Net\Framework\v3.0\Windows Communication Foundation folder.

Receiving an Unable to start debugging with error code 0x800710D8 when attaching to local IIS

The other day I couldn’t attach my debugger to my web application I published to my local IIS 7 on a Windows 7 machine.

To fix this on Windows Vista or Windows 7 enable Window Authentication for your web application in the IIS Manager.