Windows Vista and Windows 2008 configuration requirements

Deployment to and from Windows Vista or Windows 2008

When you run PowerBuilder on Windows Vista or Windows 2008 under a standard user account, and attempt to deploy Web Forms or Web Service projects, the User Account Control (UAC) dialog box displays. This dialog box allows you to elevate your privileges for the purpose of deployment.

Deploying .NET targets to a remote Windows Vista or Windows 2008 computer might require changes to the Windows firewall, UAC, or the Distributed Component Object Model (DCOM) settings.

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.

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.

Deploying to the default application pool

Virtual directories in IIS 7 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 in PowerBuilder, the application is deployed to a PowerBuilder-specific application pool named PBAppPool. On 64-bit Vista, the PBAppPool pool is configured to run 32-bit applications.

To avoid compatibility issues with some features, Web Forms applications deployed from PowerBuilder to IIS 7 must run in an application pool that uses the classic managed pipeline mode, where ASP.NET runs as an ISAPI extension. The PBAppPool application pool uses the integrated managed pipeline mode by default, but you should change it to use the classic mode if your applications use TreeView controls, StaticHyperLink controls, or currency mask conversions.

To change the PBAppPool managed pipeline mode to classic:

In IIS Manager, select Application Pools.
In the list of Application Pools, double-click PBAppPool.
Set Managed Pipeline Mode to Classic and click OK.

Changing this setting affects all applications running in the PBAppPool application pool.

Creating a new application pool

You can also create a different application to host PowerBuilder Web Forms applications.

To create and configure a new application pool for Web Forms applications:

In IIS Manager, select Application Pools.
In the Actions pane, select Add Application Pool.
Provide a name, such as PBWebForms, for the application pool.
Set .NET Framework version to .NET Framework v2.0.50727.
If necessary, set Managed Pipeline Mode to Classic and click OK.

Enabling 32-bit applications on 64-bit Vista

On 64-bit Vista, you must enable the application pool to run 32-bit applications.

To enable 32-bit applications on 64-bit Vista:

In IIS Manager, select Application Pools.
In the list of Application Pools, select the application pool you have configured for use with PowerBuilder Web Forms.
In the Actions pane, select Advanced Settings under Edit Application Pool.
Expand the General settings, set Enable 32-bit Applications to True, and click OK.

Moving an application into a different application pool

If you have created and configured a new application pool for PowerBuilder, you need to move your PowerBuilder Web Forms applications into the pool.

To move an application into a different application pool:

In IIS Manager, expand Web Sites and Default Web Site.
Right-click the virtual directory for your application and click Advanced Settings.
Select the drop-down list next to the Application Pool property, select the application pool you created, and click OK
Reload the application.

Application directory permissions

When you deploy a new Web Forms target, a temp directory is created in the Inetpub\wwwroot\application_name directory, where application_name is the name of your application, and several subdirectories are created in the Inetpub\wwwroot\application_name_root directory. Files are written to and deleted from these directories, therefore the IIS_IUSRS group must have full permissions on temp and application_name_root.