{"id":14613,"date":"2018-03-05T06:00:50","date_gmt":"2018-03-05T14:00:50","guid":{"rendered":"https:\/\/www.sapien.com\/blog\/?p=14613"},"modified":"2018-03-02T09:31:30","modified_gmt":"2018-03-02T17:31:30","slug":"installing-windows-services-created-with-powershell","status":"publish","type":"post","link":"https:\/\/dev.sapien.com\/blog\/2018\/03\/05\/installing-windows-services-created-with-powershell\/","title":{"rendered":"Installing Windows Services Created with PowerShell"},"content":{"rendered":"

Last week we introduced a new PrimalScript template for Windows PowerShell<\/a> which makes writing Windows Services much easier. In this article, we will show you how to use MSI Builder to create an installer for your Windows Services.<\/p>\n

We created the services packager engine to allow for self-install \/ uninstall of a service, but that is not always the best option. For example, if your service requires other files, you will most likely want to create an installer. It is quite easy to create an installer using the MSI builder, which is part of the PrimalScript and PowerShell Studio deployment package.<\/p>\n

The MSI Builder had no special accommodation for Windows Services\u2014until now. Since a service needs to be registered and started on install rather than just copied as a file, the MSI file needs to contain some extra information. Likewise, when uninstalling, the service needs to be stopped and unregistered before the file can be removed.<\/p>\n

But fear not, there is not much for you to do.\u00a0When you create the installer, simply select Windows Service<\/strong><\/em> as the ‘Product Type’, and you are\u00a0almost<\/em> done:<\/p>\n

\"image\"<\/a><\/p>\n

 <\/p>\n

Almost\u2014<\/em>because there is one important detail that needs your attention. Since MSI does not know which file in your installer is a service and which is not, you need to make sure the actual service executable is the first file in the ‘Files’ list:<\/p>\n

\"image\"<\/a><\/p>\n

 <\/p>\n

In future releases, we will add some more options for your service installers, but for this scenario, you simply need to select Windows Service<\/strong><\/em> as the ‘Product Type’ and choose the service executable as the first file. The installer will install your files, register the service, and start it. On uninstall it will stop the service and unregister it before it removes any files.<\/p>\n

Note:<\/em> Uninstalls can take longer for services since Windows Installer will wait for the service to stop.<\/em> Depending on how you programmed the service, that can mean a 20 to 30-second delay.<\/p>\n

Learning from a working example is always a little easier, so we updated last years SolitaireKiller service<\/a> to use the new service template and create an installer for it. Download the code and working installer here: https:\/\/sapien.s3.amazonaws.com\/Blog_Post_Files\/SolitaireKiller2018.zip<\/a><\/p>\n

Feedback<\/h3>\n

As always, if you have any ideas, comments, or feedback, please visit our feedback forum<\/a> and reference this post.<\/p>\n","protected":false},"excerpt":{"rendered":"

Last week we introduced a new PrimalScript template for Windows PowerShell which makes writing Windows Services much easier. In this article, we will show you how to use MSI Builder to create an installer for your Windows Services. We created the services packager engine to allow for self-install \/ uninstall of a service, but that […]<\/p>\n","protected":false},"author":5,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[1143,703,410,21,25],"tags":[816,548,28,1016,37,300],"class_list":["post-14613","post","type-post","status-publish","format-standard","hentry","category-powershell","category-powershell-studio","category-primalscript-software-news","category-software-news","category-windows-powershell","tag-installer","tag-msi","tag-powershell","tag-powershell-studio","tag-primalscript","tag-service"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t