Windows

Core functionality for deploying to Windows-based servers.

  • About
  • Release Notes
  • Version History
  • Installation

The Windows Extension gives you the ability to add built-in operation to you deployment plan.

This extension contains core functionality for configuring and orchestrating Windows-based servers. It's delivered as an extension to allow for easier patching and code sharing between products.

Do not uninstall this extension, or most things will not work.

It's always shipped with BuildMaster itself, and you can safely update it as needed.

This operation are:

  • Ensure App Pool – Ensures the existence of a file on a server.
  • Ensure Service –Ensures the configuration of a Windows service on a server.
  • Ensure Site – Ensures the existence of a site on a server.
  • Ensure Virtual Directory – Ensures the existence of a virtual directory within an IIS site.
  • PSCall –Calls a PowerShell Script that is stored as an asset.
  • PSExec – Executes a specified PowerShell script.
  • Recycle App Pool –Recycles an application pool.
  • Start App Pool –Starts an application pool.
  • Start Site –Starts an IIS Site.
  • Start Windows Service –Starts an existing Windows service.
  • Stop App Pool –Stops an application pool.
  • Stop Site –Stops an IIS Site.
  • Stop Windows Service –Stops an existing Windows service.

5.6.3

3/1/2017 4:16:54 PM
No notes for this release

5.6.2

1/20/2017 8:48:52 PM
No notes for this release

5.6.1

12/13/2016 11:06:27 PM
No notes for this release

5.6.0

11/30/2016 4:37:28 PM
No notes for this release

5.5.0

10/17/2016 1:10:03 PM
No notes for this release

5.4.0

9/23/2016 10:41:43 PM
No notes for this release

5.3.3

8/16/2016 9:57:24 PM
No notes for this release

5.3.2

8/11/2016 1:45:05 PM
No notes for this release

5.3.1

8/9/2016 9:43:30 PM
No notes for this release

5.3.0

8/5/2016 11:31:18 PM
No notes for this release

5.1.1

6/21/2016 10:47:11 PM
No notes for this release

5.1.0

6/17/2016 9:03:17 PM
No notes for this release

5.0.1

5/27/2016 9:27:15 PM
No notes for this release

5.0.0

4/29/2016 5:56:49 PM
No notes for this release

4.90

2/15/2016 9:31:52 PM
  • 30 - Check if app pool and/or web site exist in IIS and omit action if true
  • 24 - Add the Application Pool Identity account type for IIS7+ application poo...
  • 26 - Change "Create IIS Site" and "Create IIS Application Pool" to not fail if the site/pool exists

4.13

11/12/2015 8:43:13 PM
  • 29 - Use More Unique UniqueId for PSHost

4.12

10/19/2015 4:42:13 PM
  • 28 - Capture Write-Host messages to the BuildMaster debug log stream

4.11

12/16/2014 4:14:18 PM
  • 25 - FIX: Boolean parameters are sometimes not processed correctly in PowerShell v2
  • 21 - Create IIS 7+ App Pool Action support for ApplicationPoolIdentity

4.10

9/12/2014 3:46:20 PM
  • 23 - Add configurer option for default PowerShell parameter value behavior

4.9

6/26/2014 3:44:08 PM
  • 20 - FIX: AppPool and Service selectors do not show initial value when editing actions
  • 19 - FIX: AppPool selector and Service selector not working in BuildMaster 4.3

4.8

6/12/2014 6:30:10 PM
  • 18 - FIX: PowerShell scripts writing null to an output pipeline will log a NullReferenceException

4.7

5/5/2014 9:21:05 PM
  • 17 - FIX: Default values not used for PowerShell script arguments
  • 16 - FIX: Metadata not being extracted from a PowerShell script if there is an additional comment between the main comment block and the param keyword
  • 15 - Automatically set [switch] and [bool] parameters to checkbox input types for imported PowerShell scripts
  • 14 - Improve support for [switch] PowerShell parameters

4.6

4/18/2014 8:30:29 PM
  • 13 - UI refresh for BuildMaster 4.2
  • 12 - Add install and uninstall service actions
  • 11 - FIX: Exception is displayed when trying to stop an app pool that is already stopped
  • 10 - Stop/Start Service actions should utilize cancellation token

4.5

2/6/2014 3:05:50 PM
  • 9 - FIX: Execute PowerShell Script action cannot find script file in a path relative to default directory

4.4

2/3/2014 8:54:30 PM
  • 8 - FIX: Variables not displayed on Execute PowerShell action

4.3

1/31/2014 10:39:29 PM
No notes for this release

4.2

12/30/2013 11:50:22 PM
  • 5 - AppPool Actions Should Have Option to Ignore Errors
  • 7 - New actions to create IIS application pools and websites
  • 6 - Support for PowerShell parameters

4.1

12/2/2013 3:49:39 PM
  • 4 - FIX: IIS detection always detects IIS7
  • 3 - PowerShell Action - log Script Output shoudl be checked by default
  • 2 - Make PowerShell variables field more descriptive

4.0

10/7/2013 11:30:11 PM
No notes for this release

3.12

8/8/2013 4:48:11 PM
  • 1 - FIX: Azure SQL Database Initialization

3.11

5/1/2013 3:55:58 PM
  • BMXWINDOWS-11 - Allow start/stop IIS AppPool action editors to accept any text input

3.10

1/18/2013 11:53:59 PM
No notes for this release

3.9

12/3/2012 11:56:49 PM
  • BMXWINDOWS-10 - FIX: IIS action editor validation and execution is not compliant with the new TCP agent interface

3.8

11/20/2012 8:10:19 PM
  • BMXWINDOWS-9 - FIX: Start/Stop Services action editor validation is not compliant with the new TCP agent interface

3.7

6/29/2012 7:42:31 PM
  • BMXWINDOWS-8 - FIX: Change script history on the provider details page does not display deleted change scripts with the same name if one is recreated
  • BMXWINDOWS-7 - Remote __BuildMaster_ExecSql Proc, Execute Directly

3.6

4/9/2012 4:36:08 PM
  • BMXWINDOWS-6 - FIX: IIS App pool actions should not specially handle server groups

3.5

3/4/2012 10:46:08 PM
  • BMXWINDOWS-5 - FIX: Vaidation Error on StopService Action

3.4

2/28/2012 4:53:36 PM
  • BMXWINDOWS-4 - FIX: Start Service Action is not compatible with action Retry Count

3.3

2/27/2012 2:46:50 AM
  • BMXWINDOWS-3 - FIX: Service Action Editors Crash If Server Group Selected

3.2

2/16/2012 11:50:51 PM
  • BMXWINDOWS-2 - FIX: PowerShell script files do not resolve the script path appropriately

3.1

2/1/2012 9:25:12 PM
No notes for this release

3.0

1/7/2012 6:51:14 AM
No notes for this release
VersionReleasedRequires Version
5.6.33/1/2017BuildMaster 5.6.0download
5.6.21/20/2017BuildMaster 5.6.0download
5.6.112/13/2016BuildMaster 5.6.0download
5.6.011/30/2016BuildMaster 5.6.0download
5.5.010/17/2016BuildMaster 5.5.0download
5.4.09/23/2016BuildMaster 5.4.0download
5.3.38/16/2016BuildMaster 5.3.0download
5.3.28/11/2016BuildMaster 5.3.0download
5.3.18/9/2016BuildMaster 5.3.0download
5.3.08/5/2016BuildMaster 5.3.0download
5.1.16/21/2016BuildMaster 5.1.1download
5.1.06/17/2016BuildMaster 5.1.0download
5.0.15/27/2016BuildMaster 5.0.4download
5.0.04/29/2016BuildMaster 5.0.0download
4.902/15/2016BuildMaster 4.9.0download
4.1311/12/2015BuildMaster 4.7.1download
4.1210/19/2015BuildMaster 4.7.1download
4.1112/16/2014BuildMaster 4.3.1download
4.109/12/2014BuildMaster 4.3.1download
4.96/26/2014BuildMaster 4.3.1download
4.86/12/2014BuildMaster 4.2.2download
4.75/5/2014BuildMaster 4.2.2download
4.64/18/2014BuildMaster 4.2.0download
4.52/6/2014BuildMaster 4.1.0download
4.42/3/2014BuildMaster 4.1.0download
4.31/31/2014BuildMaster 4.1.0download
4.212/30/2013BuildMaster 4.0.7download
4.112/2/2013BuildMaster 4.0.7download
4.010/7/2013BuildMaster 4.0.2download
3.128/8/2013BuildMaster 3.5.0download
3.115/1/2013BuildMaster 3.5.0download
3.101/18/2013BuildMaster 3.5.0download
3.912/3/2012BuildMaster 3.3.0download
3.811/20/2012BuildMaster 3.3.0download
3.76/29/2012BuildMaster 3.2.0download
3.64/9/2012BuildMaster 3.1.0download
3.53/4/2012BuildMaster 3.0.0download
3.42/28/2012BuildMaster 3.0.0download
3.32/27/2012BuildMaster 3.0.0download
3.22/16/2012BuildMaster 3.0.0download
3.12/1/2012BuildMaster 3.0.0download
3.01/7/2012BuildMaster 3.0.0download

If your installation of BuildMaster can access inedo.com, simply navigate to Admin > Extensions, and install or update extensions from the gallery.

You can also manually install the extension.

  1. Copy the extension file (Windows.bmx) to the Extension Library path (by default, this is c:\BuildMaster\Extensions).
  2. Restart the BuildMaster Service (Admin > Service).
  3. Restart the BuildMaster Web Application (Admin > All Settings > Save).
  4. Verify that the new extension has been loaded (Admin > Extensions)