When you run PowerBuilder on Windows Vista or Windows 7 under a standard user account, and attempt to deploy Web Forms or Web Service projects, the User Account Control (UAC) dialog box appears. This dialog box allows you to elevate your privileges for the purpose of deployment.
| Settings for | Required changes |
|---|---|
| Windows firewall | Enable exceptions for WMI and file and printer sharing |
| UAC (When you are not running PowerBuilder with the built-in Administrator account) | If the development and deployment computers are in the same domain, connect to the remote computer using a domain account that is in its local Administrators group. Then UAC access token filtering does not affect the domain accounts in the local Administrators group. You should not use a local, nondomain account on the remote computer because of UAC filtering, even if the account is in the Administrators group. If the development and deployment computers are in the same workgroup, UAC filtering affects the connection to the remote computer even if the account is in the Administrators group. The only exception is the native “Administrator” account of the remote computer, but you should not use this account because of security issues. Instead, you can turn off UAC on the remote computer. and if the account you use has no remote DCOM access rights, you must explicitly grant those rights to the account. |
| DCOM | Grant remote DCOM access, activation, and launch rights to a nondomain user account in the local Administrators group of the remote computer if that is the type of account you are using to connect to the remote computer. |
Virtual directories in IIS 7 and later are hosted in an application pool. An application pool is the host process for one or more Web applications. When you deploy a PowerBuilder Web Forms application to IIS 7 or later, the application is deployed to a PowerBuilder-specific application pool named PBDotnet4AppPool. On 64-bit operating systems, the PBDotnet4AppPool pool is configured to run 32-bit applications.
To avoid compatibility issues with some features, Web Forms applications deployed from PowerBuilder to IIS 7 or IIS 7.5 must run in an application pool that uses the classic managed pipeline mode, where ASP.NET runs as an ISAPI extension. The PBDotnet4AppPool application pool uses the classic managed pipeline mode by default.