Vmware Vcenter Server 6.0

admin

VMware vCenter Server™ on Microsoft Windows and VMware vCenter™ Server Appliance™, with recommendations and best practices for providing acceptable levels of protection. Availability Considerations for vCenter Server 6.0 vCenter Server can be a single point of failure in the environment. Many VMware® solutions, such as. The VMware vCenter Converter Standalone 6.0 provides: Support for virtual machine hardware version 11. Compatibility with vSphere 6.0 and Workstation 11. Support for additional guest operating systems: Red Hat Enterprise Linux 7, Ubuntu 14, CentOS 6-7, Windows Server 2012 R2, Windows 8.1. Support of pure IPv6 environments.

Download Vmware Vcenter Server 6.0 Update 3b. Configure a temporary network identity, once the VCSA 6.5 has been successfully upgraded it will take the network identity of the old VCSA 6.0. Review the summary and click on Finish. Once the newly VCSA 6.5 has been deployed we can move on onto Stage 2. Click on Continue. For information on vCenter Server behavior in mixed version environments, see Upgrade or Migration Order and Mixed-Version Transitional Behavior for Multiple vCenter Server Instance Deployments. For information about upgrading Platform Services Controller 6.0, see Upgrade vCenter Platform Services Controller 6.0 on Windows.

Checklist Summary:

The VMware vSphere 6.0 vCenter Server for Windows Security Technical ImplementationGuide (STIG) provides security policy and configuration requirements for the vCenter Servermanagement application running on Windows to manage VMware vSphere 6.0 ESXihypervisors and hosted virtual machines.The VMware vSphere 6.0 vCenter Server for Windows STIG presumes the application isinstalled on a STIG-compliant Microsoft Windows server, using Active Directory services, in anenvironment compliant with all applicable DoD guidance.

Checklist Role:

  • Virtualization Server

Known Issues:

Not Provided

Target Audience:

The security requirements contained within this STIG are designed to assist Security Managers (SMs), Information Assurance Managers (IAMs), Information Assurance Officers (IAOs), and System Administrators (SAs) with configuring and maintaining security controls in a VMware vSphere environment centrally managed by a vCenter Server.This document is not a guide to Windows system administration.

Target Operational Environment:

  • Managed
  • Specialized Security-Limited Functionality (SSLF)

Testing Information:

Not Provided

Regulatory Compliance:

DoD Directive (DoDD) 8500.1 and 8500.2

Comments/Warnings/Miscellaneous:

Comments or proposed revisions to this document should be sent via email to disa.stig_spt@mail.mil. DISA Field Security Operations (FSO) will coordinate all change requests with the relevant DoD organizations before inclusion in this document.

Disclaimer:

Not Provided

Product Support:

Not Provided

Point of Contact:

Vmware vcenter server 6.0 update 3 appliance

disa.stig_spt@mail.mil

Sponsor:

Not Provided

Licensing:

Not Provided

Change History:

Dependency/Requirements:

URLDescription

Vmware Vcenter Server 6.0 Installation & Configuration Step By Step

References:

Reference URLDescription
https://dl.dod.cyber.mil/wp-content/uploads/stigs/pdf/U_VMWare_vSphere_6-0_V1R1_Overview.pdfSunset - VMware vSphere 6.0 Overview - Ver 1, Rel 1
https://dl.dod.cyber.mil/wp-content/uploads/stigs/pdf/U_VMware_vSphere_6-0_STIGs_V1_Release_Memo.pdfVMware vSphere 6.0 STIG Release Memo

NIST checklist record last modified on 11/25/2019

Updated on: 23 April 2015

vCenter Server 6.0.0a | 16 APR 2015 | ISO Build 2656757

vCenter Server Appliance 6.0.0a | 16 APR 2015 | ISO Build 2656757

vCenter Server 6.0.0a on Windows |16 APR 2015 | Build 2656760

vCenter Server 6.0.0a on vCenter Server Appliance | 16 APR 2015 | Build 2656761

Check for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

What's New

This release of vCenter Server 6.0.0a delivers a number of bug fixes that have been documented in the Resolved Issues section.

Note: vCenter Server 6.0 is no longer available for download.

Earlier Releases of vCenter Server 6.0

For compatibility, installation and upgrades, product support notices, and features see the earlier release notes of vCenter Server

Patches Contained in this Release

This release of vCenter Server 6.0.0a delivers the following patches. See the VMware Patch Download Center for more information on downloading patches.

Vmware Vcenter Server 6.0 Free

Internationalization

VMware vSphere 6.0 is available in the following languages:

Vmware
  • English
  • French
  • German
  • Japanese
  • Korean
  • Simplified Chinese
  • Traditional Chinese

Components of VMware vSphere 6.0, including vCenter Server, ESXi, the vSphere Web Client, and the vSphere Client do not accept non-ASCII input.

Resolved Issues

vCenter Single Sign-OnIssues

  • Erroneous string in an error message displayed when you add Integrated Active Directory Identity Source
    When you attempt to add an Integrated Active Directory (IWA) Identity Source on a Platform Services Controller (PSC) that has not joined a domain, an error message similar to the following is displayed:
    'The vCenter Single Sign-On service is not currently joined to any domain. You cannot complete the current operation. Go to Administration and select System Configuration, then navigate to the infrastructure node associates with vCenter Single Sign-On and join the node to Active Directory domain. SUGGEST SHORTENING THIS AND POINT TO DOC.'
    The error message contains an erroneous string 'SUGGEST SHORTENING THIS AND POINT TO DOC'
    This issue is resolved in this release by removing the erroneous string.
Vcenter

Security Issues

Vmware Vcenter Server 6.0 Crack

  • Oracle (Sun) JRE is updated to version 1.7.0_76
    The Oracle (Sun) JRE is updated to version JRE 1.7.0_76 to address multiple security issues. See Oracle Update Release Notes for details. For more information, see 2111641.

Upgrade and Installation Issues

  • Post upgrade of vCenter Server Appliance 5.5 to 6.0 identity stores might be missing in vRealize Automation
    After you upgrade from vCenter Server Appliance 5.5 to 6.0, the identity stores contained in non-vsphere.local tenants do not migrate.
    This issue is resolved in this release.

  • Policy tag and category merge during vCenter Server upgrade from 5.5 to 6.0 can cause a Rule-Set1 alert
    When you upgrade vCenter Server 5.5 to 6.0, policy tags and categories with case-insensitive names are merged incorrectly. For example, if a vCenter Server database has two tags in two categories with different cases before upgrade, such as 'One' and 'one,' with each tag belonging to a separate storage profile before the upgrade, the upgrade process merges the tags into a single tag and a single category, such as'One.'
    As a result of the case-insensitive tag and category merge, the storage profile which has the tag that was removed, such as 'one' in the example above, has a Rule-Set1 alert.
    This issue is resolved by fixing the dangling tags by adding the property pbm.fixPolicyTags = true in the pbm.properties file and restart the VMware vSphere Profile-Driven Storage Service.

  • Attempts to install or upgrade to the vCenter Server Appliance 6.0 fails with error while configuring vSphere Auto Deploy Waiter First Boot
    If you have configured the Password Policy 'Maximum Lifetime' to Never Expire by changing the value to zero (0), you might experience upgrade and fresh install failures during the vSphere Auto Deploy Waiter First Boot operation. An error message similar to the following is displayed on the VCSA HTML5 Deployment Wizard:
    Error while configuring vSphere Auto Deploy Waiter firstboot.
    Operation failed with error ERROR_NOT_SUPPORTED (50)
    This issue is resolved in this release.

  • Upgrade to VMware vCenter Server 6.0 fails after pre-install check
    Attempts to upgrade to vCenter Server 6.0 might fail with an error message similar to the following:
    'python.exe has stopped working'
    You will see entries similar to the following in the <vc-support bundle>vcsUpgradeupgradeRunner.log:
    <YYYY-MM-DD>T<TIME>Z ERROR __main__ Upgrade Runner has encountered an exception
    Traceback (most recent call last):
    File 'Z:PFilesVMwareCIScis_upgrade_runnerUpgradeRunner.py', line 1285, in main
    components.repository = components.ComponentRepository(metadata, probedData)
    ...
    ...
    ...
    GetLocalIPs
    ipAddr = adNode.ipAddress
    AttributeError: 'LP_IP_ADDR_STRING' object has no attribute 'ipAddress'
    <YYYY-MM-DD>T<TIME>Z ERROR __main__ Upgrade mode requirements failed

    This issue is resolved in this release.

  • Upgrade from vCenter Server Virtual Appliance (vCSA) 5.5 to 6.0 might fail
    Attempts to upgrade from vCSA 5.5 to 6.0 might fail with Authz backup error due to an out of memory issue. Logs similar to the following are logged in the IS export log:
    nnnn-nn-17T09:57:16.nnnZ INFO upgrade.states.component_states is:Export:
    nnnn-nn-17T09:57:16.nnnZ INFO upgrade.states.component_states is:Export: Mar 17, 2015 9:57:15 AM com.vmware.vim.dataservices.BackupAuthz main
    nnnn-nn-17T09:57:16.nnnZ INFO upgrade.states.component_states is:Export: SEVERE: Backup Authz failed
    nnnn-nn-17T09:57:16.nnnZ INFO upgrade.states.component_states is:Export: java.lang.OutOfMemoryError: Java heap space

    This issue is resolved in this release.

  • Upgrade from VMware vCenter Server Appliance 5.x to 6.0 fails at pre-upgrade check
    Attempts to upgrade vCenter Server Appliance 5.x to 6.0 might stop responding during validation on the 'Connect to source Appliance' stage.

    The issue occurs as the vCenter Single Sign-On SSL certificate does not have an IP address specified.

    This issue is resolved in this release.

vCenter Server, vSphere Client, and vSphere Web Client Issues

  • Adding a third-party host of type VMware vCloud Air to vCenter Server fails.
    Connecting to vCloud Air Third-Party option in the vCenter Host Gateway appliance task fails. Few Third-Party Hyper-visors are not currently supported although the options are listed in the vSphere Web Client.

    This issue is resolved in this release.

  • Tag associations are missing after backup and restore operation
    The tag association is not displayed in the vSphere Web Client after backup and restore operation of different nodes in the system. This issue occurs when the data in different nodes are not in sync with each other.

    • This issue is resolved in this release.

Known Issues

For other existing issues that have not been resolved and documented in the Resolved Issues section, please see Known Issues section in the VMware vSphere 6.0 Release Notes.