This documentation applies to Adxstudio Portals 6.0. PortalDeploy has been removed from Adxstudio Portals 7.0, in favour of the Adxstudio Installer system.

PortalDeploy.exe is a wizard application that assists with the setup of a new IIS 7 website consisting of an operational Adxstudio sample portal. An existing Microsoft Dynamics CRM 2011 server is required along with an organization prior to running the tool. Depending on the current state of the organization, the tool can import the required solutions as well as import sample website content.

To use the PortalDeploy.exe, download and install AdxstudioPortals.msi on the IIS 7 server.

PortalDeploy.exe is located in %PROGRAMFILES(X86)%\Adxstudio\XrmPortals\4.x.xxxx\Utilities\

The following demonstrates the steps to getting a Basic Portal sample website running on a new organization.

Create a New Organization

Sign into the Microsoft Dynamics CRM 2011 server as a deployment administrator. Launch the Microsoft Dynamics CRM Deployment Manager to create a new organization.

Specify the Organization Settings

Continue through the New Organization Wizard until the organization is created.

New organization created

Open Internet Explorer and sign into the new organization as the deployment administrator that created the organization. Adxstudio Portals connects to CRM based on a proxy system user account. Navigate to Settings -> Administration -> Users in order to create the proxy account. Assign the user to the System Administrators role.

New user form

Run the Portal Deploy Tool

Sign into the IIS server that will be hosting the deployed portal and launch the tool. The welcome screen provides an overview of the steps to be performed. You may quit the tool anytime prior to the final step without applying any changes.

Welcome to the wizard

IIS Configuration

The portal can be deployed to a new website or to an application within an existing website. Specify a new target folder where the website files will be copied. This is a required step.

Create a new website or application

Portal Configuration (web.config)

This step deals with the connection string and other configuration elements of the portal web.config. The (optional) connection string settings should specify the proxy user created prior to running the tool.

Depending on the authentication type selected, there may be subsequent steps shown to provide settings relevant to the authentication type.

Since this is a fresh organization without existing authenticated contacts that are associated to a particular machine key, a new random machine key can be generated.

Specify configuration

The "Windows Azure AppFabric ACS" authentication type was selected in the previous step. As a result, an intermediate configuration step is shown to provide specific settings.

ACS configuration

Deployment Administrator Operations

In order for the tool to import the required solutions, it needs to connect with an administrator account. Since the tool is running as the deployment adminstrator used to create the organization, an integrated authentication connection is used in this step.

Connect to the CRM

Import Solutions

This step shows that there are no customizations applied to the organization as expected. It is also visible in the Publisher value of the Default Solution that the tool is connected to the correct organization. This step can be skipped and performed later by following the steps from here. In this case, the subsequent "website copy" step is also performed separately.

Import solutions

Website Copy

It is also expected that a fresh organization does not contain website content. Click 'Next' to allow the tool to copy sample content to the organization. Alternatively, this step may be skipped and performed later using the Website Copy tool.

Import portal entities

Review

This step is the last chance to review the changes and cancel if necessary.

Apply changes

It takes several minutes for the changes to be applied.

Progress

Completed

If the correct values are specified during the portal configuration step(s), the new sample portal should open successfully on the home page. Otherwise, it may be necessary to edit the web.config of the deployed files to correct any errors.

At this point, PortalDeploy.exe can be rerun to deploy another sample website to the same organization.