UPDATED: November 11, 2014.
Does Moka5 support Apple OS X 10.10 (Yosemite)?
Moka5 4.1.2 and Moka5 4.0.5 include an integrated version of VMware Fusion 7 and support for Apple OS X 10.10 (Yosemite). Please see the
4.1.2 and
4.0.5 Release Notes for information on how to upgrade your installation.
Can Moka5 users upgrade to Yosemite now?
Advise your users not to upgrade to Yosemite unless they are running Moka5 4.1.2 or 4.0.5. Users who upgrade to Yosemite and run pre-4.1.2 or pre-4.0.5 versions of Moka5 may not be able to launch their LivePCs.
What is the expected behavior if Moka5 users upgrade to Yosemite anyway?
Moka5 Version | Supported VMware Fusion Version | Expected Behavior | Support Guidance |
---|
3.18 - 4.0.4 | 6.0.2 - 6.0.3 | Unable to launch LivePCs on Yosemite. | This configuration is not supported by Moka5 or VMware. |
4.1 - 4.1.1 | 6.0.4 | LivePCs will launch, but may have significant compatibility/performance issues. | This configuration is not supported by Moka5 or VMware. |
4.1.2 | 7 | LivePCs launch and run normally. | This is a supported configuration. |
4.0.5 | 7 | LivePCs launch and run normally. | This is a supported configuration. |
How can I prevent users from upgrading to Yosemite ahead of Moka5 support?
While there is no technical control that can be used on unmanaged hosts to restrict users from upgrading, we have created a sample host script that can be run automatically at Player launch to help educate users on the implications to their Moka5 experience of upgrading to Yosemite ahead of Moka5 support for it.
What does the host script do?
The host script displays a warning message instructing users not to upgrade to Yosemite. This message displays every time the Moka5 Player launches, until the user clicks a checkbox acknowledging that they have read the message. Once they click the checkbox, the message will no longer be displayed and the action will be reported to the server so that admins can track in the Console which users have clicked the checkbox.
How can I implement this host script?
To implement this host script, upload the .zipped host script bundle to your Management Server and use Player Policies to target it to applicable user groups. The Management Server delivers the host script bundle to the targeted users as part of the Moka5 Player update process. Once the users apply the update, the host script will run automatically on Player launch. Note that if you have already deployed a Mac host script bundle, you will want to modify the existing bundle to include this new host script, rather than replace the existing bundle.
What if I want to make changes to the host script?
You can customize the text that displays in the host script by making changes to warning.txt. Making changes to elements of the host script allow you to display different messages.
You can customize the window title, the header, the body text, and the acknowledgement checkbox text.
To change the title or header text, open tasks.xml in a text editor. Find the following line:
<command>Warning\ Dialog.app/Contents/MacOS/warning-app --file warning.txt --title “Warning” –-header “Please don’t upgrade to Mac OS X 10.10 yet!” --ack 1 –-ack_text “Don’t remind me about this again.”</command>
Modify the text highlighted in yellow above to change the title and header. The title can contain up to 20 characters, and the header can contain up to 200 characters.
To change the body text, open warning.txt in a text editor. Make text changes up to 2MB in size, and save the file.
Set ack to 0, rather than 1, to disable the acknowledgement checkbox. The checkbox text can contain up to 40 characters.
Users who check the box will not see the warning message again. Checking the box sends a notification to the Moka5 Server that the warning has been read and acknowledged. Admins can then track in the Console which users have clicked the checkbox.
For more information on how to use information sent by host scripts to the Moka5 Server, read
this section of the Knowledge Base article on host scripts.
What if I already have a host script bundle running?
If you're already using host scripts, you can add the warning message by adding the downloaded Warning Dialog.app directory to your host script bundle, and modify your existing tasks.xml. The new tasks.xml should look like this:
<?xml version="1.0" encoding="UTF-8"?>
<tasks>
<!--Warning script configuration -->
<task name_id="Warning_Mac_v1" version="7/24/2014">
<enable>true</enable>
<command>Warning\ Dialog.app/Contents/MacOS/warning-app --file warning.txt --title "Warning" --header "Please don’t upgrade to Mac OS X 10.10 yet!" --ack 1 --ack_text "Don’t remind me about this again."</command>
<context>user</context>
<launch>on player start</launch>
<output>
<stdout>
<format env="true">kvp</format>
</stdout>
</output>
</task>
<!--Old script configuration -->
<task name_id="Old_host_Script" version="1/1/2014">
<enable>true</enable>
<command>python Old_Host_Script.py </command>
<context>user</context>
<launch>on player start</launch>
<output>
<stdout>
<format env="true">kvp</format>
</stdout>
</output>
</task>
</tasks>
How do I let my users know when it’s okay to upgrade to Yosemite?
Click this link to download a host script that notifies users that it is safe to upgrade to Yosemite.
Upload this new host script bundle to your Management Server to replace the warning host script bundle. Target the new host script bundle to the same groups, then deploy the Player update. The new host script will display when the updated Player launches. Note that if you have other host scripts in your Mac host script bundle that you would like to continue to run, you will want to modify the existing bundle to include this new host script, rather than replace the existing bundle completely.
Alternatively, use the customization process outlined above to modify the existing warning host script with new text to indicate that it is safe to upgrade to Yosemite.
If you choose to modify the deployed warning host script rather than replace it, note that users who have clicked the acknowledgement checkbox do not see the host script message. To make sure that users who have clicked the checkbox are notified that it is now okay to upgrade to Yosemite, you must clear the checkbox so the host script message will display again.
To clear the checkbox, modify the task name_id tag in tasks.xml. This clears the checkbox and forces the message to display on Player launch. For example:
Changing <task name_id="Warning_Mac_v3" version="1">
To <task name_id="Warning_Mac_v4" version="1">
Ensures that the message displays to users on Player launch.