WAPWS-EasyDeploy_v2

Introduction

The purpose of the tool is to setup a WAP Web Sites environment on a single HyperV host, thus allowing user to experience the basics of WAP Web Sites. This is suitable for performing POC's, demos and doing testing. It is not intended to be used to create a production deployment. Please look to the technet information here: http://technet.microsoft.com/en-us/library/dn457745.aspx for production installation instructions.

Prerequisite

1. Host machine requirement, 8960MB memory required, 40GB hard disk needed, supported OS's are: Windows Server 2008 R2, Windows 8, Windows Server 2012 and Windows Server 2012 R2
2. Internet access is needed for all VM's. The network adapter in every VM will connect to
   • An existing virtual network named as "WAP Network"
   • If not there, the first available external virtual network
   • If there are no existing virtual networks, a new external virtual network with name "WAP Network" will be created
3. A sys-preped OS virtual hard disk, which will be used by all VM's as the base. Both VHD and VHDX is supported (be noticed that 2008 Server does not support VHDX).
   • Get a VHD from the internet. Server 2012 R2 can be downloaded from http://technet.microsoft.com/en-us/evalcenter/hh670538.aspx
   • Or DIY by running "sysprep.exe /generalize /oobe /shutdown" in a VHD-making VM. It is recommended to add a read-only flag to that disk right after the VM shutdown and never turn on the VHD-making VM.
4. DeployWAP.exe must be run with administrative level if UAC is enabled.

Command Line Options

1. [Required] -BaseVHD A VHD file served as the base for all VM's. Should contains a basic OS installation and sys-preped.
2. [Optional] -SiteDomain Default to "test.com", which is the domain suffix for web sites
3. [Optional] -VMSuffix Default to host machine name, which will be appended at the end of VM name and corresponding machine name

Command Line Example: DeployWAP.exe -BaseVHD WinServerImage.vhd -SiteDomain wapdemo.com -VMSuffix mydemo

Process Details

1. 8 VMs will be created with the name as "-". Default VMSuffix is the machine name, and any VMSuffix will be truncated to 10 characters to make actual machine name valid. If there is a corresponding VM already using the name, it will got reimaged. Originally attached VHD will be deleted. The is
   • CN Controller
   • DB Database Server
   • FS File Server
   • LB Load Balancer
   • MN Management Server
   • PB Publisher
   • PT Portal
   • W Shared Worker
2. VHD's will be created under the HyperV's "Virtual Hard Disk" path, which can be changed through HyperV management UI. The default is C:\Users\Public\Documents\Hyper-V\Virtual hard disks. If you run the tool multiple times and remove the VM's you may still need to clean up the left over vhd's and this is where they are.
3. Inside each VM, user "websitesadmin" with password "Wap2013!" will be created and assigned to "Administrators" group.
4. Both Sql and MySql will be installed on the database server. The admin user for Sql server is "sa" with password "Wap2013!". The admin user for MySql server is "root" with password "Wap2013!"
5. The management end point is on the management server, port 443 with basic authentication. The user is "cloudadmin" with password "Wap2013!"
6. A plan "WAP Default Plan" will be created after successful deployment and promotion code is "Wap2013!"

Using WAP Web Sites

1. This install does not supply it's own DNS. In order to use the system it needs to be properly configured with DNS per the guidance here: http://technet.microsoft.com/en-us/library/dn469319.aspx#BKMK_DNS If performing a quick demo and configuring DNS is too much overhead then the you can create entries in the windows\system32\etc\hosts file to add the ftp and publish entries as well as the entries for each website being created. If using the hosts file, the entries you need to add are: 'publisher ipaddress' publish.'sitedomain'
   'publisher ipaddress' ftp.'sitedomain'
   'front end ipaddress' 'sitename'.'sitedomain'
   'front end ipaddress' 'sitename'.scm.'sitedomain'
   example:
   10.121.136.207 publish.wapwsdemo.com
   10.121.136.207 ftp.wapwsdemo.com
   10.121.136.222 mydemo.wapwsdemo.com
   10.121.136.222 mydemo.scm.wapwsdemo.com
   As you add new sites you would need to add new sitename based entries of course.
2. The tenant portal is at https://pt-'*VMsuffix*':30081 example: https://pt-mydemo:30081
3. The admin portal is at https://pt-'*VMsuffix*':30091 example: https://pt-mydemo:30091
4. You can start using the system immediately as a tenant and create an account. Then add a subscription to your account. When doing so use the subscription code "Wap2013!" If using the hosts file for DNS create the entries and save them before creating the web site.

Troubleshooting

1. DeployWAP failed on creating or modifying VM
   • Cause: most likely DeployWAP can't access the HyperV WMI interface
   • Solution: run DeployWAP as administrator
2. DeployWAP can't mount the Vhd

• Cause: Target Vhd is still mounted in the host machine
• Solution: On 2008 Server, use WMI Msvm_ImageManagementService to umount. On 2012 Server, VHD can be directly umounted from Disk Management. Bottom line, reboot the host machine.

3. Host machine lost network connectivity during deployment

• Cause: DeployWAP is creating a new virtual network and disrupted the connectivity
• Solution: Wait till connectivity restored. To prevent it from happening, make sure there is virtual network named "WAP Network" or there is an existing external virtual network

4. No user "websiteadmin" in the VM

• Cause: initial setup script was not properly executed during first boot, and this is because the base vhd is not properly syspreped
• Solution: Get the official VHDor do nothing after "sysprep.exe"

5. Machine names not resolved , as a result, Infinite waiting for controller and other waiting

• Cause: the virtual network all VMs connected to are not configed correctly
• Solution: Make sure the virtual network VMs connected to are healthy and can provide correct name resolution

6. Infinite waiting for Azure pack to be installed

• Cause: WebPI failed
• Solution: The failure model is quite complex, the simplest solution is to rerun DeployWAP. To find out the real trouble, go inside the Vm and check the WebPI log.