Articles on this Page
- 07/28/17--20:02: _VMware Workstation ...
- 01/09/19--08:57: _error occured durin...
- 01/09/19--08:59: _Horizon Client on a...
- 01/09/19--09:49: _Unable to connect t...
- 01/09/19--09:51: _Blast is still tras...
- 01/09/19--02:34: _SAN LUN corrupted r...
- 11/28/18--06:10: _Office Pro Plus ins...
- 01/09/19--01:50: _unsupportedDiskType...
- 01/09/19--09:54: _is it possible to a...
- 12/28/18--16:38: _Unable to Enter Log...
- 12/13/18--12:47: _High Availability (...
- 01/09/19--10:01: _vcenter login to gr...
- 12/29/18--23:08: _Fresh install of vC...
- 01/09/19--10:32: _Changing the MAC ad...
- 01/09/19--07:54: _"All hosts contribu...
- 01/09/19--10:52: _Unable to determine...
- 01/09/19--10:31: _Attempting to find ...
- 01/09/19--06:48: _Error "Failed to lo...
- 05/08/14--08:25: _Cannot modify any v...
- 01/07/19--14:47: _VMs in vAPP prompt ...
- 01/09/19--08:57: error occured during vCentre Operation
- 01/09/19--08:59: Horizon Client on appstack
- 01/09/19--09:51: Blast is still trash and PCoIP is stagnant
- 11/28/18--06:10: Office Pro Plus installs/configures on every launch of Outlook
- 01/09/19--01:50: unsupportedDiskType2 issue in ESXi 6.5
- 01/09/19--09:54: is it possible to add an HDD to a VM without shutting it down?
- 12/28/18--16:38: Unable to Enter Login Credentials with Windows 10
- 12/13/18--12:47: High Availability (Redundant) UEM Share
- 01/09/19--10:01: vcenter login to grey screen
- 01/09/19--10:32: Changing the MAC address of the VM
- 01/09/19--07:54: "All hosts contribution stats" warning
- 01/09/19--10:31: Attempting to find vlan's with no vm's
- 01/07/19--14:47: VMs in vAPP prompt for root password
I am currently preparing a lab in VMware Workstation 12 and every time I click Share VM I receive the following message.
. I have WS 12 installed on Windows server 2016 and log into the domain.
The currently logged in user does not have permissions to
connect to the Workstation server. Enter the credentials of a
user that has sufficient permissions.
I already have full administrator rights to the domain.
Why do I keep getting the above message. ?? I am trying to create a vm.
Error occured during vCentre Operation when trying to provision Linked clones
Did anyone try to install Horizon Client in the Appstack. It looks like it will get installed, creates a shortcut on desktop and then Install Fails every time. If I open my packaging machine (not in provisioning mode) it works just fine. It is only when I want to package it.
Any help would be much appreciated.
I have a server that runs Arch linux. I've installed VMware Workstation 15 on it, and was able to setup a user and connect from macOS 10.14.2 using Fusion 11.0.2. I then did the following from my Mac:
1. Created a new VM
2. Configured the VM (CPU, Memory, drive, etc...)
3. Right clicked on the VM and choose "Power On"
That's when it kind of went sideways. The VM starts in Workstation, but Fusion gives me the error "Unable to connect to the MKS: Failed to connect to server X.X.X.X:902" where X.X.X.X is the IP of the system. I get a blank console window. From Fusion I can still power off the VM, power it back on, suspend it, etc... I just can't access the console. Things I have tried:
1. There is NO firewall between the two machines.
2. Made sure that DNS was setup and working correctly (Saw this as a suggestion elsewhere).
3. Added the machine to the hosts file just to make sure, though I'm connecting by IP.
4. I've verified that I can connect to an ESXi 6.5 system and perform all tasks as expected.
5. I've verified that hostd is running on the linux box
I've attached the hostd.log file removing IPs and usernames:
1. X.X.X.X is the Workstation server
2. Y.Y.Y.Y is the Fusion client
3. USERNAME is the username I connected from Fusion to Workstation as.
I'm stumped and am hoping somebody will read the above wall of text and tell I'm less intelligent than a rock and point out my failing. Thanks!
We've been searching for upgraded monitor configurations with the proliferation of higher resolution larger screens and finding that we are severely limited due to blast being useless and Zero/Thin client support for multiple high resolution monitors pretty limited. The best we've found is the 10zig 1200-qpd. But it can't even drive 3 2560x1440 and does 0 4k ...
What are people doing? Is blast ever going to stop being laggy? We use grid
All, I have a Datastore that will not mount. It is on a HP P2000 and VMware (5.5.0 u3b) on the host required a rebuild after corruption. Note the store would not mount previously. 9 out of 10 stores mount and are visible in VMware.
I have already tried to reset the partition table - using partedUtil. following the guidance here - VMware Knowledge Base
~ # partedUtil getptbl /vmfs/devices/disks/naa.600c0ff00014c353c7c00f5001000000
497976 255 63 8000000000
1 2048 7999997951 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0
getUsableSectors returned - 7999999966
Current status -
~ # partedUtil getptbl /vmfs/devices/disks/naa.600c0ff00014c353c7c00f5001000000
497976 255 63 8000000000
1 2048 7999997951 AA31E02A400F11DB9590000C2911D1B8 vmfs 0
Note - have tried both 7999997951 and 7999999966 for usable sectors
The drive does not show within /vmfs/volumes yet the device shows as mounted via the vSphere Client, under storage adapter, Operational State.
Errors in the kernel log show - 'No FS driver claimed device 'naa.600c0ff00014c353c7c00f5001000000:1': Not supported'
Calculated value for usable sectors was - 7999984439 - and this also fails.
This volume is 4TB.
Any ideas? Many thanks.
We just upgraded from AppVol 2.12 to 2.14.2 (latest). After the upgrade, users are calling in with an issue where Outlook 2016 Pro Plus tries to run an install or configure every time it is launched. In our case we have Office installed directly on the master image which has not changed, it is not an AppStack. We use Writable Volumes and I have verified that the issue is not related to any changes in the snapvol.cfg file with the update as I've tried the old version of snapvol.cfg as well and get the same behavior, so it's definitely an issue with the 2.14.2 upgrade somehow.
Has anybody else experienced this and know of a workaround? I've been looking and so far no solution that I can find.
Thanks in advance!
We have our product vmdk file (monolithic sparse format) which works fine in ESXi 5.5 and 6.0. Recently we have installed ESXi 6.5 afresh and tried deploying VM with our exisiting VMDK file. But in ESXi 6.5, we get the below error in VM's log file vmware.log in host machine,
2019-01-02T10:51:17.977Z| vmx| I125: DumpDiskInfo: ide0:0 createType=2, capacity = 524288000, numLinks = 1, allocationType = 4294967295
2019-01-02T10:51:17.977Z| vmx| I125: Virtual Device for ide0:0 was already successfully destroyed
2019-01-02T10:51:17.977Z| vmx| I125: Msg_Reset:
2019-01-02T10:51:17.978Z| vmx| I125: [msg.scsi.esx.unsupportedDiskType2] Unsupported or invalid disk type 2 for 'ide0:0'. Ensure that the disk has been impor
2019-01-02T10:51:17.978Z| vmx| I125: [msg.scsi.esx.virtualDevFailed] Unable to create virtual SCSI device for 'ide0:0' (/vmfs/volumes/5c0f9295-b139f418-b471-
2019-01-02T10:51:17.978Z| vmx| I125: ----------------------------------------
We tried to convert the existing VMDK file using the vmkfstool in new ESXi 6.5 box as below,
vmkfstools -i "our_existing_vmdk.vmdk" "our_new_vmdk.vmdk" -d thin
We tried launching a VM with this converted file (our_new_vmdk.vmdk) and its works fine in ESXi 6.5. The above command internally created a flat file as well.
We cannot ship have two different VMDK files (one for ESXi 5.5 & 6 and other for ESXi 6.5). We trying to check if we can use the same VMDK across ESXi versions 5.5, 6, 6.5. Or should we ask customers to convert the file if they use ESXi 6.5. Any suggestions on this would be helpful?
FYR: We are creating VMDK from qcow2 image using the below command,
qemu-img convert -f qcow2 our_qcow2_file.qcow2 -O vmdk our_vmdk_file.vmdk
We tried using compat6 in the above command (qemu-img convert -f qcow2 our_qcow2_file.qcow2 -O vmdk our_vmdk_file.vmdk compat6) but still it didn't help.
Thanks in advance.
recently I have been told that with VMware (don't know what product: Fusion, ESX, Workstation...) it is possible to add another HDD to a VM without having that VM shut down.
I have Fusion and the system tells me that, in order to add another resource I need to stop the VM.
Thanks for your collaboration!
Having a weird problem with the Remote Desktop Connection client and pretty much anything else that requires you to enter a username and password. If I delete the users writable profile then everything works like normal and allows you to enter your credentials to connect. The next time the users logs in and opens the RDP client or tries to "Run As" another user you are not able to enter any credentials. I attached the screenshot. I tried to exclude the MSTSC.exe process from the snapvol.cfg file but no luck.
Any other ideas?
I'm trying to determine the best method for providing a high availability file share for UEM configs and user data files. I've looked into DFS-R (while disabling multiple login sessions) and this seems better than nothing, but even if I dial down the client namespace cache down to 1 second the user shares will still hang if one of the servers is rebooted or fails. This would also interrupt any user files that are open, file transfers that are in progress, etc..
Therefore I was thinking that maybe a better solution would be to leverage the SMB (3.0) Transpartent Failover feature outlined here: SMB Transparent Failover – making file shares continuously available – clausjor
Has anyone tried these methods (or others) that they would recommend? Any thoughts, considerations or experiences that would be helpful in determining the best path forward?
My vCenter 6.5 web interface (port 9443) after login becomes gray and hang without obvious event causing it. I performed update through port 5480 and rebooted but did not fix the problem. Anyone ran into similar problems?
This is an install of a fresh lab and fresh deployment of vCenter Appliance 6.7 with ESXi 6.7.
All machines have internet connectivity.
My domain controller is also the DNS server and DNS works fine forward and reverse/PTR.
Each ESXi host is time sync'd to the IP for pool.ntp.org [22.214.171.124]
The esxi hosts can ping the the time server...
I configured my Domain controller to sync time with the below commands...
w32tm /config /manualpeerlist:pool.ntp.org /syncfromflags:MANUAL
The DC sync's fine....
The server I am using to deploy the virt appliance is also sync'd to with the same above method.
Below are my setting when deploying the virtual appliance...
All those settings gets me past the first step to deploy the virtual appliance to my esxi server....
Here are the virtual appliance network, SSO and ntp settings....
I also attached the logs from my 7th attempt.......lol
Here's the error message..."A problem occurred while - Starting VMware Content Library Service..."
Any help is appreciated.
We might need to restore a Linux VM (using Veeam). As you know, once a VM is restored, the network interface would not work due to a different MAC address. In the past, we would log in via the login console of that VM and update the new MAC address in some configuration files. In this case, our Login screen doesn't work (it just have a Centos logo without the login prompt).
Is there a procedure/edit route to force the restored machine to reuse the old original MAC address?
This is probably the solution just found.
I have a stretched cluster of 2 ESXi 6.5u2 (SERVER1 and SERVER2) + 1 Witness (WITNESS1).
When I check the vSAN health screen everything is OK except one which is in Warning : "All hosts contributing stats". The warning says that the host SERVER2 is not contributing to stats.
I followed this tutorial to determine which server was the stats master : vSAN hosts not contributing stats reports - vSAN Health check fails - vhabit
My stats Master is SERVER1
If I check the vsanmgmt.log file, I have this warning :
2019-01-09T14:21:49Z VSANMGMTSVC: WARNING vsanperfsvc[Collector-1] [statscollector::RetrieveRemoteStats] Error happened during RetrieveRemoteStats of host IP_of_SERVER2, type: <class 'socket.timeout'>, message: timed out
2019-01-09T14:21:50Z VSANMGMTSVC: WARNING vsanperfsvc[Collector-1] [statscollector::RetrieveRemoteStats] Error happened during RetrieveRemoteStats of host IP_of_WITNESS1, type: <class 'socket.timeout'>, message: timed out
Communications between servers work well. I checked it with vmkping. The rest of the vSAN works perfectly.
Any idea ?
I've successfully installed and integrated VRNI 4.0 with my vSphere 6.7 and NSX 6.4.4
But i have one little issue - VM Path Topology doesnt't work correctly for VMs which are located at regular (non-NSX) Port Groups
For example Path to Internet throws the following error 'Unable to determine path: Unable to determine router for Gateway IP 10.10.40.1'
10.10.40.1 is the gateway (SVI) on a physical switch
The same thing with a VM on NSX network works just fine
How would I go about finding vlan's with no vm's assigned to the vlan. A report listing all vlan's with the number of vm's associated with the vlan would be helpful.
Thank you for your responses.
I'm trying to migrate my virtual machine present on private cloud environment (Nephoscale) to the local environment. Since automated disk image exporting feature is not available in their enviornment, we have took the 'dd'/'raw' full byte copy of the instance's disk and converted it into VMDK as mentioned in the steps given in the link
I have then attached this VMDK to my local Virtual Machine vSphere as a "Existing Hard Disk" but when I tried to power on the VM then it is throwing following two errors.
a. "Cannot open the disk '/vmfs/volumes/53671f4a-5bfc16da-6053-002590e74eac/img/hard_disk.vmdk' or one of the snapshot disks it depends on."
b. "Failed to lock the file"
Can you please help me with the steps to restore this VMDK to my new VM.
Also, what is the meaning of above 2 errors and in which case it occurs?
Thanks in advance.
This is killing me. All I want to do is add an additional NIC to two VMs. I can't. This is a new installation. I have 5 running production VMs plus the vcenter appliance. Things WERE working fine and just quit working out of the blue.
I can't even "connect" an ISO image to a CDROM.
I tried powering down the VM with no change. (Actually the VM never would even show is was powered off in the client, but since the only power option was "power on" at this point, I assumed it was off.)
I can't modify ANY VMs at all. I have restarted the vCenter Appliance with no change in behavior. Why are we forced to use this horrible Web Client??????
Running 5.5 build 1750787 - Have been pushing to sell hyper-v since the support options for vmware are cost prohibitive for SMB, but vendor for this customer requested vmware.
In vCenter 6.5 I created a vAPP with no resource management. In that vAPP I added my vRA stack which consists of three vRA appliances, SQL, 2 each of DEM, agent, and ISA for a total of 10 servers in the stack. Outside the vAPP start up is as expected. Inside the vAPP two of the three appliances fail to start with the error Property 'Initial root password' must be configured for the VM to power on. Where do I configure this?