<?xml version="1.0" encoding="UTF-8"?><!--
- Licensed Materials - Property of IBM Corp.
- IBM UrbanCode Build
- IBM UrbanCode Deploy
- IBM UrbanCode Release
- IBM AnthillPro
- (c) Copyright IBM Corporation 2002, 2016. All Rights Reserved.
-
- U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by
- GSA ADP Schedule Contract with IBM Corp.
--><pluginInfo>
  <!--

  **author name IS required**

  The Author Section is used to give credit to the author of the plugin.
  Name is the only required element/attribute, but feel free to also include your email,
  website  or bio to allow users of your plugin to praise your work, ask questions
  or share their use case to help grow your plugin's functionality.
  -->

  <author name="UrbanCode">
    <organization>UrbanCode</organization>
    <email>info@urbancode.com</email>
    <website>http://urbancode.com</website>
    <bio/>
  </author>

  <!--

  **intergration type IS Required**

  The integration type section identifies where the plugin fits into the process
  excepted types are SCM, Build, Artifact, Automation, Deploy

  For example:

  The plugin pulls Artifacts from an artifact repository during deployment
  the Type would be "Artifact"
  or
  The plugin deploys to a middleware server
  the Type would be "Deploy"
  -->

  <integration type="automation"/>


  <!--
  **source is NOT required**

  The source section identifies the location of the plugin source code
  For example
  https://github.com/...
  -->
  <!--
  <source url=""/>
  -->
  <!--
  **license type is NOT required**

  If your plugin uses any licensed software please acknowledge it by
  listing the license type below
  -->
  <!--
  <licenses>
    <license type=""/>
  </licenses>
  -->
  <!--
  **tool-description IS required**

  The tool-description section is used to summarize the software
  the plugin was created to integrate with.

  For example:
  Apache Ant is a software tool to automate software processes during the build or
  deployment of an application. Ant uses an propitiatory XML file to define build
  and/or deployment steps(referred to as targets by ant) . The Ant executable is
  called to execute the targets in the build.xml.
  -->

  <tool-description>This is an UrbanCode devoloped plugin for performing various Windows tasks</tool-description>

  <!--
  **related-info is NOT required**

  The releated-info section is used to define links which may be useful to users of the plugin
  but don't fall into the release-notes or tool-description section.

  For example: releated-info can be links to pdf documentation, help videos related to plugin setup or the product's
  website.

  excepted values for type include: PDF, WEBSITE, VIDEO
  -->
  <!--
  <related-info>
    <link title="" type="" description="" url =""/>
  </related-info>
  -->
  <!--
  **meta-html in NOT required**

  The meta-html section is used define the meta description and the meta keywords of the plugin page.The meta
  description tag allows you to influence the description of your page in the web crawlers that support the
  tag The meta keywords tag allows   you to provide additional text for crawler-based search engines to index
  along with your body copy.

  If multiple keywords are used they must be comma(,) delimited
  -->

  <meta-html>
    <meta content="" name="description"/>
    <meta content="" name="keywords"/>
  </meta-html>

  <!-- Do not change the release-version, the build process injects it. -->
  <release-version>23.876575</release-version>


  <release-notes>
    <!--
      **release-note IS required**

      The plugin-version name must match the plugin version found in the plugin.xml file

      The release-note should document the changes, improvements, or bug fixes introduced
      with the new plugin version

      The release-note may contain text or reference a file in the plugin zip package

      For example your release note could be:
      Support for was added for version 10.0 for software X
      or
      releaseNotes/release1.html (where release1.html contains html formatted version information)

      To add a new release note add this with a description in it of the changes:
      <release-note plugin-version="10">....</release-note>

      Our automated release process will replace 'LATEST' with the released version.

      If this already exists in the file, then the described changes have not been released yet and
      you should just append to the existing 'LATEST' tag.
      -->

      <release-note plugin-version="10">
Installing this plugin will give you access to the steps listed below. These steps can be used when designing a component process.
      </release-note>
      <release-note plugin-version="11">
This update adds support for icacls, in addition to xcacls and cacls, when setting permissions using the Modify ACLs step.
      </release-note>
      <release-note plugin-version="12">
This update adds support for exporting registry keys to file.
      </release-note>
      <release-note plugin-version="13">
This update adds support for creating custom Windows event logs.
      </release-note>
      <release-note plugin-version="14">
This update adds support for logging user sessions off.
      </release-note>
      <release-note plugin-version="15">
This update adds support for creating/deleting/running/ending scheduled tasks.
      </release-note>
      <release-note plugin-version="16">
This update adds the Delete Registry Key step and fix a bug in the Import Registry File step
      </release-note>
      <release-note plugin-version="17">
This update adds an additional option to the Delete Registry Key step.
      </release-note>
      <release-note plugin-version="18">
Fixed PI32983 - WINDOWS SYSTEM TOOLS PLUGIN HAS A SPELLING ERROR (REG_MUTLI_SZ INSTEAD OF REG_MULTI_SZ) IN PLUGIN.XML
      </release-note>
      <release-note plugin-version="19">
Fixed PI38873 - WINDOWS SYSTEM TOOLS DOES NOT LOG OFF SESSIONS IN DISCONNECTED STATE
      </release-note>
      <release-note plugin-version="20">
This update adds support for safely shutting down an agent before reboot. Implemented specifically for Windows 2012 machines.
      </release-note>
      <release-note plugin-version="21">
This update adds the following functionality to the Create Windows Scheduled Task step:
    - /U, /P, /RU, and /RP parameters have been added as hidden properties.
    - An Additional Arguments parameter has been added as a hidden property.
      </release-note>
      <release-note plugin-version="22">
Lowered the mandatory wait period for Windows 2012 machines using the Reboot step from 1 minute to 30 seconds.
Support property file encryption.
      </release-note>
      <release-note plugin-version="23">
Adding missing classpath to the Check File Contents step.
      </release-note>
  </release-notes>
</pluginInfo>