The following custom inventory will query WMI for IIS virtual directories. The custom inventory will return the virtual directory name and the physical path it points to. Other WMI classes in this name space returned the virtual directory name but this is the only one found to include the path, so it was chosen for this example.

Microsoft includes a WMI provider for IIS. This information is in the root\MicrosoftIISv2 namespace, rather than the root\cimv2 namespace, which we usually tend to utilize in custom inventories. Check with Microsoft for other names for this namespace as it appears to have a version embedded in the name. You may need to update the wmi query to suit your own environment. You also may need multiple copies of this custom inventory source file and corresponding collections, policies, and so on, if different versions of IIS are installed in your environment.

Also, there are many other properties in this WMI class that may or may not prove helpful....

Just in case you forgot exactly what page of the documentation details the Wise switches, here's a list (from user kv17675) that you can bookmark.

Wise Setup.exe Switches

/T test mode
/X pathname extracts files into pathname
/Z pathname extracts files into pathname and reboots
/S silent install
/M prompts for windows, system, temp dirs
/M=filename specifies a value file similar to /d above,
but for standard variables
/M1 same as /m plus it prompts before any file that is self-registered
/M2 reserved for internal use by Wise during debugger sessions

Uninstall (Unwise.exe switches)

/Z remove empty directories, including one with unwise itself in it.
/A automatic mode, no user choices other than cancel.
/S silent mode, automatic mode...

How does the Software Portal manage Tasks and Collections for Software Requests?

Get answers to these modern mysteries and a few extras thrown in for good measure.

Collections and Tasks
The Software Portal Creates hidden Tasks and Collections to manage the distribution of Requested Software to the target system.

Request Versus Deployment
When accessing the Software Portal, the Portal is constructed based off the Logged On User. The available packages are those the user had rights to within the Software Portal. Deployment Software switches the focus from the Logged On User to the Computer from where the request was initiated from.

Items created by a Software Portal Request

• The Software Delivery Solution Agent (AeXSWDAppReqAgent.dll) contacts the Notification Server to have the items created.
• A Task with the naming convention: Software Request: is created. For example, to bring back every...

Here are the step-by-steps to follow if you find yourself needing to move your NS Tasks and/or Packages from one server to another.

The following items should be exported from the console. Use the right-click context menu to choose the Export option. It is recommended to simplify the process by exporting folders containing the items rather than each individual item.

1. Software Delivery Packages located at the Resources tab > Resources > Software Management > Software Delivery Packages > Windows.
2. Software Delivery Tasks located at the Tasks tab > Software Management > Software Delivery > Windows > Software Delivery Tasks. (Note: You may want to export folders only under this folder as this folder contains the code for the Wizard and Status utility.)
...