Jump to content
Welcome to InsanelyMac Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.


  • Content count

  • Joined

  • Last visited

About ipas

  • Rank
    InsanelyMac Protégé
  1. Indeed.. and I'm very happy with this patch anyway. I will test the configuration with another machine with different hardware to be sure. If there is another outcome i'll let you know. ... tested this on the other esx server: Have not seen the 503 error, but also got the console issue.
  2. A bit true but the only limitation Vcenter had with with version 5.1 and earlier is not having the ability to start/stop a OSX VM with Vcenter. I could easily bypass this connecting directing to the patched host using the Vsphere Client. The management interface of the host itself seems unstable now and the Vcenter webconsole of every VM of the patched host is not working anymore.
  3. Unfortunately I have some critical problems with osx-unlocker version 1.2 on Vsphere ESXi 5.5. I got two issues: 1. The management webservice seems unstable. I got a "503 Service unavailable" after a boot of the esxi server. When I restart de management interfaces in the console the webservice is sometimes running. 2. Opening a console in VCenter Web Client does not work anymore. Got this error: "Unable to connect to the MKS: The operation is not allowed in the current state". Sometimes I got this error also: "Unable to connect to the MKS: A general system error occurred: Invalid response code: 503 Service Unavailable". After uninstalling the unlocker these problems disappear.