RemoveIcon

Delete Program Manager Icon

Definition

Use this command to delete a Program Manager icon.
When deleting a program icon, you can use the standard Program Manager properties.

Settings

Input

Description
Describes the program icon; the entered text will appear below the icon in the Program Manager.
Command line
Displays the location and name (including the file name extension and required parameters) of the program file. This line will not be deleted!

Options

To ensure that the correct icon is deleted, the Installer compares the parameters. You can set the parameters for comparing icons and programs using the following options

Path
The path statements specified in the Command line text box must be identical.

File name extension
The file name extensions specified in the Command line text box must be identical.

Call parameters
The parameters specified in the Command line text box must be identical (entered directly after the program file name).

Description
The description of the program icon must be identical.

Old description
The "old" description of the program icon must be identical. You can use wildcards; for example, *Word* or dsm?. The number of wildcards is not restricted and there are no general restrictions for the use of wildcards, as they exist under DOS.

Overwrite settings

When deleting program icons, you can additionally specify the origin of the program file (network or local installation) in the Drive section of the command dialog box:

Network
Deletes the program icon only if the executable program file resides on the network.

Local
Deletes the program icon only if the executable program file resides on a local drive.

Unspecified
Deletes the program icon regardless of the origin of the executable program file.

Confirmation

Confirm delete
If checked, the user has to confirm that an existing program icon will be deleted.

Disable file redirection on x64 machines
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.