No RDP, no enter-pssession, no invoke-command from powershell can be used even if they were all able to be used before. It becomes an issue because your host machine will never receive the 'ctl-alt-del' to allow you to login. That's a great feature, unless you happen to be on a domain that requires you to login. The 'enhanced keyboard' passes key combinations such as 'ctl-alt-del' to VMs in Workstation. You were lucky in that you could actually log into the machine, I was completely locked out of my host machine and had to boot into a linux live usb. Additionally, hopefully VMWare will see this answer and make some changes to the vmkdb for future iterations. Hopefully someone else who has this issue will find this. I understand that this is more than 6 months old and this person probably has either resolved the issue or done what ever else was necessary to get around the issue. I was going to copy all %temp% *.log and *.txt but I guess that would be illegal, even though I usually need it for the rare circumstances where our stuff does not run after install.I had the same issue just now. My MSI installers also copy the MSI logs to a product folder under our %ProgramData% area for ease of access when they call us for support. It pays to look at ALL the logs in %TEMP% if they are willing to share them. An MSI log informed me of the drive error. then repaired our install and it worked like a champ. One rare case a customer had to chcdsk /f and reboot because his drive was messed up. I mean they always blame me and when I look at all the logs, I see it's usually their system. We never get any support tickets that things did not install. The ONLY time our apps have trouble by our customers is 99.9% their machine is hosed or misconfigured. I like to test all our stuff with it on as well so we don't get those gotcha's I was just thinking about using PSExec for this too. The script will restart in " & $sleep & " seconds.", $sleep ) EndFunc Script will retry in " & $smallSleep & " seconds.", $smallSleep ) EndIf another way to accept the UAC - via shortcut Send("") Send("!y") Else if UAC was not found try again in $sleep seconds Sleep ( $sleep ) EndIf WEnd if some error occured which expired the loop, pause the script for $sleep seconds MsgBox ( 0, "Error", "Some Error expired the timer and the script could not recover. #ce - Func checkForImage ( ) While $counter2 < 1 search for the UAC in the entire screen - 2 screens supported local $searchUac = _ImageSearchArea ( 'UAC_ginloSetup.bmp', 1, - 2568, - 8, 5136, 1440, $x1, $y1, 0 ) If $searchUac = 1 Then if the UAC was found search for the Yes button in a an area 200 x 200 from the middle of the found UAC image local $searchYes = _ImageSearchArea ( 'UAC_Yes.bmp', 1, $x1, $y1, $x1 + 200, $y1 + 200, $x2, $y2, 0 ) If $searchYes = 1 Then if the Yes button was found click it and pause the script for $sleep seconds MouseClick ( "left", $x2, $y2, 1, 0 ) Sleep ( $sleep ) Else if the Yes button was not found retry from the beginning in $smallSleep seconds MsgBox ( 0, "UAC found error", "UAC was found but the 'Yes' button was not found. Here is my code, which works with virtualbox:Įxpand collapse popup #AutoIt3Wrapper_Icon= ".\uac.ico" #include FileInstall ( ".\ImageSearchDLL.dll", ".\ImageSearchDLL.dll", 0 ) FileInstall ( ".\UAC_ginloSetup.bmp", ".\UAC_ginloSetup.bmp", 0 ) FileInstall ( ".\UAC_Yes.bmp", ".\UAC_Yes.bmp", 0 ) set global variables for the coordinates, which should be delivered global $x1 = 0, $y1 = 0 global $x2 = 0, $y2 = 0 global $counter1 = 0 global $counter2 = 0 global $sleep = 10000 global $smallSleep = 5000 execute the script in a loop, so that it will hopefully recover from some unexpected errors While $counter1 < 1 I also noticed that while the cursor moves to the target which has to be cilcked when my vmware worstation window is not focused, it even doesn't do that when i WinActivate the vmware workstation window first.ĭid anyone experience such an issue, or maybe could give me a hint, what else i could use to send a key combination or a mouse click in a vmware workstation 14 pro guest window? Every attempt that i made to send clicks or keys from the host inside the VM did not work. I tried sending key combinations instead of a click, so that the VM can grab the input, but it also did not work. Since i switched to VMware Workstation 14, the script no longer clicks inside the VM successfully. It recognized the UAC prompt and clicked inside and the UAC was accepted. This script worked perfectly with virtual box. Both the host and the guest OS are Windows 10. I have an autoit script running on my host machine watching for the UAC prompt to be displayed in a running vm. I am writing to you after a very long struggle i had while trying to figure out how to send a simple click inside a virtual machine running in vmware workstation 14.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |