• 20Jul

    How to reduce the migration time on a datacenter move to the absolute minimum?  Powershell helps hugely with this as there are a large number of mouse clicks required to re-import the virtual environment.  More details on the move to follow, but for now lets get started.

    Go and install powershell on your windows machine, and then go to the vmware site to download their VI-plugin.

    Once installed, you can launch from the vmware folder group, but you may get an error when launching due to the unsigned script.  You can ignore this but it may cause you further issues later.

    If you get this you’ll see this:

    File C:\Program Files\VMware\Infrastructure\vSphere PowerCLI\Scripts\Initialize-VIToolkitEnvironment.ps1 cannot be load
    ed because the execution of scripts is disabled on this system. Please see "get-help about_signing" for more details.
    At line:1 char:2
    + . <<<<  "C:\Program Files\VMware\Infrastructure\vSphere PowerCLI\Scripts\Initialize-VIToolkitEnvironment.ps1"
    PS C:\Program Files\VMware\Infrastructure\vSphere PowerCLI>

    To resolve, you need to set the signing to allow the VMware bits to all run properly.  Most cmdlets will be fine, and I only ran into problems with this when I tried to use the AnswerVM class which didn’t exist.

    Note: this will remove your security on running scripts, so only do this if you are comfortable with the implications - don’t let any code run you’re not happy with and understand fully.

    set-executionpolicy unrestricted

    Then exit the shell, and restart - it will now look like this:

    VMware powershelll startup

    VMware powershelll startup

    Posted by Jamie @ 11:28 am

Leave a Comment

Please note: Comment moderation is enabled and may delay your comment. There is no need to resubmit your comment.