Solving error “The trust relationship between this workstation and the primary domain failed.”

Leave a reply

Last week I reverted an snapshot on an Virtual Server. When I restarted the VM, and try to logon, I received the following error:

“The trust relationship between this workstation and the primary domain failed.”

My domain admin account was unable to logon. My local admin account was able to logon. How to solve this issue without removing this VM from the domain.

Solution.

First, logon using the local administrator credentials.

Open an elevated Command Prompt and type the following command:

netdom resetpwd /s:[FQDN Domain Controller] /ud:[domain name]\administrator /pd:*

[FQDN Domain Controller] fill in the Domain Controller server name and domain.

[Domain name] fill in the domain name.

After running this command, restart the server and logon with the domain credentials. If everything went ok, you are able to logon on and the trust relationship is restored again.

For more information about the netdom command, see: https://technet.microsoft.com/en-us/library/cc772217(v=ws.11).aspx

VMware vExpert 2016 Announcement

Leave a reply

Yesterday the VMware vExpert for 2016 were announced. And YES I am one of them for the fourth time.

The complete list of all the vExperts can be found here.

Each of these vExperts have demonstrated significant contributions to the community and a willingness to share their expertise with others.

I would like to thank Corey Romero and the rest of the VMware Social & Community Team for making this possible.

Congratulations to all the other 2016 vExperts.

Veeam Jobs fail after adding new ESXi hosts

Leave a reply

When you add new VMware Hosts to a VMware vCenter Cluster, please remember to do a rescan of vCenter in Veeam. Veeam now rescans the complete environment and adds the new ESXi hosts to its database so everything will work correctly.

My problem was after I placed new VMware ESXi hosts in the VMware vCenter cluster, the backup was failing on every VM that was placed on the new ESXi hosts. Veeam had detected the new VMware ESXi hosts, so I thought everything was good.

My Error message was: “Failed to create processing task for VM [vm name] Error: Host ‘ESXi host’ with type ‘ESX’ and parentId ‘e2afc39e-f38c-466b-9431-cd1b7aedc48b’ not found.”

A quick google action on this error message resulted in a Veeam Forum post. See http://forums.veeam.com/vmware-vsphere-f24/problem-with-backups-after-adding-new-host-to-vcenter-t18512.html

User v.Eremin is saying in his post:

As long as VMs are added to backup console via vCenter, backup server should be vMotion aware and you shouldn’t encounter any issues after VM migration. However, it seems that vCenter added to backup console didn’t know about the new host and about the fact that certain VMs had been migrated to it, thus, backup jobs failed. So, now, when the rescan is done, everything should be ok, even without manual re-adding of VMs.

This gave me the tip to first do a rescan of vCenter to see if this solved my problem. And this worked for me, thanks Veeam Forums!

VMworld 2015 General Sessions

Leave a reply

This week is VMware organizing there yearly event VMworld. I can’t attend, but I’ve watched both keynotes with all the new things. VMware has published the General session from Monday, August 31 on there YouTube channel.

It was a very interesting keynote with a lot of new things…

Resetting an expired password in vCenter 5.1 Single Sign-On (SSO)

Leave a reply

A customer of ours was unable to login to their VMware vCenter 5.1 environment. I researched the environment and concluded that there SSO password was expired.

Error messages in the vSphere webclient: “provided credentials are not valid”. Also the admin@system-domain account was unable to logon, same error message. And I was 100% sure this was the correct password.

I started searching the VMware KB articles and found one that describes how to reset the password. See VMware KB2035864.

Resetting an expired password in vCenter Single Sign-On (SSO) (2035864)

Details

  • vCenter Single Sign-On account (SSO) passwords expire after 365 days, including the password for admin@system-domain.
  • In vSphere 5.1, you see this error on a login attempt with an expired password:
    Web Client: “provided credentials are not valid”
  • In the vsphere_client_virgo.log, you see the error:
    SOAP fault javax.xml.ws.soap.SOAPFaultException: Authentication failed

Solution

vCenter Single Sign-On administrator users can change expired passwords for System-Domain users. Request that an administrator resets your password.

If you are a vCenter Single Sign-On administrator user, use the ssopass command-line tool to reset the password.

On the Windows host running vCenter Single Sign-On:

  1. Open an elevated command prompt and run the command:
    SET JAVA_HOME=C:\Program Files\VMware\Infrastructure\jre
    Note: This is the default path of the JRE folder for vCenter Server 5.1. If vCenter Server has been installed in a custom location, change command accordingly.
  2. Navigate to the ssolscli directory
    c:\>cd C:\Program Files\VMware\Infrastructure\SSOServer\ssolscli
  3. Run the following command:
    ssopass -d https://FQDN_of_SSO_server:7444/lookupservice/sdk username
  4. Type your current password, even if it is expired.
  5. Type the new password, and then type it again to confirm.

Note: If the above steps fail to update the password, see Logging in to the vSphere Web Client using admin@system-domain fails with the error: associated users password is expired (2060150).

From the vCenter Server Appliance (VCSA):

  1. Log in to the vCenter Server Appliance as root.
    Note: The default password is vmware.
  2. Navigate to this directory:
    /usr/lib/vmware-sso/bin
  3. Run this command:
    ./ssopass -d https://FQDN_of_SSO_server:7444/lookupservice/sdk username
  4. Type the current password for the user, even if it is expired.
  5. Type the new password, and then type it again to confirm.

This document helped me to regain access to the VMware vCenter environment. Problem solved.

Veeam Backup & Replication 8 Update 2 released

Leave a reply

Yesterday Veeam launched update 2 for the Veeam Backup & Replication 8 application. With this update Veeam is fully compatible with VMware vSphere 6.

There are the release notes.

Engine

  • Job performance improvements. A number of optimizations focused on reducing the time jobs spend performing auxiliary tasks should significantly reduce the overall job execution time for incremental runs of backup and Backup Copy jobs.
  • Slow backup storage optimization. Target data mover now caches metadata from backup files, instead of requesting it from backup files residing multiple times over the course of the job run. This significantly improves performance of jobs targeting storage with poor random I/O performance (such as EMC Data Domain), while reducing the overall storage load. Important notes:
    • The cache is only enabled when using a 64-bit OS on backup repository (or gateway server), and increases RAM consumption of each job by 2GB on average, depending on backup chain size. Using non-default backup block size changes cache RAM requirements proportionally.
    • Using the default “Automatic selection” gateway server setting for Shared folder, EMC DataDomain or HP StoreOnce based backup repositories disables the cache.
    • Disabling built-in deduplication disables the cache.
  • 64-bit Linux data mover. For increased scalability, a 64-bit data mover will now be used on 64-bit Linux backup repositories with an OS kernel version of 2.6.18 or later.
  • Linux data mover update. To enable new functionality, jobs will leverage the new version of the data mover on Linux servers with kernel version 2.6 or later. For compatibility with existing servers, jobs will use a legacy data mover when OS kernel version is earlier than 2.6 or cannot be detected.
  • Direct data mover communication. When both data movers are running on the same server (e.g., when backing up to a local storage attached to a backup proxy server, etc.), they will now exchange data through shared memory. This should improve data transfer performance of local backup jobs currently reporting Network as the bottleneck, or when you see high load on some of the backup proxy server NICs when the data was supposed to stay local to the server.
  • vPower NFS performance. Increased scalability of vPower NFS server by significantly reducing CPU usage associated with guest I/O operations using small data blocks
  • VeeamZIP performance. Improved VeeamZIP performance when using a Veeam backup repository as the target.
  • Replication from backup file enhancements. Replication from backup files no longer requires matching block size between the backup file and replica job settings

VMware

  • vSphere 6 support. Added support for ESXi 6.0 and vCenter Server 6.0 (including vCenter Server Appliance).
  • vCloud Director 5.6 support. Added support for backup and restore of vCloud Director 5.6 virtual machines (VMs) and vApps.
  • VMware Virtual Volumes (VVols) support. VMs residing on virtual volumes can be processed in Virtual Appliance (Hot Add) and Network (NBD) processing modes. Hot add processing mode requires that all proxy VM disks are located on the same virtual volume with the processed VM.
  • VMware Virtual SAN (VSAN) 2.0 support. VMs residing on VSAN can be backed up in Virtual Appliance (Hot Add) and Network (NBD) processing modes. For VMs with existing snapshots, hot add processing requires that all proxy VM disks are located on the same VSAN datastore.
  • Storage Policy-Based Management (SPBM) policy backup and restore. Storage policy associations are backed up and restored for each virtual disk upon full VM restore. This eliminates the manual process, which directly impacts recovery time. SPBM policies are important to restore because “out of policy” VMs can impact availability of either the restored VM itself or other VMs sharing the same storage.
  • Support for Fault Tolerant VMs (FT VMs) for backups and replicas. VMs with Fault Tolerance enabled can now be backed up and replicated. Legacy Fault Tolerant VMs must have Fault Tolerance re-enabled after vSphere 6 upgrade using vSphere Web Client to enable this capability.
  • vSphere 6 tags integration. vSphere 6 introduces new APIs for programmatic access and management of vSphere tags. With vSphere 6 tag support, you can continue building new advanced backup policies based on tags, even after you upgrade to vSphere 6. Due to new unique tag IDs in vSphere 6, be sure to review your job setup after you upgrade to vCenter Server 6.0.
  • Cross-vCenter vMotion awareness. Added support for cross-vCenter vMotion to the Quick Migration functionality. Now, when migrating a VM to another vCenter Server, the associated entries on backup or replication jobs will be updated automatically to keep the VM protected
  • Quick Migration to VVols. Enables moving VMs to VVols when using vMotion is not an option due to unreliable or slow network links, in scenarios when vMotion is not supported, or due to lack of VMware licensing. This functionality can help perform full migrations to new vSphere 6 clusters built from the ground up without inheriting new design problems from previous clusters.
  • Hot-Add transport mode of SATA virtual disks. On ESXi 6.0, SATA virtual disks can now be processed in Virtual Appliance (Hot Add) processing mode, which was previously limited to SCSI virtual disks only.
  • vSphere tags priority. vSphere tags priority has been raised one level above containers priority to ensure that jobs behave in line with customers’ expectations when job’s inclusion and/or exclusion lists use both containers and tags.
  • Disable CBT reset. The workaround for VMware Changed Block Tracking (CBT) corruption issue at 128GB boundaries (VMware KB2090639) can now be disabled by customers with ESXi hosts patched against this issue. To disable automatic CBT reset upon virtual disk size change, create theResetCBTOnDiskResize (DWORD) registry value under HKLM\SOFTWARE\Veeam\Veeam Backup and Replication, and set it to 0.

Storage integration

  • Granular rescan settings. Added ability to control which storage LUNs and volumes should be rescanned periodically for new VMs. These settings can be accessed directly from the Add Storage wizard while registering the storage, or by right-clicking the already added storage in the Storage Infrastructure tab.
  • NetApp integration enhancements. The following NetApp-specific enhancements have been added:
    • Added support for triggering updates of non-qtree and vFiler-based SnapMirror and SnapVault
    • Added support for backing up VMs from NetApp MetroCluster in the failed over state
    • Preferred Network settings of Global Network Traffic Rules dialog now also used to pick preferred storage adapters for data transfer. And in cases when multiple adapters use the same subnet, NetAppOrderedIPList (STRING) registry value underHKLM\SOFTWARE\Veeam\Veeam Backup and Replication can now be created to specify preferred adapters’ IP addresses separated by a semicolon.

Hyper-V

  • SMB3 restore performance. Improved performance of full VM restore to SMB3 shares with caching disabled (such as in Nutanix).
  • Hyper-V Integration Services status check. To prevent situations with some VMs unexpectedly going into the Saved State during a volume snapshot creation, jobs will now check that Hyper-V Integration Services (HIS) are running and reachable, waiting for HIS to respond for up to 10 minutes before failing the VM processing.
  • Replica VM adjustment. Maximum RAM value of the replica VM is now automatically reduced according to the target host capabilities.

File-Level Recovery

  • Native 4K disk support. Windows File-Level Recovery now supports mounting native 4K virtual disks from backups out of the box, without requiring a user to switch to the mount engine via the corresponding registry value.
  • Linux ACL preservation. Multi-OS File-Level Recovery now preserves Linux ACL when restoring a file via Restore and Copy To operations. This requires that both backed up and destination VM runs Linux with kernel version 2.6 or later.
  • Linux host selection. Multi-OS File-Level Recovery now allows choice of a target Linux host to restore guest files to without having to add it to the managed servers first.
  • Restored files logging. Multi-OS File-Level Recovery now logs restored files in its session log, similar to the way Windows File-Level Recovery performs its restore activity logging.
  • SNMP traps. Both Windows and Multi-OS File-Level Recovery can now trigger SNMP notifications. To enable such notifications, create theEnableRestoreSNMPTraps (DWORD) registry value under HKLM\SOFTWARE\Veeam\Veeam Backup and Replication, and set it to 1.

Veeam Explorer for Microsoft SQL Server

  • Improved restore performance. Database restore performance has been improved by up to 3x.
  • Increased scalability. Reduced load on SQL Server hosting Veeam® Backup & Replication™ database in scenarios when transaction logs are being backed up from multiple SQL servers on a frequent schedule.
  • Log truncation retry. In cases when log truncation fails under the specified guest processing account, it will be retried from the LOCAL SYSTEM account, which often carries the necessary privileges to perform this operation.
  • SQL database restore. Added a warning when restoring a SQL database to a different location where the database with the same name already exists when using the Enterprise Manager web UI
  • Improved issues reporting. Backup job now detects and reports more issues around transaction log processing, such as failure to truncate logs. This may result in the appearance of a new warning after the update, simply because existing issues were not previously reported.

 

Veeam Cloud Connect

  • Multiple subscriptions support. Added ability to add the same service provider multiple times using different credentials.
  • Reconnect performance improvements. Reconnecting to a service provider should now occur much faster when a cloud provider has multiple Cloud Gateways deployed.
  • Enhancements for service providers. The following are enhancements relevant to Veeam Cloud Connect service providers only:
    • Added ability to granularly purge global cache from WAN accelerator for the specific tenant.
    • When deleting a tenant, global cache belonging to the tenant is now deleted automatically.
    • Added ability to query the amount of protected VMs for the given tenant through RESTful API using the vmCount property.
    • Service Providers node of the management tree is always shown when Cloud Connect Service Provider license is installed, without requiring the service provider to register at least one hypervisor host first. This enables service providers to more easily client consoles to user for testing or manipulating client backups.
    • Enhanced debug logging to include initiator information for when the connection is terminated.

 

Tape

  • Job performance. File to Tape and Backup to Tape job performance was further improved.
  • Synthesized full backup enhancements. Synthesized full backup functionality has been reworked for better reliability, performance and support for very large backup files.
  • Third-party tape handling. Added support for detecting and reusing tapes written by third-party tape backup vendors.

User Interface

  • Manual job chain execution. By popular demand, when manually starting a job that has other jobs chained to it via “After this job” scheduling option, you will now be offered a choice between starting the selected job alone, or starting the entire chain.
  • Disable network traffic rules. Both traffic throttling and encryption can now be temporarily disabled without requiring you to delete the corresponding rule completely, which is useful for troubleshooting or for temporarily removing bandwidth consumption restrictions.
  • Improved guest credentials test. Guest processing credential test will now additional verify the presence of mlocate, which is required for Linux guest file system indexing.

Setup

  • Silent install. Starting with Update 2, updates will fully support automated silent install, including triggering update of remote backup infrastructure components. This should significantly reduce the time required to update Veeam deployments with a large number of backup servers.

PowerShell

  • Support in Free Edition. Start-VBRZip cmdlet is now enabled in Veeam Backup™ Free Edition, allowing users to schedule periodic VeeamZIP™ backups using external task schedulers, such as Windows Task Scheduler. This should make Veeam Backup Free Edition a viable alternative to ghettoVCB and other similar script-based free backup solutions.

Integration with Veeam Endpoint Backup FREE

This update enables you to take full advantage of Veeam backup repositories as additional target locations for your Veeam Endpoint Backup jobs, with backups for each endpoint being stored in a separate folder named after the endpoint.

To assign end-user permissions to individual Veeam backup repositories, use the new repository properties dialog that will appear in the repository’s shortcut menu upon first connection attempt from Veeam Endpoint Backup™ FREE to the Veeam Backup & Replication server. Before that, this dialog can be accessed by Ctrl-right-clicking the backup repository.

Global network traffic rules defined in Veeam Backup & Replication apply to endpoint backup jobs using Veeam backup repository as the target, allowing you to ensure that concurrent backups from multiple endpoints do not impact your available bandwidth, or that endpoint backup network traffic is encrypted.

Using a Veeam backup repository as the target for your endpoint backup jobs enables the following additional functionality:

  • Centralized monitoring. Perform basic monitoring and management for all incoming endpoint backup jobs, including email notifications about endpoint backup status.
  • Offsite protection. Get your endpoint backups off site to disk-based storage, tape or your Veeam Cloud Connect service provider with Backup Copy and Backup to Tape jobs.
  • Backup encryption. You can choose to optionally encrypt your endpoint backups stored in Veeam backup repositories. All standard Veeam encryption features are supported for endpoint backups, including password loss protection.
  • Application item-level recovery. Restore application items from backups of server machines with Veeam Explorers™ for Microsoft Active Directory, Exchange, SharePoint and SQL Server.
  • Disk export. Export physical disk content from backup into VMDK/VHD/VHDX virtual disk files

To obtain this update, please click here (you need to be logged in to download the update).

 

 

 


Downloading VMware software with the VMware Software Manager tool

Leave a reply

I was reading the VMware blogs and ran into a very useful blog post. This blogpost was titled: Downloading a VMware Suite with the Push of a Button using VMware Software Manager. That sounds realy interesting, especially now that VMware vSphere 6.0 is available for download.

 

What does the VMware Software Manager do?

  • Provides an easy to use interface to find, select & download the content needed to install or upgrade a VMware suite
  • Verifies the suite or product was downloaded without corruption
  • Automatically detects the release of new VMware suites, products and versions and displays them for download

This sounds very promising. You can download the tool from the VMware Site. It is free to use.
After a very simple installation, the managers starts your internet explorer. You need to login with your My VMware credentials. 


After login with your My VMware credentials, an overview is given with the software where you are entitled to. 


You can than simply select the product or the version. 


Push the download button, and the download starts.. 


The files are placed in the Depot directory that is configured at the setup.
This method safes me a lot of searching and downloading.. VMware states in there blog post that more products will be added.
Conclusion, a very useful tool to keep up with all the VMware Software releases.

Solving the vSphere Web Client cannot connect to the vCenter Single Sign On server error.

5 Replies

After a power failure in my home lab, I tried to login to my vCenter Appliance and get this error “The vSphere Web Client cannot connect to the vCenter Single Sign On Server”.


The solution for this problem is quite simple. For the vCenter Appliance, log in to the Management page of the vCenter Appliance. Stop and Start the vSphere Web Client Services. 


For the Windows based vCenter, restart the vSphere Web Client Services.
After a few minutes everything is ok. Problem Solved.

** Edit 02-03-2016 **

Reboot of the vCenter Appliance should also solve the problem.

VMware vExpert 2015 Announcement

Leave a reply

Yesterday the VMware vExpert for 2015 were announced. And YES I am one of them for the third time.

The complete list of all the vExperts can be found here.

Each of these vExperts have demonstrated significant contributions to the community and a willingness to share their expertise with others.

I would like to thank Corey Romero and the rest of the VMware Social & Community Team for making this possible.
Congratulations to all the other 2015 vExperts.

What’s new in VMware vSphere 6?

2 Replies

Yesterday VMware announced VMware vSphere 6. Here is an overview of the main improvements and new features (over 650 new features and innovations).

Scalability 

  • vSphere Clusters: Up to 64 nodes and 8000 VMs
  • Hosts: 480 physical CPUs, 12 TB RAM, 64 TB datastores, 1000 VMs and 32 serial ports. vGPU Nvidia support
  • VMs: Up to 128 vCPUs and 4 TB vRAM

vCenter Server

  • Platform Services Controller (PSC). The Platform Services Controller (PSC) contains common Infrastructure Services such as:
    • Single Sign-On
    • Licensing
    • Certificate Authority
    • Certificate Store
    • Service (Product) Registration
    • Other future services
    • PSC is a central part that is used for example by vCoud Suite parts such as vCenter, vRealize Operations, etc.). For most environments (8 or less vCenter Servers) a vCenter Server with 1 embedded PSC is sufficient.
  • Enhanced Link Mode (ELM). Enhanced Link Mode (ELM) will support Windows and vCSA deployments and require a Platform Services Controller (PSC).
  •  vCenter Server Appliance (vCSA):
    • ISO file that contains a guided installer
    • Embedded vPostgres database. As external database Oracle is supported.
    • Enhanced Linked mode support
    • VDP support for backup and recovery of the vCSA

 Storage

  • Storage I/O Control (SIOC).  Per VM storage reservation
  • NFS 4.1 with Kerberos support. NFS client support for NFS 4.1
  • Virtual Volumes (VVols) and Storage Policy-Based Management. Enables VM-aware storage. VVOl is offered by storage vendors such as NetApp, Dell, PureStorage, EMC, Nimblestorage, IBM and Tintri
  • Virtual SAN (VSAN) 6 contains the following improvements:
    • Scalability improvements


    • New On-Disk format for higher performance, efficient and scalable high performance snapshots and clones.
    • All flash support
    • Usability improvements in Web Client such as:
      • Storage consumption information
      • Resync status information
    • Failure Domains. Allow grouping of hosts into different logical failure zones. This ensures replicas from a VM are not provisioned onto the same logical failure zone. Failure Domains are no metro/stretched clusters! Failure Domains is also known as rack awareness.
    • Disks serviceability. Map the location of a magnetic or flash device from the Web Client on failures, SSD, local etc.
    • VSAN is sold as separate product and not included in the license

Availability

  • 64 node cluster support and 6000 VMs
  • VMware VM Component Protection (VMCP)
  • vMotion Across vCenter Servers.
  • vMotion across virtual (distributed) switches
    • No need of shared vMotion is needed
  • Long-Distance vMotion up to 100ms RTTs
    • Benefits: Permanent migrations between data centers
    • Disaster avoidance (DA)
    • SRM/DA testing
    • Multi-site load balancing
  • Fault Tolerance (FT) increase support for 1, 2 and 4 vCPU VMs
  • Integration with vCloud Air (replication and backup)
  • vSphere Replication. 5 mins increments (5.5 was 15 minutes) and 2000k replicated VMs per vCenter
  • App HA. Support for more business critical applications

Network

  • Network I/O Control (NIOC). Per VM and Distributed Switch bandwidth reservation

Management

  • vSphere Web Client enhancements such as better performance and tagging improvements.
  • The vSphere Client C# is still available in this release. No new features are in this release. Hardware versions 9 to 11 features are read-only or unavailable in the vSphere Client C#.
  • Multi-Site Content Library. Stores and sync VMs, Templates, OVFs, ISOs and scripts from one central location and sync the content across other vCenter Servers (sites)
  • vSphere 6 has support for Hardware Version 11. Main improvements of Hardware Version 11 are:
    • Maximum video memory up to 2 GB (512 MB in Hardware Version  10)
    • PCI pass-through 16 devices (6 in Hardware Version  10)
    • 32 serial ports (4 in in Hardware Version  10)

When you compare vSphere 5.0, 5.1, 5.5 & 6, vSphere 6 makes a giant leap forward.

Feature

VMware vSphere 5.0

VMware vSphere 5.1

VMware vSphere 5.5

VMware vSphere 6.0
VM HW Version

Virtual Hardware 8

Virtual Hardware 9

Virtual Hardware 10

Virtual Hardware 11
vCPU

32 vCPUs

64 vCPUs

64 vCPUs

128 vCPUs
VM Memory

1 TB

1 TB

1 TB

4 TB
Graphics Support

Software based 3D graphics

Hardware based 3D graphics

Improved 3D graphics Support

WDDM 1.1 GDI graphics acceleration
Cluster Nodes

32 Nodes

32 Nodes

32 Nodes

64 Nodes
Max CPU per Host

160

160

320

480
Max Mem per Host

2 TB

2 TB

4 TB

12 TB
Max vCPU per FT VM

1 vCPU

1 vCPU

1 vCPU

4 vCPU
vCSA with Embedded
Database

5 hosts and 50 VMs

5 hosts and 50 VMs

300 hosts and 1000 VMs

1000 Hosts and 10000 VMs
Content Library

NA

NA

NA

Content Library introduced with
vSphere 6.0
VSAN

NA

NA

VSAN 5.5

VSAN 6.0
vMotion Enhancements

vMotion Supported

vMotion without Shared Storage

vMotion without Shard Storage
Long Distance vMotion (10ms RTTs)

vMotion across vCenters vMotion
across Virtual Switches Long
Distance vMotion (100+ms RTTs)
Virtual Volumes (Vvols)

NA

NA

NA

Available with vSphere 6.0
NFS Support

NFS v3

NFS v3

NFS v3

NFS 4.1 Support Multipathing and
Kerberos Authentication
vCenter Single Sign-on

NA

Introduced with 5.1

SSO with Improved architecture

SSO incudes as part of
Platform Services Controller

 

More information:

Try the new VMware vSphere 6.0 features, go to the VMware Hand on Labs!