In this example we are going to configure a few different types of custom properties. The properties we are going to configure are:
- VMware.VirtualCenter.Folder – This property allows you to define the folder in vCenter that a virtual machine will be placed in. If the folder does no exists it will be created when a machine is crated to be placed in the folder.
- Cost.Center – This is not a reserved custom property, it’s one we are going to make up to attach a cost center to the machine request.
- Project.ID – This is not a reserved custom property, it’s one we are going to make up to attach a Project ID to the machine request. We are going to prompt the user to input this value as part of the request.
- Plugin.ADMachine.Cleanup.X – There are actually a few properties associated with this. The AD Cleanup wizard is a set of properties that allows you to configure what action to take in AD when a machine is destroyed. In my example I’m going to remove the machine record, however you can also configure it to move the machine to a specific OU and not delete it’s record.
Defining the VMware.VirtualCenter.Folder Property
We are going to define this property at the provisioning group and assign a unique folder to two different groups.
1. Go to “Enterprise Administrators” and select “Provisioning Groups” Select the first group you want to edit.
2. At the bottom of the page select “New Property” and enter “VMware.VirtualCenter.Folder” without the quotes in the “Name” field. Remember properties are case sensitive. In the “Value” field enter the folder you would like the machine provisioned by this group placed in. Use the format “Folder\” If you want nested folders you can simple as them by formatting it like “Folder\Sub Folder\“. When finished click the “Green Check” and then click “New Property” again.
The Cost.Center Property
The Project.ID Property
4. Now select another group and repeat steps 1-2. Once steps 1-2 are complete we will add an additional property like we did for the Cost.Center only this time it will be Project.ID. When you create the property select the check box for “Prompt User”.
The AD Clean-Up Wizard Properties
5. Go to “Enterprise Administrator” and select “Build Profiles“. Once there select “New Build Profile” in the upper right corner.
6. Name your build profile and then select “ActiveDirectoryCleanupPlugin” from the drop down list and then click “Load”
7. This will add (5) properties under custom properties. Remove the “Plugin.AdMachineCleanup.MoveToOu” property as we will not be utilizing it. Edit the UserName and Password properties and input account properties that has permissions to delete machines in AD. For the Password property make sure to check the “Encrypted” check box to mask the password. Click “Ok” to save the build profile.
Adding the AD Clean-Up Wizard Properties to a Blueprint
Now we need to add our Build Profile to a blueprint to enable the properties to be attached to a provisioned machine.
8. Go to “Enterprise Administrator” then “Global Blueprints” and select a blueprint to edit. Once the blueprint opens select the “Properties” tab and then within the “Build profiles” section check the box next to the “AD Clean-Up” build profile you just crated. Make sure under the “Blueprint Information” tab that both groups are enabled for access to this blueprint. Click “Ok” to save the blueprint.
Testing the custom properties
9. Go to “Self Service” and make a new request under the first group. Once You make your request go to “Enterprise Administrator” and select “Enterprise Machines” then select the machine you just requested. Once the edit machine page appears select the “Properties” tab. You will see the “Cost.Profile“, “VMware.VirtualCenter.Folder“, and “AD Clean-Up” properties and values listed.
10. Repeat step 9, but make the request under your second group. You will see the “Project.ID“, “VMware.VirtualCenter.Folder“, and “AD Clean-Up” properties and values listed.
11. Now if you go to vCenter you will see your two new VM’s under the folders your specified.