PREVIOUS WORK: https://greencircle.vmturbo.com/docs/DOC-3390
Yes Turbonomic internal documentation reference
Yes Field tested
Yes Peer revision
APPLIES TO TURBONOMIC VERSION(S):
6.x (Note: Native WMI probe only, up to v6.0.x | v:6.1 uses revamped SDK Probe, this procedure should not be needed)
Turbonomic and Microsoft (MS) Active Directory (AD) Group Policy Objects (GPO):
Applications in Turbonomic sit at the top of the supply chain (1), they are the ultimate consumers (re. vCPU, vMEM, etc). Turbonomic automatically creates an instance of a ‘GuestLoad’ application on every VM (no extra configuration needed), which represents the demand of the VM. Ultimately, all system behavior is driven by application demand. We can take this one step further by identifying the process table (e.g. task manager) of a running VM and this is where WMI and SNMP come handy in an MS AD network environment.
This article covers the specific case of bulk configuring WMI on VMs using GPO within an MS Windows AD network environment. The GPO will carry required WMI registry changes that will ultimately facilitate the ‘GuestLoad’ application identification by the Turbonomic Instance.
REQUIREMENTS & SCOPE:
- Applies to Virtual Machines within a Microsoft Windows Active Directory network environment.
- The target environment is running Windows Server 2003 Active Directory or later as these are the only editions of Windows which include support for Hyper-V (re. GPO)
- Creation of an domain based GPO (not a local GPO)
- An AD account that is used by Turbonomic to add WMI Targets
- The AD account used by Turbonomic must be given FULL permission to the the WMI registry key injected via GPO.
- Proper WMI Registry Keys:
- Create and/or Edit a GPO adding the necessary registry key settings (values and access rights).
- Link the GPO to the proper AD container (relevant to Turbonomic VM targets)
- Add WMI target in Turbonomic
Disclaimer: Instructions are based on a Windows 2008R2 AD platform. There may be slight differences between OS versions. Microsoft Documentation resources should be used to find congruent instructions.
Creating a GPO
GPO Creation is out of scope for this article. The specifics of how to create a domain GPO are better served by official MS documentation. We offer references to the following non-Turbonomic resources, hoping they are of guidance. Refer to your official source documentation and even share with our GC community if you feel the information can fill a gap.
Edit GPO: Adding WMI Turbonomic relevant registry keys.
Go to and expand Computer Configuration
>> Windows Settings
>> Security Settings
>> and Right-click on Registry
>> Select Add Key
Browse for the following Registry Key:
Select the Key
The Security applet opens, here you will set owner and permission access rights.
Click ADD under ‘Group or user names:’
>> Enter AD username that authorizes Turbonomic to connect to your Windows (Server) VMs..
>> Grant this user FULL control (check under the ALLOW column)
>> Click APPLY
Click the Advanced button
This opens the Advanced Security settings
>> Select the Owner tab
>> Add the same AD user for Turbonomic (see above)
>> Click APPLY and/or OK.
You will be presented with the Add Object screen
Select Configure this key then:
>> Propagate inheritable permissions to all subkeys.
Repeat the previous process for the following Registry Key as well:
SAMPLE IMPLEMENTATION VIDEO
Disclaimer: recorded procedure performed on a Windows 2008R2 AD domain network, shared for illustration purposes only and as-is (2).
You can now link the GPO to the AD container relevant to Turbonomic WMI targets (e.g. OU that contains the Hosts and VMs that you want to manage with Turbonomic):
Refer to your MS documentation for specific instructions on linking, enabling and/or enforcing a GPO on an AD OU.
(1) Interested in a more in depth Turbonomic knowledge? Look for ACE Certification Training here
(2) Credits to the IT Team of Goodwill Industries NY & NJ for assisting creating this video.