Ok, here is the deal...  It will work if you set the
serviceProcessInstaller's account set to "LocalSystem".  If you have it set
to user, the service will install, but it cannot be started.  We are
suspecting that is why it is trying to use the NetLogon service.

The fix we came up with was to set the account to "User", and in the
ProjectInstaller.cs, we added the following code in the
InitializeComponent() function:

String ComputerName = "";
try
{
RegistryKey rkey =
Registry.LocalMachine.OpenSubKey("SYSTEM\\CurrentControlSet\\Control\\Comput
erName\\ComputerName");
ComputerName = (String)rkey.GetValue("ComputerName", "unknown");
} catch(Exception e) {
System.Console.WriteLine("Error retrieving Computer Name from local
registry.  " + e.Message);
}

this.serviceProcessInstaller1 = new
System.ServiceProcess.ServiceProcessInstaller();
this.serviceInstaller1 = new System.ServiceProcess.ServiceInstaller();
//
// serviceProcessInstaller1
//
this.serviceProcessInstaller1.Account =
System.ServiceProcess.ServiceAccount.User;
this.serviceProcessInstaller1.Password = "somepassword";
this.serviceProcessInstaller1.Username = ComputerName + "\\someusername";

We ran into issues between Windows NT and Windows 2000 that is why we are
having to use the local computer name...  Using \\computername worked on
Windows 2000, but did not work on Windows NT.  Using the physical computer
name solved the problem.