Before you can enroll a VM in Guest OS Services, it must meet the following requirements:
Rackspace encourages using the Rackspace complementary VM templates when deploying VMs you want to enroll in Guest OS Services. Rackspace OS Administrators are accustomed to the operating system configurations of these VM templates.
The VM OS must be a supported type and version.
VM is powered on.
VMware Tools version 10.x is installed and running.
We recommend installing the latest supported version of VMware tools for best results during the automated enrollments.
The OS of the VM must have the local firewall disabled and allow remote access and privileged process execution by the enrollment account.
Do not enable two-factor authentication (2FA) for the enrollment account or the
rackuser account created during the enrollment process.
The VM must have at least one NIC connected to a physical network with at least one IPv4 IP address configured that matches the physical network topology.
The VM must have a reachable public IP address configured in the Rackspace Technology CMDB.
Guest OS Services does not support IPv6 addresses. You must disable IPv6 before enrollment in Guest OS Services.
The following requirements apply to Windows installations:
Install PowerShell v3 or higher.
If you increase the MaxMemoryPerShellMB quota for PowerShell v3, you must apply hotfix 2842230 or update to a newer version of PowerShell. If you apply the hotfix, set MaxMemoryPerShellMB to 2048.
Disable User Account Control (UAC) for all users that are members of the local Administrators group.
Ensure that WinRM is startable and enable TLS 1.2.
Provide an Administrator-privileged login for remote access for enrollment.
Enable Remote Desktop sessions.
For servers joined to customer Active Directory, configure the AD DNS service with Rackspace DNS forwarders. Contact your Account team for details.
For servers joined to customer Active Directory, any group policy settings active for the servers being enrolled in Guest OS Services must not conflict with or revert any changes being made during or after enrollment.
The following requirements apply to Linux installations:
Allow remote SSH logins for the provided user credentials.
Provide a root privileged login for enrollment.
Configure a valid repo for dependent package installation.
Remove all invalid repo references, including original ISOs used.
The valid repo requirement does not apply if you select Rackspace patching.
Ensure that you do not use customer-provided RHEL licensing. If you select the patching service, configure the Rackspace patching service instead of the existing patching service subscription.
Ensure that you install rhn packages on your CentOS servers to qualify for enrollment of the patching service. Verify that you installed the following packages:
rhn-client-tools, rhn-check, rhn-setup, rhnsd, m2crypto, yum-rhn-plugin