Here are some common settings that can be changed in CrossOver's defaults file.Ĭhange where a user's bottles are located. Copy that file into the same location in a user's account and CrossOver will have the same preferences when launched. CrossOver's defaults file is located in ~/Library/Preferences/. This can be done either by running scripted commands in each user account or by preparing a ready-made defaults file. Sysadmins may want to modify some of CrossOver's default behavior before distribution. Providing custom or ready-made Preferences Make sure you distribute the icons that refer to the published bottle. One points to your private bottle, and the other to the published bottle. ![]() Note that after publishing a bottle, you will have two sets of icons. Once CrossOver is launched via the icon, it will check the icon file and may replace it with a similar system-local icon if necessary. Copying the icon from one machine to another will still work, as long as the bottle path is the same on both. If you can automatically add icons to users' docks, you might want to consider including icons from CrossOver in your distribution package. Users on that system only need to run CrossOver once after the bottle has been added, at which point CrossOver will create any icons that are a part of that bottle.ĭepending on your needs and network configuration, you may wish to provide some or all of the following customizations before pushing packages out to the target machines. The default location to make the bottle available to all users is /Library/Application Support/CrossOver/Bottles. To distribute a published bottle to another Mac, you can simply copy it to the same location on the new system. Other users cannot see changes to a published bottle until it is updated with the Bottle>Update Published Bottle menu item. The stub bottle is named the same as the published bottle it refers to. ![]() These stub bottles store a user's customized changes to the bottle and have symbolic links that direct back to large files and directories in the published bottle. When a user opens a published bottle, a stub bottle is generated in their home account. Other users on the computer can now log in, launch CrossOver, and have access to the Windows applications in the published bottle. The published bottle will appear in the left-hand sidebar of CrossOver. ![]() ![]() Enter an administrator account password and CrossOver will publish the bottle. It's recommended to keep this name so you can reference which initial bottle was used. Finally, go to the Bottle menu > Publish Bottle.īy default, the published bottle will be named published_ExistingBottleName. Then remove any private data from the Windows applications (for example, cached passwords and user names). Start by installing the Windows application you want to share into a new bottle. A Published Bottle allows all the users of a single system to share a single installation of each Windows application in the bottle. Publishing BottlesĬrossOver supports rolling out Windows applications to many users and on many systems through the use of the Publish Bottle command. You should not attempt any of these procedures unless you have passing knowledge of the command line since many of these sections require text commands to be used. Most users will not need to use the instructions in this chapter.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |