Book Image

VMware vRealize Configuration Manager Cookbook

By : Abhijeet Shriram Janwalkar
Book Image

VMware vRealize Configuration Manager Cookbook

By: Abhijeet Shriram Janwalkar

Overview of this book

VMware vRealize Configuration Manager (VCM) helps you to automate IT operations, manage performance, and gain visibility across physical and virtual infrastructure. It is continuously being used by enterprises to audit the configurations of the VMware infrastructure as well as the Windows, Linux, and UNIX operating systems. This book is filled with practical recipes through which you will learn about the latest features of vRealize Configuration Manager 5.8.X, starting with installation of various tiers of VCM followed by configuration management across physical and virtual servers. Throughout this book, you will explore how VCM can perform tasks such as patch management, compliance assessment, and software package distribution along with Machine filters for new platforms such as RHEL 7 and Windows 10. This book will ease your troubles while upgrading from the existing VCM to the latest version by providing you with step-by-step instructions about the process of migration along with upgrade and maintenance support. This book will help you understand how to integrate vRealize Configuration with other applications along with schedule management and also guide you on how to handle security issues. After reading this book, you will have a clear understanding of how VCM fits in the overall picture of the data center design from a patching and compliance perspective.
Table of Contents (18 chapters)
VMware vRealize Configuration Manager Cookbook
Credits
About the Author
Acknowledgments
About the Reviewer
www.PacktPub.com
Preface
11
Understanding VCM Console

Introduction


Compliance means meeting requirements. It is also used to refer to industry-wide or government rules and regulations that mention how data should be managed, and the need for organizations to be compliant with those regulations.

Consider a rule for password complexity, such as the length of the password not being fewer than 12 characters. Now, you need to check whether this is true for all the machines in your infrastructure. Let's assume you have a few thousand machines to check and, if they aren't in compliance, reconfigure.

You can understand how much time it would take to go through each machine, check the setting, and correct it if it's to be found noncompliant. Now, multiply those efforts for a few hundred rules–how do you document all the statuses to show the auditor? This becomes more complex when you want to be compliant for various government and industry standards such as ISO, HIPPA, and Suburban Oxley. They have a few hundred rules per standard and changes per operating...