Share your videos with friends, family, and the world. Feb 17, 2012 If you are looking to install lion on an unsupported mac, then download 10.7 lion The 64bit patch and kext have only been tested on macs that are running 10.7.3 build 11D50, and have the GMA X3100 GPU. I have not tested this with the GMA 950 GPU. Only use Multibeast and Xmove, if you wish to install 10.7 on a PC, to create a Hackintosh setup.
Since publishing my Automating Cross vCenter vMotion between the same and different SSO Domain article back in early 2016, I have had a large number of customers reach out to me and share their success stories of allowing them to perform datacenter migrations to consolidating vCenter Servers all due to this awesome capability that was introduced in vSphere 6.0. In fact, many of the VM migration numbers were in the 4,000 to 8,000+ range which completely blew me away. It was great to hear from customers on how the xMoveVM.ps1 script had enabled them to do things that was simply not possible before, especially without impacting their workloads.
I still get pinged on a regular basis from customers about using my script and one thing that surprises many customers when I mention to them that this functionality has already been ported over to the native Move-VM cmdlet that was introduced with the PowerCLI 6.5 release. This had always been my original intention to provide an example using our vSphere API and enabling our customers in the short term and working with Alan Renouf and the PowerCLI team to get this folded back into the official PowerCLI cmdlets. This means, you no longer have to use my script for basic Cross vCenter vMotions whether that is between the same or different SSO Domain, which is quite nice as the number of user inputs is significantly reduced by using Move-VM cmdlet.
UPDATE (01/01/2018) - One additional option is the recently released Cross vCenter vMotion Utility Fling. For more details, please have a look at the blog post here.
Lets take a look at an example below where I have a VM called TestVM-1 which is residing in vcenter65-1 and I want to vMotion it to vcenter65-3:
With just 5 simple and easy to read lines of PowerCLI, you can perform this operation:
2 4 6 | $sourceVC=Connect-VIServer-Server vcenter65-1-User administrator@vsphere.local-Password VMware1! $targetVC=Connect-VIServer-Server vcenter65-3-User administrator@vsphere.local-Password VMware1! $vm=Get-VM-Server$sourceVC'TestVM-1' Move-VM-VM$vm-VMotionPriority High-Destination(Get-VMhost-Server$targetVC-Name$vmhost)-Datastore(Get-Datastore-Server$targetVC-Name iSCSI-01) |
Now, having said that ... there is one use case in which I would still recommend my xMove-VM.ps1 script over the Move-VM cmdlet, which is a VM that has multiple VMDKs AND you wish to ONLY perform what is known as a Compute-only Cross vCenter vMotion. This is to say, that you are only migrating the running state of the VM between vCenter Servers as the underlying storage is shared and available across both vCenter Servers. Below is a screenshot of a VM called TestVM-2 which has two VMDKs stored respectively on datastore iSCSI-01 and iSCSI-02 running on vcenter65-1 and we wish to relocate it to vcenter65-2 which you can also see has both those datastores available.
Today, there is a limitation with the Move-VM cmdlet for a compute-only Cross vCenter vMotion where VMDKs stored across different datastores will actually be relocated to a single datastore after performing the migration. It is possible to override this behavior via the vSphere API which my xMove-VM.ps1 supports by simply enabling setting the $xvcType property to 1. The script makes use of the granular VirtualMachineRelocateSpecDiskLocator which allows you to specify the location for individual disks which you can have a look here for the specific implementation supporting this use case. Hopefully the PowerCLI team will consider this enhancement in the future and to help with that, I have also filed the following PowerCLI Feature Request here. If you wish to see this functionality get added to Move-VM cmdlet, feel free to vote it up!
In summary, if you are looking for a quick and easy way to automate Cross vCenter vMotions, just update to the latest PowerCLI release and you can simply use the built-in Move-VM cmdlet. Not only is it super easy to use, but its fully supported by VMware. For compute-only Cross vCenter vMotion, you can continue using my script and hopefully we will get this gap closed in the future.
Additional Resources:
More from my site
There is a separate XModules installer for Windows, Mac and Linux. The installer includes the latest FileAccess, RealUser Simulation and DesktopAutomation XModules. Their version numbers are:
- FileAccess XModule: V1.0.12
- RealUser XModule: V1.0.20
- DesktopAutomation XModule: V1.0.19
The XModules work with UI.Vision for Firefox, UI.Vision for Chrome and the Copyfish Free OCR addon. So if you use one or more of our extensions, you need to install the XModules only once.
We tested on the following OS systems, but others should work as well. Please report any issues in the forum.
- Windows: Win 10, Win 7, Server 2016, Server 2019
- macOS: High Sierra, Mojave, Catalina
- Linux: Ubuntu 18.04, Ubuntu 19.04, Ubuntu 20.04
The XModules installers do not include the UI.Vision browser extension itself. You can download the UI Vision core module here:
- UI.Vision for Chrome
- UI.Vision for Firefox
- UI.Vision for Edge
License: End User License Agreement (EULA)
- UI.Vision for Chrome
- UI.Vision for Firefox
- UI.Vision for Edge
License: End User License Agreement (EULA)
How to install on Windows
Just run the setup file, it takes care of everything. All installations are done in your user account, so no admin rights are required. To test that everything works correctly, switch UI.Vision RPA to file storage mode. The screencast below shows the installation process:
As an optional last step, you can customize the UI.Vision home folder location. By default, UI.Vision RPA uses ' /uivision' as the UI.Vision RPA home directory. If you want to change this, open the UI.Vision RPA browser extension, open 'Settings', go to the 'XModule' tab and enter a new UI.Vision RPA Home folder - macros, testsuites and CSV files will be stored in this folder.
In some companies the download of EXE installers/files is blocked. If this happens to you, please use the ZIP file download link. To install from the ZIP archive, unzip the archive and then run '1install.bat'. This is almost the same procedure that is used in the macOS and Linux versions below.
How to install on macOS
First extract the content of the downloaded ZIP archive to a folder of your choice. Then open a command prompt and navigate to this folder.
(1.) Run the included shell script '1install.sh'. You do this by opening the terminal, navigate to the folder to which you copied the files and type
sh 1install.sh
You should then see a few messages that say 'Native messaging host... installed'
The installation is done now!
sh 1install.sh
You should then see a few messages that say 'Native messaging host... installed'
The installation is done now!
Do not move the XModules folder after the installation. The reason is that the installation script tells Chrome and/or Firefox where to find the the XModules. The files itself are not copied to a new location. So if you would move the folder, UI.Vision RPA would report the XModules as uninstalled, as it can not find them any longer. If you want to move the location of the folder later, it is best if you first run the uninstall scripts in the old location and then run the 1install.sh installation script again in the new location.
(2.) (Optional) As the last step you can customize the UI.Vision RPA home folder location. By default, UI.Vision RPA uses ' /uivision' as the UI.Vision RPA home directory. If you want to change this, open the UI.Vision RPA browser extension, open 'Settings', go to the 'XModule' tab and enter a new UI.Vision RPA Home folder - macros, testsuites and CSV files will be stored in this folder. To test that everything works correctly, switch UI.Vision RPA to file storage mode.
macOS Mojave: Since the Mojave update macOS has a new security feature. All apps that can control the mouse and keyboard - like the UI.Vision RPA RealUser XModule - need explicit permissions to do so. To add these permissions, go to Settings > Security & Privacy > Privacy > Accessibility option and add allow Chrome and/or Firefox to control your computer. Since UI.Vision RPA 'lives' inside the browsers, the browsers are the apps that need to be added to the accessibility dialog. The FileAccess XModule does not need these permissions.
UI.Vision RPA to control your Mac (RealUser module only)'>
The first time you use a realuser command (XClick, XMove,...) your Mac will ask you to add Chrome and/or Firefox to the accessibility menu. But it does this only once. If you missed the dialog the first time, future realuser commands will fail silently and you need to give Chrome/Firefox the required permissions manually (as shown in the screenshot above).
Xmove Mac Catalina
macOS Catalina: With the Catalina update (10.15) macOS got a new security feature called notarization. In addition to the steps described for Mojave above, you need to explicitly allow the XModules to control the mouse and keyboard of your system. Here is how to do it:
The video and this forum post shows how to enable the XModules on Catalina . This is a one time task. Once all three XModules are allowed to run, everything works fine. Note that unlike in the video, the XModules are meanwhile code-signed and verified by Apple. So the 'developer can not be verified' warning dialog (as seen in the video) no longer shows. We are a registered Apple developer.
macOS Big Sur: Big Sur and the new M1 processor are fully supported. Everything works just as with Catalina.
How to install on Linux
First extract the content of the downloaded ZIP archive to a folder of your choice. Then open a command prompt and navigate to this folder.
Important: Please make sure that the extracted files are executable. If they are not, you need to make them executable with chmod +x before running the 1install.sh script.
(1.) Run the included shell script '1install.sh'. You do this by opening the terminal, navigate to the folder to which you copied the files and type
bash 1install.sh
You should then see messages that say 'Native messaging host... installed'
The installation is done now.
bash 1install.sh
You should then see messages that say 'Native messaging host... installed'
The installation is done now.
Xmove Mac Os
Do not move the XModules folder after the installation. The reason is that the installation script tells Chrome and/or Firefox where to find the the XModules. The files itself are not copied to a new location. So if you would move the folder, UI.Vision RPA would report the XModules as uninstalled, as it can not find them any longer. If you want to move the location of the folder later, it is best if you first run the uninstall scripts in the old location and then run the 1install.sh installation script again in the new location.
Xmovie Maria Valverde Three Stars Above
(2.) (Optional) As the last step you can customize the UI.Vision RPA home folder location. By default, UI.Vision RPA uses ' /uivision' as the UI.Vision RPA home directory. If you want to change this, open the UI.Vision RPA browser extension, open 'Settings', go to the 'XModule' tab and enter a new UI.Vision RPA Home folder - macros, testsuites and CSV files will be stored in this folder. To test that everything works correctly, switch UI.Vision RPA to file storage mode.