1. Manuals
  2. Brands
  3. Symantec Manuals
  4. Software
  5. PCANYWHERE - V12.5
  6. Administrator's manual

Symantec PCANYWHERE - ADMINISTRATOR GUIDE V12.5 Administrator's Manual

Hide thumbs Also See for PCANYWHERE - ADMINISTRATOR GUIDE V12.5:
Table of Contents

Advertisement

Quick Links

Download this manual See also: User Manual, Manual
Symantec pcAnywhere
Administrator's Guide

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the PCANYWHERE - ADMINISTRATOR GUIDE V12.5 and is the answer not in the manual?

Questions and answers

Related Manuals for Symantec PCANYWHERE - ADMINISTRATOR GUIDE V12.5

Summary of Contents for Symantec PCANYWHERE - ADMINISTRATOR GUIDE V12.5

  • Page 1 Symantec pcAnywhere Administrator's Guide...
  • Page 2 Symantec, the Symantec Logo, Symantec pcAnywhere, Symantec Packager, ColorScale, SpeedSend, LiveUpdate, Virtually Anywhere and Work Virtually Anywhere are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners.

  • Page 3: Technical Support

    The Technical Support group also creates content for our online Knowledge Base. The Technical Support group works collaboratively with the other functional areas within Symantec to answer your questions in a timely fashion. For example, the Technical Support group works with Product Engineering and Symantec Security Response to provide alerting services and virus definition updates.
  • Page 4 Troubleshooting that was performed before contacting Symantec Recent software configuration changes and network changes Licensing and registration If your Symantec product requires registration or a license key, access our technical support Web page at the following URL: www.symantec.com/techsupp/ Customer service Customer service information is available at the following URL: www.symantec.com/techsupp/...
  • Page 5 North America and Latin America supportsolutions@symantec.com Additional enterprise services Symantec offers a comprehensive set of services that allow you to maximize your investment in Symantec products and to develop your knowledge, expertise, and global insight, which enable you to manage your business risks proactively.

  • Page 7: Table Of Contents

    Migrating from pcAnywhere 12.1 to 12.5 in Windows 2000/2003/2008 Server/XP to ( ) ......... 13 Migrating from pcAnywhere 12.0.2 in Windows 2000/2003 Server/XP to Vista ............13 Using Symantec Packager to streamline migrations and upgrades ..13 Chapter 2 Creating custom installation packages ......15 About Symantec Packager .............
  • Page 8 Contents Deploying installation packages using Web-based deployment ..... 43 About Web-based deployment requirements ....... 43 Setting up the installation Web server ........44 Customizing the deployment files ..........47 Testing the installation on the Web server ........51 Notifying users of the download location ........51 Deploying pcAnywhere using SMS 2.0 ..........
  • Page 9 Setting up the host computer to use directory services ....81 Setting up the remote computer to use directory services ....82 Chapter 6 Managing security in Symantec pcAnywhere ....83 Controlling access to pcAnywhere hosts ........... 83 Limiting connections to specific computer names or IP addresses ...............
  • Page 10 Contents...

  • Page 11: Planning A Migration And Upgrade Strategy

    A system restart for migrations and upgrades is required on Vista, but is only required on Windows 2000/2003/2008 Server/XP if system files need to be updated. Symantec Packager helps you simplify the process of uninstalling previous versions or distributing preconfigured settings to multiple users.
  • Page 12 Planning a migration and upgrade strategy About migrations and upgrades Migration and upgrade strategy matrix Table 1-1 Symantec Operating Restart required Data preserved pcAnywhere system automatically version 12.0 Windows Yes (for Vista) Host items 2000/2003/2008 Caller items Server/XP/Vista Remote items...

  • Page 13: Migrating From Pcanywhere 12.1 To 12.5 In Windows 2000/2003/2008 Server/Xp To ( )

    Using Symantec Packager to streamline migrations and upgrades Symantec Packager is an administrator tool that lets you create, modify, and build custom installation packages that you distribute to target systems. Symantec Packager is available for download. Symantec Packager helps you streamline the process of migrating or upgrading...
  • Page 14 Planning a migration and upgrade strategy Using Symantec Packager to streamline migrations and upgrades The product installation requires you to Create a custom installation package for the restart the computer to complete the product installation and configure the installation process.

  • Page 15: Creating Custom Installation Packages

    About Symantec Packager Symantec Packager lets you create, modify, and build custom installation packages that you can distribute to target systems. You can use Symantec Packager to tailor installations to fit your corporate environment by building packages that contain only the features and settings that your users need.

  • Page 16: What You Can Do With Symantec Packager

    Simplify application deployment and migration by including custom commands with product installations How Symantec Packager works Symantec Packager uses a phased approach for creating custom installation packages. Each phase depends on the output of the previous phase. Figure 2-1 shows the process for creating custom installation packages with Symantec Packager.
  • Page 17 38. Deploy the package. The Deploy Packages tab holds the packages that you create, which you can deploy to your users. Symantec provides a Package Deployment tool in Symantec Packager and a Web-based deployment tool on the pcAnywhere CD. You can also use your current deployment tools.

  • Page 18: Importing A Product Module

    Symantec Packager automatically checks the Packager/Products folder for product module files and imports them automatically. If no products appear on the Import Products tab when you open Symantec Packager, you must import the product module manually. To import a product module Open Symantec Packager.

  • Page 19: Selecting Product Features

    Building the product configuration file creates a Microsoft Installer (.msi) file. Symantec Packager supports the installation of pcAnywhere .msi and .exe files. “Building a product configuration file”...
  • Page 20 Customizing product settings Some features in pcAnywhere have dependencies on other components. Although Symantec Packager has a level of built-in dependency checking, it is possible to build a pcAnywhere installation package that does not include all required files. As you select product features to include or exclude from a package, you should read the feature descriptions that are provided in the Product Editor window on the Features tab.

  • Page 21: Including Configuration Files

    For product-specific configurations, you must configure these files in the product first, and then add them to the Configuration Files tab in Symantec Packager. Configuration files cannot be edited in Symantec Packager.
  • Page 22 This information is required to launch a host. For more information, see the Symantec pcAnywhere User's Guide. Symantec pcAnywhere configuration files are located in the following folders: Windows 2000/2003 Server/XP \Documents and Settings\All Users\Application Data\Symantec\pcAnywhere...

  • Page 23: Integrity Stamping A Product Configuration

    Warning: Use caution when configuring a registry key file. An incorrect setting could make the operating system or product inoperable. To include a configuration file In the Symantec Packager window, on the Configure Products tab, do one of the following: Create a new product configuration.
  • Page 24 “Implementing policy-based administration” on page 91. To integrity stamp a product configuration In the Symantec Packager window, on the Configure Products tab, do one of the following: Create a new product configuration. Double-click an existing product to edit it.

  • Page 25: Serializing A Pcanywhere Installation

    Deploy and install the package. Generating a serial ID file Symantec pcAnywhere lets you generate a security code, or serial ID, which can be embedded into a custom installation. Serial IDs must be a numeric value between 0 and 4,294,967,296.
  • Page 26 To allow a connection between a host and remote computer, the host and remote computers must have matching serial IDs. To create a serialized installation file In the Symantec Packager window, on the Configure Products tab, do one of the following: Create a new product configuration.

  • Page 27: Managing Configuration Settings Globally

    Preconfigured option sets can be used for custom installation packages created with Symantec Packager. They can also be used as the default preferences for the local computer. Configuring an option set in pcAnywhere Symantec pcAnywhere groups the option set properties by tabs.
  • Page 28 After the package or custom product is installed on the target computer, the option set can be applied on the local computer. To add an option set to a custom installation file In the Symantec Packager window, on the Configure Products tab, do one of the following: Create a new product configuration.

  • Page 29: Setting Product Installation Options

    If prompted, type a file name, and then click Save. Applying an option set on the local computer Symantec pcAnywhere lets you maintain multiple option set files to accommodate unique configuration requirements. For example, if you work in different locations, you can avoid changing the default settings each time you change locations.
  • Page 30 Packager are installed by default in the Program Files directory under Symantec\pcAnywhere. You can specify a different directory. To change the target installation directory In the Symantec Packager window, on the Configure Products tab, do one of the following: Create a new product configuration.
  • Page 31 If prompted, type a file name, and then click Save. Selecting the default template for host connections Symantec Packager lets you select the host configuration file that you want to use as a template for new host connection items that the user creates after installation.
  • Page 32 If prompted, type a file name, and then click Save. Selecting the default template for remote connections Symantec Packager lets you select the remote configuration file that you want to use as a template for new remote connection items that the user creates after installation.
  • Page 33 (LIVEUPDT.HST) to include the location of the LiveUpdate Server. For more information, see the LiveUpdate documentation. To update products In the Symantec Packager window, on the Configure Products tab, do one of the following: Create a new product configuration. Double-click an existing product to edit it.

  • Page 34: Creating A Custom Command

    Creating custom installation packages Creating a custom command To preserve existing configuration settings In the Symantec Packager window, on the Configure Products tab, do one of the following: Create a new product configuration. Double-click an existing product to edit it.

  • Page 35: Creating Installation Packages

    Creating custom installation packages Creating installation packages To create a custom command In the Symantec Packager window, on the Configure Products tab, on the File menu, click New Custom Command. In the Command Editor window, on the Parameters tab, double-click Description.

  • Page 36: Adding Products And Commands To A Package Definition

    Creating custom installation packages Creating installation packages which creates an .msi file that can be installed locally. You can deploy the Symantec pcAnywhere .msi file using a third-party deployment tool. The Symantec Packager Deployment Tool does not support MSI deployment.

  • Page 37: Building Product Installations And Packages

    Symantec Packager stores the .msi files in the Symantec Packager data directory. You can view these files on the Deploy Packages tab if you edit the Symantec Packager preferences to list supported .msi files.

  • Page 38: Building A Package

    Symantec Packager then checks the contents of the package for product conflicts. If Symantec Packager encounters a product conflict, the build process stops. You must resolve the conflict, and then repeat the build process.
  • Page 39 Creating custom installation packages Testing packages if Symantec Packager encounters a conflict that it cannot resolve. You should test packages to verify that product requirements are met and that the installation sequence is correct. You should also open each installed program to ensure that it functions correctly.
  • Page 40 Creating custom installation packages Testing packages...

  • Page 41: Deploying Symantec Pcanywhere Custom Installations

    Opening an .exe file or supported .msi file on the Deploy Packages tab in Symantec Packager starts the installation process. Ensure that the target computer meets the system requirements for pcAnywhere installation. For more information about using the Deploy Packages tab, see the Symantec Packager Implementation Guide.

  • Page 42: About Package Installation File Locations

    Preconfigured package and product installation files are stored in the Packages directory on the Symantec pcAnywhere CD. Packages and product installation files that you create with Symantec Packager are listed on the Deploy Packages tab in Symantec Packager. To view .msi files, you must edit the Symantec Packager preferences to list supported product .msi files.

  • Page 43: Deploying Installation Packages Using Web-Based Deployment

    Deploying installation packages using Web-based deployment Packages that are created with Symantec Packager can be deployed over your corporate intranet using a Web-based deployment tool that is provided by Symantec. All of the source files that are necessary to implement Web-based deployment are included on the Symantec pcAnywhere CD in the Tools/Web Deploy folder.

  • Page 44: Setting Up The Installation Web Server

    Deploying Symantec pcAnywhere custom installations Deploying installation packages using Web-based deployment Web server and target computer requirements (continued) Table 3-1 Deployment Requirements Target computer Internet Explorer 4.0 or later. Symantec pcAnywhere requires Internet Explorer 6.x or later for installation. Windows Installer 3.1 or later (required only for MSI installations).
  • Page 45 On the Web server, create a directory in which you want to place the deployment files. For example: Deploy From the Packages folder on the Symantec pcAnywhere CD, copy the installation files that you want to make available for deployment to the Webinst subfolder on the Web server. For example: Deploy\Webinst\Webinst Ensure that the default document for the virtual directory is Default.htm.
  • Page 46 Deploying Symantec pcAnywhere custom installations Deploying installation packages using Web-based deployment The Web-based deployment tool supports Microsoft Internet Information Server (IIS) or Apache HTTP Web Server. The procedures for creating a virtual directory on these servers vary. To create a virtual directory on a Microsoft Internet Information Server Do one of the following to launch the Internet Services Manager: In IIS version 4.0: On the Windows taskbar, click Start >...

  • Page 47: Customizing The Deployment Files

    Deploying Symantec pcAnywhere custom installations Deploying installation packages using Web-based deployment This file is installed by default in C:\Program Files\ Apache Group\Apache\conf. Type the following lines at the end of the file: DirectoryIndex default.htm <VirtualHost 111.111.111.111> #ServerName machinename DocumentRoot "C:\Client\Webinst"...
  • Page 48 Deploying Symantec pcAnywhere custom installations Deploying installation packages using Web-based deployment Customizing Start.htm The parameters in the Start.htm file contain information about the Web server and the location of the files that need to be installed. The configuration parameters are located near the bottom of the Start.htm file, inside the <object> tags.
  • Page 49 Deploying Symantec pcAnywhere custom installations Deploying installation packages using Web-based deployment You can also include additional files to support the deployment of third-party applications. To customize Files.ini for package deployment In a text editor, open Files.ini In the [General] section, edit the line LaunchApplication= so that it references the package executable file that you want to start after the download completes.
  • Page 50 Deploying Symantec pcAnywhere custom installations Deploying installation packages using Web-based deployment To customize Files.ini for MSI deployment In a text editor, open Files.ini In the [General] section, edit the line LaunchApplication= so that it references Launch.bat. For example: LaunchApplication=Launch.bat This launches the MSI installation after the download is complete. You must also edit the Launch.bat file to include the name of the .msi file that you want...

  • Page 51: Testing The Installation On The Web Server

    To install a pcAnywhere installation package, users must have Internet Explorer 6.0 or later on their computers. The Internet Explorer security level for the local intranet must be set to Medium so that Symantec ActiveX controls can be...

  • Page 52: Deploying Pcanywhere Using Sms 2.0

    Deploying Symantec pcAnywhere custom installations Deploying pcAnywhere using SMS 2.0 downloaded to the client. When the installation is complete, the security level can be restored to its original setting. Make sure that users understand the system requirements and have the administrative rights that are required for the products that they are installing.

  • Page 53: Minimum Requirements For Sms Deployment

    SQL Server 6.5 or higher SMS 2.0 with Service Pack 1 or Service Pack 2 (recommended) Symantec Packager 1.0 or later with customized packages created for deployment All deployment clients must be members of the same domain as the SMS...
  • Page 54 Preparing the Package Definition File A default Package Definition File (pcAnywhere.pdf) is provided with pcAnywhere. This file can be modified to accommodate any package created with Symantec Packager. To use the supplied Package Definition File without modification, do one of the following: For .exe-based packages, rename the pcAnywhere package that you want to...
  • Page 55 Do not select This package does not contain any files. Click Browse to locate the folder that contains the pcAnywhere package that you created with Symantec Packager (or a supplied, preconfigured package). The Create Package from Definition Wizard uses this folder to point to the pcAnywhere package.

  • Page 56: Using Windows 2000/2003/2008 Server/Xp/Vista Logon Scripts

    Deploying Symantec pcAnywhere custom installations Using Windows 2000/2003/2008 Server/XP/Vista logon scripts Click Browse, and then and pick the collection to which you want to advertise the installation. Set the schedule, requirements, and appropriate security rights of the package. After the advertisement is created, pcAnywhere should deploy to all of the selected clients.
  • Page 57 Deploying Symantec pcAnywhere custom installations Using Windows 2000/2003/2008 Server/XP/Vista logon scripts @echo off setlocal REM ***** Package Variable -- Change to name of pcA Package ***** Set Package=Package.MSI REM ***** EXE or MSI Variable -- Change to package type (MSI or EXE)

  • Page 58: Testing The Windows Logon Script

    Deploying Symantec pcAnywhere custom installations Using NetWare logon scripts rd pcapkg Net Use Z: /DELETE :End endlocal Testing the Windows logon script Test the completed script on one or two workstations before setting up the script for all users. Windows 2000/2003/2008 Server/XP/Vista users must have local administrative rights on their computers to install the pcAnywhere package.

  • Page 59: Writing The Netware Logon Script

    Deploying Symantec pcAnywhere custom installations Using NetWare logon scripts Writing the NetWare logon script Use the following sample logon script and deployment batch file to roll out pcAnywhere. The script creates the appropriate drive mappings to the local workstation and launches the deployment batch file. The batch file installs the pcAnywhere package and removes the installation files when complete.

  • Page 60: Testing The Netware Logon Script

    Deploying Symantec pcAnywhere custom installations Using NetWare logon scripts REM ***** Creates a folder in the Temp dir, and copies the package ***** CD %TEMP% MD pcapkg CD pcapkg COPY %Package% c: REM ***** Launches package installation ***** IF %PkgType% == MSI msiexec -i %Package%...

  • Page 61: Performing Centralized Management

    About the Microsoft Distributed Component Object Model (DCOM) About centralized logging About centralized management Symantec pcAnywhere includes the pcAnywhere Host Administrator tool, which lets you remotely manage multiple pcAnywhere hosts on a network. The pcAnywhere Host Administrator tool is a Microsoft Management Console (MMC) snap-in and requires MMC to run.

  • Page 62: Installing The Pcanywhere Host Administrator Tool

    In the Add/Remove Programs window, click Symantec pcAnywhere. Click Change. In the Modify or Remove Symantec pcAnywhere panel, click Next. In the Program Maintenance panel, click Modify, and then click Next. In the Custom Setup panel, under pcAnywhere Tools, click the down arrow next to Host Administrator, and then click This feature will be installed on local hard drive.

  • Page 63: Adding The Host Administrator Snap-In To Mmc

    Administrator tool, you can add it as a snap-in to MMC. MMC is included with the operating system in Windows 2000/2003/2008 Server/XP/Vista. If you need to install MMC, you can install it from the Symantec pcAnywhere CD. To add the Host Administrator snap-in to MMC Do one of the following: On the Windows 2000/2003/2008 Server/ XP taskbar, click Start >...

  • Page 64: Adding Computers To A Configuration Group

    These files contain the connection and security settings needed to support connections between the pcAnywhere Host Administrator console and the host computers that you want to manage. Symantec pcAnywhere provides the following preconfigured host and remote connection items that you can use as templates:...
  • Page 65 In the Remote Properties window, on the Connection Info tab, select one of the following network protocols: TCP/IP NetBIOS In the Remote Properties window, configure the other settings that you want to use. When you are finished, click OK. For more information, see the Symantec pcAnywhere User's Guide.
  • Page 66 A user name and password is required for all host sessions. You can configure other settings. For example, access privileges. For more information, see the Symantec pcAnywhere User's Guide. In the Host Properties window, configure the other settings that you want to use, and then click OK.

  • Page 67: Configuring A Host Item In Pcanywhere Host Administrator

    Configuring a host item in pcAnywhere Host Administrator The pcAnywhere Host Administrator tool lets you create a host item that you can distribute to the host computers in your configuration group. Symantec pcAnywhere requires that you set up a logon account for users who connect to your computer, and select an authentication method to verify their identities.

  • Page 68: Managing Hosts In A Configuration Group

    Performing centralized management Managing pcAnywhere hosts remotely In the Distribute pcAnywhere Files dialog box, select the computers to which you want to distribute the file. Select the file that you want to distribute. Click OK. Managing hosts in a configuration group Once you have configured the computers in your configuration group, use the pcAnywhere Host Administrator console to start, stop, or connect to any managed host in the group.

  • Page 69: Integrating With Microsoft Systems Management Server

    Management Server (SMS). SMS is a scalable change and configuration management system for Microsoft Windows-based computers and servers. Symantec pcAnywhere provides the support files needed to integrate with SMS. These files are offered only on the Symantec pcAnywhere CD. Importing the package definition file into SMS Symantec pcAnywhere provides a package definition file (pcAnywhere.pdf), which...

  • Page 70: Implementing Dcom In Windows 2000/2003/2008 Server/Xp/Vista

    The administrator's computer and the client's computer must be in the same domain. Modifying DCOM settings Symantec pcAnywhere configures DCOM during the installation process. The default settings should be sufficient for pcAnywhere management applications to function normally and maintain a sufficient level of security. However, administrators can modify the default security settings in DCOM to allow or deny access to a system.

  • Page 71: About Awshim

    Performing centralized management About the Microsoft Distributed Component Object Model (DCOM) For more information, consult the dcomcnfg.exe online documentation. To modify DCOM settings In Windows 2000/2003/2008 Server/XP/Vista, open the \WinNT\System32 folder, and then run dcomcnfg.exe. About AwShim AwShim is the management component that bridges pcAnywhere and the centralized management integration.

  • Page 72: About Centralized Logging

    The pcAnywhere Host Administrator tool lets you retrieve log files from a host computer on the network . You can then view and process them locally. Symantec pcAnywhere also supports logging to a Simple Network Management Protocol (SNMP) console. SNMP is used to send SNMPv1 traps to a compatible console that records the information.

  • Page 73: About The Pcanywhere Mib File

    Performing centralized management About centralized logging Select the events that you want to log. For more information, see the Symantec pcAnywhere User's Guide. Click OK. About the pcAnywhere MIB file The pcAnywhere MIB file outlines the SNMP traps that pcAnywhere can generate.
  • Page 74 Performing centralized management About centralized logging...

  • Page 75: Integrating Pcanywhere With Directory Services

    Chapter Integrating pcAnywhere with directory services This chapter includes the following topics: About directory services Using directory services with pcAnywhere Configuring the directory servers Configuring pcAnywhere to use directory services About directory services The directory services capability in pcAnywhere is an example of a Lightweight Directory Access Protocol (LDAP) client application, which stores and retrieves information about users.

  • Page 76: Configuring The Directory Servers

    Integrating pcAnywhere with directory services Configuring the directory servers When the remote starts, a new application, the directory services browser, launches and connects to an LDAP server. The directory services browser queries all entries that satisfy its filter criteria and displays the entries in a list view. You can then select the host to which you want to connect from this list.
  • Page 77 Integrating pcAnywhere with directory services Configuring the directory servers Adding the snap-in Follow this procedure to add the snap-in to the Microsoft Management Console (MMC). To add the snap-in On the Windows taskbar, click Start > Run. Type mmc Click OK. On the Console1 toolbar, click Console >...
  • Page 78 Integrating pcAnywhere with directory services Configuring the directory servers Click OK. In the left pane, right-click the Classes folder, and then click Create Class . Continue through the warning message. Creating the pcaHost object Follow this procedure to create the pcaHost object. To create the pcaHost object In the Common Name entry field, type pcaHost...
  • Page 79 Integrating pcAnywhere with directory services Configuring the directory servers Click OK. In the left pane, right-click Active Directory Schema. Click Reload the Schema. Setting the rights for the pcAnywhere user To set up the rights for the pcAnywhere user, you must first set up view rights, and then set up edit rights.

  • Page 80: Configuring Pcanywhere To Use Directory Services

    Integrating pcAnywhere with directory services Configuring pcAnywhere to use directory services Click OK. In the Allow column, select Write. Click Advanced. Select the Self group that you just added, and then click View/Edit. On the Object tab, in the Apply onto list, click Child objects only. Click OK until you close the Security property page.

  • Page 81: Setting Up The Host Computer To Use Directory Services

    Click OK. Symantec pcAnywhere attempts to connect to the directory server and search for the entry specified in the Name field. If multiple entries are found, users must select the one that represents them. Once the entry is identified, pcAnywhere stores its Distinguished Name in the registry for easy identification, and labels the entry as Verified.

  • Page 82: Setting Up The Remote Computer To Use Directory Services

    Integrating pcAnywhere with directory services Configuring pcAnywhere to use directory services Setting up the remote computer to use directory services When you set up a remote connection to use directory services, the remote looks on the directory server for waiting host connections. Configure the directory server entries before beginning this procedure.

  • Page 83: Managing Security In Symantec Pcanywhere

    “Limiting connections to specific computer names or IP addresses” on page 84. Serialize pcAnywhere installations. Symantec pcAnywhere lets you create custom installation packages with an embedded security code, or serial number. This serial number must be present on both the host and remote computers to make a connection.

  • Page 84: Limiting Connections To Specific Computer Names Or Ip Addresses

    Limiting the number of consecutive times that a remote user can attempt to log on to the host computer helps protect against hacker and denial of service attacks. Symantec pcAnywhere ends the connection if a remote user is not able to log on successfully before reaching the limit.

  • Page 85: Leveraging Centralized Authentication In Pcanywhere

    Click OK. Leveraging centralized authentication in pcAnywhere Symantec pcAnywhere requires you to create a caller logon account for each remote user or user group who connects to the host computer and to select an authentication method for verifying the user's identity. This information is required for all host sessions to prevent unauthorized access.
  • Page 86 Networking Shared Directory. Setting up Windows NT authentication for global users Symantec pcAnywhere lets you configure a server using NT authentication to support callers from the local administrator user group and any global groups that are included in the local group.
  • Page 87 Managing security in Symantec pcAnywhere Controlling access to pcAnywhere hosts To set up Windows NT authentication for global users In the pcAnywhere Manager window, on the left navigation bar, click Hosts. Do one of the following: To add a new connection item, on the File menu, click New Item >...

  • Page 88: Protecting Session Security

    Protecting session security Symantec pcAnywhere provides a number of options to protect the privacy of a session and prevent users from performing specific tasks that might interfere with the host session. These security measures provide an additional layer of security, but are most effective when used in combination with stronger security features in pcAnywhere.
  • Page 89 Managing security in Symantec pcAnywhere Protecting session security Session security options Table 6-3 Option Description Strong encryption Protect the data stream, including the authorization process, from eavesdropping and hacker attacks by using strong encryption. Symantec pcAnywhere supports public-key and symmetric types of strong encryption.

  • Page 90: Configuring Pcanywhere To Use Public-Key Encryption On Windows Vista/2008 Server

    Log off the host user. Restart the host computer. Lock the computer. For more information, see the Symantec pcAnywhere User's Guide. Configuring pcAnywhere to use public-key encryption on Windows Vista/2008 Server Although a user can be logged on as an administrator on Vista/2008 Server, it runs all applications with standard user privileges.

  • Page 91: Maintaining Audit Trails

    Symantec pcAnywhere lets you save chat logs in a local directory. Although logging can be a useful tool, be aware that tracking some types of events can degrade performance.

  • Page 92: Importing The Pcanywhere Administrative Template

    Open. In the Add/Remove Templates window, click Close. Managing user policies Symantec pcAnywhere lets you control whether users can access certain portions of the user interface or perform certain functions in pcAnywhere. Table 6-4 lists information about the policy settings that pcAnywhere lets you...
  • Page 93 Managing security in Symantec pcAnywhere Implementing policy-based administration Location of pcAnywhere policy settings Table 6-4 Folder Description Actions Contains policy settings to prohibit users from doing the following: Launching the pcAnywhere Manager window, which is the main user interface for pcAnywhere...
  • Page 94 Managing security in Symantec pcAnywhere Implementing policy-based administration Location of pcAnywhere policy settings (continued) Table 6-4 Folder Description UI Changes\Remote Objects Contains policy settings to prohibit users from doing the following: Editing remote objects Creating remote objects Changing the directory location of remote objects...
  • Page 95 Under User Configuration, click the plus sign next to Administrative Templates to expand the list. Click the plus sign next to Symantec pcAnywhere to expand the list. Open the folder that contains the policy settings that you want to edit.
  • Page 96 Managing security in Symantec pcAnywhere Implementing policy-based administration...

  • Page 97: Index

    Index Symbols connection items host 31 .bhf files 22, 66 remote 32 .chf files 22, 65 custom commands .cif files 22, 66 adding to package definition files 36 .cqf files 22 overview 34 .sid files 25 custom installations. See packages ACE/Agent.
  • Page 98 36 building 38 integrity management 23 importing into SMS 69 IP addresses viewing product requirements 36 limiting connections by 84 Packager. See Symantec Packager packages adding configuring files 21 adding custom commands 34 license agreements building 38 Symantec Packager 15...
  • Page 99 33 SNMP traps 91 product updates 33 logging 72 remote templates 32 Start.htm file 48 serializing 25 Symantec Packager setting global options 27 customizing products 18 testing 38 importing product modules 18 pcAnywhere Tools process overview 16 Host Administrator 61 system requirements 16 pcAnywhere.adm file 92...

This manual is also suitable for:

Pcanywhere 12.5

Table of Contents