R730 SSD Drives for VMware VSAN 7.0

This post was originally published on this site

R730 SSD Drives for VMware VSAN 7.0



Hi All.

I am hoping someone can assist me.

We are going to build a new All Flash VSAN 7.0 setup with following specs.

Hardware model R730 PowerEdge.

DELL HBA 330 controller.

I have a doubt on disk selection.

8 drives in total(total drives we are going to use on R730).

I wish to use 1 TB SSD SAS drives for cache tier and 2 TB SSD SAS drives for capacity tier. The most economical SSD drives that are fully supported from both VSAN and DELL.

I’m not sure what SSD drives(with SAS protocol) are compatible with my R730 servers and also it should be on the vSAN HCL (which is crucial)

The VMware HCL does not mention the Dell part numbers so matching them is proving very difficult. My supplier is sending me pricing for drives that differ hugely but still hasn’t confirmed support on both platforms.

Please can someone help me identify which 1 TB SSD SAS drives for cache tier and 2 TB SSD SAS drives for capacity tier so that I can double check and use in R730 servers. Whatever we choose, that also should be listed on the VMware vSAN Hardware Compatibility list,

https://www.vmware.com/resources/compatibility/pdf/vi_vsan_guide.pdf    dell disk starts from page 237.



Manivel RR


WebEx Meetings and Productivity Tools Settings

This post was originally published on this site

I searched and do not find where anyone was successful with this. I am in the middle of trying to capture the WebEx Meetings App without the productivity tools to see if it is just the productivity tools that cause the problem.




I have looked at existing configs people have posted. I have used the profiler, I have stared at procmon until my head hurts on multiple days. I do not see any access denied or any issue that points to something not working but on every restart, the user has to login to WebEx.


Does anyone have it successfully working in their environment?


Here is my current non working config I borrowed from this elsewhere in the forum:




HKCUSoftwareCisco Systems, Inc.Cisco Webex Meetings Virtual Desktop



HKCUSoftwareCisco Systems, Inc.Cisco Webex Meetings



















































<LocalAppData>CiscoUnified CommunicationsWebexMeetingsCSFLogs

Microsoft Teams installed in an App Package on AppVolumes 4.1 (2006)

This post was originally published on this site

We’ve successfully been using MS Teams on an appstack with 2.18.x without too many issues, but we are running into weird issues with the same setup using AppVolumes 4.x.


We have the Teams installer stored with our Office365 package and everything related to office365 seem to work, but Teams doesn’t load.   It seems to missing the c:programdata%username% folder where Teams is installed from.


IF we chose to install it with the ALLUSER=1 ALLUSERS=1 switches, it seems to want to validate the Horizon or Citrix Agents are also installed.  Our app stack builders historically do not have the horizon agents installed.  I’m willing to try this, but do not know if there are adverse affects with the agent installed when we build the packages.



Does anyone have any concrete ways to install Teams successfully with appvolumes?

We do have a use case where we do _not_ want it on the golden image because we have exempt staff that do not use Teams or an Office365 license.

Adding a choice before component selection

This post was originally published on this site

Hello support.


I’m wondering if there is a way to have a drop down choice that gets after the license agreement and selecting the install directory but before component selection?  trying to control which components are visible based on a choice before the selection, but can’t find away to add a choice before component selection.


My plan B is to put both options in the component selection as components and use a non visible component with rules to allow only one of the option components to be selected, but this seems clunky compared to just asking the user to make a choice before selecting components.

PowerCLI and Powershell Windows 7.0.3: Exception: VMware.VimAutomation.HorizonView module is not currently supported on the Core edition of PowerShell

This post was originally published on this site

When I do an Import-Module VMware.PowerCLI I receive the following error:


Import-Module Vmware.PowerCLI

Exception: VMware.VimAutomation.HorizonView module is not currently supported on the Core edition of PowerShell.


PS 7.0.3 version:

PS C:> $psversiontable

Name                           Value
—-                           —–
PSVersion                      7.0.3
PSEdition                      Core
GitCommitId                    7.0.3
OS                             Microsoft Windows 10.0.14393
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
WSManStackVersion              3.0


PS C:> Get-Module -ListAvailable  -Name *Vmware* | FT -AutoSize

    Directory: C:UserslocalscriptuserDocumentsPowerShellModules

ModuleType Version         PreRelease Name                                    PSEdition ExportedCommands
———- ——-         ———- —-                                    ——— —————-
Script            VMware.CloudServices                    Desk      {Connect-Vcs, Get-VcsOrganizationRole, Get-VcsService, Get-VcsServiceRole…}
Script             VMware.DeployAutomation                 Desk      {Add-DeployRule, Add-ProxyServer, Add-ScriptBundle, Copy-DeployRule…}
Script             VMware.ImageBuilder                     Desk      {Add-EsxSoftwareDepot, Add-EsxSoftwarePackage, Compare-EsxImageProfile, Export-EsxImageProfile…}
Manifest            VMware.PowerCLI                         Desk
Script             VMware.Vim                              Desk
Script            VMware.VimAutomation.Cis.Core           Desk      {Connect-CisServer, Disconnect-CisServer, Get-CisService}
Script            VMware.VimAutomation.Cloud              Desk      {Add-CIDatastore, Connect-CIServer, Disconnect-CIServer, Get-Catalog…}
Script            VMware.VimAutomation.Common             Desk      {Get-Task, New-OAuthSecurityContext, Stop-Task, Wait-Task}
Script            VMware.VimAutomation.Core               Desk      {Add-PassthroughDevice, Add-VirtualSwitchPhysicalNetworkAdapter, Add-VMHost, Add-VMHostNtpServer…}
Script            VMware.VimAutomation.Hcx                Desk      {Connect-HCXServer, Disconnect-HCXServer, Get-HCXAppliance, Get-HCXComputeProfile…}
Script            VMware.VimAutomation.HorizonView        Desk      {Connect-HVServer, Disconnect-HVServer}
Script            VMware.VimAutomation.License            Desk      Get-LicenseDataManager
Script            VMware.VimAutomation.Nsxt               Desk      {Connect-NsxtServer, Disconnect-NsxtServer, Get-NsxtPolicyService, Get-NsxtService}
Script            VMware.VimAutomation.Sdk                Desk      {Get-ErrorReport, Get-PSVersion, Get-InstallPath}
Script            VMware.VimAutomation.Security           Desk      {Add-AttestationServiceInfo, Add-KeyProviderServiceInfo, Add-TrustAuthorityKeyProviderServer, Add-TrustAuthorityKeyProviderServerCertificate…}
Script            VMware.VimAutomation.Srm                Desk      {Connect-SrmServer, Disconnect-SrmServer}
Script            VMware.VimAutomation.Storage            Desk      {Add-EntityDefaultKeyProvider, Add-KeyManagementServer, Add-VsanFileServiceOvf, Add-VsanObjectToRepairQueue…}
Script                    VMware.VimAutomation.StorageUtility     Desk      Update-VmfsDatastore
Script            VMware.VimAutomation.Vds                Desk      {Add-VDSwitchPhysicalNetworkAdapter, Add-VDSwitchVMHost, Export-VDPortGroup, Export-VDSwitch…}
Script            VMware.VimAutomation.Vmc                Desk      {Add-VmcSddcHost, Connect-Vmc, Disconnect-Vmc, Get-AwsAccount…}
Script            VMware.VimAutomation.vROps              Desk      {Connect-OMServer, Disconnect-OMServer, Get-OMAlert, Get-OMAlertDefinition…}
Script            VMware.VimAutomation.WorkloadManagement Desk      {Get-WMNamespace, Get-WMNamespacePermission, Get-WMNamespaceStoragePolicy, New-WMNamespace…}
Script              VMware.VumAutomation                    Desk      {Add-EntityBaseline, Copy-Patch, Get-Baseline, Get-Compliance…}

Issue with installing Windows Server 2019 on ESXi 6.0.0

This post was originally published on this site

Now that I’ve got my additional space in ESXi, I am trying to install Windows Server 2019, but I can’t get vsphere client to boot to my Server 2019 ISO. Just for troubleshooting, I setup a new VM, attached Windows Server 2012 ISO and booted right up.  I looked up requirements and 2019 is supported with ESXi 6.0.  The 2019 ISO is valid, since I’ve used it with Hyper-V.


I can only go up to Windows Server 2012 when selecting a version.  Any ideas why I can’t boot to Server 2019?

SecretManagement and SecretStore Updates

This post was originally published on this site

Two updated preview releases are now available on the PowerShell Gallery:

Please note that these preview releases contain breaking changes. This version of SecretStore is incompatible with previous versions because the configuration format has changed. The previous file store cannot be read by the new version and you will need to reset the store Reset-SecretStore after installing the new version. Be sure to save your current stored secrets before upgrading so they can be re-added after you Reset your SecretStore.

To install these updates run the following commands:

Install-Module SecretManagement -Force -AllowPrerelease 
Install-Module SecretStore -Force -AllowPrerelease 

SecretManagement Preview 4 Updates

This update to SecretManagement addresses a bug blocking vault registration on Windows PowerShell, adds additional pipeline support, and makes several changes to improve the vault developer experience. Read the full list of changes below:

  • Fixes issue with registering extension vaults on Windows PowerShell (Error: Cannot bind argument to parameter ‘Path’ …)
  • Changes SecretVaultInfo VaultName property to Name, for consistency
  • Changes Test-SecretVault -Vault parameter changed to -Name for consistency
  • Adds -AllowClobber parameter switch to Register-SecretVault, to allow overwriting existing vault
  • Register-SecretVault uses module name as the friendly name if the -Name parameter is not used
  • Unregister-SecretVault now supports Name parameter argument from pipeline
  • Set-DefaultVault now supports Name and SecretVaultVaultInfo parameter arguments from pipeline
  • Set-Secret now supports SecretInfo objects from the pipeline
  • Adds -WhatIf support to Secret-Secret
  • Adds -WhatIf support to Remove-Secret

SecretStore Preview 2 Updates

This update to SecretStore includes updates to the cmdlet interface based on user feedback and desire to conform to PowerShell best practices. This update also updates error messaging to provide a clarified user experience. Read the full list of changes below:

  • Set-SecretStoreConfiguration now supports -Authentication and -Interaction parameters instead of -PasswordRequired and -DoNotPrompt switches
  • Update-SecretStorePassword has been renamed to Set-SecretStorePassword
  • Unlock-SecretStore no longer supports plain text passwords
  • Set-SecretStoreConfiguration now throws an error if called with no parameters
  • Added ProjectUri and “SecretManagement” tag to manifest file
  • Reset-SecretStore now defaults to ‘No’ when prompting to continue.

Tagging your extension vault on the PowerShell Gallery

If you are publishing an extension vault to the PowerShell Gallery we ask that you add the tag “SecretManagement” to the module manifest. This will the vault to be more discoverable for SecretManagement users.

Feedback and Support

As we approach General Availability for these modules now is the time to test the modules against your scenarios to request changes (especially breaking ones) and discover bugs. To file issues or get support for the SecretManagement interface or vault development experience please use the SecretManagement repository. For issues which pertain specifically to the SecretStore and its cmdlet interface please use the SecretStore repository.

Sydney Smith

PowerShell Team


The post SecretManagement and SecretStore Updates appeared first on PowerShell.

KB article to create custom alerting is not working for me

This post was originally published on this site

Hi team,


Hoping to see if you can pin point the root cause of this 400 error pasted below. I am trying to create a new email template and I get 400 error.


VMware Knowledge Base


Executed step 3 from KB article by replacing IP address of the master node.


]# curl -k -X POST -i -H “X-vRealizeOps-API-use-unsupported: true” -H “Content-Type: application/json; charset=UTF-8” -u admin -d ‘{
“id” : null,
“name” : “Email Template 1”,
“html” : true,
“template” : “$$Subject=[Email Template 1 Subject] State:{{AlertCriticality}}, Name:{{AffectedResourceName}} nn New alert was generated at: {{AlertGenerateTime}} Info: {{AffectedResourceName}} {{AffectedResourceKind}}
Alert Definition Name: {{AlertDefinitionName}}
Alert Definition Description: {{AlertDefinitionDesc}}
Object Name : {{AffectedResourceName}}
Object Type : {{AffectedResourceKind}}
Alert Impact: {{AlertImpact}}
Alert State : {{AlertCriticality}}
Alert Type : {{AlertType}}
Alert Sub-Type : {{AlertSubType}}
Object Health State: {{ResourceHealthState}}
Object Risk State: {{ResourceRiskState}}
Object Efficiency State: {{ResourceEfficiencyState}}
{{Anomalies}} Recommendations: {{AlertRecommendation}} vROps Server – {{vcopsServerName}} Alert details
“others” : [ ],
“otherAttributes” : {}
Enter host password for user ‘admin’:
HTTP/1.1 400 400
Date: Wed, 30 Sep 2020 19:01:08 GMT
Server: Apache
X-Request-ID: 4hh8Gupwd06DRmHiPoyKGdqIXSDJic1s
Access-Control-Allow-Origin: *
Cache-Control: no-cache, no-store, max-age=0, must-revalidate
Pragma: no-cache
Expires: 0
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-XSS-Protection: 1; mode=block
X-Frame-Options: SAMEORIGIN
X-Content-Type-Options: nosniff
Content-Security-Policy: default-src https: data: ‘unsafe-inline’ ‘unsafe-eval’; child-src *
Vary: User-Agent
Connection: close
Transfer-Encoding: chunked
Content-Type: application/xml

<?xml version=”1.0″ encoding=”UTF-8″ standalone=”yes”?><ops:error xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance” xmlns:xs=”http://www.w3.org/2001/XMLSchema” xmlns:ops=”http://webservice.vmware.com/vRealizeOpsMgr/1.0/ httpStatusCode=”400″ apiErrorCode=”400″><ops:message>Invalid input format.</ops:message><ops:moreInformation><ops:info name=”api-uri”>/suite-api/api/notifications/email/templates</ops:info></ops:moreInformation></ops:error>





RDM Peer Persistence disk disconnect issues

This post was originally published on this site

We have a pair of Server 2016 servers VMs configured as a failover cluster with RDMs presented from our 3PAR-9450.  When we failover the RDM to our other 3PAR the disks on the VMs disconnect and we can’t get the disks to come back on line.


This is an error we see in the cluster logs.

Cluster resource ‘Cluster Disk 1’ of type ‘Physical Disk’ in clustered role ‘<REDACTED>’ failed. The error code was ‘0x80070490’ (‘Element not found.’).
Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it.  Check the resource and group state using Failover Cluster Manager or the Get-ClusterResource Windows PowerShell cmdlet.


We have to shutdown both VMs and cold boot one VM.  Once it brings the disk online we can start the second VM.  Any thoughts on what is causing our problem? 



Fusion 8.5.10 hijacks route to 192.168.2.x

This post was originally published on this site

Running Fusion 8.5.10 on macOS 10.14.6.


I have 3 sites; let’s call them Office (, Home1 (, and Home2 ( They are fully meshed via pfsense 2.4.4/IPSec hardware tunnels connecting:





I’m at Home1, and my Mac can’t see through the tunnel to Home2 whenever I have Fusion running with networking.


Here’s my Mac’s route through the working tunnel to Office:


route get

   route to: <hostname>

destination: default

       mask: default


  interface: en0


recvpipe  sendpipe  ssthresh  rtt,msec    rttvar  hopcount      mtu     expire

       0         0         0         0         0         0      1500         0


Here’s my Mac’s to Home2 when Fusion is running with a network adapter installed:


route get

   route to:



  interface: vmnet1

      flags: <UP,DONE,CLONING>

recvpipe  sendpipe  ssthresh  rtt,msec    rttvar  hopcount      mtu     expire

       0         0         0         0         0         0      1500   -205028


and my Mac can no longer access any resources at 192.168.2.x. Curiously, the Win7 VM in Fusion can get to resources at 192.168.2.x just fine.


My VM is configured with Bridged networking, so it gets a 192.168.1.x address from my DHCP server, so I don’t know why it’s messing with 192.168.2.x. But even if I change the networking type to NAT, it doesn’t fix the problem of my Mac getting to 192.168.2.x.


If I remove the network adapter from the VM _or_ if I shut off Fusion, then my Mac sees:


route get

   route to:

destination: default

       mask: default


  interface: en0


recvpipe  sendpipe  ssthresh  rtt,msec    rttvar  hopcount      mtu     expire

       0         0         0         0         0         0      1500         0


and then my Mac has the expected access to everything in 192.168.2.x.


How do I change the configuration of this VM so that it has networking but doesn’t hijack the route to 192.168.2.x? I don’t see any reference to that in the .vmx file (attached).