User manual SYMANTEC PCANYWHERE ADMINISTRATOR GUIDE V12.1

[. . . ] Symantec pcAnywhereTM Administrator's Guide Symantec pcAnywhereTM Administrator's Guide The software described in this book is furnished under a license agreement and may be used only in accordance with the terms of the agreement. Documentation version 12. 1 Legal Notice Copyright © 2007 Symantec Corporation. Federal acquisitions: Commercial Software - Government Users Subject to Standard License Terms and Conditions. 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. [. . . ] The default value for this parameter does not need to be changed unless you have renamed Files. ini. The subdirectory that contains the source files to be downloaded locally. This subdirectory contains the package and Files. ini (for example, Webinst). The default value is appropriate. VirtualHomeDirectory ConfigFile ProductFolderName MinDiskSpaceInMB ProductAbbreviation To customize Start. htm 1 2 3 In a text editor, open Start. htm. Save and close the file. Customizing Files. ini for package deployment Modify Files. ini to contain the name of the package executable file that you want to deploy. See "Customizing Files. ini for MSI deployment" on page 49. Deploying Symantec pcAnywhere custom installations Deploying installation packages using Web-based deployment 49 You can also include additional files to support the deployment of third-party applications. To customize Files. ini for package deployment 1 2 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. For example: LaunchApplication=Symantec pcAnywhere - Full Product. exe 3 If you are deploying multiple files, edit the FileCount= line to reflect the number of files that you want to deploy. The default setting is FileCount=1. 4 In the [Files] section, edit the line File1= so that it references the name of the package that you want to deploy. For example: File1=Symantec pcAnywhere - Full Product. exe Long file names are supported. 5 6 For each additional file, add a new Filen= filename line, where n is a unique number and filename is the name of the file. Save and close the file. Customizing Files. ini for MSI deployment Modify Files. ini to contain the names of the . msi files that you want to deploy. MSI deployment requires Launch. bat, which is used to start the installation program. You can also include additional files to support the deployment of third-party applications. 50 Deploying Symantec pcAnywhere custom installations Deploying installation packages using Web-based deployment To customize Files. ini for MSI deployment 1 2 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 to deploy. 3 Edit the FileCount= line to reflect the number of files that you want to deploy. MSI deployment requires two files, so the FileCount= line must be set at least to two. For example: FileCount=2 4 In the [Files] section, edit the line File1= so that it references the Launch. bat file. For example: File1=Launch. bat 5 6 Delete the semicolon next to the line File2= to uncomment the entry. Edit the line File2= so that it references the name of the . msi file that you want to deploy. For example: File2=Symantec pcAnywhere - Host Only. msi Long file names are supported. 7 8 For each additional file, add a new Filen= filename line, where n is a unique number and filename is the name of the file. [. . . ] These settings include registry keys and values, the location in which the registry settings will be written, and other descriptive information. Importing the pcAnywhere. adm file for Windows 2000/2003 Server/XP/Vista The pcAnywhere. adm file for Windows 2000/2003 Server/XP/Vista is located on the pcAnywhere CD in the Tools\Policy folder. You can copy this file to a secure location, and then import it into MMC. Before you import this file, ensure that you have added the Group Policy snap-in to MMC. For more information about how to add the Group Policy snap-in to MMC, see the online documentation for your operating system. Managing security in Symantec pcAnywhere Implementing policy-based administration 99 To import the pcAnywhere. adm file for Windows 2000/2003 Server/XP/Vista 1 On the Windows taskbar, click Start > Run, and then type the following: gpedit. msc 2 3 4 5 6 In the console window, in the left pane, select the Group Policy object for which you want to set policies. [. . . ]