Month: April 2018

Leave a reply

using Runonce to move VM to different OU

If you are using Horizon View and creating full clones, undoubtedly you’ve run into the issue of having the VM joining the domain but placed in the wrong OU.   To get around this you either moved it yourself, have a GPO do it or some VBScript.

After many searches and trial and errors, I’ve finally got it working in my environment.

In the customization specification, I have the VM join the domain using the UPN format, user@domain.com, then in the Runonce field I have the following:

cmd.exe /c dsmove -u user@domain.com cn=%computername%,cn=computers,dc=domain,dc=com -d domain.com -newparent "ou=NEW OU,dc=domain,dc=com" -p "P@ssword"

To get this to work, you’ll need to copy dsmove.exe and dsmove.exe.mui from a another computer that has AD tools installed.

You’ll need to copy dsmove.exe from c:\windows\system32 and dsmove.exe.mui from  c:\windows\system32\en-us and place them in the same folders on your image\template.

Please keep in mind this tested and verified on Windows 7,  other Windows versions may be different.  So please test thoroughly.

Hope this helps anyone using Horizon View using full desktops or manual pools.


Leave a reply

Certificates

i hate dealing with them….


Leave a reply

multiple sVmotions via powercli

I’m currently working on a project to move our server VM infrastructure from our old VMAX3 to a new all flash VMAX 250F SAN.   So for my own sanity sake, and to save myself from one less Google search, below is what I used to sVmotion all VMs from the “old” LUN to the new LUN

get-datastore “old-datastore” | get-vm | move-vm -datastore(get-datastore “new-datastore”)

 


%d bloggers like this:
Bitnami