05.05.2020

Client Update Wont Launch For Mac

31
Client Update Wont Launch For Mac Average ratng: 7,4/10 3540 votes
  1. My Mac Won T Update
  2. Windows Update Won't Launch
  3. Mac Won't Update Os
  4. My Mac Won't Update Software

Seamlessly install, update and launch into your favorite online games all in one place. Browse and download games with a beautifully designed easy-to-use interface. Stay Connected. Steam won't launch after update. No steam update nothing!, it just won't start my other application's are working fine. I'm running on mac os x 10.6.8 snow leopard. On the Mac, go into your Applications Folder and find the Steam Application. Drag it into the trash.

Last year, a standalone Virtual Machine Remote Console (VMRC) was released for Windows as part of vSphere 5.5 Update 2b which provides an alternative way of launching the VM console due to NPAPI deprecation. There was of course a huge request for Mac OS X support and the VMRC team has been working hard and today I am please to announce that standalone VMRC is now available for Apple Mac OS X which you can download using the following URL: www.vmware.com/go/download-vmrc

Note: Mac OS X 10.8 or greater is required to use the new Standalone VMRC. The release notes will be updated to reflect this requirement

There are currently two methods of launching a remote console to a Virtual Machine using the vSphere Web Client as seen in the screenshot below:

  1. Using HTML5 VMRC simply by clicking on the thumbnail preview
  2. Using the new Standalone VMRC by clicking on the 'Launch Remote Console' link


When using the Standalone VMRC method, instead of opening the VM console in the browser, it will launch the native VMRC application on your system whether that be Windows or Mac OS X. All basic functionalities of the Standalone VMRC is available as you would expect such as power operations, device management, etc.

Note:There is not a specific version of vSphere that is required to directly launch the Standalone VMRC. However, to launch it within the vSphere Web Client, you will need vSphere 5.5 Update 2b or greater.

My Mac Won T Update


The other great thing about the Standalone VMRC is that it can function without vCenter Server and the vSphere Web Client and you can actually use it to connect to VM directly on an ESXi host. To use the VMRC without the vSphere Web Client, you will need to construct the VMRC URI which looks like the following:

vmrc://clone:[TICKET]@[HOST]:[PORT]/?moid=[VM-MOREF]

where TICKET is obtained by calling the AcquireCloneTicket() method using the SessionManager in vCenter Server. The HOST will either be the Hostname/IP Address of vCenter Server and the PORT should be default to 443 and you will need to specify the VM MoRef ID. In the case of a standalone ESXi host, you would just change the HOST property. If you do not wish to use the clone ticket, you can also just provide the following URI which will prompt for your ESXi credentials

Ssh client for a mac. The first approach is to type ssh hostname or ssh user@hostname into the terminal window. This is more familiar for Linux and Unix users who are used to using a command line.

vmrc://@[HOST]:[PORT]/?moid=[VM-MOREF]

Once you have generated the VMRC URI, you MUST launch it through a web browser as that is how it is passed directly to the Standalone VMRC application. In my opinion, this is not ideal especially for customers who wish to automatically generate this as part of a VM provisioning workflow to their end users and not having to require a browser to launch the Standalone VMRC application. If you have some feedback on this, please do leave a comment.

In the mean time, a quick workaround is to use the 'open' command on Mac OS X along with the VMRC URI which will automatically load it into your default browser and launch the Standalone VMRC application for you.

open 'vmrc://clone:cst-VCT-52e44ad7-712f-9f45-a9ee-13ec6a74acaf-[email protected]192.168.1.60:443/?moid=vm-18'

UPDATE (05/31/15) - If you are connecting directly to an ESXi host you can either use the vSphere API to query for the VM MoRef ID or you can easily pull it by running the following command directly in the ESXi Shell:

vim-cmd vmsvc/getallvms

I am sure there are probably a few of you asking, what about for Linux users? Well, you can probably guess what is being worked on next 😉

More from my site

Join GitHub today

GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.

Sign up New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Comments

commented Jul 5, 2015

It tells me I'm updated and everything but when I launch the client it simply opens the console and it stays blank

commented Jul 5, 2015

For me it says 'Could not find or load main class mage.client.MageFrame' in client console and 'Could not find or load main class mage.server.Main' in server console
Already forced update, no improvement.

Update

commented Jul 5, 2015

What os and os version is used?
I found this:
http://www.slightlymagic.net/forum/viewtopic.php?f=70&t=16358&p=169586&hilit=mage.client.MageFrame#p169579
Delete the 'installed.properties' file in the directory of the XMage launcher.
Then all should be again downloaded and installed.

commented Jul 5, 2015

Tried that, doesn't work for me, same problem persists

commented Jul 5, 2015

Also there is nothing in my xmage folder, if that helps

commented Jul 5, 2015

Operating system?
Some mac OS users had problems in the past. There is a XMage home
http://xmage.de/xmage_mac
that you can set in the launcher settings.
That uses still an old launcher version that seemed to work on macs.

commented Jul 5, 2015

Using Windows 7 64 bit so OS probably isn't a problem. Anyone know of any links to old versions of the launcher?

commented Jul 5, 2015

You can set the xmage home in the launcher to:
http://xmage.de/xmagelauncher31
to get the old launcher and the current xmage release.

commented Jul 6, 2015

Yep, still does the exact same thing for me

commented Jul 6, 2015

I can imagine 2 possible reasons now:

  1. Windows Firewall blocking (check in the setting of windows firewall that 'Java(TM) Platform SE binary' is allowed to cross the firewall).
  2. Problem with the file path you located the launcher.jar. Maybe it can help to use another directory, best with no blanks or special chars in the complete path.

added the launcher / installation label Jul 6, 2015

commented Jul 6, 2015

The firewall is what it was. Thank you very much!

commented Jul 6, 2015

I can confirm that after updating to 1.4.2.v1 everything works fine again. Launcher 'updated' itself to v0.3.1.
Thanks for the effort.

commented Jul 6, 2015

I can confirm that after updating to 1.4.2.v1 everything works fine again. Launcher 'updated' itself to v0.3.1.

You're using a mac?
And the default launcher did not work?

commented Aug 9, 2015

Windows Update Won't Launch

Using Windows 8.1 (64 bit).
Initially when running client nothing happened, checking logs:

I created 'mage-client' folder inside xmage folder, but now the error is: 'Error: Could not find or load main class mage.client.MageFrame'.

• Run in Terminal app: ruby -e '$(curl -fsSL /dev/null and press enter/return key. Shrew vpn client for mac. If the screen prompts you to enter a password, please enter your Mac's user password to continue.

Now I suppose maybe is something related to Java, doing java -version in console I get:

as this program requires other version maybe is something there..

I don't know, some help is appreciated.

commented Aug 9, 2015

There was also for some people a problem with the launcher 34.
Please try if it helps to use the old launcher 31.

To test this you can switch the xmage home in the launcher settings to
http://xmage.de/xmagelauncher31
update the launcher and reinstall java with the launcher if needed.

commented Aug 9, 2015

I don't know if I did what is need, if you can be my explicit.

Exactly what I did:

  • download launcher from http://xmage.de/xmage/XMageLauncher-0.3.1.jar
  • edited from installed.properties part:

complete file after install:

Now log file is:

and yes, still nothing works,

commented Feb 28, 2017

Mac Won't Update Os

I'll close this issue because it seems to be outdated but feel free to create a new one if this problem still exists.

commented Jan 12, 2018

Update

Specify this for the Mage Client Main Class:
mage.client.MageFrame
Sometimes, it doesn't automatically find it.

My Mac Won't Update Software

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment