This application note was provided by Softblox, Inc., 1201 West Peachtree Street, Atlanta, GA 30309.
AppScape/Manage delivers the benefits of reducing total cost of operation (TCO) by allowing the administrator to control, restrict, and log the use of specific features within users applications. AppScape/Manage controls availability of functionality within applications to provide a custom interface based on each users needs. Non-essential or problematic application activity is prevented. Corporate data is protected from accidental misuse. Network and bandwidth-clogging features such as splash screens are removed and user productivity increases.
The AppScape/Manage Administrator module is installed and run on a MetaFrame, Microsoft Windows NT 4.0, or Windows NT 4.0 Server, Terminal Server Edition server.
The AppScape/Manage Runtime module is installed on any server to which clients can log on. Users connect to the MetaFrame server as usual, with AppScape monitoring the usage.
Hardware Requirements (Server)
• IBM compatible 586/Pentium server
• 133MHz or faster
• 64MB memory
• 32MB disk space
• MetaFrame Version 1.8 or higher
• Microsoft Windows NT 4.0, Terminal Server Edition
• Softblox AppScape/Manage
• Installing AppScape/Manage Administrator
1. Log on to the computer as an administrator.
2. Insert the AppScape CD-ROM and view the Readme.txt file located in the root directory. Readme.txt can include updated information that you need before or during installation.
3. After viewing Readme.txt, run Setup.exe, located in the AppScape CD root directory.
4. After Setup initializes, a Welcome window appears. Follow the on-screen instructions in this window, making sure all other applications are closed. Click Next.
5. Read and accept or reject the Software License agreement. If you do not accept the terms of the agreement, press No to exit Setup and return all physical copies of the software to Softblox. If you accept the terms of the agreement, press Yes.
6. Enter your name and company information in the User Information Window.
7. Enter your serial number or leave blank for a timed evaluation license. Click Next.
8. Keep the default Typical Installation by choosing to install all components. Choose the destination folder where you want to install AppScape/Manage. Click Next.
9. Select any optional components you want to install. Click Next.
10. Select the name of your program folder. Click Next.
11. Verify that the settings you selected are correct. Click Next.
12. Click Finish to Restart Computer.
13. Log on to the computer with the same account.
14. Setup registers the administrator.
15. Select Interaction Modules to Install. Click Import.
AppScape/Manage Setup is complete.
Quick Start Instructions for Running AppScape/Manage
NOTE: AppScape supports multiple methods to complete many tasks. These Quick Start Instructions demonstrate only one method.
Starting AppScape Administrator
AppScape can modify application behavior on a user-by-user basis. An applications behavior is modified based on AppScape rules. AppScape comes with several pre-packaged sets of rules (you can also define your own custom rules as described later in this note).
An AppScape policy links users and rules. At its simplest, a policy links a single user and rule, causing that rule to be enforced on that user.
Creating a New Policy
1. In the AppScape Administrators menu bar, click the AppScape menu, point at New, and then select Policy. The Rule Wizards New Policy dialog box appears.
2. In the Name field, type Disable Printing.
3. In the Description field, type Disable Printing in Word and Excel.
4. Click Next. The Policy Wizards Select Rules dialog box appears.
5. Click the listbox by the Available Rules label and select Elements in the drop-down list that appears. The Available Rules dialog box now lists the defined rule elements (instead of rule packages).
6. In the Available Rules dialog box, scroll to the Disable Printing in Word 97 entry. Click on that entry and then click Add. Disable Printing in Word 97 now appears in the Selected Rules dialog box.
7. Click Next. The Policy Wizards Select Users dialog box appears. Specify the users to whom the selected rules will apply.
8. Click the listbox by the Available Users label and select NT users in the drop-down list that appears. The Available Users dialog box now lists all Windows NT users known to this server (in the currently active domain).
9. For this example, use yourself as a test user. In the Available Users dialog box, click your own username and then click Add.
10. Click Next. The Rule Wizards Select Schedule dialog box appears. Specify an optional schedule for the policy. The default means the rule is always enforced.
11. Click Next. The Rule Wizards Summary dialog box appears.
12. Click Finish.
NOTE: As you become more advanced, you may find it easier to create a policy than drag and drop rules and users into the existing policy.
13. Expand the tree view for Rules and expand Excel 97 Rule Package under Packages.
14. Drag Disable Printing in Excel 97 to the Disable Printing policy you just created under Policies.
15. Click the Disable Printing policy to make it consist of both rules.
You have created and edited a policy that disables printing when you run Word 97 and Excel 97. However, this policy has no effect until you update the AppScape monitors, as described next.
Activating the New Policy
New policies (and changes in existing policies) are not activated until the AppScape application monitors are updated. These monitors oversee user operations and induce the changes in application behavior specified by rules that are applied to users through policies.
To update the monitors, click the Apply Policy Changes button in the AppScape Administrator Toolbar.
Your newly created Policy is now active.
Testing the New Rule and Policy
You have now completed all the steps to modify the behavior of Word 97 and Excel 97 for your own user account. To test this, run Word 97 or Excel 97. Notice that print functions are no longer available, including:
No Print button in the toolbars
No Print option in the File menu
Because the policy you created specifies only your account, this behaviors appears only when you are logged on under that username. To confirm this, log on with a different username and you will see that Word 97 and Excel 97 operate as usual.
To learn more about AppScape, see the complete electronic documentation on the CD-ROM and continue exploring AppScape Administrator.