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. [. . . ] See "Customizing Launch. bat" on page 50. 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. Save and close the file. Customizing Launch. bat Launch. bat contains the command line argument used to execute an MSI installation. This file is required only for MSI installations. Modify Launch. bat to specify the . msi file that you want to deploy. The default Launch. bat file sets the path to the Windows system directory. Deploying Symantec pcAnywhere custom installations Deploying installation packages using Web-based deployment 51 You must also modify the Files. ini file to run Launch. bat. See "Customizing Files. ini for MSI deployment" on page 49. Note: Installation of . msi files requires Windows Installer 3. 1 or later. You should ensure that the target computer meets the system requirements before you deploy the product installation. To customize Launch. bat 1 2 3 In a text editor, open Launch. bat. Ensure that the following command line is included in the file: @SET PATH=%path%;%windir%\system Edit the line @msiexec -i Package. msi so that it reflects the name of the . msi file that you want to deploy. For example, @msiexec -i Symantec Packager - Host Only. msi 4 Save and close the file. Testing the installation on the Web server To test the installation, go to the Web site (for example, <your web site>/webinstall), and then click Install. If the installation fails, note any error messages that are displayed. Use the following guidelines to troubleshoot the problem: If there is a problem with the parameters in Start. htm, an error message shows the path of the files that the Web-based installation is trying to access. [. . . ] 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. Under the Group Policy object, right-click Administrative Templates, and then click Add/Remove Templates. In the Add/Remove Templates window, click Add. Browse to the location of the pcAnywhere. adm file, select it, and then click Open. [. . . ]