At Security > Applications > User Installed Applications you can configure User Installed Applications. User Installed Applications give users the right to install software on specific computers. This can be particularly useful to give expert users a degree of control over their own computer, so that they can install software themselves as and when needed. User Installed Applications are always restricted to specific computers, based on Workspace Containers and/or Zones, and can optionally be further restricted to specific users.
For example, a department may be in the process of developing a new application. They receive new versions several times a week, and each version needs to be installed before it can be tested. It is extremely inefficient for the administrator to have to do this each time. Instead, you can enable User Installed Applications with Access Control set to specific people in that department, and Workspace Control set to a Workspace Container that holds the computers in that department. As a result, the specified users can install the updates on the specified computers.
Similarly, a small number of people might use a highly specialized software package such as AutoCAD. They may well know more about the software than the administrator does, and so it makes more sense to allow them to install the AutoCAD updates or extensions themselves.
Users who are allowed to install User Installed Applications on a computer, get an extra tab in their Workspace Preferences tool, the Other tab. From this tab users can install software using a wizard. With this wizard, they can create shortcuts for these applications in their Start menu, on their Desktop, on their Quick Launch bar and in their Startup items. These applications can also be deleted via the Workspace Preferences tool and be changed.
Export log to CSV file
To export the information found under the Log tab as a CSV file, follow these steps:
Open the Workspace Control Console and navigate to Security > Applications > User Installed Applications > Log tab.
Right-click on any entry and then select Export to file from the context-menu.
Select a location where to save the CSV file, enter an appropriate name for the file and then select Save.
Export log using the command line
Ivanti recommends to test first by exporting just one or two days of data.
Security logs can also be exported using the pwrtech command line:
pwrtech.exe /exportlog /type=uia /output=<output filepath> [/outputtype=csv] [/start=<start date>] [/end=<end date>]
/outputtype, /start and /end are optional parameters. If /outputtype is not specified, then the security logs are exported as XML files instead of CSV files.
Replace the following with the appropriate values:
<output filepath> — Enter the full filepath where to save the CSV or XML file.
For example: C:\export\user_installed_apps.csv.
<start date> — Enter the start date to export log entries starting with the specified date.
The format for date is YYYYMMDD. For example: 20161130.
<end date> — Enter the end date to export log entries up to the specified date.
The format for date is YYYYMMDD. For example: 20180523.
pwrtech.exe /exportlog /type=uia /output=C:\export\user_installed_apps.csv /outputtype=csv /start=20161130 /end=20180523