LucDHere is the result from the get-powercliversion command.
PowerCLI Version
------------------
VMware vSphere PowerCLI 5.5 Release 2 build 1671586
------------------
Snapin Versions
------------------
VMware AutoDeploy PowerCLI Component 5.5 build 1598391
VMware ImageBuilder PowerCLI Component 5.5 build 1598391
VMware License PowerCLI Component 5.5 build 1265954
VMware VDS PowerCLI Component 5.5 build 1671576
VMware vSphere PowerCLI 5.5 Release 2 build 1671576
For whatever it is worth, two of my Windows 10 VMs (one on VMware Workstation 12.5.5 and the other on Fusion 8.5.6), the tools are on 10.1.6-5214329.
The CentOS 7 VM (closest thing to RHEL 6) the tar-gz file name also show 10.1.6-5214329 when I select Update VMware Tools on Workstation 12.5.5.
Can you tell me where I can set the timeout value? Is it a config file I can edit? I could try setting it to a large value, 30 seconds for instance.
I've done some more printing to try to detect a pattern. For a normal dense document, a typical PDF, web page, etc., the printer will print about a half page of information on sheet 1 and then page-eject and continue printing beginning at the top edge of sheet 2 (still logically, page 1 data). Assuming that the data hitting the printer is essentially a graphics file (whether text, images, or whatever) it seems like we are talking about a buffer or memory limit... However, there is no "timeout" (no pause). Sheet 2 starts printing immediately after the sheet 1 page-eject. The page-eject occurs without regard to whitespace and will print the top half of a line of text on sheet 1 and the bottom half of the same line of text on sheet 2. If I format a small 200 word document with wide margins and lots of whitespace between paragraphs, so the formatted memo occupies the entire page, but is a small file, then the amount of data sent to the printer is small and prints normally on a single sheet of paper even if it occupies an entire page as formatted.
Thanks for continuing to look into this.
Hi mauser,
NFS will always be slower for the speed as per this website benchmark:
https://sion-it.co.uk/tech/linux/which-is-faster-iscsi-or-nfs-when-used-as-an-esxi-datastore/
So iSCSI is the better way to go for performance.
But yes, for simplicity reason, you can go with NFS.
I had this same exact error in IE but it worked in Firefox and the buttons showed up right. Maybe also try Chrome. I think you are missing a key dependency.
hi whibr
have you had any luck identifying this issue?
""Cheers
Gerardo
It seems like you have ghost driver. So, Reboot the system with safe mode option and remove the like - "set devmgr_show_nonpresent_devices=1" or devcon.
This happens to me on Fusion a few times in a row now and then, but it always works right eventually. This especially has been the case after Windows updates. I use Fusion every day for a Windows 10 VM. But it has been better behaved the past 6 weeks or so. Wher happens generally is a "red screen of death".
We seem to have slightly different causes and symptoms for this, but I would advise that you take the same precaution as me, which is to have 1-2 snapshots handy at all times. VMware recommends not keeping them older than 72 hours.
Another observation I get is that when I power off the Windows VM that it has a higher probability of issues. However, it almost always works for me if I hard kill the window by hitting the X and letting it take some kind of automatic hidden state snapshot. I wish I had a technical term for what happens when you kill a Fusion window like that, but it's much better on average than just leaving it and being at the mercy of Windows to install whatever it wants unattended. I also have just been shuttting down my MacBook most of time.
Hi,
I found a display of an abnormal problem.
First, narrow the browser, and then drag the horizontal scroll bar to the far right, and then the blank appeared on the right side of the page.
The smaller the browser, the bigger the blank is.
The problem is shown below.
Has this problem been solved?
Yes, In your case it is good because users are not going to c:\username.....\documents
it is good for you, but if we use windows GPO we will never loss user data
however our UEM team is working on this issue to fix it in UEM 9.2 version
Thanks.
You are right liorshe, Initially I used UEM 9.1 for folder redirection and later we adopted windows GPO redirection
ok, solved it....not really...but the solution was there....in the Item-->Machines tab screen in VRA ....where it lists all the provisioned machines, there is a column that shows the external IP.
Your storage is either VAAI Capable or not.
This can be seen with esxcli or through the storage in the webclient
Vmware uses the PSA and the VAAI Filter to determine if you can use VAAI (hardware acceleration) will be "supported" or "unsupported"
The question i have is how does the host know?
Does each storage vendor bake this VAAI ability via drivers or something that talks to the kernel on the vmware host and on a scan/discover of storage, the storage reports that it has this to the VAAI Filter? I have never loaded any special drivers or PSP/SATP stuff into our hosts yet they can see that our storage is VAAI capable without even doing anything or loading anything special.
To create alarms for the Hardware Health states you have to use the com.vmware.vc.cim.CIMGroupHealthStateChanged eventtypeID.
In fact I already did a post on that, a long time ago, in Alarms – Cody’s Abandon Ship
That created a general alarm, that fired when anything in the Hardware Health status turned red.
The ones you discovered are for specific groups of Hardware Sensors.
These groups are listed under the HostNumericSensorType enumeration.
Once you know the group, it is straightforward to create an Alarm.
For example, this one will fire when one of the SystemBoard sensors fires.
$si=Get-ViewserviceInstance
$alarmMgr=Get-View-Id$si.Content.AlarmManager
$alarms=Get-View-Id ($alarmMgr.GetAlarm($si.Content.RootFolder))
$ha=$alarms|where{$_.Info.Name -match"Host hardware"}
$spec=New-ObjectVMware.Vim.AlarmSpec
$spec.Name ='TestHW2'
$spec.Description ='Test HW alarm'
$expr1=New-ObjectVMware.Vim.EventAlarmExpression
$expr1.EventType ='EventEx'
$expr1.EventTypeId ='com.vmware.vc.cim.CIMGroupHealthStateChanged'
$expr1.ObjectType ='HostSystem'
$expr1.Status ='red'
$exprComp1=New-ObjectVMware.Vim.EventAlarmExpressionComparison
$exprComp1.AttributeName ='group'
$exprComp1.Operator ='equals'
$exprComp1.Value ='SystemBoard'
$exprComp2=New-ObjectVMware.Vim.EventAlarmExpressionComparison
$exprComp2.AttributeName ='newstate'
$exprComp2.Operator ='equals'
$exprComp2.Value ='red'
$expr1.Comparisons =$exprComp1,$exprComp2
$spec.Expression =$expr1
$alarmMgr.CreateAlarm($si.Content.RootFolder,$spec)
The layout for these Hardware Sensor alerts is always the same, you specify the group ($exprComp1).
And then you specify the state on which the alarm shall fire ($exprComp2).
Needless to say, you can combine multiple of these HW Sensor expressions with AndAlarmExpression and OrAlarmExpression
Hi Raul, thanks for the suggestions... In response to your comments I've included my responses in red
- View Connection Server can't communication with the View Agent on a the VM - This is true because the VDI desktop with the view agent doesn't have a valid IP address
- When the VM is not getting the DHCP address when provisioned - This is true
- Try ipconfig /renew on the VM getting 169.254 & see if you get a valid IP - This does fix the issue
- Try to Pings a specified host until stopped. To see statistics use -t - Once I manually release/renew the IP and it goes from a 169.254 address to a valid address everything ping fines and the VDI desktop refreshes itself
- Try doing ipconfig /release & ipconfig /flushdns on the master VM before shutting it down for new snapshot - We do am ipconfig /release on the master images but not an ipconfig /flushdns, we will add that to our prep batch scripts.
- Check your DNS & DHCP scope size & IP lease expiration. Maybe it's a DHCP problem & No a Horizon View issue - The scopes are fine, we are only using 8% of our available 900+ IPs in that subnet
- Check the user account & OU you use to recompose the pools, sometimes VDI is not able to update the DNS records and therefore failed to receive the DHCP addresses. Finally check your antivirus. - Our DHCP server takes care of the dynamic DNS update on the client's behalf. Once I manually release and renew the DHCP settings the DHCP server registers the VDI system's IP in DNS
When some of our employees sign into their InstantClones using their Teradici PCoiP Dell Wyze Zero Clients, they get the stated message when trying to connect to the InstantClone. We're thinking it has something to do with their writable volumes(after we disable their writable volume) and then have them sign in again, they sign in fine, but with the stock image generated by the parent.
Any help would be appreciated.
Hi
I am doing a deployment of VRA 7.2
I have used windows 2012 R2 standard as AD and Windows 2008 R2 for Iaas server
All the service in VRA and Iaas server are up and running and i am able to login successfully
I face issue when i try to add the directory from Administration > directory .
I am using the Active Directory ( Integrated Windows Authentication ) and logged in to tenant using Tenant Administrator
I know my domain admin is correct because same i used to add other computers to domain.
But in this case when i try to add the directory i am getting the error
"Could not join domain: Error occurred while joining domain. Verify Domain Admin username and password is correct, and the username is the sAMAccountName."
I know the credentials are correct and have the the required priveledge
Hi Rick,
The graphics processor is and Intel Iris 6100 in a MacBook Retina 13" Early 2015. I'm also attaching the vmware.log file.
Thanks!
Jeff
Sorry for not making it clear.
I was talking about transfer timeout in the driver. But unfortunately, it's not configurable.
I checked the USB printer class spec. the BULK IN endpoint is optional and is for status reporting purposes. I think that's the reason. We should have had a longer timeout or no timeout in our driver. But I still need to reproduce it and verify the fix in house.
In the meantime, if you need to have the printer work in a VM, you can disable the native driver before the issue is fixed. Please use
esxcli system module set -m=vmkusb -e=FALSE
If I am understanding your question correctly, I believe you are looking to take some AD values and add them to a new provisioned machine, is that correct? If so, I am doing something similar but using ServiceNow and values as what I add to a provisioned VM. I have a workflow subscription that runs as the first workflow once a request is made that will do some processing with values presented in the request and then will update the vm be provisioned with the values that were just calculated. Actually take workflow populated 25 different values colllected during that stage so long story short, yes you can add AD values to the virtual machine. One of the first things I would do to setup that process is to create a Property Group in the Property Dictionary for your AD values you are looking to populate. For the name you can do something like this.... VirtualMachine.ActiveDirectory.DomainName.Attribute
Here is my template that I use to make updates
//var entity = virtualMachineEntity
System.log("Processing VM Information")
var virtualMachine = virtualMachineEntity.getInventoryObject();
if (virtualMachine == null)
{
throw "The virtual machine ID is invalid";
}
var MachineProperties = new Properties();
var virtualMachinePropertyEntities = virtualMachineEntity.getLink(vCACHost, "VirtualMachineProperties");
for each (var virtualMachinePropertyEntity in virtualMachinePropertyEntities)
{
var propertyName = virtualMachinePropertyEntity.getProperty("PropertyName");
var propertyValue = virtualMachinePropertyEntity.getProperty("PropertyValue");
MachineProperties.put(propertyName, propertyValue);
if (propertyName == "VirtualMachine.ActiveDirectory.DomainName.Attribute") {
System.log("Found the droid we have been looking for")
break;
}
}
//Got info and ready to update entity
var vmUpdate =
{
"PropertyName" : "VirtualMachine.ActiveDirectory.DomainName.Attribute",
"PropertyValue" : Attribute
};
//var virtualMachineProperties = new Properties();
var model = "ManagementModelEntities.svc";
var entitySet = "VirtualMachineProperties";
var links = new Properties();
links.put("VirtualMachineProperties",virtualMachineEntity); //The property needs to link back to the blueprint
var entityKey = virtualMachinePropertyEntity.entityKey;
var entityKeyId = entityKey.get("Id");
var entityUpdate = vCACEntityManager.updateModelEntityBySerializedKey(vCACHost.id , model , entitySet, entityKeyId , vmUser, links