I have run into the below error in both my lab and production environments when running the assessment tool. It's not clear what is failing on the checks. I did open a support case this morning but wanted to also post here...

Hi,

I have created a linked clone desktop pool and specified a disposable disk of 5G to relocate the windows page file. In the master image (Windows Server 2019 LTSC) I set the pagefile with min 2G and max 4G)

After recompose, the desktops have the correct pagefile settings but on the C-drive instead of the disposable disk.

Any idea where to look (logs) to find out why it doesn't use the disposable disk?

Is it even necessary to have the disposable disk, because it's a non-persistent desktop pool which is refreshed at logoff (we're using FSLogix profile containers for user settings)?

Thanks,

Michiel.

Version info: Horizon 7.9, Master image: W2019 LTSC (version 1809), FSLogix 2.9.7205.27375

Hi all,

I'm seeing very poor SSD performance on my Windows 10 guests (not that I've benchmarked any other guest OS's) running on Windows 10 hosts.

This is happening on both my Desktop workstation and my laptop.

I'll give more details of the laptop scenario.

Host: Dell XPS15 9560 with a 512GB SSD and 16GB RAM, running Windows 10 1803.

Guest: VMWare workstation hardware compatibility 14, 4GB Memory allocated, 1 processor, 4 cores, VT-x/EPT enabled. Running Windows 10 1803.

No snapshots, all disks compacted/defraged.

As detailed below, performance is pretty dire - especially when you look at the non-sequential tests. Performance is a factor of 4-7 times slower than on the host. I've been using Workstation for years and expect some performance drop within a guest, but not on this scale. It is bad enough that it seriously impacts Windows performance and usage.

I've tried experimenting with different disk types (NVMe/SCSI, pre-allocation/lazy provisioned) - none make a significant difference.

The performance is similar with antivirus disabled on both host and guest (Windows Defender on both)

Does anyone have any ideas for resolving this, or investigating the cause? Might this be a performance bug in Workstation itself?

All help gratefully received.

Host disk performance is good:

Guest performance is poor:

12GB SCSI, pre-allocated, single file:

14GB NVMe, pre-allocated, single file:

Hello all,

On fresh installation I'm trying to create datastore on bellow drive and after selection of free space on left first thing I do not understand, why there is any VMFS partition (on right) when on before (on left) there is none and it even has almost same size as "Free Space" on left

When I try to create partition like this with any size like for examle 40GB pm mext screen it looks like this and instead of VMFS it will mark it as basic data:

After click of finish it will write following error:

Here is dump of vmkernel.log:

2019-12-02T14:25:13.512Z cpu4:2097662)NMP: nmp_ThrottleLogForDevice:3781: Cmd 0x85 (0x459a40d7cf00, 2099236) to dev "t10.NVMe____INTEL_SSDPE2MX012T7_CVPF636600QS1P2NGN__00000001" on path "vmhba2:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 $

2019-12-02T14:25:13.512Z cpu4:2097662)ScsiDeviceIO: 3082: Cmd(0x459a40d7cf00) 0x85, CmdSN 0x20 from world 2099236 to dev "t10.NVMe____INTEL_SSDPE2MX012T7_CVPF636600QS1P2NGN__00000001" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x0 0x0.

2019-12-02T14:25:13.515Z cpu2:2097667)NMP: nmp_ThrottleLogForDevice:3781: Cmd 0x85 (0x459a40d7cf00, 2099236) to dev "t10.NVMe____INTEL_SSDPE2MX012T7_CVPF637100SY1P2NGN__00000001" on path "vmhba3:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 $

2019-12-02T14:25:13.515Z cpu2:2097667)ScsiDeviceIO: 3082: Cmd(0x459a40d7cf00) 0x85, CmdSN 0x28 from world 2099236 to dev "t10.NVMe____INTEL_SSDPE2MX012T7_CVPF637100SY1P2NGN__00000001" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x0 0x0.

Here is also my setup as it is showed on main screen of WebGUI:

Can you please help me with it? I tried to google it but common guides like change of MTU and simillar didn't helped me. Also tried to reinstall it several times but issue is still there.

My old vCenter crashed and I'm trying to add custom certificates on the new one however when I complete the CSR generation on the web UI there are just two options, copy and download.

Copy does what it says, copies the CSR to the clipboard and download downloads it, just the CSR, no private key. The CSR, naturally, is enough to get the signed certificate but at import time I have no private key to match and thus it won't accept the certificate.

How can I get a hold of the private key? Why after so many iterations can't VMware get it right--I mean, vCenter is really expensive, you sort of expect it to be flawless. What's the point of the web UI if you still have to hunt down files in the CLI. I tried using this wildcard certificate I'm using in several places but it won't accept it, I assume it's because it doesn't explicitly has the hostname.

I looked it up (the private key) on /usr/lib/vmware-vmca/bin already expecting it not to be there, and surely it wasn't. I went to /tmp and looked up anything with today's timestamp (/tmp/jna-root) but it was empty. The rest on /tmp are .part files.

Anyway, I appreciate your help on this -- and thanks !

I'm thinking of purchasing VM 11.5 to run on my Mac Book Pro with OS High Sierra- don't plan to do the Catalina upgrade.  I want to be able to run Storyline 2 ... am familiar with parallels but last I used it on a Mac it was super clunky and created a lot of drag.  I'd be interested in others experiences..  I've read it works great for some on Mac if using VM Fusion ...   would like to hear experience from the trenches before taking the plunge.. thank you in advance!!

We’re excited to announce a new VMware Skyline release that includes several new features designed to provide even more value to you and your organization. Be sure to update your Skyline Collectors to the latest version (2.3) to take advantage of the new features and functionality. If you have the “Auto Update” feature enabled, your Collectors will update approximately within the next seven days.

New features in this release include:

Enhanced Security Policies: As of November 19^th, Skyline has enhanced security policies and now Skyline Advisor explicit grant access is required. Your Skyline Admin must grant users access permissions to ensure no interruption to their service. To do this, Admins (organization owners) must log into their VMware Cloud Services Platform (CSP) organizations and use the identity and access management feature to assign access permissions to each user they wish to use to Skyline. This will enable users to access the Skyline Findings and Recommendations as well as other features including Log Assist for automatic support log bundle upload. Please refer to the Skyline Advisor Security Enhancement KB article for additional information.

If you need assistance, you can visit the Skyline documentation center or the Skyline Community, which is monitored by expert Skyline engineers.

VMware Skyline Integration with Dell EMC SupportAssist: Thousands of VMware customers leverage Dell EMC SupportAssist to proactively support Dell hardware. SupportAssist Enterprise (SAE) is Dell’s proactive support technology for hardware that is included with their support plans. Skyline and SAE have joined forces, enabling a best-in-class proactive support experience for customers running Dell and VMware. Skyline now integrates with SAE to help customers proactively optimize joint solutions. VMware and Dell PowerEdge 12G+ server customers will see an alert in SAE that provides information about Skyline, with a call to action to download and install Skyline. Similarly, Skyline users will see an alert in Skyline Advisor that provides information about SAE, with a call to action to download and install SAE. This announcement is the first step toward tighter integration between Skyline and SAE. In addition to Skyline Collector 2.3, Dell EMC SupportAssist Enterprise v.4.0.5 is required. Visit the Dell Technologies SupportAssisthttps://www.dell.com/support/driver/us/en/04/sae-ve-download/supportassist-enterprise-v4.0page for more details.

New Proactive Findings: This release includes ten new proactive Findings for vSphere, further expanding Skyline’s ability to alert you to potential issues in your environment.

Log Assist for Horizon Connection Server: We've just made it easier for you to upload a support log bundle for Horizon Connection Servers. Within Skyline Advisor, you can use Skyline Log Assist to initiate a log bundle for a Horizon Connection Server within your environment. To enable this functionality, you need to update your Skyline Collector to version 2.3, as well as update Horizon 7 Connection Server(s) to version 7.10. Please see the Horizon 7 version 7.10 Release Notes for more details.

Collector Health in Skyline Advisor:  The Collector health status is now included on the Collector Details page accessible from the Advisor Dashboard. For additional information, please visit the Troubleshooting an Unhealthy Skyline Collector KB article.

Skyline Advisor Federated Identity Management: Advisor now supports federated identity management. You can use your corporate domain account to access Skyline Advisor within VMware Cloud Services. To set up federated identity management, please see the Setting Up Federated Identity Management documentation. After completing the setup of federated identity management, ensure to add applicable Skyline service roles to each corporate domain user. These roles include Skyline Advisor and Skyline Collector.

Skyline Collector Improved Active Directory Authentication: Before this release, anonymous bind was required to enable Active Directory authentication. Now, anonymous bind is no longer required, and an Account Username and Password is now utilized to validate the Skyline Collector to Active Directory.

For more information on the new features above see our Skyline blog post, Advisor and Collector release notes.

Thank you for your continued use of Skyline proactive support!

Hello,

We released Skyline Collector version(v)2.3 on Tuesday, November 26th. We have discovered a bug within Skyline Collector v2.3 that could result in lost networking configuration after upgrading and restarting the Skyline Collector virtual appliance. After upgrading to Skyline Collector v2.3, when using a static IP configuration, the network configuration will be lost, and viewing the console window of the Skyline Collector virtual appliance will display the following:

NOTIFICATION:

Red Banner: No Networking Detected. Please login and run the command /opt/vmware/share/vami/vami_config_net to Reconfigure the Network

Resolution:

Follow these steps to reconfigure a static IP address for the Skyline Collector virtual appliance:

1. Open the console of the Skyline Collector virtual appliance VM.
2. Log in to the Skyline Collector virtual appliance with account 'root'.
3. Run '/opt/vmware/share/vami/vami_config_net.
4. Use this program to reconfigure a Static IP configuration.
5. After reconfiguring the network, run the command 'restart -f' to restart the Skyline Collector virtual appliance.

I've included a GIF of what steps 1-3 look like within the Skyline Collector virtual appliance console. You can see the networking options presented (Step 4) after running the command in Step 3.

If you have trouble completing any of the above steps, please start a discussion in the Skyline Community. If you have misplaced, or forgotten, the root account 'password', follow these instructions to reset the root password.

Hello,

We released Skyline Collector version(v)2.3 on Tuesday, November 26th. We have discovered a bug within Skyline Collector v2.3 that could result in lost networking configuration after upgrading and restarting the Skyline Collector virtual appliance. After upgrading to Skyline Collector v2.3, when using a static IP configuration, the network configuration will be lost, and viewing the console window of the Skyline Collector virtual appliance will display the following:

NOTIFICATION:

Red Banner: No Networking Detected. Please login and run the command /opt/vmware/share/vami/vami_config_net to Reconfigure the Network

Resolution:

Follow these steps to reconfigure a static IP address for the Skyline Collector virtual appliance:

1. Open the console of the Skyline Collector virtual appliance VM.
2. Log in to the Skyline Collector virtual appliance with account 'root'.
3. Run '/opt/vmware/share/vami/vami_config_net.
4. Use this program to reconfigure a Static IP configuration.
5. After reconfiguring the network, run the command 'restart -f' to restart the Skyline Collector virtual appliance.

I've included a GIF of what steps 1-3 look like within the Skyline Collector virtual appliance console. You can see the networking options presented (Step 4) after running the command in Step 3.

If you have trouble completing any of the above steps, please start a discussion in the Skyline Community. If you have misplaced, or forgotten, the root account 'password', follow these instructions to reset the root password.

This document was generated from the following discussion: Skyline Collector 2.3 Auto Upgrade Bug

Have a strange issue. We have DLR with multiple networks attached to it that has decided to stop forwarding traffic.

All of the configured networks can ping the DLR.

If you run a trace to something like 8.8.8.8 the DLR responds destination unreachable.

From DLR, we can ping the next hop ESG.

"show ip route" reports all of the expected routes.

Now for the really strange part, any VMs on the same host as the DLR will work as expected and traverse the network.

VMs on other hosts can only ping the internal interface of the DLR.

Hola amigos,

Tengo un problema en produccion a ver si me pueden ayudar, tengo 1 vcenter que tiene 2 maquinas fisicas y n maquinas virtuales, de un momento al otro se desfazo la hora y justo veia las maquinas virtuales apagadas pero en el host seguian ejecutando. luego de arreglar lo de la hora veo las maquinas pero lo veo con una advertencia amarilla donde me dice que las estadisticas rapidas en el host  xxxx no estan actualizadas.

Saludos

Hi All,

in vRealize Operation Manager 7.5 when you create a custom group and hit the "Keep group membership up to date" a warning sign apper.

This warning message notice to you the refresh interval is 20 minutes.

In the earlier versions it was 5 minutes.

I would like to ask, how can I change this 20 minutes to 5 minutes.

Thank you for your help!

Hi,

I am looking to collect the Model Number, S/N, Type etc of the local hard disk on HP Proliant servers using powercli. Esxi 6.x are running on these servers.

Pls help.

ESXi 6.7.0 Build 13981272

On the web client, when I click the Updates tab on one of the hosts, or the cluster, the expected behavior is present.  However, when I highlight a VM and click the Updates tab, I get "An unexpected error has occurred".  This happens on every VM when it is selected.  I can scan/remediate from the host or the cluster level, I just cannot do so from the VM level.  Any ideas?

I've attached a screenshot of the updates tab from both the host, and the VM to illustrate the issue I am having. 

I am running Workstation Player 12.5 on a Windows 7 system.

When I start my Windows 7 VM, the list of devices in the frame show the keyboard card reader with a card in it and the card reader on the laptop itself.

However, the OS in the VM doesn't see the card readers at all. I get no other error messages, and I could find nothing in the log to shed any light on this.

This VM is a clone of one that works or worked fine on at least two other host machines. That leads me to suspect some sort of local policy issues, but I'm no expert on that, either.

Can anyone point me in useful directions?

yours,

Michael

Hi All,

I have a 6 node VSAN cluster.During maintenance,I have taken only one ESXi host reboot(before that,I enabled the ESXi host in to maintenance with the below command line).

esxcli system maintenanceMode set -e true -m ensureObjectAccessibility

Now Im seeing "Host maintenance mode warning" alert and when we try to put the ESXi host in to maintenance again via vCenter server,Im seeing VSAN data migration option as "cannot be completed.Taken esxi reboot as well but no luck.

rest all other 5 nodes are running good.

What actions we need to take to fix this warning issue ?

I've been using VMware for the last 8 years on my mac with absolutely no issues. Today I started one of my VM (Debian 8) and after the guest started and ran for 5mn I got a "VMWare Fusion has encountered an error and has shut down the virtual machine." error without much more details.

I was running on VMware Fusion 10.1.16 and Mojave 10.14.6. I then tried other Linux VMs and they all had the same issue after few minutes of operation. I tried Windows VMs with similar results.

I decided to purchase an upgrade to VMware Fusion 11.5.1 and I got exactly the same problem.

I've tried to disable/enable "Accelerate 3D Graphics", Intel VT-x/EPT. I've tried several Hardware Versions (from 6 to 16), without any success.

I do not know what changed on my computer since last time VMware was running flawlessly; maybe an update from 10.14.5 to 10.14.6?

I have generated some VMware Fusion Problem Reports but I don't know where to look to see what is causing this error/shut down?

Hello,

In vRO 8.0 how can I register a new plugin (IBM spectrum connect plugin) ?

Thank you

Dominic

I need some help validating this Network config for a stretched cluster.

Ill summarize whats on the attached, not so good, diagram.

- cluster is running 6.7u1

- Each data site has Nexus vpc Pairs as cores.

- L2 between data site. the vsan vlan has an EIGRP advertised SVI which is part of an HSRP group with 4 members (1 SVI per nexus, so 2 per site) (this is one of the key things i want to validate) 

- Each host has static route which uses the vsan SVI (10.10.1.0      255.255.255.0        10.10.0.0   vmk2       MANUAL) (want to make sure this is recommended or if i should use something else)

- das.usedefaultisolationaddress = false

- HA advance setting is configured with the following das.isolationaddress(1-4): IPs 10.10.0.2(Site A),  10.10.0.4(SiteB), 10.10.0.3(SiteA),  10.10.0.5(SiteB) in that order (want to validate this too)

- As you can see vsan witness traffic always flows through the primary site (sub optimal routing, not big deal unless HSRP fail-over time is too high and could cause vsan issues after a site failure while 10.10.0.1 becomes available again.

Questions:

1- Should i advertise (route) the vsan SVIs.

2- Can i use a different route for witness traffic to avoid traversing the ISL

3- Is the HA advanced settings (Isolation addresses) configured properly.

What would you recommend to improve this design. Dont be shy with the details .

I understand this is very networking "heavy" but that is what we have to deal with by using Ethernet based distributed storage systems which HCI is. As we always hear.. network reliability is key to HCI.

Thanks in advance folks!!

Looking forward to your responses.

After upgrading VCSA to v6.7.0.40000, I am no longer able to create new VMs from a template in a Content Library when using the customize os option.

A "Deploy OVF package from Content Library to Resource Pool" task starts after selecting the compute resource that never completes and I cannot proceed past the network selection step.

There are also javascript errors indicating a failure to populate the "IP Allocation Settings" due to a null reference. The network drop down populates, but the IP allocation section stays blank.

If I do not "customize" the os, I'm able to create the new VM. I can also deploy from a template in the datacenter and use the customize os option.

Any thoughts on how I can troubleshoot/which log files to look at specifically? Or is this possibly just a bug with the release.