Add-OemEnvironmentPath
PackageDeployment Module Help |
Package Deployment Module (DSM eScript Commands) |
Add-OemEnvironmentPath Cmdlet |
Version 1.0.0.3 |
Add-OemEnvironmentPath
Synopsis
Append Path to Any File
Syntax
Add-OemEnvironmentPath [-Path] <String> [[-Position] <String>] [[-DialogTitle] <String>] [-ConfirmChanges] [-ContinueOnError] [-Wow64] [-BatchFile] <String> [[-Context] <String>] [<CommonParameters>]
Description
Use this command to extend the path statement in any batch file (*.BAT).
Parameters
-BatchFile <String> |
||||||
Specify the name (with path, if necessary) of the batch file you want to change. |
||||||
|
-ConfirmChanges <SwitchParameter> |
||||||
If checked, all changes must be confirmed. When the installation package is executed, a dialog box will be displayed, containing two text boxes: the entry in the first text box shows the current version of the AUTOEXEC.BAT file and the second text box contains the proposed new version (You cannot access this dialog box from Windows NT). |
||||||
|
-Context <String> |
||||||
User: Execution under user account; logging in HKEY_CURRENT_USER, i.e. for the user. |
||||||
|
-ContinueOnError <SwitchParameter> |
||||||
Continues script execution in spite of errors in the respective command |
||||||
|
-DialogTitle <String> |
||||||
If you want to inform the user about modifications to the path statement, you must enter the name of the application for which you extended the path statement. A message box will be displayed when the installation package is executed. |
||||||
|
-Path <String> |
||||||
Enter the directory or directories you want to add to the path statement. Check the option to ensure that the extension is inserted at the beginning of the statement. |
||||||
|
-Position <String> |
||||||
Enter the line in the AUTOEXEC.BAT file before or after which the new path statement should be placed. You can use wildcards here. |
||||||
|
-Wow64 <SwitchParameter> |
||||||
For reasons of compatibilty, Ivanti DSM maps file and registry access to the default storage location for 32 bit applications (provided that the storage location differs from that of 64-bit applications). File access: whenever a 32-bit application attempts to access %windir%\System32, the access is redirected to %windir%\SysWOW64. Registry commands: when accessing HKEY_LOCAL_MACHINE\SOFTWARE the calls are redirected to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node. The x64-switch stops this redirection of file and registry accesses when running the script command on a x64 computer; the eScript command runs on the specified path. CallScript command: the script runs in a 64-bit process. |
||||||
|
<CommonParameters> |
For more information about common parameters, type "Get-Help about_CommonParameters". |