Firefox Policy


Firefox is a streamlined web browser provided by Mozilla. ZENworks Linux Management provides a policy that enables you to configure and lock down the Firefox browser on any of the managed devices.

You can configure the following options for the Firefox policy by checking or unchecking the corresponding check box. When a check box is selected, that component is activated.

  • Disable JavaScript control of window chrome

  • Disable URL bar

  • Disable bookmark editing

  • Disable toolbar editing

  • Disable history

  • Disable saving of passwords

  • Disable updates to themes

  • Disable updates to extensions

The following options of the Firefox policy have additional data entered. Additionally, beyond placing the default values for the following options, the policy may lock the value. To lock the value, select the lock button next to the corresponding value. This prevents the user from modifying that value on the assigned managed device.

  • Homepage URL The default value is not initially defined. You need to enter the default value into the Homepage field.

  • Allow Popups The default value is Yes.

  • Allow Java The default value is Yes.

  • Allow JavaScript The default value is Yes.

  • Allow Sites to Set Cookies The default value for this setting is Yes. There is then an additional value that complements this setting: Keep Cookies. The Keep Cookies value defaults to Until They Expire. Optional values for this setting include Ask Me Every Time, or Until I Close Firefox.

  • Allow Loading of Images The default value for this setting is Anywhere. Optional values include From Originating Website Only, or Never.

  • Disk Space for Temporary Files The default value for this field is set at 50MB.

Generic GNOME Policy

The Generic GNOME policy is unlike any of the other policies that are available in ZENworks Linux Management. This policy allows the free selecting and setting of any Gconf configuration setting. These settings are used by operating systems and many applications. Providing this generic policy enables administrations to manage keys within the system.

There are two ways to create the GNOME policy: importing settings from an existing managed desktop or manually. The first page of the wizard asks you which you would prefer.

Should you choose to have ZENworks automatically retrieve effective settings from a managed device, the following steps will be taken:

  • On the next page of the wizard you are asked to either select a device from the ZENworks system (because the device had been previously registered with the system) or enter a DNS name or IP address for a workstation to which you want to connect. Additionally you must also enter the user that represents the effective settings you want to collect. Press Next.

The collected keys are displayed on the next wizard page. If you chose to not collect keys from a device, an empty Gconf tree is displayed. Complete the following to edit the directories, keys, and values:

  • To add a key or a directory, press the Add menu item and choose either Directory or Key. Enter the Directory or Key name and then for the key, the corresponding value.

  • To remove a key, select a set of keys or directories from the list and press the Delete menu item. Deleted directories remove all keys in that directory and subdirectories.

  • To edit a key, select the key and a pop-up dialog is presented where you can modify the key name and/or value.

Novell Linux Desktop Policy

The Novell Linux Desktop policy enables you to configure a Novell Linux Desktop workstation.

You can configure the following options for the Novell Linux Desktop policy by checking or unchecking the corresponding check box. When a check box is selected, that component is activated.

  • Disable launching of command line programs.

  • Disable screen locking.

  • Disable logging off.

  • Disable panel configuration.

  • Disable printing.

  • Disable print setup.

  • Disable applets. This setting also includes the set of applets that are available on the desktop. You can select any of the set of applets and press the arrow buttons to move or remove the applets from the Applets to Be Disabled box. The list of available applets includes Dictionary, Clock, Fish, Weather, OpenOffice Quickstart, Sticky Notes, Stock Update, Geyes, CD Player, Volume Control, and Address Book.

The following options of the Novell Linux Desktop policy have additional data entered. Additionally, beyond setting the default values for the following options, the policy may lock the value. Lock the value by selecting the lock button next to the corresponding value. This prevents the user from modifying that value on the assigned managed device.

  • Background image file name There is no default filename specified. You must specify a file local to the managed device (for example, /opt/gnome/share/images/roses.jpeg).

  • Background position The default setting is Centered. The optional values include Fill Screen, Scaled, Tiled, No Background.

  • Background shade The default value is Solid. The optional values include Vertical or Horizontal.

  • Theme file name There is no default filename specified for this value. You must specify a local theme file for the managed device (for example, /opt/gnome/share/themes/small.gtk).

  • Proxy settings This setting enables you to choose one of the following options:

    • Direct Internet connection.

    • Manual proxy configurationUnder this setting you may specify the following parameters: HTTP Proxy Address and Port, HTTP Secure Proxy and Port, FTP Proxy Address and Port, and Socks Proxy and Port.

    • Automatic proxy configuration with a specified Autoconfiguration URL.

Remote Execute Policy

The Remote Execute policy enables you to specify when a script should be executed on the assigned managed device.

Execute the following to construct a Remote Execute policy:

1.

After you specify the name and folder for the policy and any optional description, press Next.

2.

Specify the executable type for this policy. Values include Script, Binary, or Java.

3.

Specify the maximum wait time for the execution to complete. You may choose from any of three choices:

  • Do not wait.

  • Wait until the program completes the execution.

  • Wait for X seconds. You may enter the number of seconds for ZENworks to wait for the execution to complete.

If you chose to run a script, follow these steps:

1.

Specify the script to run. Your choices include Specify a File or Define Your Own Script. If you choose to specify a file, enter the path to the script file in the Script File Name field. The script must already be on the managed device. If you choose to define your own script, a box appears in the screen and you can enter the script manually into the box.

2.

Specify the additional parameters for the script: Script Parameters, Script Engine, and Script Engine Parameters. When the script is to be executed, ZENworks launches the specified script engine to run the script, with the parameters specified. Press Next.

If you chose to run a Binary or Java file, follow these steps:

1.

Specify the executable filename. The executable file must already exist on the managed device.

2.

Specify any executable parameters you want to give to the executable file.

If you chose to run a Java file, follow these steps:

1.

Enter the Java program name. The Java file must already exist on the managed device.

2.

Enter any program parameters you want to send to the Java program when it is launched.

3.

Enter the path to the JRE (Java Run-time Engine) that will be used to run the Java program. The JRE must already have been installed on the managed device.

4.

Enter the JRE parameters you want included in the launching of the program.

Press Next to get a summary of the execution policy, and then Finish to have the policy created.

Text File Policy

The Text File policy enables the administrator to modify any text files on the managed device.

Complete the following steps to create and define your Text File policy:

1.

Complete the name and folder where you want to have the policy. Enter any additional description and press Next.

2.

Enter the name of the file you want to modify.

3.

Enter the maximum number of revisions you want to keep. The default value is 5. Whenever ZENworks begins to modify a text file, it saves a backup copy of the file before proceeding. This parameter specifies the number of copies to keep.

4.

Enter a change name. You may have a number of changes in the Text File policy. Each change must be given a name.

5.

Choose the type of change: Search File, Append Lines to File, Prepend Lines to File.

If you choose the Search File type, complete the following:

1.

Enter in a search string, using regular expression formats.

2.

Mark whether the search should be case sensitive. The default is to be case sensitive.

3.

Select the search occurrence option. This option may be any of the following: First Occurrence, Last Occurrence, or Find All Occurrences.

4.

Select the resulting action after an occurrence is found. The options include the following:

  • Add Lines After the Current Line

  • Add Lines Before the Current Line

  • Add String After

  • Add String Before

  • Add Word After

  • Add Word Before

  • Append String to Line

  • Prepend String to Line

  • Delete String

  • Delete Line

  • Delete All Lines After

  • Delete All Lines Before

  • Replace String

  • Replace Line

  • Replace All Lines After

  • Replace All Lines Before

  • Append String to File if Not Found

  • Prepend String to File if Not Found

5.

Enter the new string in the text box provided and press Next.

If you choose to append or prepend lines to the file, just enter the text you want placed into the file. Press Next.

The Text File Policy also enables you to specify that a script, binary file, or Java application should be executed before changes are made to the text file. This can be useful, for example, if you need to stop some daemon before its configuration file is modified. The additional administration involved in choosing Script or Binary or Java is the same as described earlier in the "Remote Execute Policy" section.

Execute the following to complete the policy:

1.

After entering any execution that should be completed prior to changes, select how you want ZENworks to behave should the execution fail. The execution fails if it returns a non-zero value to ZENworks. The options include Continue Modifying the Text Files and Do Not Modify the Text Files.

2.

Choose any executable you want to run after the text file editing has been completed. This is defined in the same manner as in the prior step. Press Next.

3.

Complete the wizard and press Finish.

To add changes to the policy, you must browse to the policy and then select to see the details of that policy. There you may add changes to the one file or add files to change.

To add changes, select the file and select New, Change, and enter the changes requested. All the changes are entered into a dialog box that mimics the wizard.

To add another text file to change, select the New, File menu option and enter the filename. All the changes are entered into a dialog box that mimics the wizard.




Novell ZENworks 7 Linux Management Administrator's Handbook
Novell ZENworks 7 Linux Management Administrators Handbook
ISBN: 0672327848
EAN: 2147483647
Year: 2005
Pages: 147

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net