Good morning experts

Is there a way via powercli to fix the problem of inconsistent folder names?

Thank you for any and all input!!

Norm

Hi, hope someone can point me in the right direction.

I will be backing up my VCSA 6.5 via HTTPS. As 6.5 does not have a scheduling solution out of the box, I am looking to use powershell running from a scheduled task. The way I see it, I can either call the REST API using Invoke-restMethod or I could use Get-CisServer. Where I am struggling to find a solution is, how to permission an account that has the least possible privileged to perform this action.

Using the cron option (Link below) from within the VCSA is not an option, I will fail all my security audits, unless someone can explain how I could not have the passwords exposed in plain text. And the configuration would need to be automated.

VMware vSphere 6.5 Documentation Library

Thanks

Anyone know if possible to set the NetFlow collector IP/settings on a vDS with PowerCLI?  Running through the Get-vDSWitch stuff, I can see how to query erspans already configured but I don't see a place where I can set the Collector IP & related settings.

Thanks for the help in advance!

This happens with any image that I use. Even known working images. Right after I make the instance and boot it up it then freezes.

I have reinstalled VMware workstation 15.

Downloaded a new copy of the program and installed that one.

When it freezes it will not shut down, and I can not kill vmware-vmx.exe. Even with psexplorer or cmd.exe. I have to reboot the computer. It looks like these two issues are hand in hand.

Event viewer doesn't seem to come up with anything related.

Maybe when uninstalling a corrupted file remains?

Hardware is a ProLiant DL360e Gen8 with the last SPP applied.

Error:

Snippet of log from today.:

2019-04-17T21:02:36.467Z cpu0:35479)WARNING: LinChar: LinuxCharWrite:574: This message has repeated 9 times: M=235 m=0 flags=0x101002 write 8 bytes at offset 0x0 failed (-16)
2019-04-17T21:32:40.035Z cpu10:35479)WARNING: LinChar: LinuxCharWrite:574: This message has repeated 10 times: M=235 m=0 flags=0x101002 write 8 bytes at offset 0x0 failed (-16)
2019-04-17T21:59:00.594Z cpu6:33253)WARNING: LinScsi: SCSILinuxProcessCompletions:826: Error BytesXferred > Requested Length Marking transfer length as 0 - vmhba = vmhba1, Driver Name = hpvsa, Requested length = 512, Resid = 4072
2019-04-17T21:59:00.606Z cpu6:33253)WARNING: LinScsi: SCSILinuxProcessCompletions:826: Error BytesXferred > Requested Length Marking transfer length as 0 - vmhba = vmhba1, Driver Name = hpvsa, Requested length = 255, Resid = 4072
2019-04-17T22:29:00.819Z cpu3:32866)WARNING: LinScsi: SCSILinuxProcessCompletions:826: Error BytesXferred > Requested Length Marking transfer length as 0 - vmhba = vmhba1, Driver Name = hpvsa, Requested length = 255, Resid = 4072
2019-04-17T22:34:17.398Z cpu11:35518)WARNING: LinChar: LinuxCharWrite:574: This message has repeated 11 times: M=235 m=0 flags=0x101002 write 8 bytes at offset 0x0 failed (-16)
2019-04-17T22:34:17.398Z cpu11:35518)WARNING: LinChar: LinuxCharWrite:574: This message has repeated 12 times: M=235 m=0 flags=0x101002 write 8 bytes at offset 0x0 failed (-16)
2019-04-17T23:33:30.614Z cpu3:35479)WARNING: LinChar: LinuxCharWrite:574: This message has repeated 13 times: M=235 m=0 flags=0x101002 write 8 bytes at offset 0x0 failed (-16)
2019-04-17T23:59:01.004Z cpu6:35515)WARNING: LinScsi: SCSILinuxProcessCompletions:826: Error BytesXferred > Requested Length Marking transfer length as 0 - vmhba = vmhba1, Driver Name = hpvsa, Requested length = 512, Resid = 4072
2019-04-17T23:59:01.016Z cpu6:35515)WARNING: LinScsi: SCSILinuxProcessCompletions:826: Error BytesXferred > Requested Length Marking transfer length as 0 - vmhba = vmhba1, Driver Name = hpvsa, Requested length = 255, Resid = 4072
2019-04-18T02:29:01.627Z cpu3:33253)WARNING: LinScsi: SCSILinuxProcessCompletions:826: Error BytesXferred > Requested Length Marking transfer length as 0 - vmhba = vmhba1, Driver Name = hpvsa, Requested length = 512, Resid = 4072
2019-04-18T02:29:01.639Z cpu3:33253)WARNING: LinScsi: SCSILinuxProcessCompletions:826: Error BytesXferred > Requested Length Marking transfer length as 0 - vmhba = vmhba1, Driver Name = hpvsa, Requested length = 255, Resid = 4072
2019-04-18T02:33:59.031Z cpu8:35479)WARNING: LinChar: LinuxCharWrite:574: This message has repeated 14 times: M=235 m=0 flags=0x101002 write 8 bytes at offset 0x0 failed (-16)
2019-04-18T02:33:59.032Z cpu8:35479)WARNING: LinChar: LinuxCharWrite:574: This message has repeated 15 times: M=235 m=0 flags=0x101002 write 8 bytes at offset 0x0 failed (-16)
2019-04-18T02:59:01.623Z cpu10:35641)WARNING: LinScsi: SCSILinuxProcessCompletions:826: Error BytesXferred > Requested Length Marking transfer length as 0 - vmhba = vmhba1, Driver Name = hpvsa, Requested length = 512, Resid = 4072
2019-04-18T02:59:01.635Z cpu10:35641)WARNING: LinScsi: SCSILinuxProcessCompletions:826: Error BytesXferred > Requested Length Marking transfer length as 0 - vmhba = vmhba1, Driver Name = hpvsa, Requested length = 255, Resid = 4072
2019-04-18T03:29:01.747Z cpu10:34373)WARNING: LinScsi: SCSILinuxProcessCompletions:826: Error BytesXferred > Requested Length Marking transfer length as 0 - vmhba = vmhba1, Driver Name = hpvsa, Requested length = 255, Resid = 4072
2019-04-18T03:59:01.849Z cpu5:33253)WARNING: LinScsi: SCSILinuxProcessCompletions:826: Error BytesXferred > Requested Length Marking transfer length as 0 - vmhba = vmhba1, Driver Name = hpvsa, Requested length = 512, Resid = 4072
2019-04-18T03:59:01.860Z cpu5:33253)WARNING: LinScsi: SCSILinuxProcessCompletions:826: Error BytesXferred > Requested Length Marking transfer length as 0 - vmhba = vmhba1, Driver Name = hpvsa, Requested length = 255, Resid = 4072
2019-04-18T04:29:01.951Z cpu5:34351)WARNING: LinScsi: SCSILinuxProcessCompletions:826: Error BytesXferred > Requested Length Marking transfer length as 0 - vmhba = vmhba1, Driver Name = hpvsa, Requested length = 512, Resid = 4072
2019-04-18T04:29:01.963Z cpu5:34351)WARNING: LinScsi: SCSILinuxProcessCompletions:826: Error BytesXferred > Requested Length Marking transfer length as 0 - vmhba = vmhba1, Driver Name = hpvsa, Requested length = 255, Resid = 4072
2019-04-18T05:59:02.265Z cpu8:32875)WARNING: LinScsi: SCSILinuxProcessCompletions:826: Error BytesXferred > Requested Length Marking transfer length as 0 - vmhba = vmhba1, Driver Name = hpvsa, Requested length = 512, Resid = 4072
2019-04-18T05:59:02.276Z cpu8:32875)WARNING: LinScsi: SCSILinuxProcessCompletions:826: Error BytesXferred > Requested Length Marking transfer length as 0 - vmhba = vmhba1, Driver Name = hpvsa, Requested length = 255, Resid = 4072
2019-04-18T06:36:19.518Z cpu7:35479)WARNING: LinChar: LinuxCharWrite:574: This message has repeated 16 times: M=235 m=0 flags=0x101002 write 8 bytes at offset 0x0 failed (-16)
2019-04-18T06:36:19.519Z cpu7:35479)WARNING: LinChar: LinuxCharWrite:574: This message has repeated 17 times: M=235 m=0 flags=0x101002 write 8 bytes at offset 0x0 failed (-16)
2019-04-18T07:59:02.661Z cpu10:32790)WARNING: LinScsi: SCSILinuxProcessCompletions:826: Error BytesXferred > Requested Length Marking transfer length as 0 - vmhba = vmhba1, Driver Name = hpvsa, Requested length = 512, Resid = 4072
2019-04-18T07:59:02.673Z cpu10:32790)WARNING: LinScsi: SCSILinuxProcessCompletions:826: Error BytesXferred > Requested Length Marking transfer length as 0 - vmhba = vmhba1, Driver Name = hpvsa, Requested length = 255, Resid = 4072
2019-04-18T08:06:57.401Z cpu8:35479)WARNING: LinChar: LinuxCharWrite:574: This message has repeated 18 times: M=235 m=0 flags=0x101002 write 8 bytes at offset 0x0 failed (-16)
2019-04-18T08:37:01.382Z cpu9:35479)WARNING: LinChar: LinuxCharWrite:574: This message has repeated 19 times: M=235 m=0 flags=0x101002 write 8 bytes at offset 0x0 failed (-16)
2019-04-18T09:29:02.977Z cpu9:33022)WARNING: LinScsi: SCSILinuxProcessCompletions:826: Error BytesXferred > Requested Length Marking transfer length as 0 - vmhba = vmhba1, Driver Name = hpvsa, Requested length = 512, Resid = 4072
2019-04-18T09:29:02.988Z cpu9:33022)WARNING: LinScsi: SCSILinuxProcessCompletions:826: Error BytesXferred > Requested Length Marking transfer length as 0 - vmhba = vmhba1, Driver Name = hpvsa, Requested length = 255, Resid = 4072
2019-04-18T09:46:49.247Z cpu10:35518)WARNING: LinChar: LinuxCharWrite:574: This message has repeated 20 times: M=235 m=0 flags=0x101002 write 8 bytes at offset 0x0 failed (-16)
2019-04-18T09:46:49.247Z cpu10:35518)WARNING: LinChar: LinuxCharWrite:574: This message has repeated 21 times: M=235 m=0 flags=0x101002 write 8 bytes at offset 0x0 failed (-16)
2019-04-18T10:07:39.270Z cpu5:35479)WARNING: LinChar: LinuxCharWrite:574: This message has repeated 22 times: M=235 m=0 flags=0x101002 write 8 bytes at offset 0x0 failed (-16)
2019-04-18T10:07:39.271Z cpu5:35479)WARNING: LinChar: LinuxCharWrite:574: This message has repeated 23 times: M=235 m=0 flags=0x101002 write 8 bytes at offset 0x0 failed (-16)
2019-04-18T10:29:58.728Z cpu10:35516)WARNING: LinChar: LinuxCharWrite:574: This message has repeated 24 times: M=235 m=0 flags=0x101002 write 8 bytes at offset 0x0 failed (-16)
2019-04-18T10:29:58.728Z cpu10:35516)WARNING: LinChar: LinuxCharWrite:574: This message has repeated 25 times: M=235 m=0 flags=0x101002 write 8 bytes at offset 0x0 failed (-16)
2019-04-18T10:37:39.257Z cpu7:35479)WARNING: LinChar: LinuxCharWrite:574: This message has repeated 26 times: M=235 m=0 flags=0x101002 write 8 bytes at offset 0x0 failed (-16)
2019-04-18T11:08:08.833Z cpu8:35479)WARNING: LinChar: LinuxCharWrite:574: This message has repeated 27 times: M=235 m=0 flags=0x101002 write 8 bytes at offset 0x0 failed (-16)
2019-04-18T11:38:30.229Z cpu6:35479)WARNING: LinChar: LinuxCharWrite:574: This message has repeated 28 times: M=235 m=0 flags=0x101002 write 8 bytes at offset 0x0 failed (-16)
2019-04-18T11:38:30.229Z cpu6:35479)WARNING: LinChar: LinuxCharWrite:574: This message has repeated 29 times: M=235 m=0 flags=0x101002 write 8 bytes at offset 0x0 failed (-16)
2019-04-18T12:29:03.585Z cpu8:33230)WARNING: LinScsi: SCSILinuxProcessCompletions:826: Error BytesXferred > Requested Length Marking transfer length as 0 - vmhba = vmhba1, Driver Name = hpvsa, Requested length = 512, Resid = 4072
2019-04-18T12:29:03.596Z cpu8:33230)WARNING: LinScsi: SCSILinuxProcessCompletions:826: Error BytesXferred > Requested Length Marking transfer length as 0 - vmhba = vmhba1, Driver Name = hpvsa, Requested length = 255, Resid = 4072
2019-04-18T12:37:21.862Z cpu8:35517)WARNING: LinChar: LinuxCharWrite:574: This message has repeated 30 times: M=235 m=0 flags=0x101002 write 8 bytes at offset 0x0 failed (-16)
2019-04-18T12:37:21.862Z cpu8:35517)WARNING: LinChar: LinuxCharWrite:574: This message has repeated 31 times: M=235 m=0 flags=0x101002 write 8 bytes at offset 0x0 failed (-16)
2019-04-18T13:08:58.249Z cpu2:35479)WARNING: LinChar: LinuxCharWrite:574: This message has repeated 32 times: M=235 m=0 flags=0x101002 write 8 bytes at offset 0x0 failed (-16)
2019-04-18T13:08:58.250Z cpu2:35479)WARNING: LinChar: LinuxCharWrite:574: This message has repeated 33 times: M=235 m=0 flags=0x101002 write 8 bytes at offset 0x0 failed (-16)
2019-04-18T13:29:03.773Z cpu8:33009)WARNING: LinScsi: SCSILinuxProcessCompletions:826: Error BytesXferred > Requested Length Marking transfer length as 0 - vmhba = vmhba1, Driver Name = hpvsa, Requested length = 512, Resid = 4072
2019-04-18T13:29:03.785Z cpu8:33009)WARNING: LinScsi: SCSILinuxProcessCompletions:826: Error BytesXferred > Requested Length Marking transfer length as 0 - vmhba = vmhba1, Driver Name = hpvsa, Requested length = 255, Resid = 4072
2019-04-18T13:29:03.879Z cpu8:33009)WARNING: LinScsi: SCSILinuxProcessCompletions:826: Error BytesXferred > Requested Length Marking transfer length as 0 - vmhba = vmhba1, Driver Name = hpvsa, Requested length = 512, Resid = 910
2019-04-18T13:29:03.891Z cpu8:33009)WARNING: LinScsi: SCSILinuxProcessCompletions:826: Error BytesXferred > Requested Length Marking transfer length as 0 - vmhba = vmhba1, Driver Name = hpvsa, Requested length = 255, Resid = 910
2019-04-18T13:30:01.335Z cpu7:34405 opID=2dcff5ed)WARNING: NMP: nmpUnclaimPath:1516: NMP device "naa.600508b1001caa3204a6276a4c5c8894" quiesce state change failed: Busy
2019-04-18T13:59:03.872Z cpu11:33230)WARNING: LinScsi: SCSILinuxProcessCompletions:826: Error BytesXferred > Requested Length Marking transfer length as 0 - vmhba = vmhba1, Driver Name = hpvsa, Requested length = 512, Resid = 4072
2019-04-18T13:59:03.884Z cpu11:33230)WARNING: LinScsi: SCSILinuxProcessCompletions:826: Error BytesXferred > Requested Length Marking transfer length as 0 - vmhba = vmhba1, Driver Name = hpvsa, Requested length = 255, Resid = 4072
2019-04-18T14:59:04.078Z cpu3:33253)WARNING: LinScsi: SCSILinuxProcessCompletions:826: Error BytesXferred > Requested Length Marking transfer length as 0 - vmhba = vmhba1, Driver Name = hpvsa, Requested length = 512, Resid = 4072
2019-04-18T14:59:04.090Z cpu3:33253)WARNING: LinScsi: SCSILinuxProcessCompletions:826: Error BytesXferred > Requested Length Marking transfer length as 0 - vmhba = vmhba1, Driver Name = hpvsa, Requested length = 255, Resid = 4072
2019-04-18T15:29:04.181Z cpu9:33010)WARNING: LinScsi: SCSILinuxProcessCompletions:826: Error BytesXferred > Requested Length Marking transfer length as 0 - vmhba = vmhba1, Driver Name = hpvsa, Requested length = 512, Resid = 4072
2019-04-18T15:29:04.193Z cpu9:33010)WARNING: LinScsi: SCSILinuxProcessCompletions:826: Error BytesXferred > Requested Length Marking transfer length as 0 - vmhba = vmhba1, Driver Name = hpvsa, Requested length = 255, Resid = 4072
2019-04-18T16:59:04.488Z cpu6:33228)WARNING: LinScsi: SCSILinuxProcessCompletions:826: Error BytesXferred > Requested Length Marking transfer length as 0 - vmhba = vmhba1, Driver Name = hpvsa, Requested length = 512, Resid = 4072
2019-04-18T16:59:04.500Z cpu6:33228)WARNING: LinScsi: SCSILinuxProcessCompletions:826: Error BytesXferred > Requested Length Marking transfer length as 0 - vmhba = vmhba1, Driver Name = hpvsa, Requested length = 255, Resid = 4072
2019-04-18T17:59:04.696Z cpu10:33023)WARNING: LinScsi: SCSILinuxProcessCompletions:826: Error BytesXferred > Requested Length Marking transfer length as 0 - vmhba = vmhba1, Driver Name = hpvsa, Requested length = 512, Resid = 4072
2019-04-18T17:59:04.708Z cpu10:33023)WARNING: LinScsi: SCSILinuxProcessCompletions:826: Error BytesXferred > Requested Length Marking transfer length as 0 - vmhba = vmhba1, Driver Name = hpvsa, Requested length = 255, Resid = 4072
2019-04-18T18:10:39.790Z cpu6:35479)WARNING: LinChar: LinuxCharWrite:574: This message has repeated 34 times: M=235 m=0 flags=0x101002 write 8 bytes at offset 0x0 failed (-16)
2019-04-18T19:10:40.848Z cpu7:35479)WARNING: LinChar: LinuxCharWrite:574: This message has repeated 35 times: M=235 m=0 flags=0x101002 write 8 bytes at offset 0x0 failed (-16)
2019-04-18T19:59:05.113Z cpu8:32879)WARNING: LinScsi: SCSILinuxProcessCompletions:826: Error BytesXferred > Requested Length Marking transfer length as 0 - vmhba = vmhba1, Driver Name = hpvsa, Requested length = 512, Resid = 4072
2019-04-18T19:59:05.123Z cpu8:32879)WARNING: LinScsi: SCSILinuxProcessCompletions:826: Error BytesXferred > Requested Length Marking transfer length as 0 - vmhba = vmhba1, Driver Name = hpvsa, Requested length = 255, Resid = 4072
2019-04-18T20:25:09.102Z cpu2:34733 opID=b0172488)WARNING: NMP: nmpUnclaimPath:1516: NMP device "naa.600508b1001ca65eca46457b40bca13d" quiesce state change failed: Busy
2019-04-18T20:34:38.191Z cpu8:33713)WARNING: NMP: nmp_DeviceStartLoop:725: NMP Device "naa.600508b1001ca65eca46457b40bca13d" is blocked. Not starting I/O from device.
2019-04-18T20:34:38.191Z cpu3:128847)WARNING: NMP: nmp_DeviceStartLoop:725: NMP Device "naa.600508b1001ca65eca46457b40bca13d" is blocked. Not starting I/O from device.
2019-04-18T20:34:38.191Z cpu2:34733 opID=114e2832)WARNING: NMP: nmpUnclaimPath:1516: NMP device "naa.600508b1001ca65eca46457b40bca13d" quiesce state change failed: Busy
2019-04-18T20:41:02.460Z cpu3:35479)WARNING: LinChar: LinuxCharWrite:574: This message has repeated 36 times: M=235 m=0 flags=0x101002 write 8 bytes at offset 0x0 failed (-16)
2019-04-18T20:44:28.775Z cpu2:35518)WARNING: LinChar: LinuxCharWrite:574: This message has repeated 37 times: M=235 m=0 flags=0x101002 write 8 bytes at offset 0x0 failed (-16)
2019-04-18T20:44:28.776Z cpu2:35518)WARNING: LinChar: LinuxCharWrite:574: This message has repeated 38 times: M=235 m=0 flags=0x101002 write 8 bytes at offset 0x0 failed (-16)

Background.  OS was updated from 5.5 to 6.0 U3 in February going from and to an HPE customized image.  First Purple Screen was last week.  Since then I applied the SPP which updated the following:

I did the iLo and BIOS back in Feb. 

Yesterday it purple screened again with pretty much the same error

I've noticed that the drives aren't marked as local even though they are so we get a false degraded status:

I tried the solution here but it didn't work:

Disks degraded in ESXi

Its probably not related to the purple screen but its a thread you know?  Running out of ideas.  Any suggestions would be predicated.  I'm not finding much info on Failed to Ack TLB invalidate or the "WARNING: LinScsi: SCSILinuxProcessCompletions:826" error in the log.  I've got 3 other servers with the exact same history.  One of those purple screened a month ago but i didn't get the error message.  The other two haven't had any issues.  Any ideas?

Good day everyone my name is David and I have the following questions,

We are starting to prepare for building a small vsphere environment with the following specs.

1. total of 7 guest, 2 in DMZ, and 5 vm's in regular network

2. budget of approximately $40000

3. should have HA

4. don't need DRS

5. shared storage

6. vcenter and 2 esxi hosts 6.7

My questions/concerns are

1. this document from vmware states that minimum 3 hosts are recommended for HA/DRS - vCenter HA Hardware and Software Requirements

2. is this true you need minimum 3 hosts for HA or is it just saying for DRS you need 3 hosts?

3. What is the best solution for low budget decent performing shared storage?

4. do you recommend vsan for storage on a small setup? is it expensive?

5. A friend of mine was saying not to use HA and just use vsphere replication to copy vm's to second host in 15 minute intervals, I don't like this idea because of the significant extra disk I/O's and much less flexibility when it comes to patching and failover etc..., is this a legit approach to a poor mans HA?

6. Would you consider hosts with only 1 cpu? the vm's wont be real cpu hungry but I want good performance. (this might be to difficult to answer)

I appreciate any assistance you can proved.

Thank you.

Hi Folks,

Wonder if anyone can help - This issue has been driving me nuts for a while  - I have imported a .vmdk and attached to new Virtual machine.

When I try to reconfigure, I get the following error 'Enter a disk size which is larger than its original capacity'

So, I increase the size of the disk in the GUI.. click save and then get another error message

"Failed to reconfigure virtual machine xxx-yyy. Invalid operation for device '3"

The only Solution online points to snapshots - I don't have any.  And I had this issue with running ESXi 6.5 as well.

Any ideas on how to get around this will be greatly appreciated - This a homelab btw.

Thanks!

These are VDIs running Citrix XenDesktops. I just saw that in VSphere it was showing as 2 IP addresses. Could it be due to outdated VMWare tools, or why would this show like this?

I am trying to use workstation 15 pro to install an image provided via pxe boot.  The pxe server is hosted on a Freenas server.

I am able to pxeboot on bare metal with the same setup.  Also, I can pxe boot from within the vm system in freenas.

What am I missing?  I'm assuming it's an option in the dhcpd.conf file or in pathing, but i've been unable to find an answer.

Hello

Might be a hard one to answer with no real perf metrics however I would like to gain some info on scaling out app volumes 2.14 for around 30 appstacks and 1000 concurrent users, appstackes using around 120gb at present on one datastore running on SSD San.

At the moment there's very little users doing the PoC I need to understand when we ramp up the usage will I need a handful of datastores or just one?

What's the best approach for distributing the load?

Create a storage group and replicate the stacks? My colleague reckons one will be ok and it will perform fine as mostly reads on the Hitachi San when mounting the vmdks.

We will have 1000 users using horizon 7.7 with floating instant clone pools. A mix of laptop users and zero clients.

There will be ten + pools with appstack assigned to user at logon.

Our users will be on o365 eventually and using writeable volumes the uia template was increased to 30gb thin provisioned. Created at logon and assigned to a group containing all users. Uem is setting the location for outlook 2016 to the snapvolumetemp.

With the writeable volumes we are going to have 10 * 3tb datastores and create a storage group to spread the WV across the group and this seems to work quite well for a couple of small tests I've done granted again only a handful of users on the PoC. Windows 10 1803 with office 2016 click to run in the gold image.

We have horizon vrops in the environment but to be honest my understanding of it is not the best.

Any info on scaling this out would be helpful we are using vcsa 6.5 with esxi 6.5.

We went to our partner who helped set this up but no response as of yet.

Hi, I had been testing waters with Microsoft Visual Studio Code (VS Code).

Running into some inconsistences.  Cannot run PowerCLI scripts that call PSDrive. It appears VScode cannot access VIM Inventory providers. I am running VS Code as Administrator

Any suggestions on how to work with PSDrive under VS Code? Perhaps I need to adjust VS code settings\permissions to get access to VimInventory? Below is comparison of VS Code vs ISE

Thank you

Example: Get-PSDrive under VScode. There are no vi or vis listed

**************************************************************************

PS C:\> Get-PSDrive

Name           Used (GB)     Free (GB) Provider      Root                                                                                                                                                                                            CurrentLocation

----           ---------     --------- --------      ----                                                                                                                                                                                            ---------------

Alias                                  Alias

C                  71.65        166.21 FileSystem    C:\

Cert                                   Certificate   \

D                                      FileSystem    D:\

Env                                    Environment

Function                               Function

HKCU                                   Registry      HKEY_CURRENT_USER

HKLM                                   Registry      HKEY_LOCAL_MACHINE

Variable                               Variable

WSMan                                  WSMan

********************************************************************

Example: Get-PSDrive under ISE. There are vi and vis, vmstore and vmstores!

*************************************************************

PS C:\> Get-PSDrive

Name           Used (GB)     Free (GB) Provider      Root                                                                                                                                                                                         CurrentLocation

----           ---------     --------- --------      ----                                                                                                                                                                                         ---------------

Alias                                  Alias                                                                                                                                                                                                                     

C                  71.66        166.21 FileSystem    C:\                                                                                                                                                                                                         

Cert                                   Certificate   \                                                                                                                                                                                                           

D                                      FileSystem    D:\                                                                                                                                                                                                         

Env                                    Environment                                                                                                                                                                                                               

Function                               Function                                                                                                                                                                                                                  

HKCU                                   Registry      HKEY_CURRENT_USER                                                                                                                                                                                           

HKLM                                   Registry      HKEY_LOCAL_MACHINE                                                                                                                                                                                         

Variable                               Variable                                                                                                                                                                                                                 

vi                                     VimInventory  \LastConnectedVCenterServer                                                                                                                                                                                

vis                                    VimInventory  \                                                                                                                                                                                                          

vmstore                                VimDatastore  \LastConnectedVCenterServer                                                                                                                                                                                

vmstores                               VimDatastore  \                                                                                                                                                                                                          

WSMan                                  WSMan          

Hi there,

If you are a Shared VMs(VMware Workstation Server) user, could you pls let us know:

1. How do you use this Shared VM feature?
2. What works and what needs to improved?
3. How important is this feature to you?

Thanks,

VMware Workstation team

Dear all,

I have an issue when I am trying to create a new entry under Images in Component Profiles.

I cannot save the entry created and it fails with an error that Form cannot be saved - I tried different browsers but not luck. Any ideas?

Thx

Tasos

Hi I am signed up for free Lab: HOL-1903-01-NET - VMware account

but I can't get internet access there please help me ASAP thanks.

Hi, here's my setup, we have a Dell FX2 server with 3 SLEDS and 1 storage. Storage was set to Split Dual Hosts

SLED1 - has RAID controller and disk 0-7

SLED2 - has RAID controller and disk 8-16

SLED3 - has no RAID controller but has 2x 200GB internal SSD drives

So I set the 3 SLEDS by installing ESXI 6.7 Update 1. I installed ESXi VCSA on SLED 3's disk 1, I deployed vsan witness appliance on SLED 3's disk 2. Procedures I've done:

1. create a datacenter

2. create a cluster

3. add host 1 and host 2 (SLED 1 and SLED 2) on the cluster, enabled HA and vsan . After successfully adding the first 2 hosts, I went ahead and proceed with the 3rd step is to configure vsan cluster. BTW, I used the Quickstart wizard in configuring from adding the host in configuring vsan.

4. Host 3 or SLED 3 is not part of the cluster

The first part of the Cluster configuration is about Distributed Switches and I set both vmnic0 and vminic1 to both DSwitch, didn't modify anything under storage traffic, under Advanced options > vsan options I set to Two Host vSAN cluster. under Claim disk, I set the HDD for the storage and flash disk for the cache tier, next is letting me select the witness host which I did, the next part is where I'm kinda lost, it's looking to Claim Disks for witness host and I have nothing on the list.

Not sure where I missed or what part of the configuration I missed???

Thanks

Jeff

Hi,

I have a Dell VxRail solution which is vSAN.

By looking at the available free disk space, it shows an X (RAW) value.

However, the calculated free space is actually less, since we have to take into account the RAID-1 of the solution.

As VMware makes use of all the space (RAW), I ask myself:

1 - If I exceed the available space space limit, what will happen with vSAN?

2 - According to information from Dell there is a trigger that will warn us when it reaches 70% of use. Is this true? Even so, it does not prevent the end user from continuing to build servers and this is very bad.

3 - Where can we check how much we already use of the useful area we can use of vSAN?

Thank you.

VMWare Fusion 10.1.6 host running on Mac OS 10.13.6.

Client taken from 2007 Macbook running 10.7.5.

Client window opens with light grey, Apple logo and spinning wheel at the bottom. Remains that way overnight.

Other client VMs start up and run fine. Taken from other machines (older Macs as well) or fresh installs of Mojave, linux, Windows, experimental VMs like Haiku, etc.

I have Parallels on host machine. Started it up and converted the Macbook client to Parallels and it starts up and runs fine. Therefore I suspect that the disk image is fine since Parallels had to read and convert it for use.

Why won't Fusion get past the spinning wheel screen?

- Is the actual disk image the wrong version so when Parallels imported it, it was converted from older vmware to correct Parallels?

- Will Fusion just not boot up 10.7.5 even though I can set the vm type as 10.7?

Other options?

Where to look for logs and what should I be looking for?

Thanks!

Hi everyone

I had a issue with datastore on ESXI 6.5, I use FC connection from host to storage

Last time, after i shutdown and start my host for maintenant. On one Esxi host i can't see 1(Datastore) datastore (I have map 5 datastore). If somebody has same issue, please share my how to fix it. Thank!

Host Esxi cannot found datastore.

Other host Esxi found datastore, it same connected and topology

Hi All,

I seem to be having issues when using uia_plus_profile WV where the start menu will not open.

start menu works when writable volume without profile is attached.

start menu works with normal AppStacks it’s just uia_plus_profile That the start menu doesn’t open.

now we using the following

Windows 10 1709

Appvolumes 2.14

UEM 9.4

Horizon 7.5.1

in my play test environment

ive used the following with same result

windows 10 1709/1803

Appvolumes 2.15

UEM 9.5

Horizon 7.5.1

The WV uia_plus_profile works it’s just the stupid start menu will not open.

Thanks in advance

I work at a university student's log into our external facing vdi connection broker on there laptops, is there a log file somewhere on the connection broker that will show me who has logged onto the system? Thanks.