TestingThe to fivepackage canatonly be deployed using Casper Remote not a policy , and can only be pushed computers a time. Non-DeployableThe be deployed. This setting out of productionpackage cannot licensing or other reasons. Allow Uninstall Selecting this option allows administrators to uninstall a package using a policy or Casper Remote.
Administrators will not be able to uninstall a package using a policy or Casper Remote unless this option is selected. Some packagesfor example, operating system updates and security updatesshould not be uninstalled, since they contain files required to boot the client computer.
Note: A package must be indexed before this option can be selected. For more information on indexing packages, see the Indexing Packages section. OS Requirements If certain operating system requirements are needed to install a package, specify the requirements in this field using the following guidelines:. If a package can be installed on any version of Mac OS X If a package can only be installed on Mac OS X If the entry has more than one requirement, separate each requirement with a comma.
If a package does not have any operating system requirements, leave this field blank. You can specify this information by selecting this option and choosing PowerPC or X86 from the pop-up menu.
To install an alternate package if a non-compliant architecture is encountered, choose an alternate package from the If the target computers processor is not there pop-up menu.
For this feature to work properly, you must remove the. If this still does not work, run the following command in a Terminal window: softwareupdate l. It is important to ensure the information provided in the Display Name field matches the name of the package that is displayed in Software Updates command-line version. Note: This option is only available for PKG-style packages.
If you download installer media directly from Adobe, it is already in disk image format. Open Disk Utility from the Utilities folder. Click the DVD button in the sidebar. Save as a compressed disk image. This copies the disk image directly to the master distribution point. After Casper Admin copies the disk image, the Info pane is displayed.
If it does not appear, click the Info button in the toolbar. It can take Casper Admin up to 30 seconds to analyze the contents of the disk image. When this process is complete, the Options pane appears and a list of payloads available with the installer is displayed.
Click the New Adobe Install button in the toolbar. If you have multiple Adobe Installer Images, choose the one on which you want to base your installation from the Installer Image pop-up menu. If you have more than one Adobe Installer Image, choose the image on which you want to base your installation from the Installer Image pop-up menu.
Click the Options tab and set the installation options. For more information about these options, see the Options for an Adobe Install section. Options for an Adobe Installation The Options pane lets you specify the following information for an Adobe installation: Priority Setting the priority determines the order in which packages are installed. Serial Number Providing this information identifies the serial number of products you are installing.
Suppress Installer Dock Button An Adobe Installer icon will appear in the Dock of any logged-in user even if the installer is deployed in silent mode. Selecting this option ensures that the icon does not appear in the Dock. Common conflicts include Safari, Firefox, and Microsoft Office applications. Selecting this option prompts the installer to ignore these conflicts.
As a result, any plug-ins installed for applications that are running during the installation will not be available until the applications are re-opened.
You can use a single Adobe Installer Image to create multiple distributions of Adobe products that may contain different sets of the payloads. Suppress Registration Ensures that users are not prompted to register Adobe products. Suppress Updates Ensures that users are not prompted with available Adobe updates when using Adobe applications. Stage You can set limitations on the use or deployment of a package by choosing one of the following options from the Stage pop-up menu:.
TestingThe to fivepackage canatonly be deployed using Casper Remote not a policy and can only be pushed computers a time. Allow Uninstall If you want the ability to uninstall the contents of your Adobe Install, select this option to make the Uninstall feature available when using Casper Remote or a policy. The Adobe Silent Installer is used to uninstall software. Adding a Disk Image of an Adobe Updater Most Adobe updates available for download on the Adobe support website are already in disk image format.
Updaters that support silent installation can be installed without repackaging. If you add the disk image to Casper Admin and it is not recognized as an Adobe Updater, it is possible that the updater does not support silent installation. To add an Adobe Updater disk image: 1. Drag the disk image of the Adobe Updater into Casper Admin. When this process is complete, the Options pane appears and a list of payloads available with the updater is displayed.
If you download installer media directly from Apple, it is already in disk image format. You can use a single image to create multiple installations, each with custom software and language settings. Open Disk Utility from your Utilities folder. When this process is complete, specify a default language for the installation from the Language pop-up menu. Click the link for the Mac OS X installation on which you want to base the new installation.
Indexing Packages Indexing creates a log of the individual files contained within a package. If prompted, authenticate to the JSS. Select the package that you want to index in the Package pane, and then click the Index button at the bottom of the pane. The user name for an account on the client computer is displayed by default.
Specify the corresponding password, and then click OK. When the indexing process is complete, Casper Admin defaults back to the main window. Enabling the Self Healing Feature Self Healing is a maintenance feature used to ensure that the files from a package remain in their originally configured state on the client computer.
For instance, if the permissions for an application installed on a client computer are changed due to an overwrite, Self Healing will detect the change and reinstall the application as originally configured. Self Healing determines whether a maintenance action is needed by comparing the files in a package to those on the client computer.
If the files on the client computer do not match those in the package, a Self Healing action is triggered. Triggering files to time, the does These are the files that you wantfiles,monitor for changes. If, at any specified client computer not contain matching triggering Self Healing will perform the Self Healing actionsThere are three maintenance actions that SelfinHealing can perform in the event that the triggering files on the client computer do not match those the package: Reinstall the Entire Package Reinstall the Triggering File Send an Email Notification maintenance action.
There are two components that make up the Self Healing process:. The instructions in this section explain how to specify these components of the Self Healing process. Note: Before you enable Self Healing on a package, the package must be indexed. See the Indexing Packages section for details. To enable Self Healing: 1. In the list of packages, click the link for the package on which you want to enable Self Healing. If you do not want the package to be reinstalled, select the Do Not ReInstall option.
If you want an email notification to be sent each time a Self Healing event takes place, select the Send Email Notification option. Click the Self Healing tab and select a reinstallation option:. Use the Compare pop-up menu to specify the type of change that you want to monitor for each triggering file.
For instance, if you select File Exists from the pop-up menu, Self Healing will be triggered if the triggering file does not exist on the client computer. If you select Permissions from the pop-up menu, Self Healing will be triggered if the permissions for the file on the client computer do not match those in the package.
When you delete a package, the package file is moved from the Packages folder to the Deleted Packages folder that is located in the Casper Data folder. To permanently delete the package, empty the trash after the package has been deleted. After a package is deleted, change the stage to Deleted so it cannot be used. Open Casper Admin, and make sure the Repository list is highlighted in the sidebar. Select the packages that you want to delete.
Click OK to confirm the deletion. To delete a package using the JSS:. Click Casper Admin link. In the list of packages, click the link for package that you want to delete. Click the Options tab and choose Deleted from the Stage pop-up menu. To empty the trash using Casper Admin:. Click the Deleted Items button in the toolbar and click Empty Trash.
Managing Scripts Add new scripts Change script attributes Delete scripts This section explains how to do the following:. Drag the script into Casper Admin Copy the script directly to a distribution point There are two ways to add a new script to Casper Admin. Dragging a Script into Casper Admin When you drag a script into Casper Admin, it is copied to the master distribution point and displayed in blue text in the Unknown category until you assign it to a software category.
To add a script using Casper Admin: 1. Drag the script from the Finder into the Package pane in Casper Admin. Copying the Script Directly to the Distribution Point This method copies the script to the Scripts folder at the root of the file share.
You can enter information about the script into the JSS manually. If you open Casper Admin after adding the script, the name of the script is displayed in blue text in the Unknown category in the sidebar. To add a script manually: 1. Add the script to the Scripts folder on your distribution point. Click the New Script button and enter information about the script on the Info pane. Note: The information entered in the File Name field must match the name of the file exactly. Changing Script Attributes You can change the attributes that determine how a script is executed.
Select the script that you want to change. To change script attributes using the JSS:. Click the Casper Admin link and click the name of the script. Summary Pane This pane displays an overview of the script. The button labeled Reveal in Finder displays the script in a Finder window. The following attributes are displayed on this pane: Display Name This is the customizable name that identifies a script when it is displayed in a list of scripts or policies.
The display name does not have to match the name of the script file. File Name This is the name of the script file. Category This identifies the organizational category to which a script belongs. Info The information displayed to the administrator when a script is being deployed.
They are helpful when tracking information about a script, such as who created it and when it was created. Options Pane This pane lets you specify deployment information and limit the operating systems on which a script can be run. The following attributes are displayed on this pane: Priority This determines the order in which scripts will run.
For example, you can specify whether a script should run before the imaging process, after the imaging process, or the first time the computer boots after imaging. Parameter Labels Three parameters are predefined for every script by default, but you can assign up to eight additional parameters. You can specify names for these additional parameters in the Parameter Labels fields. If you do not specify a name, the script will be displayed as Parameter x in deployment interfaces.
Stage You can limit how a script is used and deployed by choosing one of the following options from the Stage pop-up menu:. TestingThe script can only be five client computers at a time. This setting is useful if the script needs to be taken out DeletedThe script has been deleted from Casper Admin. OS Requirements If certain operating system requirements are needed to run a script, specify the requirements in this field using the same guidelines that you would use for a package see the Managing Packages section.
When you delete a script, the script file is moved from the Scripts folder to the Deleted Scripts folder that is located in the Casper Data folder. To permanently delete a script, empty the trash after the script has been deleted.
After a script is deleted, change the stage to Deleted so it cant be used. Select the scripts that you want to delete. To delete a script using the JSS:. In the list of scripts, click the link for the script that you want to delete. Click the Empty Trash button in the toolbar. Managing Printers Add a new printer Change printer attributes Delete printers This section explains how to do the following:.
To add a printer using Casper Admin: 1. Click the Add Printers button in the toolbar. Authenticate locally if prompted. Select the checkbox next to each printer you want to add. Using the Category pop-up menu, choose the category to which the printers should be added, and then click the Add button. Changing Printer Attributes Printers, like packages and scripts, have attributes that determine how they are organized and deployed.
Select the printer. To change printer attributes using the JSS:. Click the Casper Admin link and click the printer name. Summary Pane This pane displays an overview of the printer. The following attributes are displayed on this pane: Display Name This is the customizable name that identifies a printer when it is displayed in Casper Imaging, Casper Remote, or policies. Category This identifies the organizational category to which a printer belongs.
Info The information displayed to the administrator when a printer is being deployed. They are helpful when tracking information about a printer or package, such as who created it and when it was built.
Options Pane This pane lets you specify deployment information and limit the operating systems to which a printer can be mapped. The following attributes are displayed on this pane: Stage You can limit how a printer is used and deployed by choosing one of the following options from the Stage pop-up menu:. Non-DeployableThe out of productionprinter cannot be deployed.
This setting is useful if the package needs to be taken temporarily for licensing or other reasons. DeletedThe printer has been deleted from Casper Admin. Deleting Printers If you no longer need a printer, you can delete it using Casper Admin.
After a printer is deleted, change the stage to Deleted so it cannot be used. Select the printers that you want to delete. To delete a printer using the JSS:.
In the list of printers, click the link for printer that you want to delete. To empty the trash using the JSS:. To add a Dock item: 1. Click the Add Dock Items button in the toolbar. Select the checkbox next to each item you want to add, and then click the Add button. To delete a Dock item: 1. Select the items you want to delete.
You can create the following directory bindings:. The instructions in this section explain how to create each directory binding. To create an Active Directory binding: 1. Click the New Directory Binding button in the toolbar. Enter a display name for the binding. This is an arbitrary name that allows you to choose the correct binding if more than one exists.
Enter the Active Directory domain. Specify the user name and password for an Active Directory account that has permissions to add computers, and enter the password again to verify it. If you are binding client computers with more than one directory binding, use the Priority pop-up menu to assign the order in which the bindings should be applied.
The information specified on these panes is the same information entered when using Apples Directory Utility application. If you want to allow users from Open Directory to log in to other bound clients, select the Use For Authentication option.
If you want users from Open Directory to be listed as contacts on other client computers, select the Use For Contacts option. If you want to bind to Open Directory securely, select the Perform Secure Bind checkbox and specify the user name and password for the directory account.
To create a Likewise Active Directory binding:. Click the New Directory Bindings button in the toolbar. Select the Likewise Binding option and click the Continue button. Enter the domain to which you are binding. Specify the user name and password for an administrator account and enter the password again to verify it. If you are binding client computers with more than one directory binding, use the Priority pop-up menu to specify the order in which the bindings will be applied.
The information specified on these panes is the same information entered when using Thursbys ADmitMac interface. Select the Centrify Binding option and click the Continue button. Enter any additional information on the Centrify Options pane. The information specified on this pane is the same information entered when using the Centrify interface.
Click the Global Management Framework Settings link. This includes:. The built-in CA has the signing and root CA certificates uploaded for you. To integrate with an existing CA: 1.
Click the Public Key Infrastructure tab. To upload the signing and root CA certificates, click the Signing Certificate Assistant link and follow the onscreen instructions. The assistant guides you through the steps to generate a certificate signing request CSR and upload the signing and root CA certificates. Click the Push Notification Certificate tab, and then click Upload. Upload the APNs certificate, and then click Save. Enter the keystore password for the certificate, and then click Next.
Computer Management Framework Settings Client check-in frequency Login and logout hooks Self Service application Application Usage Security The Computer Management Framework settings allow you to set up and manage preferences for the following aspects of client management:. Check-In Frequency The check-in frequency allows you to control how often client computers check the JSS for available policies. To view or modify the check-in frequency: 1.
Click the Computer Management Framework Settings link. On the Check-In Frequency pane, choose a check-in frequency from the pop-up menu. Startup Item Use this pane to create or remove a startup item and set preferences for how you want to use it.
The following options are displayed on this pane: Create startup item Creates a launchd item that executes once at startup. Log startup action Logs the startup action and IP address of each client computer at reboot Click the Startup Item tab. Select or deselect the Create startup item checkbox to create or remove the startup item.
Select or deselect additional options as needed. For more information about these tasks and how to perform them, see the following sections in this guide:. Application Usage Use this pane allows you to enable application usage for client computers. For information about application usage, see the Application Usage section. To enable application usage monitoring: 1. Click the Application Usage tab. Select or deselect the Enable application usage monitoring checkbox to enable or disable application usage monitoring, and then click Save.
The JSS rejects the message if the signature is invalid. This option is selected by default for all fresh installs of the JSS. See the APNs Certificate section for more information. This JSS has a valid certificate installed Indicates that there is a valid web server certificate installed on the server.
Maximum Clock Skew Sets a maximum difference in clock settings for the server and managed computers. Click the Security tab. Select or deselect options as needed.
Set or modify a maximum clock skew by choosing an option from the Maximum Clock Skew pop-up menu. This makes utilizing USB Ethernet dongles during imaging problematic, since the JSS assumes that each computer with a specific dongle is connected to the same computer. To work around this issue, you can specify a list of MAC addresses that the JSS should ignore when identifying a computer. The instructions in this section explain how to add, edit, and delete a removable MAC address.
To add a removable MAC address: 1. Click the Inventory Options link. Click the Add Address button. Policies Policies let you automate remote management tasks on client computers by pre-configuring the tasks and caching them in the JSS. This reduces the time you spend configuring individual tasks and pushing them out to computers by allowing clients to initiate the tasks when they check in with the JSS. Installing and uninstalling packages Running scripts Adding and removing printers Running Software Update Adding and removing Dock items Binding clients to directory services Updating computer inventory Performing maintenance functions Self Healing, fix permissions, update computer names, etc.
Managing account passwords The following tasks are common tasks that you can perform with a policy:. How Policies Work Using policies to automate remote management tasks allows you to specify the task s you want to perform, when and how often the task s should take place, and the clients that should execute the task s.
After saving the policy, it is stored in the JSS. Each time clients check in with the JSS, they check to see if any policies are available. Clients execute policies based on three main criteria: trigger, scope, and execution frequency.
Trigger None Self Service only End users initiate the policy through the Self Service application AnyThe next time the client checks in with the JSS StartupWhen the client starts up LoginWhen a user logs in on a client LogoutWhen a users logs out on a client Check-In FrequencyThis is one of the following intervals: 5 minutes 15 minutes 30 minutes A trigger is the action on a client that executes the policy.
Clients can execute policies at the following triggers:. Check-in frequency is configured as part of your Computer Management Framework settings. For information on how to change the check-in frequency, see the Changing the Computer Management Framework section. Scopes can be based on one or more of the following components:. Execution Frequency The execution frequency is how often clients execute the policy.
This depends largely on the task you want to perform. For example, if youre installing a piece of software, you may want to choose Once Per Computer to ensure only one copy of the software is installed on each computer. Once per computer Once per user At login or logout Once every day Once every week Once per month Every 30 days after the first day the policy runs on the computer Ongoing Every time the trigger takes place Disable Makes the policy inactive Policies can be set at the following execution frequencies:.
The Policy Assistant guides you through the process of configuring a policy to perform the following, basic tasks:. Install a cached package Uninstall a package Add a printer Remove a printer Run a script Configuring a policy manually gives you a variety of extended policy options.
The following options include configuring date, time, and network limitations:. Overriding default settings Performing multiple tasks with a single policy Setting reboot criteria. For this reason, it may be helpful to familiarize yourself with the panes in the manual policy interface.
The manual policy interface is made up of the following panes:. The General and Scope panes let you configure trigger, scope, and execution frequency, while the other eight panes let you set tasks and specify additional criteria. This section explains each pane in the policy framework and provides basic instructions on how to configure policies using the Policy Assistant, manually, and using the JSS Mobile application.
This pane lets you configure the following criteria for a policy: Display Name Required Enter a display name for the policy. Category Assign the policy to a category. Triggered By Required Choose the event which client computers initiate the policy. Execution Frequency Required Specify how often client computers execute a policy.
Server-Side Limitations Specify when you want the policy to become active and expire on the server. The policy is available to client computers between the times you specify. Client-Side Limitations Specify the days and times you dont want client computers to execute the policy. Network Limitations Specify the network requirements client computers must meet to run a policy.
Override Default Policy Settings Specify the distribution point, Software Update Server, or NetBoot Server from which client computers should pull packages, run software updates, or reboot.
This lets you install packages to a drive other than the current boot drive. This pane lets you specify which client computers execute the policy. This pane lets you make the policy available through Self Service. For detailed instructions on how to make policies available through Self Service, see the Making Policies Available in Self Service section. For detailed instructions on how to configure a policy to perform these tasks, see the Software Distribution chapter and the Running Software Update section.
This pane lets you configure the policy to run a script and set the following script-related information:. For detailed instructions on how to configure a policy to run a script, see the Running Scripts section.
This pane lets you configure the policy to add or remove a printer. For detailed instructions on how to configure a policy to add or remove a printer, see the Managing Printers section. This pane lets you configure the policy to add or remove a Dock item.
If you are adding a Dock item, you can also specify where to add the item on the Dock. For detailed instructions on how to configure a policy to add or remove a Dock item, see the Managing Dock Items section. For detailed instructions on how to configure a policy to perform these tasks, see the following chapters:.
This pane lets you set reboot specifications for client computers executing the policy, display a message at reboot, and specify the drive to which clients reboot.
Note: If youre running the Casper Suite v7. If you are using the Self Healing feature, you can also configure the policy to run Self Healing on this pane. For detailed instructions on how to configure a policy to run Self Healing, see the Using the Self Healing Feature section.
To configure a policy using the Policy Assistant: 1. Open the JSS in a web browser. Click the Management tab. Click the Policies link. Click the Create Policy button. Select the task you want to perform with the policy and click the Continue button. Follow instructions on each pane to configure the policy.
When youre finished using the assistant, you can make changes or configure additional options manually by clicking the Edit Manually button on the last pane. To configure a policy manually: 1. Click the Create Policy button in the toolbar. Enter a display name for the policy and assign it to a category. Choose a trigger from the Triggered By pop-up menu. If you choose Other, you will need to specify a manual trigger.
Choose an execution frequency from the Execution Frequency pop-up menu. If you Ongoing, you the policy chooseMake Availablecan makecheckbox.
If you want every computer to execute the policy, select the Assign to All Computers option. If you only want certain the policy: Select the Assign tocomputers to executeoption. Specific Computers b. Select the Add checkbox across from the computers or groups you want to add to the scope. Click the Add User Group link. Select the Add checkbox across the groups you want to add. Click the Add button at the bottom of the list.
Client computers execute the policy the next time they check in with the JSS and meet all of the criteria on the General and Scope panes. To configure a policy using JSS Mobile:. Then, tap the Save button. Tap the General icon. Specify a display name, category, trigger, and execution frequency for the policy, and then tap the New button at the top of the screen.
Tap the Scope icon and specify the computers you want to execute the policy. If you want every computer to execute the policy, turn the Assign to All Computers option on. Tap the New button at the top of the pane.
Tap the appropriate icons to configure the rest of the policy. Tab the Save button. Managing Policies View the plan for a policy View the status of a policy Duplicate a policy Edit a policy Delete a policy The instructions in this section explain how to do the following:. Click the Show Plan link across from the policy.
A complete task list for the policy is displayed. Tap Policies. Click the View Status link across from the policy. The table at the top of the page displays an overview of the policys status. Beneath it is a list of client computers that have executed the policy. Clients that have encountered a problem while executing the policy are displayed in red text. If there are clients that encountered problems, you can have them execute the policy again by clicking the Flush All History With Problems link.
If you want to execute the policy again on all of the clients, click the Flush Entire Policy History link. This resets the policy, making it appear as if it had never been executed. Clients execute the policy the next time they check in with the JSS and meet all of the criteria on the General and Scope panes. Click the Duplicate Policies button in the toolbar. Locate the policy you want to duplicate and click the Duplicate link across from it.
Make changes if necessary. To edit a policy using the JSS:. Click the Edit Policy link across from the policy and make changes. To edit a policy using JSS Mobile:. In the list of policies, tap the policy you want to edit and make the necessary changes. Tap the Save button. Internet Download Manager. Advanced SystemCare Free. VLC Media Player.
MacX YouTube Downloader. Microsoft Office YTD Video Downloader. Adobe Photoshop CC. VirtualDJ Avast Free Security. WhatsApp Messenger. Talking Tom Cat. Clash of Clans. Subway Surfers. As such there is no image to download.
This sofware set and Casper workflows are not machine specifice and should work on all current Intel Apple hardware that can boot to A good copy of the correct edu. Note that the casper policy installs OpenAFS for Use the following command:. OIT is providing a Universal Lab Software only for Intel i based Macintosh hardware supporting 32 bit and 64 bit machines where possible.
0コメント