I have an exe file which needs to be running on the VMs (win7 and win8 VM images) on VMWarestation 9.
The exe usually runs for more than 3 hours, so I need to make sure the VM is not going to suspension mode within the 3 hours.
I have disabled the screensaver mode and sleep mode from the Control Panel of the VM images, and also I disabled the screensaver and sleep mode on the host machine which is running the workstation.
But, the VM images still go to the suspension mode within the 3 hours, in that case, I cannot have the exe finishing running.
Does anyone know how to prevent the VM image from going to suspension mode please? Thanks in advance.
Related
I am using Docker Desktop on Windows 11 to start and stop containers. When I close Docker Desktop and the computer goes to sleep, whenever I come back and relaunch Docker Desktop, the containers are gone. If I then restart the computer, they reappear. I have observed this consistently. Why are the containers lost after a sleep ?
If I don't close the Docker Desktop application, then after a sleep the containers remain there. I also have a hard time restarting Docker Desktop from the mouse menu. It just hangs there displaying : "Docker Desktop stopping..."
I am running FreeNAS 11.1-U5 at home. I have everything configured and have created VM's for Windows Server, Ubuntu, pfSense, FreePBX. I was able to install Windows and Ubuntu, but shortly after (a few hours after installing them), and after turning them off through the FreeNAS GUI, they have stopped turning on. FreeNAS reports at the top of the GUI that the start was successful, but the VM details still read "stopped".
I have run the VM's before and have the required settings in my CMOS configured for the Host (FreeNAS machine). Restarting the host will fix the problem for a while and it will let me work with the VM's, but I cannot keep restarting FreeNAS. Can anyone tell me why this happens and how to fix it please?
I created a program in Powerbuilder, and when ran on a personal computer it launches right away, however whenever I launch it on a Virtual machine, it takes up to two minutes before it actually launches.
Look at where runtime are. If they are in LAN you could have performance problem. Put them in a local disk of you VM
So I am connecting to my work computer from home and the Remote Desktop Connection app is annoyingly slow.
I pinged my work pc from my computer and it returned at a reasonable time of 50ms~ with 0 loss. I then attempted to ping my home IP from the RDP session and it timed out every time. Not sure if this might help anyone come to a conclusion but hopefully it does. Note I am also using it in conjunction with Cisco AnyConnect Secure Mobility Client if that helps at all. Work is Windows 7 and Home is Windows 8
I attempted switching off my home pc's firewall but that did nothing.
Any assistance would be great, surely a setting in the RDP file might make it run a little smoother.
I'll edit this post with further attempts at fixes below
Did three things and now RDP is running screaming fast:
Change RDP settings:
Run the RDP session and connect to the remote machine
Find mstcsc.exe in the Task Manager and and set priority to Realtime
I installed Ubuntu server XRDP. Went through Windows and terribly slowed down. I solved this problem. In the /etc/xrdp/xrdp.ini file, change crypt_level=high to crypt_level=None
Our remote chain is Citrix then RDP, target machine is Win 10.
I solved this issue by changing the mouse pointer scheme to None and disabling the pointer shadow.
In Windows 10. Go to Display Settings >> Scale and Layout >> Set the custom scale to 120 [you may need to experiment, try 110 - 150]
After that log in to your Remote Desktop, it should adjust the resolution and scaling factors.
It gave me a faster experience. If you need more then follow the answer of Mr. B
I am aware that autoit MouseClick() would not work when the system is locked.
My Question is ::
I have VsphereClient installed on my machine and i access VMs using this client. Now if autoit script is running on VM and i lock my pc (VM is not locked), then will the mouse interaction functions work on the VM?
VM is not located on my local pc. It is located on an ESX server.
So if the VM is not in locked mode and my pc is in locked mode, will the mouseclick() of AutoIT work on the VM?
vSphere is purely a configuration utility. It is not required for the virtual machines to run in anyway.
Therefore... If you have a script on your VM and that VM is not locked it would work exactly the same if you had it on a PC.
Don't make the mistake that vSphere is require for the machines on ESXi hypervisor to run.
Hope this helps :)
If your VM is not locked and Autoit is running on your VM, the MouseClick() will work perfectly as it will only occurs on your VM independently of your current local pc state. In fact you must see your VM as another PC and since it's running and not locked you can do everything you want, in your case an autoit script.