Leave a reply

ending the week on a high note

nothing like ending the week on a high note. Been running RecoverPoint for VM for the past few weeks with lack luster results with the same level of support. Replication was painfully slow along with a UI that was severely lacking in features. However, after setting up Zerto, which took about 15 minutes or so, I was already replicating a 9.4TB VPG, with an ETA of 20h.  This same VPG in RP4VM nearly took 2 weeks to replicate.  Even after increasing the RPA resources to 8vCPU and 16GB RAM, we only ever got 11MB/sec at best.  With Zerto I’m seeing 112MB/sec constant.

 

Next week, I’ll have enough information to make the case to go with Zerto and drop RP4VM

 


Leave a reply

Windows Update Error 8024402F

I’ve recently built a new W7 VM for AppVolume provisioning, however, when trying to install windows updates, I get the following

 

For whatever reason, my new Windows build couldn’t contact the MS Windows Update servers.  After some Googling, I ran into a post saying to add windowsupdate.microsoft.com to the list of trusted sites.  After putting that in, I was able to update the OS.

 

 

 


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”)

 


Leave a reply

Reclaiming Free Space

I was tasked earlier in the week to reclaim free space from VMs that have been deleted or from snapshots that have been consolidated.

What I discovered was that from vSphere 5.0 to 5.5 had the ability but was disabled by default due to performance issues on the arrays during reclamation.  However, reclamation can still be done manually by issuing the following command

esxcli storage vmfs unmap -l <datastore name>

What is happening here is that when a VM is either deleted, moved due to SvMotion, or snapshots deleted/ consolidated, the VMFS datastore sees that space has been freed up, but not reported back to the array, and still holds on to that space.  So in the vCenter client, you’ll see the amount of free space available to you right away, but you’ll the LUN reporting a different number. I think this is normally not an issue as long as your datastores don’t fill up or if you’re running alerts against the datastores and not the array.

In any case the above command reclaims the space, but depending on how big the LUN is, it can take long time.

For example, to reclaim 50% of free space from a 8TB LUN took about 11 hours.

Good news, VMware had re-implemented the SCSI UNMAP commands in 6.5

Please keep in mind the scsi unmap command needs to be run from the host console.


Leave a reply

Trouble installing applications

The last few months I’ve had some issues installing certain applications.  Some applications would be looking for the msi in the Windows temp directory, in one instance, VAMT would fail with Error 1651.

Well, I’ve finally resolved the issue with the following:

https://support.microsoft.com/en-us/help/17588/fix-problems-that-block-programs-from-being-installed-or-removed

According to the website, the following is fixed:

    • Corrupted registry keys on 64-bit operating systems
    • Corrupted registry keys that control the update data
    • Problems that prevent new programs from being installed
    • Problems that prevent existing programs from being completely uninstalled or updated
    • Problems that block you from uninstalling a program through Add or Remove Programs (or Programs and Features) in Control Panel

To fix my issues I would select the application that is giving me a problem, select uninstall, and then re-run the installation.

 


Leave a reply

MacOS on vSphere ESXi 6.0

I recently installed MacOS High Sierra (10.13) on ESXi 6.0 for a developer I work with.  The steps I used were from a number of sources found on the InterWebs.

First off you need a Mac to download the installer. On the Mac, go to the App Store and and download MacOS.  While that is downloading, you’ll need to run the Unlocker script found at insanelymac.com.  Please read the notes thoroughly, and yes, a reboot of the host is needed.

After the installer is downloaded, you will need to create the ISO. The following steps are all done on the Mac

Mount the installer:
hdiutil attach /Applications/Install\ macOS\ High\ Sierra.app/Contents/SharedSupport/InstallESD.dmg -noverify -nobrowse -mountpoint /Volumes/install_app

Then create a blank ISO
hdiutil create -o /tmp/HighSierra.cdr -size 7316m SPUD -fs HFS+J

Then mount the blank ISO
hdiutil attach /tmp/HighSierra.cdr.dmg -noverify -nobrowse -mountpoint /Volumes/install_build

Then restore the base image to the blank ISO
asr restore -source /Applications/Install\ macOS\ High\ Sierra.app/Contents/SharedSupport/BaseSysyem.dmg -target /Volumes/install_build -noprompt -noverify -erase

copy the install dependencies
cp /tmp/HighSierra.dmg /Volumes/OS\ X\ Base\ System/

unmount installer image
hdiutil detach /Volumes/OS\ X\ Base\ System

convert to iso
hdiutil convert /tmp/sierra.cdr.dmg -format UDTO -o /tmp/HighSierra.iso

rename to iso and place on Desktop
mv /tmp/HighSierra/iso.cdr ~/Desktop/HighSierra.iso

Enjoy on non Apple Hardware!

 

 

 

 


Leave a reply

listing vms from a portgroup

I was recently asked to get a list of all VMs in a certain VLAN along with OS and IP address.  To do that…

get-vdportgroup “<name of port group>” | get-vm | get-guest | select vm, ipaddress, osfullname | ft -autosize

if you happen to be on a standard switch, replace get-vdportgroup with get-virtualportgroup -name <name of portgroup>

 


Leave a reply

Vendor mismatch has been detected

I recently updated my Nexus 9 to the nightly build of LineageOS 14.1 October 10.  The normal update went smoothly.  However, after rebooting, I was greeted with “A vendor mismatch has been detected.  Typiucally this means yopur vendor image is out of date.  Please ensure that your vendor image matches N9F27M”

According to Lineage, the nightlies are based on the October monthly updates from Google.  Which means the vendor image needs to be extracted from the factory image from Google and updated on the Nexus 9.

Once the vendor img has been extracted or downloaded, you’ll need to use adb fastboot to install it.

  • Connect to N9
  • adb reboot bootloader
  • fastboot devices
  • fastboot vendor vendor-flounder-n9f27m.img
  • fastboot reboot

N9 will reboot and you should no longer get that popup box


%d bloggers like this:
Bitnami