Dell Community

Blog Group Posts
Application Performance Monitoring Blog Foglight APM 105
Blueprint for HPC - Blog Blueprint for High Performance Computing 0
Custom Solutions Engineering Blog Custom Solutions Engineering 8
Data Security Data Security 8
Dell Big Data - Blog Dell Big Data 68
Dell Cloud Blog Cloud 42
Dell Cloud OpenStack Solutions - Blog Dell Cloud OpenStack Solutions 0
Dell Lifecycle Controller Integration for SCVMM - Blog Dell Lifecycle Controller Integration for SCVMM 0
Dell Premier - Blog Dell Premier 3
Dell TechCenter TechCenter 1,858
Desktop Authority Desktop Authority 25
Featured Content - Blog Featured Content 0
Foglight for Databases Foglight for Databases 35
Foglight for Virtualization and Storage Management Virtualization Infrastructure Management 256
General HPC High Performance Computing 227
High Performance Computing - Blog High Performance Computing 35
Hotfixes vWorkspace 66
HPC Community Blogs High Performance Computing 27
HPC GPU Computing High Performance Computing 18
HPC Power and Cooling High Performance Computing 4
HPC Storage and File Systems High Performance Computing 21
Information Management Welcome to the Dell Software Information Management blog! Our top experts discuss big data, predictive analytics, database management, data replication, and more. Information Management 229
KACE Blog KACE 143
Life Sciences High Performance Computing 9
On Demand Services Dell On-Demand 3
Open Networking: The Whale that swallowed SDN TechCenter 0
Product Releases vWorkspace 13
Security - Blog Security 3
SharePoint for All SharePoint for All 388
Statistica Statistica 24
Systems Developed by and for Developers Dell Big Data 1
TechCenter News TechCenter Extras 47
The NFV Cloud Community Blog The NFV Cloud Community 0
Thought Leadership Service Provider Solutions 0
vWorkspace - Blog vWorkspace 511
Windows 10 IoT Enterprise (WIE10) - Blog Wyse Thin Clients running Windows 10 IoT Enterprise Windows 10 IoT Enterprise (WIE10) 4
Latest Blog Posts
  • Dell TechCenter

    SPEC Cloud IaaS 2016 performance on Dell PowerEdge servers using VMware’s ESXi 6.5 and VIO 3.1


    Dell with the help of VMware has achieved the top score with SPEC Cloud™ IaaS 2016 Benchmark.

    These results were achieved on FX2s Chassis using Dell PowerEdge FC630 with E5-2698v4 processors running VMware ESXi 6.5 and VMware Integrated OpenStack 3.1, controller by vSphere 6.5.

    This Hardware, Software combo created on a cluster of 8 data nodes were able to create 468 VMs, with a Elasticity score of 87.4 % and a Scalability score of 78.5 @ 72 Applications Instances.

    This results can be viewed on SPEC’s website, at the follow link



    Figure of the Cluster Environment.




    List of Cluster Equipment.



    Figure of the Published OSG Cloud result.



    By replacing the E5-2698v4 processors in the data nodes of the cluster with E5-2699v4, we were able to improve the SPEC Cloud score by 11.7%.

    Achieving a Scalability score of 87.7 @ 80, with an Elasticity score of 88.6%, while creating 520 VMs, without increasing the Provisioning Time of only 25 seconds.

    This 11.7% increase was due to having 2 more cores per processor, for a total of 4 cores per data node and a cluster increase of 24 cores over the previous cluster configuration.



    Figure of the update results with E5-2699v4 processors installed in all the Data Nodes. 



    As seen in the in the chart below there was a 11.1% increase in the amount of VM’s created by the cluster, after installing the E5-2699v4 processors in the data nodes.


    In the Chart below there was an 11.1% increase in the amount Application Instances that the cluster can create.



     There was an 11.7% increase in Scalability and seen in the figure below.

    Scalability is the total amount of measured work done by the application instances that are running in cloud environment in the cluster.



    There was a 1.3% increase in Elasticity. Elasticity is difference between the baseline and the clouds application workload performance.

    Each VM runs a baseline of the an application workload, before entering the cloud environment.

    As seen in the chart below there was a 81.4% decrease in Provisioning Time over  traditional Openstack clusters, when using VMware's VIO Openstack cluster. 

    The R720 and R630 in this chart are using the traditional Openstack software on physical servers.

    SPEC’s Benchmark to measure cloud performance is SPEC Cloud™ IaaS 2016. This benchmark use a suite of tools to measure cloud performance.

    The benchmark sets up VM’s as cloud instances to stress the provisioning of the Cluster and then runs computing workloads on those instances to figure out Scalability and Elasticity of the cluster.

    For more information on SPEC’s Cloud™ IaaS 2016 visit the following website .



    The VMware software used in this cluster is ESXi 6.5, VIO 3.1 and vSphere 6.5. ESXi 6.5 is an embedded hypervisor, which allow the creation of VMs without an underlying OS.

    VIO 3.1 is a VMware product that creates an OpenStack cluster on VMware infrastructure.

    This software combo allows for the creation of an integrate openstack cluster on the Dell PowerEdge servers hardware.

    Once the Cluster is created it can be controlled via VMware’s vSphere software.

    For information on the VMware Software used for this Cluster visit: and



  • vWorkspace - Blog

    What's new for vWorkspace - May 2017

    Updated monthly, this publication provides you with new and recently revised information and is organized in the following categories; Documentation, Notifications, Patches, Product Life Cycle, Release, Knowledge Base Articles.

    Subscribe to the RSS (Use IE only)


    Knowledgebase Articles


     229675 - error: disk deployment blocked due to HyperDeploy

    When re-provisioning computers the following error may be seen: Disk deployment blocked due to HyperDeploy by Host:  Hyper-V server name

    Created: May 23, 2017




    149541 - Redirection not working for Web Access

    When creating a new website, the default.aspx should get edited automatically and a redirector setup to point to the new website, for example...

    Revised: May 1, 2017


    55554 - Cannot load pit file when launching Published application through Web Access

    When browsing to the location identified in the error message, "<path><name>.pit", the file is not present. The PortWise cache cleaner has...

    Revised: May 3, 2017


    73446 - How To: Improve Performance to a Virtual Desktop VDI Session

    When connecting to a VDI over a slow connection users report that the performance on the VDI is degraded, or sessions are disconnected often.

    Revised: May 5, 2017


    227781 - How to set the minimum memory with Hyper-V

    The Hyper-V role in Windows 2012 has an improved Dynamic memory feature that adds a property called Minimum Memory. This allows you to specify a...

    Revised: May 5, 2017


    70481 - HOW TO: Secure Access Certificate Configuration

    Revised: May 11, 2017


    183146 - Smart card logon to Web access

    When using Smartcards to authenticate, by default you still need to type in a Username and Password to log into the Web Access site before you can...

    Revised: May 19, 2017


    182486 - Best practices for User Profile Management (MetaProfiles)

    Most issues with User Profile Management are due to the user&#39;s profile being too large as a result of too much being captured.

    Revised: May 22, 2017


    148502 - Saving Windows Credentials Store with Metaprofiles

    Is it possible to use Metaprofiles (User Profile Management) to save the Windows Credentials Store (for example saved Outlook passwords) so that...

    Revised: May 22, 2017


    147847 - After updating PNTools user is presented with a blank screen on login.

    After updating PNTools user is presented with a blank screen on login. 

    Revised: May 23, 2017


    Product Life Cycle - vWorkspace

    Revised: May 2017

  • Dell TechCenter

    VMware ESXi upgrade fails using VMware Update Manager

    This blog post is written by Sapan Jain and Krishnaprasad K from Dell Operating System team. 

    VMware ESXi versions (Dell customized VMware ESXi 6.0.x) shipped out of Dell factories may expose a failure when users try to upgrade to a higher version using VMware Update Manager (VUM).

    The failure would be seen in "Remediate" step in the upgrade process and error code may be similar to "Cannot execute upgrade script on the host". 

    This issue will not be seen if users have installed ESXi using Dell customized VMware ESXi images downloaded from (OR) VMware ESXi images posted at 

    How do I check the Dell customized version running on my system?

    • Login to vSphere client (HTML client) where you could see a string something similar to “You are running DellEMC Customized Image ESXi 6.0 Update 2 A00”         (OR)
    • Login to VMware ESXi shell console and read the file /etc/vmware/oem.xml


    The problem is caused by having upper case letters for the files residing in ESXi file system. For example, you may see that /altbootbank has files of upper case. 



    There are no workarounds available which can be used to proceed upgrade when this failure is hit. There is no data loss even though the upgrade is failed, you may boot back to the original ESXi configuration prior to upgrade.  The available options to recover from this failure are as follows:-


    1.    Upgrade using Dell iDRAC vMedia/CD Based method.

    2.    Use scripted upgrade using PXE infrastructure.

    This issue is fixed from the following versions of Dell customized VMware ESXi releases. 

  • Dell TechCenter

    Introduction of wbem in VMware ESXi 6.5

    This blog post is written by Elavarasan Selvaraj and Krishnaprasad K from Dell Operating System team. 

    The Common Information Model (CIM) interface on an ESXi host provides a way of remotely monitoring the hardware health of your hosts via the Web-Based Enterprise Management (WBEM) protocol. It builds on a standard HTTP(S) API, allowing secure SSL/TLS protected authentication and communication between the host and the management stations. From ESXi 6.5 onwards, VMware introduced a new namespace named as ‘wbem’ as an extension for esxcli which controls the services such as sfcbd and wsman. From ESXi 6.5 onwards, sfcdb and wsman are disabled by default as wbem is kept to false by default.

    The wbem services gets enabled automatically when an OEM provider VIB is installed.  For example when Dell OpenManage systems management software is installed on ESXi 6.5, you may see that the services such as sfcbd and wsman are started automatically. This blog detail on the options wbem provides which can help understand and troubleshooting CIM related issues. 

    Wbem Service command details

    This section summarizes some of the options provided by wbem which would be helpful for users relying on CIM systems management stack with in ESXi to monitor/manage their systems. 

    Below is what you see on a newly installed ESXi 6.5 in terms of the service status. 

    ~] esxcli system wbem get

       Authorization Model: password

       Enabled: false

       Loglevel: warning

       Port: 5989

       WSManagement Service: true

    You may see that the service is disabled by default. This also mean that sfcbd and wsman services are turned off by default.

    ~] /etc/init.d/sfcbd-watchdog status

    sfcbd is not running

    ~] /etc/init.d/wsman status

    openwsmand is not running

    After enabling wbem, you may observe that sfcbd and wsman are turned on.

    ~] esxcli system wbem set -e 1


    ~] /etc/init.d/sfcbd-watchdog status

    sfcbd is running


    ~] /etc/init.d/wsman status

    openwsmand is running


    Now, let's look into some of the options provided by wbem. Below is the help menu which detail various command parameters. 

     ~] esxcli system wbem set --help

    Usage: esxcli system wbem set [cmd options]


      set                   This command allows the user to set up ESX CIMOM agent.

     Cmd options:

      -a|--auth=<str>       Specify how to authorize incoming requests. Values are password, certificate, password is by default. Changes take effect when --enable is


      -e|--enable           Start or stop the WBEM services (sfcbd, openwsmand). Values: [yes|no, true|false, 0|1]

      -l|--loglevel=<str>   Syslog logging level: debug|info|warning|error

      -p|--port=<long>      Set the TCP port on which the CIMOM listens for requests. The default is 5989

      -r|--reset            Restore the WBEM configuration to factory defaults

      -W|--ws-man           Enable or disable the WS-Management service (openwsmand). Enabled by default. Changes take effect when --enable is specified.


    ~] esxcli system wbem -h

    Usage: esxcli system wbem {cmd} [cmd options]

    Available Namespaces:

    Available Commands:
    get Display WBEM Agent configuration.
    set This command allows the user to set up ESX CIMOM agent.

    There is an extension available for wbem (named as provider) as well which is useful to understand the providers that are registered to sfcbd and enabled. Below is a sample command output taken from an ESXi 6.5 host with default providers. When Dell OpenManage is installed, you may see an additional entry named as 'OpenManage' to the below. 

    ~] esxcli system wbem provider list

    Name Enabled Loaded
    ---------------- ------- ------
    sfcb_base true true
    vmw_base true true
    vmw_hdr true true
    vmw_hhrcwrapper true true
    vmw_iodmProvider true true
    vmw_kmodule true true
    vmw_omc true true
    vmw_pci true true
    vmw_vi true true

    The below command provides an option to enable/disable individual providers registered to sfcb. 

    ~] esxcli system wbem provider set <-e | --enable> <yes|no, true | false, 0|1>

    Few other useful commands related to wbem are the following. 

    ~] esxcli system wbem set -a | --auth=<str>

    The authentication method defines how the incoming requests are authenticated from the external HTTPs APIs. Password and certificate are the two options available. 

    ~] esxcli system wbem set -e | --enable true|false     (sfcbd, openwsmand)

    ~] esxcli system wbem set -W | --ws-man true|false (openwsmand)

    This allows the administrator to enable/disable wsman service specifically. 

    ~] esxcli system wbem set -l | --log-level=<str> debug|info|warning| error

     This is an important parameter available for wbem. This is a useful option for troubleshooting CIM issues.

               ~] esxcli system wbem set -p | --pot=<long>  

    Setting the TCP port for CIMOM communication listens the request from outside HTTPs API. By default it's set to 5989. You may use this parameter only if there is a requirement to change the default port used. 

    ~] esxcli system wbem set -r | --reset

    This command resets the wbem configuration to the default.  

    Dell systems management support for ESXi 6.5

                    DellEMC provides an inband management tool known as OpenManage in which it provides two specific solutions named as Server Administrator (OMSA) and iDRAC Service Module(iSM). Dell released an OMSA version of 8.5 supported for ESXi 6.5 which is a test and document supported version. The iSM version is yet to be out for ESXi 6.5.