5.6
Table Of Contents
- VMware vCenter Configuration Manager Administration Guide
- Contents
- About This Book
- Getting Started with VCM
- Installing and Getting Started with VCM Tools
- Configuring VMware Cloud Infrastructure
- Virtual Environments Configuration
- Configure Virtual Environments Collections
- Configure Managing Agent Machines
- Obtain the SSL Certificate Thumbprint
- Configure vCenter Server Data Collections
- Configure vCenter Server Virtual Machine Collections
- Configure vCloud Director Collections
- Configure vCloud Director vApp Virtual Machines Collections
- Configure vShield Manager Collections
- Configure ESX Service Console OS Collections
- Configure the vSphere Client VCM Plug-In
- Running Compliance for the VMware Cloud Infrastructure
- Create and Run Virtual Environment Compliance Templates
- Create Virtual Environment Compliance Rule Groups
- Create and Test Virtual Environment Compliance Rules
- Create and Test Virtual Environment Compliance Filters
- Preview Virtual Environment Compliance Rule Groups
- Create Virtual Environment Compliance Templates
- Run Virtual Environment Compliance Templates
- Resolve Noncompliant Virtual Environments Template Results
- Configure Alerts and Schedule Virtual Environment Compliance Runs
- Configuring vCenter Operations Manager Integration
- Auditing Security Changes in Your Environment
- Configuring Windows Machines
- Configure Windows Machines
- Verify Available Domains
- Check the Network Authority
- Assign Network Authority Accounts
- Discover Windows Machines
- License Windows Machines
- Install the VCM Windows Agent on Your Windows Machines
- Collect Windows Data
- Windows Collection Results
- Getting Started with Windows Custom Information
- Prerequisites to Collect Windows Custom Information
- Using PowerShell Scripts for WCI Collections
- Windows Custom Information Change Management
- Collecting Windows Custom Information
- Create Your Own WCI PowerShell Collection Script
- Verify that Your Custom PowerShell Script is Valid
- Install PowerShell
- Collect Windows Custom Information Data
- Run the Script-Based Collection Filter
- View Windows Custom Information Job Status Details
- Windows Custom Information Collection Results
- Run Windows Custom Information Reports
- Troubleshooting Custom PowerShell Scripts
- Configuring Linux and UNIX Machines
- Configuring Mac OS X Machines
- Patching Managed Machines
- VCM Patching for Windows Machines
- VCM Patching for UNIX and Linux Machines
- UNIX and Linux Patch Assessment and Deployment
- Getting Started with VCM Patching
- Getting Started with VCM Patching for Windows Machines
- Check for Updates to Bulletins
- Collect Data from Windows Machines by Using the VCM Patching Filter Sets
- Assess Windows Machines
- Review VCM Patching Windows Assessment Results
- Prerequisites for Patch Deployment
- Default Location for UNIX/Linux Patches
- Location for UNIX/Linux Patches
- Default Location for UNIX/Linux Patches
- vCenter Software Content Repository Tool
- Deploy Patches to Windows Machines
- Getting Started with VCM Patching for UNIX and Linux Machines
- Check for Updates to Bulletins
- Collect Patch Assessment Data from UNIX and Linux Machines
- Explore Assessment Results and Acquire and Store the Patches
- Default Location for UNIX/Linux Patches
- Deploy Patches to UNIX/Linux Machines
- How the Deploy Action Works
- Running VCM Patching Reports
- Customize Your Environment for VCM Patching
- Running and Enforcing Compliance
- Provisioning Physical or Virtual Machine Operating Systems
- Provisioning Software on Managed Machines
- Using Package Studio to Create Software Packages and Publish to Repositories
- Software Repository for Windows
- Package Manager for Windows
- Software Provisioning Component Relationships
- Install the Software Provisioning Components
- Using Package Studio to Create Software Packages and Publish to Repositories
- Using VCM Software Provisioning for Windows
- Related Software Provisioning Actions
- Configuring Active Directory Environments
- Configuring Remote Machines
- Tracking Unmanaged Hardware and Software Asset Data
- Managing Changes with Service Desk Integration
- Index
Procedure
1. On your VCM Collector or managed Windows machine, open a command prompt.
2. Run powershell.exe from the command line.
3. Paste your script into the PowerShell window.
If your script does not run, press Enter.
4. Make sure that your script runs without errors.
Errors appear in red in the PowerShell window.
5. If errors occur, resolve them.
A valid script returns a set of XML content without any formatting, white space, carriage returns, or
line feeds at the end of elements, nodes, or attributes.
What to do next
Install PowerShell on your VCM managed machines. See "Install PowerShell" on page 114.
Install PowerShell
Verify that PowerShell 2.0 is installed on each VCM managed Windows machine used to collect Windows
Custom Information (WCI).
PowerShell 2.0 is supported on all platforms that support PowerShell 1.0.
n
PowerShell is installed by default on Windows 2008 R2 and Windows 7 machines.
n
For Windows XP, 2003, 2003 R2, 2008, and Vista machines, you must install PowerShell separately.
n
You cannot install PowerShell on Windows 2000 or NT4 machines.
Because of its ability to set the execution policy at the process level, PowerShell 2.0 is the base requirement
for WCI in VCM. If you run the standard WCI non-inline collection filters against PowerShell 1.0 VCM
managed machines, the collection process will fail.
Procedure
1. On your VCM managed machine, check the following registry entry to verify whether PowerShell 2.0
is installed.
a. Key Location: HKEY_LOCAL_
MACHINE\SOFTWARE\Microsoft\PowerShell\1\PowerShellEngine
b. Value Name: PowerShellVersion
c. Value Type: REG_SZ
d. Value Data: <1.0 | 2.0>
If you do not check the registry, the steps to determine if PowerShell 2.0 might differ depending on the
platform type of your managed machine.
If PowerShell is not installed on the target VCM managed machine, the WCI collection returns a Not
Executed status. See "View Windows Custom Information Job Status Details" on page 116.
What to do next
Reboot the VCM managed machine after you install or upgrade PowerShell to ensure that collections
work properly.
vCenter Configuration Manager Administration Guide
114
VMware, Inc.