Get-ASVirtualReadiness
Powershell cmdlets are enabled with AdminStudio Enterprise Edition and with Workflow Manager.
Use the Get-ASVirtualReadiness cmdlet to obtain the virtualization readiness status of a given package.
Example
Get-ASVirtualReadiness -PackagePath "\\111.22.33.44\Packages\win32-setup.msi" -PackageId 425
Parameters
The Get-ASVirtualReadiness cmdlet has the following parameters:
| Parameter | Description |
|---|---|
| PackagePath | Mandatory parameter which specifies the path to the package that you want to obtain the virtualization readiness status of. |
| [PackageId] | Specify the package ID of package that you are testing so that the virtualization readiness status returned by the Get\-ASVirtualReadiness cmdlet will be stored in the Application Catalog. |
Return Values
If an error or warning is generated, one of the following values is returned
| Value | Type | Name | Description |
|---|---|---|---|
| 32 | Click Once | Package contains a ClickOnce application. ClickOnce is a per-user installation format that is often incompatible with the per-machine nature of virtual package deployment. A ClickOnce application also may try to automatically update itself, which results in invalid versioning in the application virtualization client. | |
| 64 | Shell Extension | Package contains a shell extension. Shell extensions extend Windows Explorer and cannot be loaded from a virtual package. This extension may be critical to the use of this application, and, if so, this application will not function when virtualized. However if this extension is non-critical, the application may function when virtualized. | |
| 128 | OS Integrated | Package contains files that are closely integrated with the operating system. The files that make up applications like Internet Explorer or Windows Media Player, or frameworks like the .NET Framework, do not make good candidates for virtualization. These files should instead be installed locally on the machine. | |
| 256 | Boot Service | Package contains a service that starts at boot-time. Virtualized services are limited to the lifetime of the virtual application, so services that must start at boot-time do not make good candidates for virtualization to App-V or XenApp formats. It may be possible to extract this service such that it can be installed locally on the machine and allow the rest of the package to be virtualized. | |
| 512 | Too Large | Package contains more than 4 GB of files. Since App-V 4.x and XenApp do not support packages that contain more than 4 GB of files, this application cannot be successfully virtualized to App-V 4.x or XenApp as an uncompressed package. However, if the compressed size of the package is less than 4 GB, then this application can be virtualized to these formats as a compressed package. | |
| 1024 | COM Surrogate DLLs | Package contains a COM DLL that uses surrogate virtualization. App-V, XenApp, and ThinApp do not support COM DLL surrogate virtualization, so this package may not work correctly if virtualized.. | |
| 2048 | COM Plus | Package contains a COM Plus component. App-V, XenApp, and ThinApp do not support COM+ components, so this package may not work correctly if virtualized. | |
| 4096 | Device Drive | Package contains a device driver. System-level drivers such as print drivers or USB device drivers do not work from a virtualized environment. It may be possible to extract this driver such that it can be installed locally on the machine and allow the rest of the package to be virtualized. | |
| 8192 | Questionable | Package is questionable for conversion. | |
| 16384 | Unsuitable | Package is unsuitable for conversion. | |
| 32768 | 64-Bit Package | Package is a 64-bit package. XenApp and ThinApp do not support virtualization of 64-bit packages. | |
| 65536 | ASP.NET/IIS Application | Package contains an ASP.NET or IIS application component, which is not supported by App-V 4.x, App-V 5.x, XenApp, and ThinApp. If the ASP.NET or IIS application component is not an important part of the application, or if it can be separately installed from the package, this error can be suppressed and ignored. | |
| 131072 | WMI Provider | Package contains a WMI provider component, which is not supported by App-V 4.x, App-V 5.x, XenApp, and ThinApp. If the WMI Provider component is not an important part of the application, or if it can be separately installed from the App-V package, this error can be suppressed and ignored. | |
| 262144 | J2EE Application Server | Package contains a J2EE application server, which is not supported by App-V, XenApp, or ThinApp. If the J2EE application is not an important part of the application, or if it can be separately installed from the package, this error can be suppressed and ignored. | |
| 524288 | Unsupported Application | Package contains an application known to not be a good candidate for virtualization. | |
| 1048576 | Unsupported Application | Package contains some files that indicate the presence of unsupported applications such as antivirus software or various server software such as Exchange Server or SQL Server. If these unsupported application components are not an important part of the application, or if they can be separately installed from the package, this error can be suppressed and ignored. | |
| 2097152 | URL Protocol | Package registers an URL protocol. | |
| 4194304 | Default Program | Package registers its capabilities in the Default Programs list. |