Websitepanel Deployment

WebsitePanel Control Panel Deployment Description

Control Panel Deployment Description
This document is the deployment description of the Control Panel. The deployment package contains the solution components but does not contain an automated way to deploy the solution as such.
The following components/service offerings are supported:

• Active Directory (Hosted Organizations)
• Hosted Exchange 2010 SP2 Enterprise Server
• SharePoint Foundation 2010
• OCS 2007 R2 core unified communications
• BlackBerry Enterprise Server 5.0
• Hosted CRM 4.0
• IIS7.0/7.5 based webhosting
• Microsoft SQL Server 2008 (R2) based data      hosting
• Windows 2008 R2 based external DNS

The solution package
The solution package contains the following components:

• Server
• Enterprise Server
• Webportal

Pre requisites
The following pre requisites are required for each component:

Component	Description
IIS	The following powershell cmdled will   install the required IIS Configuration: Import-Module ServerManager Add-WindowsFeature NET-Framework,   Web-Server, Web-Static-Content, Web-Default-Doc, Web-Http-Errors, Web-Http-Redirect, Web-Asp-Net, Web-Net-Ext, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Http-Logging, Web-Log-Libraries, Web-Http-Tracing, Web-Windows-Auth, Web-Client-Auth, Web-Filtering, Web-Stat-Compression, Web-Mgmt-Console, Web-Scripting-Tools –Restart
.NET Framework 4.0	Download the .NET framework 4.0 from here

This guide explains how to configure the pre-requisites required on a Windows Server 2008 R2 installation for WebSitePanel installation. To prepare a server before you install WebSitePanel, run the Web Platform Installer, which you can download from the following location:
http://www.microsoft.com/web/downloads/platform.aspx
Web PI lists the latest products and libraries that are available for the current platform (Windows Server 2008 R2).
In the search box on the top right hand corner find “Web Deployment” and select the Web Deployment Tool 3.0 without bundled SQL Support option item to install the MS Deploy library. This library is required in order for WebsitePanel to integrate with the Microsoft Web App Gallery module.



Click back from Search option.
Click on the Products link and choose the Server Category. Select the following components for installation:

• IIS 7 Recommended Configuration
• IIS:HTTP Redirection
• URL Rewrite 2.0
• IIS:CGI
• IIS:FTP Publishing Service 7.5 (unless you plan to use one of the other supported FTP servers)
• IIS:Basic Authentication
• IIS:Windows Authentication

Choose the Frameworks Category and select the following components for installation:

• ASP.NET MVC 3
• PHP 5.x
• .NET Framework 3.5 SP1
• .NET Framework 4 (plus updates)

Choose the Database Category and select the following components for installation, the items marked in BLUE should only be installed on your intended (separate) database hosting server, it is not recommended to install them on the web server.

• SQL Server Express 2012 R2
• SQL Server 2012 Shared Management Objects
• Microsoft Drivers 3.0 for PHP v5.3 for SQL Server in IIS (don’t install the express version)
• SQL Server 2012 R2 Management Studio Express 

Click Install to start the installation process for the selected components. Before SQL Server 2008 is installed, you will be asked about its security mode. SelectMixed Mode Authentication and then specify a password for the sa account.
Once the installation completes reboot your server for all changes to take affect.

Installing WebsitePanel Components One-by-One

To install WSP Enterprise Server open WSPI, click "View Available Components" button and then "Install" link over "WebsitePanel Enterprise Server" row:

Click "Next" button to proceed to WSP ES installation wizard.
WSPI will check for minimum system requirements and if they are met "Next" button will be enabled:

Click "Next" button to switch to the next wizard step:

Specify folder on server hard drive to install WSP ES files and click "Next" button to go to the next step.
Specify WSP ES web site settings. If you are not going to expose Enterprise Server to external clients (3rd-party applications consuming ES web services) and WSP Portal will be installed on the same server we recommend keeping 127.0.0.1 as a web site IP address and default 9002 TCP port; otherwise you could select different IP address (from internal or external network pools) and TCP port for ES web site.
Click "Next" button to go to the next wizard step:

"Security Settings" step allows you to specify the name of user account that will be used as ES web site anonymous identity (IIS 6 only) and ES application pool identity (IIS 6 and IIS 7). There is an auto-generated password for this account already specified in "Password" field. It's GUID and strong enough to be discovered. Change password value if only you are going to manually modify web site or application pool settings later after ES installation. If you are installing WSP Enterprise Server in Active Directory environment you have an option to "Create Active Directory account"; otherwise local Windows account (SAM database) will be created.
WSP Enterprise Server application pool must be run under "weak" user account. By default WSPI creates an account which is a member of "IIS_WPG" (on IIS 6) or "IIS_IUSRS" (on IIS 7) group only.
For WSP Enterprise Server we recommend creating "local" account for tightened security.
Click "Next" to go to "Database Settings" wizard step:

Specify SQL Server 2005 or 2008 instance name in "SQL Server" field. For default SQL Server Express edition installation you could type "(local)\SQLEXPRESS", select authentication mode and specify database name.
Please note that these database settings will be used during WSP upgrades, so make sure they could be used to access SQL Server over time.
Click "Next" button to go to "Administrator Password" step:

Specify password that will be assigned to "serveradmin" account. You use top-level "serveradmin" account to configure WebsitePanel installation and create resellers/customers.
Default "serveradmin" password pre-filled on this dialog is "serveradmin" (without quotes).
We strongly recommend to replace default "serveradmin" password with your own strong one.
Click "Next" button to start the installation of WSP Enterprise Server.
After ES setup is complete you will see the following dialog:

You could click ES URL and open it in the web browser to make sure it was properly installed:

WebsitePanel Portal

To install WSP Portal open WSPI, click "View Available Components" button and then "Install" link over "WebsitePanel Portal" row:

WSPI will check for minimum system requirements and if they are met "Next" button will be enabled:

On the “Choose Install Location” step specify folder on server hard drive to install WSP Portal files and click "Next" button to go to the next step.
Specify WSP Portal web site settings. The URL shown on this page will be used to access your control panel. If you have a free IP address assigned to the server then we recommend to dedicate it for control panel and specify "80" for the port; otherwise in the case selected IP is shared by several web sites we recommend you to leave default IP address and 9001 port.
Make sure the custom port selected for this web site (9001 in our case) is allowed on server Firewall.
Click "Next" button to go to the next wizard step:

"Security Settings" step allows you to specify the name of user account that will be used as WSP Portal web site anonymous identity and WSP Portal application pool identity.
WSP Portal application pool must be run under "weak" user account. By default WSPI creates an account which is a member of "IIS_WPG" (on IIS 6) or "IIS_IUSRS" (on IIS 7) group only.
For WSP Portal we recommend creating "local" account for tightened security.
Click "Next" button to go to the next step:

On this step you have to specify URL to WSP Enterprise Server application. For default WSP ES installation it's http://127.0.0.1:9002. To make sure WSP ES is accessible from the server where you are installing WSP Portal you could open its URL in the web browser.
Click "Next" button to start WSP Portal installation.
After WSP Portal setup is complete you could see the dialog with installation log:

You could click Portal URL and open it in the web browser to make sure it was properly installed:

Try signing in under "serveradmin" (with appropriate password set during Enterprise Server installation) to make sure account home page could be accessed.

WebsitePanel Server

To install WSP Server open WSPI, click "View Available Components" button and then "Install" link over "WebsitePanel Server" row:

WSPI will check for minimum system requirements and if they are met "Next" button will be enabled:

Specify folder on server hard drive to install WSP Server files and click "Next" button to go to the next step.
Specify WSP Server web site settings. If you are installing WSP Server on the same server with WSP Enterprise Server we recommend keeping 127.0.0.1 as a web site IP address and default 9003 TCP port; otherwise you could select different IP address (from internal or external network pools) and TCP port for Server web site.
Click "Next" button to go to the next wizard step:

"Security Settings" step allows you to specify the name of user account that will be used as WSP Server web site anonymous identity and ES application pool identity. There is an auto-generated password for this account already specified in "Password" field. It's GUID and strong enough to be discovered. Change password value if only you are going to manually modify web site or application pool settings later after Server installation. If you are going to control Active Directory from WebsitePanel and installing WSP Server in Active Directory environment you have an option to "Create Active Directory account"; otherwise local Windows account (SAM database) will be created.
WSP Server application pool runs under "strong" user account with administrative privileges. By default, WSPI creates account which is a member of local "Administrators" security group (for local mode) or "Domain Admins" security group (for AD mode).
Click "Next" button to finish WSP Server installation. After Server setup is complete you will see the following dialog with installation log:

You could click Server URL and open it in the web browser to make sure it was properly installed:

Troubleshooting Installation Issues

Could not start WebsitePanel Installer on Windows 2008

This might be due to enabled User Account Control (UAC). As a solution you could disable UAC or run WSPI in "elevated" mode by right clicking its shortcut and selecting "Run as Administrator".

Viewing WebsitePanel Installer Error Log

To view WSPI application log click "Application Settings" node in the left navigation menu and then click "View System Log" button:

WSPI log will be opened in Notepad.

"Unable to generate a temporary class" or "Root element is missing" error message while opening WSP Portal

This error is related to Windows Server 2003 platform. This error means that IIS_WPG group doesn't have Read and List Folder Contents permissions on C:\Windows\Temp folder on the server where WSP Portal is running. Just add IIS_WPG group with Read and List Folder Contents permissions on the mentioned folder on the WSP Portal server.
Please note that you should grant permissions to the domain IIS_WPG group if WSP Portal is running on domain controller or local IIS_WPG group in other cases.
Also note that it is good practice to grant those permissions to IIS_WPG on C:\Windows\Temp folder (or another folder in case of non-standard Environment Variables settings) on all servers running any WSP component.

Web App Gallery cannot install ASP.NET applications with SQL Server database

Open SQL Server service settings in control panel and change security mode to "SQL Server Authentication". Specify "sa" username and its password and click "Update" button to save changes.

WebsitePanel cannot create MailEnable mailbox on Windows 2003 x64 or Windows 2008 x64 editions

MailEnable and Merak mail server software are 32-bit applications providing COM API to WebsitePanel. If WSP Server component works in 64-bit mode it cannot instantiate 32-bit COM objects.
To solve this issue you have to switch ASP.NET on the machine where WSP Server is installed to 32-bit mode.

Switching ASP.NET to 32-bit mode on Windows 2003 x64

To switch IIS 6 and ASP.NET into 32-bit mode open command line:
Start -> Run... -> cmd
Then switch to c:\Inetpub\AdminScripts folder:
cd c:\Inetpub\AdminScripts
and run the following command:
cscript.exe adsutil.vbs set W3SVC/AppPools/Enable32BitAppOnWin64 "1"

To enable ASP.NET on IIS in command line interface switch to C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727 folder and run aspnet_regiis program with “i” switch:
cd C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727>aspnet_regiis -i

Now as ASP.NET is enabled for IIS you should go to Internet Information Services (IIS) Manager and allow “ASP.NET v2.0.50727 (32-bit)” extension in “Web Service Extensions” section:

You could find more information regarding this topic in the following Microsoft KB:
http://support.microsoft.com/default.aspx/kb/894435

Switching ASP.NET to 32-bit mode on Windows 2008 x64

To switch WSP Server application to 32-bit mode open IIS manager.
Click "Application Pools" in the left navigation menu and then open "Advanced Settings" dialog of "WebsitePanel Server Pool".
Set "Enable 32-bit Applications" to "True" and click "OK" button to save changes.

Update Web Site Panel to latest build

To perform a manual update to an existing 1.2.1.6 (or greater) installation you need to follow this steps.

Inventory list of servers to Update. Log into your current Web Site Panel and go to the tab Configuration then Servers to get a list of all servers that need to have the update.
Download latest Manual Update ZIP file.

Unzip the content of the update file. The ZIP file contains 3 folders and a SQL script to perform the update that needs to be unzipped on a temp folder.
Perform a backup of the WebsitePanel directory. Right-click over the folder C:\WebsitePanel\ and send to a ZIP file to have a backup of all files before getting replaced with the upgrade files.
Logon to SQL Server Management Studio and backup current WebsitePanel Database.
In SQL studio identify the database used by WSP (Default name is WebsitePanel) and right click on it, then go to Tasks and perform backup.
Open the provided SQL script on SQL Management Studio. Go to file, then Open and locate the unzipped SQL script in the temp folder.


On the opened script and rename the 1^st line of the query inside the brackets [${install.database}] with the name of the database to be updated as shown in the following screenshot (For this example we used default database name WebsitePanel).






Execute the script.
Click on Execute in the query window to update the database.A confirmation will be displayed in the bottom showing Query executed Successfully, then close SQL Management Studio. Replace the folders with Updated Files in order starting by Enterprise Service.
Please note the name of the unzipped folders EnterpriseServer which needs to be renamed to Enterprise Server (adding the space) in the Temp folder before replacing the one in production.
Once the folder has been renamed copy the 3 of them to the folder C:\Websitepanel\ selecting to Copy and replace any existing file so it can update all files that require to be updated. Perform this step on all servers found in the 1st step of this guide.

Verify the version of the updated website panel. Log on back to your website panel and go to Configuration – Servers and then click on any of the servers listed. The site version will show up in the right bottom.

The update has been completed successfully.

Source :

http://websitepanel.net