An MSI is a Windows Installer database. Windows Installer (a service installed with Windows) uses this to install software on your system (i.e. copy files, set registry values, etc…). A setup.exe may either be a bootstrapper or a non-msi installer. A non-msi installer will extract the installation resources from itself and manage their installation directly. … Read more
in C#: var sc = new System.ServiceProcess.ServiceController(“MyService”, “MyRemoteMachine”); sc.Start(); sc.WaitForStatus(System.ServiceProcess.ServiceControllerStatus.Running); sc.Stop(); sc.WaitForStatus(System.ServiceProcess.ServiceControllerStatus.Stopped);
I’ve had problems automating Office from a Windows Service under Windows Server 2008, even though that works fine under Windows Server 2003. The problem also occurs at the Open call, so it may be the same problem. I tried following the advice given by H Ogawa in this MSDN thread, and it seemed to work. … Read more
The following code works for me… no need to prompt for username/password 🙂 <File Id=’JobServiceEXE’ Name=”JobService.exe” DiskId=’1′ Source=”JobService.exe” KeyPath=”yes”/> <ServiceInstall Id=”ServiceInstaller” Type=”ownProcess” Name=”JobService” DisplayName=”123 Co. JobService” Description=”Monitoring and management Jobs” Start=”auto” Account=”[SERVICEACCOUNT]” Password=”[SERVICEPASSWORD]” ErrorControl=”normal” /> <ServiceControl Id=”StartService” Start=”install” Stop=”both” Remove=”uninstall” Name=”JobService” Wait=”yes” /> </Component>
In short, services set to Automatic will start during the boot process, while services set to start as Delayed will start shortly after boot. Starting your service Delayed improves the boot performance of your server and has security benefits which are outlined in the article Adriano linked to in the comments. Update: “shortly after boot” … Read more
Navigate to the installutil.exe in your .net folder (for .net 4 it’s C:\Windows\Microsoft.NET\Framework\v4.0.30319 for example) and use it to install your service, like this: “C:\Windows\Microsoft.NET\Framework\v4.0.30319\installutil.exe” “c:\myservice.exe” Regarding a comment, for 64bit apps, use below: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\installutil.exe
Though I haven’t personally tested, I have good reason to believe that the above stated AT COMMAND solution will work for XP, 2000 and Server 2003. Per my and Bryant’s testing, we’ve identified that the same approach does not work with Vista or Windows Server 2008 — most probably due to added security and the … Read more
Update: Nearly four years after my original answer and this answer is very out of date. Since TopShelf came along Windows Services development got easy. Now you just need to figure out how to support failover… Original Answer: I’m really not a fan of Windows Scheduler. The user’s password must be provided as @moodforall points … Read more
sc create <servicename> binpath= “<pathtobinaryexecutable>” [option1] [option2] [optionN] The trick is to leave a space after the = in your create statement, and also to use ” ” for anything containing special characters or spaces. It is advisable to specify a Display Name for the service as well as setting the start setting to auto … Read more
Below I have put together everything I learned about Starting/Stopping a Windows Service from a non-Admin user account, if anyone needs to know. Primarily, there are two ways in which to Start / Stop a Windows Service. 1. Directly accessing the service through logon Windows user account. 2. Accessing the service through IIS using Network … Read more