Added support for remote deployment (Vista and IIS 7)

PowerBuilder 11.5 .NET targets do not require you to have IIS installed on the development computer, and remote deployment of .NET targets has been enhanced. When you deploy directly to a remote computer, system information about the deployment computer, including its OS and IIS versions, is passed to PowerBuilder through the Windows Management Instrumentation (WMI) interface.

If you deploy to an MSI setup file, and run the setup file on a deployment computer, PowerBuilder can use the Windows API to obtain information about the OS and IIS versions on that computer.

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.

IIS 7 deployment enhancement For local or remote deployment from PowerBuilder 11.5 Web Forms or Web Service projects, you can deploy to IIS 7 servers that were not installed with IIS 6 compatibility.