I recently added a new esxi host to my cluster, and I just noticed in the EQ group manager that one of the iscsi IPs for that host is listed twice under iSCSI Connections. I suspect that's because yesterday, I had to change the name of one of my VM Port groups because the name didn't match what I had on the other hosts (capitalization error on my part). That port group is associated to the active vmkernel that has that IP address. I have a separate vSwitch with teamed nics for iscsi.
Do I need to clear VMs from the host and restart, or is there another way to get rid of the old connection?
I have ucs blades and they all have the same hardware config and same service profiles. but under storage adapters, I see the vmhba has different numbers on some hosts
"The following features have reached end of life in Workstation 12 Pro and have been removed:
Unity mode on Linux guest and host operating systems "
This is a terrible decision and will keep me from buying the upgrade. I use linux to host windows guests in unity mode and very much want this feature.
I have a strange issue with ESXi 5.5. I have got a new dedicated server from OVH and installed ESXi 5.5 from its template in OVH manager. The issue is that when I try to add this host to my existing vCenter Server located in another data center, I get the following error:
Call "Datacenter.QueryConnectionInfo" for object "Virtual DC 1" on vCenter Server "VCENTER" failed.
I have also tried installing a fresh vCenter Server on a VM hosted on this ESXi host.
DNS settings are configured on the host and VMware vCenter Agent is running on it.
I registered a vCenter Server in vCO 5.5 1281930 and it shows up in inventory with "(unusable) fqdn_of_vcenter". Since I registered this as a vCAC advanced services endpoint, I should only make changes from vCAC, but I cannot change or delete the endpoint as vCO throws the following error:
Error
Unable to create a vCO endpoint of type VC. Reason: Inconsistency between registered hosts and loaded hosts
1 - in all of vmware documents said don't keep snapshots more than 3 - 4 days but here in horizon view in link clone mode we have to use snapshots exactly why we have to use snapshot ? what is that benefit of use snapshot ?
I'm currently using UEM9 and have a need to retain user data from a Thinapp. Is it mandatory that I change the isolation mode to MERGED within the Thinapp (for the user configuration locations only) so the the user configuration data is saved to the C:\ drive?
I attend VMworld last week and during EUC7797 , the instructor demonstrated using a Thinapp with UEM, but didn't mention anything about Isolation modes.
If I change the isolation mode (and republish) from with the Thinapp, UEM works just fine. Didn't really want to go down the road of changing the Isolation modes if I didn't have to. Typically, we use Write Copy for just about everything.
it is no problem to remove and re-add (no errors), but always shows as unusable
the server.log shows that it can be added successfully (workflow finishes). but then there seems to be a problem with authentiucation (OAuth vs SAML casting fails)?
[WorkflowHandler] Starting workflow 'Add a vCenter Server instance' (8a91841857098af8015709e201f40057)...
Logging into 'VMware vCenter Server 6.0.0 build-3634793
Validated login with administrator@vsphere.local on VMware vCenter Server 6.0.0
java.lang.ClassCastException: com.vmware.vcac.authentication.http.spring.oauth2.OAuthToken cannot be cast to com.vmware.vim.sso.client.SamlToken
Any ideas?
full part in log:
===
2016-09-08 12:59:50.147+0000 [WorkflowExecutorPool-Thread-3] INFO {administrator@vsphere.local:Add a vCenter Server instance:f246b7b5-fe89-4da5-a640-36ffc6874069:token=8a91841857098af8015709e201f40057} [WorkflowHandler] Starting workflow 'Add a vCenter Server instance' (8a91841857098af8015709e201f40057)...
2016-09-08 12:59:51.029+0000 [WorkflowExecutorPool-Thread-3] INFO {administrator@vsphere.local:Add a vCenter Server instance:f246b7b5-fe89-4da5-a640-36ffc6874069:token=8a91841857098af8015709e201f40057} [VlsiHelper] Logging into 'VMware vCenter Server 6.0.0 build-3634793' at https://vCenterNameReplaced:443/sdk with username administrator@vsphere.local
2016-09-08 12:59:51.101+0000 [WorkflowExecutorPool-Thread-3] INFO {administrator@vsphere.local:Add a vCenter Server instance:f246b7b5-fe89-4da5-a640-36ffc6874069:token=8a91841857098af8015709e201f40057} [HostConfigurationUtil] Validated login with administrator@vsphere.local on VMware vCenter Server 6.0.0 build-3634793 at https://vCenterNameReplaced:443/sdk
2016-09-08 12:59:51.115+0000 [WorkflowExecutorPool-Thread-3] WARN {administrator@vsphere.local:Add a vCenter Server instance:f246b7b5-fe89-4da5-a640-36ffc6874069:token=8a91841857098af8015709e201f40057} [HttpConfigurationCompilerBase$ConnectionMonitorThreadBase] Shutting down the connection monitor.
2016-09-08 12:59:51.135+0000 [WorkflowExecutorPool-Thread-3] INFO {administrator@vsphere.local:Add a vCenter Server instance:f246b7b5-fe89-4da5-a640-36ffc6874069:token=8a91841857098af8015709e201f40057} [SCRIPTING_LOG] __item_stack:/item1
2016-09-08 12:59:51.142+0000 [WorkflowExecutorPool-Thread-3] INFO {administrator@vsphere.local:Add a vCenter Server instance:f246b7b5-fe89-4da5-a640-36ffc6874069:token=8a91841857098af8015709e201f40057} [VimPluginConfiguration] Loaded configuration version 70127b17e44bb6d7038a317e44084ca5
2016-09-08 12:59:51.146+0000 [WorkflowExecutorPool-Thread-3] INFO {administrator@vsphere.local:Add a vCenter Server instance:f246b7b5-fe89-4da5-a640-36ffc6874069:token=8a91841857098af8015709e201f40057} [VimPluginConfiguration] Adding configuration for https://vCenterNameReplaced:443/sdk
2016-09-08 12:59:51.177+0000 [WorkflowExecutorPool-Thread-3] INFO {administrator@vsphere.local:Add a vCenter Server instance:f246b7b5-fe89-4da5-a640-36ffc6874069:token=8a91841857098af8015709e201f40057} [ResourceElementManagementServiceImpl] ResourceElement 'https://vCenterNameReplaced:443/sdk' created.
2016-09-08 12:59:51.263+0000 [WorkflowExecutorPool-Thread-3] INFO {administrator@vsphere.local:Add a vCenter Server instance:f246b7b5-fe89-4da5-a640-36ffc6874069:token=8a91841857098af8015709e201f40057} [ResourceElementManagementServiceImpl] ResourceElement 'https://vCenterNameReplaced:443/sdk' updated (with content).
2016-09-08 12:59:51.294+0000 [WorkflowExecutorPool-Thread-3] INFO {administrator@vsphere.local:Add a vCenter Server instance:f246b7b5-fe89-4da5-a640-36ffc6874069:token=8a91841857098af8015709e201f40057} [VimPluginConfiguration] Saved configuration version 70127b17e44bb6d7038a317e44084ca5
2016-09-08 12:59:51.313+0000 [WorkflowExecutorPool-Thread-3] INFO {administrator@vsphere.local:Add a vCenter Server instance:f246b7b5-fe89-4da5-a640-36ffc6874069:token=8a91841857098af8015709e201f40057} [VimSession] Socket read timeout = 60000
2016-09-08 12:59:51.314+0000 [WorkflowExecutorPool-Thread-3] INFO {administrator@vsphere.local:Add a vCenter Server instance:f246b7b5-fe89-4da5-a640-36ffc6874069:token=8a91841857098af8015709e201f40057} [VimSession] Created session to https://vCenterNameReplaced:443/sdk
2016-09-08 12:59:51.372+0000 [WorkflowExecutorPool-Thread-3] INFO {administrator@vsphere.local:Add a vCenter Server instance:f246b7b5-fe89-4da5-a640-36ffc6874069:token=8a91841857098af8015709e201f40057} [SCRIPTING_LOG] __item_stack:/item0
2016-09-08 12:59:51.450+0000 [WorkflowExecutorPool-Thread-3] INFO {administrator@vsphere.local:Add a vCenter Server instance:f246b7b5-fe89-4da5-a640-36ffc6874069:token=8a91841857098af8015709e201f40057} [WorkflowHandler] End of workflow 'Add a vCenter Server instance' (8a91841857098af8015709e201f40057), state: completed
2016-09-08 13:00:30.712+0000 [http-nio-127.0.0.1-8280-exec-4] INFO {} [VimSession] Initializing vmomi for vc - https://vCenterNameReplaced:443/sdk
2016-09-08 13:00:30.821+0000 [http-nio-127.0.0.1-8280-exec-4] INFO {} [PluginCacheManager] Created cache 'administrator_vsphere.local_https___vCenterNameReplaced_443_sdk_Main_5421f122 useIS_ false'; eternal: true, maxElementsInMemory: 50000
We have multiple hosts in vCenter, running different versions of ESXi, 5.0, 5.5 and 6.0, as such I have multiple vSphere clients installed on Windows 10 laptop.
When I attempt to connect to a Console of a VM guest, I see a really odd 1/4 screen view. The easiest way to explain this is with a picture. It doesn't matter if the guest is Windows, or a Linux console, the issue is the same. Any ideas?
Before this my mouse had a large gap between where the mouse displayed on my screen and where it would actually click. It's impossible to know if this issue still persists as well as I am unable to use the console.
So we are having this issue where after joining a domain successfully, this ESX standalone box will not let users login via vsphere, either by manually entering credentials or choosing use windows session credentials.
Despite the permissions being in place, for example a user and the domain admin account has been added with all permissions over the physical host, you get this error when attempting to login:
I did a bad thing. I made a change to the DNS settings somewhere in the vcenter web client, and forgot to document it. When I came back to it after lunch, the page had refreshed and just shows a DNS error.
Chrome shows "Unable to resolve the server's DNS address"
I can connect via SSH, and there appears to be nothing wrong in either /etc/resolv.conf or etc/sysconfig/network/config
Is there anywhere else to look for config files?
It's an inherited system that I'm trying to rationalise. Unfortunately restoring from backup is not an option at the moment, as the backup server is powered down on an ESXi 5.5 host that nobody has the root password for.
Quite by accident I went to reboot a Windows Server 2000 VM on an ESXi 5.5 host after applying the August ESXi550-201608001 patch release, build 4179633. This also is called Patch 8 on the build correlation web page. And I am getting a BSOD Stop 0x0000001e - worker_thread_returned_at_bad_IRQL. I can boot it into both Safe Mode and Safe Mode with Networking, but not do a regular boot. It will boot OK on an Express Patch 10 ESXi 5.5 host (Build 3568722) and I can migrate it to the Patch 8 host and it will run OK, just not boot.
I have a backup copy of this vm, made prior to installing VMware Tools, and it has the same problem, so it's not a Tools related issue. I tried opening a case with VM Technical Support, but they won't touch it 'cause Win 2K.
What I'm guessing is that somewhere along the boot process it's probing a certain device and that's the problem. What device is the question. I've tried uninstalling and removing things that I could find, but no luck. This VM was a p2v conversion of an IBM Server from years ago, so there's probably something there from that conversion.
I do have an Windows Server 2000 installation CD. Interestingly the installer hung during the scan and configuration of a new vm on the Patch 8 host. I was able to run it on the Express Patch 10 host and create a vanilla W2K vm. And that boots OK on the Patch 8 system.
So, I've been guessing that this might be due to the USB stuff that was patched, but I have no real way of telling. We're a small shop, with only three ESXi hosts, so leaving a host at Patch 8 is not really a good option. This particular vm (and a second one similar to it) is part of the expense reporting system, so it's fairly important. And I'm not sure we have the necessary install materials to reinstall the application from scratch or I'd just rebuild the vm.
So, thought I'd see if anyone had anything to offer. Thanks for reading.
I'm working on deploying View at our campus for our Linux users, this will help me get rid of a large number of VirtualBox installations and allow our users to run our linux image from their own devices. I have successfully setup a view environment using Version 7.01 - specifically:
ESXi/Vcenter 5.5 Update 4 (soon to be 6.x)
VMware-viewconnectionserver-x86_64-7.0.1-3988
Access Point 2.5.0 v2
VMware-horizonagent-linux-x86_64-7.0.1-3967987
Client 4.1.0 on Windows and 4.1.0/4.2.0 on iOS
We are using RHEL 7.2 Workstation as the desktop (using MATE/lightdm). I have successfully created a small testing pool and connected to it from Windows / iOS clients.
There are a couple issues we are having trouble with yet that I'm hoping someone can shed some light on.
1. Login As Current User option does not work on the client from our internal workstations. I receive a message: "The Connection Server authentication failed to login as the current user." The user is logged into AD, if I then login with the same credentials to the view client authentication prompt it shows the pools for the user.
2. Single Signon from the desktop is not working nor does it seem even enabled? I have AD integration setup on our Linux Desktops via sssd. In the /var/log/vmware/viewagent-debug.log I see:
<main> [StandalongAgent] SSO isn't installed
And the file /usr/lib/vmware/viewagent/bin/SsoDBusNotify.py doesn't even exist?
3. USB doesn't work - I'm thinking it might be a firewall issue here? It just says "USB Unavailable" on the client. I tried plugging in a few different USB devices to see if it would change but nothing different happened.
4. Screensaver locks. If the user has their linux screensaver lock enabled and disconnects without logging off no one can connect to the VM, even the same user. Is the only way around this to enable the "Automatically logoff after disconnect - After XX minutes" pool setting?
5. HTML Access - I have this enabled in the Pool setting but when attempting to connect is shows an error prompt "Failed to connect to the Connection Server." - guessing a firewall issue here as well. A separate installation isn't needed for this right?
We have an issue going on in our VDI environment that has been to this point, impossible to nail down. Our users complain of instances where IE (IE11) will load with just a white screen, and spin for minutes on end. Dragging the window makes it cascade visually across the screen, essentially like a hung session. Eventually the window is closeable, and if the user reopens IE, perfect, no issue. The issue is completely un-repeatable so far. We have no process to make this happen on demand. It's totally random.
We're a Horizon 6.2 environment, we're utilizing linked clones with App Volumes and UEM. Windows 7, IE11.
One setting I found and was curious about is this one shown below, the software rendering setting in IE. The clusters our users are in I would classify as not visually high performing. IE we don't have upper end graphical cards in the hosts for any diagnostic imaging. Would this setting make a difference for the issue we've seen possibly, would it be completely benign, or should we have it enabled anyway? Right now it's disabled.
I'm facing an issue while calling a powershell script on remote server. The script runs without any issue on the target server and returns output. But while calling from vro, the workflow is only in running state. It never ends. Below is the script which generates pdf from excel file in the specified path. Kindly help me fixing it.
Also help me troubleshooting the following error from vro, I tried running close session with instance and killed the powershell process running on the server. But issue still continues. How to troubleshoot from vro?
The WS-Management service cannot process the request. This user is allowed a maximum number of 5 concurrent shells, which has been exceeded. Close existing shells or raise the quota for this user.
We are having some problems with our new infrastructure, we have 3 HPE DL380 Gen9 direct attach to an EMC Unity300, 3 servers were installed with the Customized HPE ISO (6.0 U2) downloaded from VMware.com. We also tried with the non customized ISO version but the same result. We are using one Emulex SN1100E 16Gb Dual Port FC HBA.
The problem is that when one of the FC cables is disconnected and reconnected again we can not see the luns until the server is rebooted. We tried with two single port Qlogic 4Gb HBA and everything works fine, I hace tried with different drivers and firmwares but the problem persist.
I look at the compatibility matrix at EMC looking for the correct firmware and driver for the HBA But I have not found, does any one can help me with the compatibility matrix?
I got a snapshot setup to be created automatically within the vcenter once a month and need a script to remove the snapshot 4 days later. I am testing this script on just one snap to start but will need to expand it. Also at the end I wanted it to email me just to confirm things were done.
Following recent feedback from many of you that there is insufficient guidance on how to write robust plug-ins and observing the amount of dependency issues reported on this forum we have extended the current Best practices guide with more OSGi-related recommendations.
In addition to that a new OSGi usage validation feature has been released with the HTML Client part of HTML Client SDK Fling 3. Upon HTML Client startup it automatically checks your plug-ins for OSGi problems (i.e. usage that does not comply with the OSGi best practices) immediately after deployment of all plug-ins.
You can view the validation results in the plugin-medic.log file which is generated alongside your vsphere_client_virgo.log. Fixing all reported warnings would eliminate many of the possible causes for dependency issues of your plug-in or clashes with other plug-ins.
For more details about all types of OSGi validation checks please have a look at the "Checking your plug-in for OSGi problems" section of the Getting_Started_with_HTML_Client_SDK_Fling.pdf document. The latest HTML samples also provide useful tips on making robust manifests.
Hope your plug-in's validation output looks like this:
[INFO ] [com.mycompany.myplugin:1.0.0] STARTED Validating [My Plug-in, My Company]
[INFO ] [com.mycompany.myplugin:1.0.0] FINISHED Validating [My Plug-in, My Company]
