ConfigMgr 2012 Application Creator v1.0 - PowerShell tool

Hello Guys

It feels good to write a post aster a quite a long time. Recently i have been learning PowerShell and created a new tool to create a ConfigMgr application on your command. I am gonna stop the useless talks right here and walk you through the tool.

ConfigMgr App Creator V 1.0

             ConfigMgr App Creator is a wrapper tool for ConfigMgr 2012 which can be used to create ConfigMgr application, Dt and deployment on the go without even lanching the ConfigMgr console and going through a lenghthy object creation wizards.

            This tool will be really helpful for the packaging team who tends to take control over the application packaging  as well as application delivery to the deployment tool.

Pre-Requisites

The following applications must be present in the computer on which the tool is launched.

1. ConfigMgr 2012 R2 console
2. net framework
3. PowerShell 3.0 or higher

Look Of the Tool

Site Code: Module which connects the tool with the ConfigMgr WMI provider and import required PowerShell modules.

Expected Values / Action = the user is expected to enter the 3 dig ConfigMgr site code and client on connect

 Installer File: Module with a browse button to browser and select the *.vbs or *.msi installer.

Expected Value / Action = the user is expected to click on the browse button to select the installer file, and the complete file path will be populated in the text field.

 Application Name : name of the application that needs to be created within ConfigMgr

Expected Value / Action: the User is expected to give name of the application. If the installer is a MSI this filed will be automatically be populated from the MSI property.

Publisher: Publisher of the application that needs to be created within ConfigMgr

Expected Value / Action: the User is expected to give publisher of the application. If the installer is a MSI this filed will be automatically be populated from the MSI property.

Version: version of the application that needs to be created within ConfigMgr

Expected Value / Action: the User is expected to provide the version of the application. If the installer is a MSI this filed will be automatically be populated from the MSI property.

Installation Program: Installation command line of the DT to be created for the created Application within ConfigMgr

Expected Value / Action: This filed will be automatically populated based on the installer file that the user selects. This can be edited.

 Uninstallation Program: Uninstallation command line of the DT to be created for the created Application within ConfigMgr

Expected Value / Action: This filed will be automatically populated based on the installer file that the user selects. This can be edited.

Content Source Path: Content source of the application to be created within ConfigMgr

Expected Value / Action: This filed will be automatically populated based on the installer file that the user selects. This can be edited.

 Installation Collection Name: Name of the collection to be created within ConfigMgr

Expected Value / Action: This filed will be automatically populated based on the installer file that the user selects. This can be edited.

Deployment Name: Name of the Deployment to be created within ConfigMgr

Expected Value / Action: This filed will be automatically populated based on the installer file that the user selects. This can be edited.

Target: to specify whether the collection is going to be a user based or Device based.

Expected Value / Action: By default the “Device” radio button will be selected. This can be changed.

Purpose: Purpose of the deployment to be created.

Expected Value / Action: By default the “required” radio button will be selected. This can be changed.

Create Collection / Deployment: The check boxes can be used to select if collection or deployment should be created.

Expected Value / Action: On successful connection to the ConfigMgr site both this check boxes will be checked. This can be changed.

 Read: This button validates if all the fields are correctly populated. If any of the field is not populated, this will populate it with default values. On successful validation this will enable the create button.

Expected Value / Action: The user is expected to click and validate the fields before clicking on create button.

Create: This button triggers the script execution of creating application in ConfigMgr. This will be enabled only after the successful validation.

Expected Value / Action: The user is expected to click this button after validating the fields.

Log Field: the status of each and every step that the script performs will be recorded here.

Expected Value / Action: The user is expected to observe this field to verify the successful creation of the application.

Author / Website: Information field

Version: Information filed

Link to Download the Tool

Download Link

TechyTipz

Posted in: ConfigMgr, PowerShell