Jeramy Thompson

So one thing I wanted to make people aware of is that if you upgrade your host to 5.5U3b, you will break VMware View on version older than 6.2. So why does this happen? With the release of 5.5U3b VMware has disabled SSLv3 http://pubs.vmware.com/Release_Notes/en/vsphere/55/vsphere-esxi-55u3b-release-notes.html Older version of View utilize the SSLv3 to communicate with both vCenter and the ESXi hosts. You may see errors such as: | UFA main thread 16 | FATAL | CommonLib.UfaSubsystem.UfaWorkItem - UFA error: fail in open computer operation. | UFA main thread 16 | INFO | CommonLib.UfaSubsystem.InitializeDiskUfaWorkItem - UFA error: fail to finish init disk operation for disk: datastore: [datastore_name] VMNAME1/VMNAME1-internal.vmdk, host: FQDN, port: 902. | UFA main thread 16 | FATAL | CommonLib.UfaSubsystem.InitializeDiskSetUfaWorkItem - Error: CompletionCallbackProxy failed to init disk with result If you have upgraded your host , you have 2 options. 1. Upgrade to Vi

Ran across an issue with access point the other day where it refused to start. After searching four hours found this post on editing the vmware_ap_supervisord file to fix the stale pid file issue. http://skewedhorizon.loredous.net/2015/12/04/access-point-hard-reset-recovery/

https://pubs.vmware.com/Release_Notes/en/horizon-6-view/horizon-621-view-release-notes.html Ill be upgrading tonight to see if any issues come up.

To go along with my previous post http://jeramythompson.blogspot.com/2015/09/vmware-horizon-access-point-dynamic-ip.html Im adding a new script for dynamically updating a security server. Simply replace the cn=SEC with the name of your security run the scrip on a schedule on your connection server as some one who has access to the ADAM database. Enjoy: https://drive.google.com/open?id=0Bwf718kXFFS8WVVvR1NBS1EtaVU

VMware Access Point GUI 2.0 Hi everyone, so I updated the script, added in some new features and  hope this works better than the last one for every one. Enjoy: For a much Deeper Dive into VMAP, check out Carl's Blog: http://www.carlstalhood.com/vmware-access-point/ Chang Log: Added output box to show submissions (errors are still logged in powershell console) Added pre-check on startup to verify you are on power shell 3.0 or higher Added Get Current Info option to read current settings from VMAP Added Proxy Pattern box to allow changing this to something other than default Re-arranged submission boxs for better flow Add tab ordering to allow tabbing through the fields in the natural order Added Help button, pops up new window with instruction on how to use the script. Cleaned up some of the code Download Link Here https://drive.google.com/open?id=0Bwf718kXFFS8NWdTeFFsQWFMYmM

So I was interested in getting OSX running my my T520. I had looked into this about a year ago with no luck, but now there is a great write up for it by the guys over at insanelymac.com on how to do this. After doing my own research to get the required parts , software etc I now have a core i7 , 16GB (ill explain later) , and a 250GB SSD that makes OSX scream on this awesome piece of hardware. So to get started the first thing you are going to need is a whitelist bios patch for the Bios and can be found here: https://www.bios-mods.com/forum/Thread-REQUEST-Whitelist-Request-ThinkPad-T520-v1-43-8auj24us-exe Get the 1.44 versoin and flash your bios per the readme included, once its flashed install a OSX compatible WiFi card. Lenovo locks their laptops to intel only WiFi cards. Unfortunately there is little to no support for these on OSX so the best thing to do is replace it with a compatible card. These can be found on ebay for about $5. In my case I purchased a used Ather

VMware Horizon Access Point - Dynamic IP update powershell script. Some of us do not have labs at work, a tend to like to test things out before deploying them into production. Since i have a dynamic IP i wrote this powershell script to update my VMware Horizon Access Point every day. Enjoy To run my power shell script, since its not sighned , you have to allow power shell to run unsigned scripts run to following to allow it to run open power shell as administrator Set-ExecutionPolicy Unrestricted Update the following variables: Find this line: $pwd = ConvertTo-SecureString "P@$$w0Rd!" -AsPlainText -Force replace P@$$w0Rd! with your actual password for the access point Next find this line: $cred = New-Object Management.Automation.PSCredential ('admin', $pwd) replace 'admin' with the user you setup during install lastly find $proxyDestinationUrl = "cs.home.lab" replace cs.home.lab with the internal DNS of your home lab That is