Symantec 14541094 Administration Guide - Page 52

Customizing Launch.bat, File2=Symantec pcAnywhere - Host Only.msi

Get Symantec 14541094 - pcAnywhere Host & Remote PDF manuals and user guides
UPC - 037648640480
View all Symantec 14541094 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 52 highlights

52 Deploying Symantec pcAnywhere custom installations Deploying installation packages using Web-based deployment To customize Files.ini for MSI deployment 1 In a text editor, open Files.ini. 2 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 Delete the semicolon next to the line File2= to uncomment the entry. 6 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 For each additional file, add a new Filen= filename line, where n is a unique number and filename is the name of the file. 8 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. This command

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
To customize Files.ini for MSI deployment
1
In a text editor, open
Files.ini
.
2
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
Delete the semicolon next to the line File2= to uncomment the entry.
6
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
For each additional file, add a new File
n
=
filename
line, where n is a unique
number and filename is the name of the file.
8
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. This command
Deploying Symantec pcAnywhere custom installations
Deploying installation packages using Web-based deployment
52