Setting up Load Balanced Office Web Apps 2013 Multi Server Farm with SSL (HTTPS)

It is hard to find a proper documentation on internet for this topic and that is where i thought of posting this article as i expirienced Office Web Apps 2013 Deployment in Production.

If you are not a browser fan, You can download PDF version of my Article from Microsoft Technet Gallery – https://gallery.technet.microsoft.com/Setting-up-Multi-Server-23e1f2ca 

Contents

1. Introduction

2. Server Environment

3. Requirements and Recommendations

4. Deployment

1. Introduction

Microsoft Office Web Apps 2013 is now a fully Isolated Far which supports multiple and various Integrations such as SharePoint, Lync, Skype for Business and other Third Party Applications. basically, your single Web Apps Farm will serve OWA Capabilities for Multiple applications so that is simple for you to manage and Integrate.

This Step by Step Guide will show you how to Setup an Office Web Apps 2013 Farm with High Availability and Security. The Naming and Certificates used in this scenario will be samples for demonstration purpose. You need to use meaningful names and obtain a valid SSL certificate for your scenario and environment.

This Guide will cover the following requirements.

  • Multi-Server Farm: Setup Office Web Apps with Microsoft NLB for High availability and Load balancing
  • Setup Office Web Apps Farm with Better Security using SSL for HTTPS. It is highly recommended to use HTTPS for Production Office Web Apps Deployments as HTTP meant only for developmental and testing environments only.

Before You begin with the Installation and Configurations, it is recommended to go through below references which may provide you all the basic information and knowledge about Microsoft’s Office Web Apps Server Product.

2. Server Environment

image

This Demo Setup will be using:

  • Two office Web Apps 2013 Servers with Windows NLB Enabled and Configured
  • SharePoint Server Farm with two WFE Servers and Single APP Server for Intranet Site Hosting with Host Header Site Collection (This SharePoint Farm is multitenant Environment where a Single Web Application shall contain multiple Host named Site Collections with unique URL)
  • Two Database Servers holds Always on Instance for SharePoint Environment.
  • Active Directory | DNS Server with Active Directory Certificate Service Enabled and Started
  • Two SQL Server Nodes with Always-on Instance hosts SharePoint Platform

Specifications of these servers are for Demonstration purpose only. Production Environments are highly recommended to meet Microsoft’s sizing requirements in order to get optimum performance and reliability.

clip_image002

3. Requirements and Recommendations

This guide uses windows NLB for demonstration purpose. In Production Environments, try to use a Hardware Load balancer which brings following capabilities if you are planning for more than one server for OWA.

  • Layer 7 routing
  • Enabling client affinity or front-end affinity
  • Enabling SSL offloading

Production Environments are always having firewalls in between different zones. Depends on the zone you are going to place OWA Servers; you need to open following ports in order to make OWA function properly.

  • Port 443 for HTTPS traffic
  • Port 80 for HTTP traffic
  • Port 809 for private traffic between the servers that run Office Web Apps Server (if you’re setting up a multi-server farm)

Topology Planning (Source: https://technet.microsoft.com/en-us/library/jj219435.aspx )

  • Plan for Server Level Redundancy. If You are using Virtual Machines to Host OWA, segregate them to separate Host Servers instead of Placing all in a one box (e.g. – OWA1 Hosted in Hardware Box A, OWA2 Hosted in Hardware Box B) so that if Hardware box A goes down in case, Yet the Box 2 Serves requests as OWA2 still runs there.
  • Stick to one data center. Servers in an Office Web Apps Server farm must be in the same data center. Don’t distribute them geographically. Generally, you need only one farm, unless you have security needs that require an isolated network that has its own Office Web Apps Server farm.
  • The closer the hosts, the better. The Office Web Apps Server farm doesn’t have to be in the same data center as the hosts it serves, but for heavy editing usage, we recommend you put the Office Web Apps Server farm as close to the hosts as possible. This is less important for organizations that use Office Web Apps primarily for viewing Office files.
  • Plan your connections. Connect all servers in the Office Web Apps Server farm only to one another. To connect them to a broader network, do so through a reverse proxy load balancer firewall.
  • Configure the firewall for HTTP or HTTPS requests. Make sure the firewall allows servers running Office Web Apps Server to initiate HTTP or HTTPS requests to hosts.
  • Plan for incoming and outgoing communications. In an Internet-facing deployment, route all outgoing communications through a NAT device. In a multi-server farm, handle all incoming communications with a load balancer.
  • Make sure all servers in the Office Web Apps Server farm are joined to a domain and are part of the same organizational unit (OU). Use the FarmOU parameter in the New-OfficeWebAppsFarm cmdlet to prevent other servers that are not in this OU from joining the farm.
  • Use Hypertext Transfer Protocol Secure (HTTPS) for all incoming requests.
  • If you have IPsec deployed in the network, use it to encrypt traffic among the servers.
  • Plan for Office features that use the Internet. If features such as clip art and translation services are needed, and the servers in the farm can’t initiate requests to the Internet, you’ll need to configure a proxy server for the Office Web Apps Server farm. This will allow HTTP requests to external sites.

Software Requirements for Office Web Apps

  • Office Web Apps Server/s Must Be Independent from other Applications and Services Such as SharePoint, Exchange, Lync, Skype4B. Do not try to deploy Office Web Apps on a sever which runs any of the above Applications and that is not supported.
  • Don’t Install Any Services or Applications depend on IIS 80, 443 or 809 Ports because OWA frequently removes web applications on these ports in order to bring up the OWA Web Applications.
  • Do Not Install any office Client applications on OWA Servers as it is not recommended to be. If any office Applications are installed on a server you are about to install OWA, you have to fully uninstall them prior to the OWA installation.
  • Do Not Install OWA on a Domain Controller or any Domain Server runs Critical Services such as DNS or AD DS.
  • Download the Office Web Apps 2013 with SP1 which is the latest version you can download. Also look for the recent Cumulative Updates prior r to go live in production scenarios.

4. Deployment

It is Assuming that you already have a SharePoint farm Prepared with an Accessible Site Collection. This guide will not go through the SharePoint Server Deployment but only the Integration of Office Web Apps for SharePoint in order to allow your end users to open/edit their Office Documents within the Browser.

Steps:

  • Installing Prerequisites in OWA servers for Office Web apps
  • reating DNS Host Records
  • Configuring Windows NLB for Load balancing and High Availability
  • Configuring SSL Certificates using Active Directory Certificate Services
  • Installing Office Web Apps
  • Configuring Office Web Apps Farm
  • Joining Member Servers to the Office Web Apps Farm
  • Integrating with SharePoint Farm
  • Testing Functionality

 

4.1. Installing Office Web Apps Prerequisites

You must have a Domain User account (Such as SharePoint Farm Account) created in order to Install Office Web Apps.

After Creating your Virtual Machine, Login to the same and Prepare it with necessary Network and Domain Configurations such as defining IP addresses and joining it to the respective domain.

Then Login in to the server using local administrative credentials and add the User Account created for Office Web Apps in to the Local Administrators Group.

Run the following Scripts in Windows PowerShell in order to prepare your OWA servers with Prerequisites. You can define the SXS path to source files if your server doesn’t have the internet connectivity by simply passing the -Source Parameter (e.g. -Source D:\Sources\sxs)

It might prompt for restarting once finished.

For Windows Server 2008 R2

Install Following Software’s

o Windows Server 2008 R2 Service Pack 1

o .NET Framework 4.5

o Windows PowerShell 3.0

o Platform update for Windows 7 SP1 and Windows Server 2008 R2 SP1 (KB2670838)

Right Click on Windows PowerShell and Run it as Administrator. Then run the following

Import-Module ServerManager

Add-WindowsFeature Web-Server,Web-WebServer,Web-Common-Http,Web-Static-Content,Web-App-Dev,Web-Asp-Net,Web-Net-Ext,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-Includes,Web-Security,Web-Windows-Auth,Web-Filtering,Web-Stat-Compression,Web-Dyn-Compression,Web-Mgmt-Console,Ink-Handwriting,IH-Ink-Support,NET-Framework,NET-Framework-Core,NET-HTTP-Activation,NET-Non-HTTP-Activ,NET-Win-CFAC

For Windows Server 2012

Add-WindowsFeature Web-Server,Web-Mgmt-Tools,Web-Mgmt-Console,Web-WebServer,Web-Common-Http,Web-Default-Doc,Web-Static-Content,Web-Performance,Web-Stat-Compression,Web-Dyn-Compression,Web-Security,Web-Filtering,Web-Windows-Auth,Web-App-Dev,Web-Net-Ext45,Web-Asp-Net45,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-Includes,InkandHandwritingServices,NET-Framework-Features,NET-Framework-Core,NET-HTTP-Activation,NET-Non-HTTP-Activ,NET-WCF-HTTP-Activation45

For Windows Server 2012 R2

Install – NET Framework 4.5.2

Then Run the following in PowerShell

Add-WindowsFeature Web-Server,Web-Mgmt-Tools,Web-Mgmt-Console,Web-WebServer,Web-Common-Http,Web-Default-Doc,Web-Static-Content,Web-Performance,Web-Stat-Compression,Web-Dyn-Compression,Web-Security,Web-Filtering,Web-Windows-Auth,Web-App-Dev,Web-Net-Ext45,Web-Asp-Net45,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-Includes,InkandHandwritingServices,NET-Framework-Features,NET-Framework-Core,NET-HTTP-Activation,NET-Non-HTTP-Activ,NET-WCF-HTTP-Activation45

4.2. Creating DNS Host Records

Next to create the HostA Record for NLB Cluster Name (Which will be the ultimate Server Name of OWA Farm).

Direct to your DNS Server and Simply Create a Host AAA Record points to your Target NLB IP. You need a dedicated IP V4 address for this.

Open Up the DNS Manager Console in your DNS Server and Right Click on the Respective Zone and hit New Host (A or AAAA) to create a new Host record.

clip_image001

Provide the Name and IP It points to (which is the desired NLB Cluster IP) and hit Add Host to create.

clip_image002[6]

Record is ready for you now.

4.3. Configuring Windows NLB

Then the next step is to Install Windows NLB for both OWA Servers in order to configure the Load balancing

Open up Server Manager and Click Add Roles and Features from the top. This has to be done in both OWA servers.

clip_image003

Just Click next on the first Screen

clip_image004

Leave the Default Selection here and hit Next

clip_image005

Default choice here too and hit Next to proceed

clip_image006

Select the Network Load Balancing from the Feature list and hit Next to Install the feature then restart the server if prompted.

clip_image007

That Installed NLB feature for us and now let’s Setup Load Balancing Cluster. Open up Windows NLB Console from the primary Machine (OWA1). Make sure both Nodes are now ready with IP, Host Names, NLB Feature.

clip_image008

Right Click on the top level and Create a New Cluster

clip_image009

Provide the Name or IP of the Primary Server which will host the Cluster (Local Server). It will automatically resolve the IP and display the interface for you. Simple hit Next to proceed.

clip_image010

Leave these settings as it is unless you need a specific configuration for IP and Network Interfaces

clip_image011

Next Step is to define the Cluster IP. At this scenario it will be 192.168.150.132

clip_image012

clip_image013

IP Address will be already selected and define the FQDN of the Cluster name here and choose Operation mode based on your network. This server only got a single Network Interface so it has to be Multicast. If you have Multiple Interfaces, you may choose Unicast Mode to make it function properly.

Hit Next to go ahead

clip_image014

clip_image015

You can edit the Port Rules to customize Ports or Protocols but not really necessary to get this function. Leaving the defaults will bring us what we need in this case.

clip_image016

If all went well, you can see the Cluster is created with the defined name and settings and Primary Host is added/Started with green health status.

clip_image018

Let’s go ahead and Add the second node here. Right Click on the Cluster Name and Add Host to Cluster

clip_image019

Type the Host Name or IP of your Secondary OWA Machine (OWA2 at this Case). Make sure it can communicate with the primary host and Windows Firewall Exceptions are added or Switched off so nothing will block the communication at this point.

If all good, it will resolve the IP over Name and Name over IP as below. Just Hit next to proceed.

clip_image020

Leave the Priority to Default (2) and State as Started

clip_image021

And then the Port Rules. Load Left as Equal and you can define if you need. Leave it as Default for better load Sharing.

clip_image022

Give it a moment

clip_image023

And Both nodes will come online and appear as Healthy if you have configured it properly.

clip_image025

To Verify the Availability of the Cluster, lets ping the Name. do it from one of the SharePoint Machine so you can identify any issues in the network.

clip_image026

So the NLB Cluster is All Set for us. Next is to Prepare the OWA Servers with SSL Certificates.

4.4. Configure SSL Certificates for OWA HTTPS

We are using Active Directory Certificate Service to Issue Web Server Certificates for our OWA Farm which will only be trusted and validated within the domain Network. For External Networks Such as Internet you need to purchase a Genuine SSL Certificate from a Third party vendor such as Verisign.

If you use Internal Certificates (Such as the one used in this scenario) your OWA WOPI URL will not be Valid for External Access and It Will Prompt the security Message with critical warning of content. So for Production environments, always use a valid Certificate.

Setting UP SSL

Open up Active Directory Certificate Services from your AD. At this point, our NORTHWIND AD will be the ultimate Certification Authority.

clip_image027

If you do not have this feature in your AD. You can Get it installed via Server manager Roles and Feature Installation Wizard.

clip_image028

This Server Already has it Installed so it’s just to go ahead. Expand the Server and hit Manage

clip_image029

Now the Certificate Templates Console will be Opened for you in Edit mode. Right Click on the Web Server Template and Direct to Properties.

clip_image031

Add the Computer Accounts (OWA1.Northwind.Int |OWA2.Northwind.Int) of your OWA Servers and the Service Account which will be using to setup OWA Farm for following Permissions. This will enable the Web Server Certificate Template to Enroll from these Two Servers.

Change Object types to following types.

clip_image032

clip_image033

Allow all three objects for Read and Enroll Permissions.

clip_image034

That’s all from the Active Directory Side. Let’s move back to the OWA Servers and Open up MMC.EXE to Obtain Certificates.

clip_image036

From the Console Root, Add/Remove Snap-In

clip_image037

Select Certificates

clip_image038

clip_image039

clip_image040

clip_image042

Expand the Certificates Root and Drill down to Personal. Right click on Personal and Request a New Certificate

clip_image044

New Certificate Enrolment Wizard will be prompted for you. Just Hit next to proceed

clip_image045

Active Directory Enrollment Policy will be selected by Default here so nothing much to do/ Hit Next here.

clip_image046

You will then see the Web Server Policy is highlighted with the Exclamation Mark. Click on the Message there.

clip_image047

That will bring you to the Certificate Properties where you will be providing all the details of this certificates. Select the Subject Name Type as “Common Name” and Alternative Name Type as “DNS”. Value for both of these field can be the same which is our OWA Farm Name. Basically this Certificate will be dedicated to the OWA Farm. It won’t validate any other purposes. Yet this may depend on your scenario and Environment.

clip_image048

Once Entered, Add them to the selection on the right side.

clip_image049

Direct to the General Tab and Provide the same Value for Friendly Name. Friendly name is the Name that you will use to recognize this Certificate at later time when you are pointing this Certificate from other Applications. Description Could be any.

Hit Apply to Complete

clip_image050

Then the Exclamation Message will be gone as you have successfully completed the Indexing of Information of the Certificate. Simply Check the Web Server Check box and Hit Enroll to obtain the Cert.

clip_image051

clip_image052

Give it a few seconds and If everything good, the certificate will be successfully enrolled. If you are getting an error here saying that “Server or Service Unavailable”, You might need to restart the Certificate Server Service at your AD Server.

clip_image053

We can now see the Certificate at the Certificate Store

clip_image055

Repeat the same for secondary OWA (OWA2) Server as well and then it completes our SSL Certificate Configuration Part.

4.5. Installing Office Web Apps Server 2013

Here Comes the real thing. As we have completed almost all the Prerequisites and Background Preparations for OWA Farm, we can proceed to the Installation and Farm Deployment.

Log in to the OWA Servers using the domain Account (Northwind\sp_farm_svc) you have crated. In this case it’s going to be the SharePoint Farm Account which will be used to Install OWA.

Map the Office Web Apps Server 2013 ISO (With Service pack 1) and Run it.

clip_image056

As Always, you have agree to the License terms and Continue to Proceed then.

clip_image058

The Success Message will be appeared in just Few Minutes If everything went well.

clip_image059

Now the Most Important Steps. Configuring the OWA farm is done through PowerShell. Best Tool for this is PowerShell ISE. From the OWA1 Right click on PowerShell Icon and Run ISE as Administrator

clip_image061

To Create the New OWA Farm. Run the Following Script. If you are using SSL Offloading the Parameters will be bit different.

New-OfficeWebAppsFarm -Verbose -InternalUrl https://OfficeApps.Northwind.int -CertificateName OfficeApps.Northwind.Int -ClipartEnabled -TranslationEnable -EditingEnabled

clip_image063

-Verbose (This Switch is to display the status)

-InternalUrl (This is the Internal Url referred from SharePoint Later)

-EditingEnabled (This will allow your users to Edit Documents in Browser itself)

-CertificateName (You can Define your SSL Cert using this Parameter. Or you can do it yourself manually via IIS Later)

-ExternalUrl (Can be Defined in addition to InternalUrl Swith if you are setting up an External Scenario)

If all went well, you will see the Result as above. And under the Machines it will show the OWA1 which is our Primary OWA Server in this farm.

clip_image064

Check the IIS to verify the Web Applications Creation and SSL Certificate Assignment

Open IIS manage and Check if These Two Web Applications are created

clip_image065

Note the Certificate Binding under the Site Bindings on the Right Panel and the Protocol is HTTPS.

clip_image066

 

4.6. Joining Secondary OWA machine to the Farm

Next step is to Join our Second Machine to the OWA Farm. Login to the OWA2 Machine using the same Domain credentials you used to Setup OWA1.

Open the PowerShell ISE as Administrator and run the Following from OWA2.

New-OfficeWebAppsMachine -MachineToJoin OWA1

-MachineToJoin (This switch is to Define your Primary OWA Server Name). basically this is the Master Machine.

clip_image067

That’s all from the OWA Farm Side. Next step is to Integrate OWA Farm to SharePoint but before that Let’s test our setup.

 

4.7. Testing the OWA farm

Simply try the Hosting Discovery URL from a Different Server (SharePoint Server Will do) https://officeapps.northwind.int/hosting/discovery

If you are Retrieving this XML Page as below with the parameters. It means you are all good to go.

clip_image069

Discovery URL working Means that your OWA Farm is accessible and Functioning well. so the next step is to Integrate OWA for SharePoint. Sometimes the Hosting URL may not work within the OWA Servers itself due to the loopback checking, best thing is you can check it outside the OWA Servers

The URL will not show any Warnings about the Certificate or Trust because it is valid internally within our Northind.Int Domain Environment. It will not be valid for Outside access unless it’s a valid External Certificate from a Vendor.

clip_image070

 

4.8. Integrate Office Web Apps with SharePoint 2013

SharePoint Environment is already done with a Host Named Site Collection which is also using HTTPS. This Scenario is fully setup for HTTPS in order to test the production level functionality. If you are using HTTPS for OWA Your SharePoint Site must use HTTPS too otherwise there is no point of using HTTPS on OWA.

Note: Recommended Way to Deploy OWA is Using HTTPS with a Valid SSL Certificate. HTTP is not recommended and it meant only for testing and Developmental Environments only.

In this scenario, we are using https://intranet.Northwind.Int Host header Site Collection for Integration testing. Below is the Default SharePoint Site which has some Sample documents uploaded and all good to go in SharePoint Side.

This SharePoint Farm also has two WFE Servers with NLB configured and this URL is fully load balanced with NLB.

clip_image072

Login to Your SharePoint APP Server and Run the Following in SharePoint Shell or PowerShell ISE.

From SharePoint Shell

New-SPWOPIBinding -Server OFFICEAPPS.NORTHWIND.INT

From PowerShell ISE

Add-PSSnapin Microsoft.SharePoint.Powershell -EA 0

New-SPWOPIBinding -Server OFFICEAPPS.NORTHWIND.INT

-Server (This parameter to Define Your OWA Farm Name. Not the Name of any OWA Machines)

clip_image074

If all Went well, you will see the above result. With defined Inputs such as Zone, Server Name etc…

That’s all from the SharePoint Fram side.

Let’s test out the functionalities from SharePoint Side now.

Note: Do not use Farm Account to test OWA. You must use a Different user account to test this as SharePoint Farm account is not allowed to open Documents from browser for security reasons.

Preview of a Document in Browser in WOPI Frame

clip_image075

Opening a Document

clip_image077

Editing a Document in Brower

clip_image079

4.9. Glossary

Server Did Not Respond – Error when Adding WOPI Zone in SharePoint – If you already have some other WOPI Zones this could happen, Or else Due to an Invalid Certificate on OWA Server.

Hosting/discovery Doesn’t Load – Mostly this happens if you try to open it from the OWA server itself. Try from another server. Also try to add the secondary Server and then load the URL.

Issue the Certificate for the Relevant Name – IF OWA1 (OWA1) or if OfficeApps.Northwind.int: Cert has to be for the same Name if it’s a SAN Cert.

To Test the availability across the Nodes, Shutdown one of the OWA Server and Check the Functionality. If you have completed above steps properly, OWA should work with the remaining node without any issue.

 

<

p align=”justify”>I will post another article on Troubleshooting OWA 2013 ……………………………………………….

Advertisements

Feature/Role Installation Fails in Windows Server 2012 (Installation of one or more roles, role services, Features failed).

Sometimes you will experience that feature installation in windows server 2012 fails commonly on .Net 3.5.

image

this is because this installation refers to source files which includes in Server 2012 media. by giving the path to SXS folder manually of your media on Confirmation window in Feature installation wizard resolves this as figured below.

image

Insert media and Click on “Specify alternate source path” and provide location of SXS folder within Server 2012 Media  – E:\sources\sxs

image

Now the setup can find the files and the installation would be success.

Change Product key in Windows 8/Server 2012

New Windows 8/Server 2012 Operating Systems doesn’t allow you to Change Product key through system properties. Only way is to change the product key is to run PowerShell CMD let.

This is how it shows at system properties. You may activate but not change the key. activating without installing a valid key wont be possible too.

clip_image001

clip_image002

So simply run PowerShell in privileged (run as admin) mode and type below lines step by step.

  1. slmgr -upk (this uninstalls the current Product Key)

clip_image003

  1. slmgr -ipk XXXX-XXXX-XXXX-XXXX (replace X’es with your Key – this installs the new Product Key) You will see below message if your key is valid with media.

clip_image004

  1. Now direct to system properties and click "Activate"

clip_image005

clip_image006

That’s it and enjoy your Genuine OS..

SharePoint 2010 Compatibility with Windows Server 2012

This is a bad? news for SharePointers out there which still has a good news inside as well ;). who’s going to deploy SharePoint 2010 on Windows Server 2012? Keep a note below.

The Bad News Is – As per Microsoft SharePoint Server 2010 does not compatible with Server 2012 platform and we have to wait till the SharePoint 2010 SP 2 released which will contain the patches and updates accordingly.

And here’s The Good News -Yes We have an workaround for this.

Though MS says that we have to wait till the SP 2 released, I cannot because somebody is waiting for the solution out there and there’s no excuse for it, couldn’t revert back my Server in to 2008 R2 as well. So started dig down in to a workaround and got finally SP 2010 on Server 2012 installed and configured nicely, Tons of thanks for the web community who Shares their experiences all over the world for others (I’m community a Lover…)

So, From the point of prerequisites preparation you will get below issues.

1. Prerequisites installer gives an incompatibility pop up (still you can go ahead by saying ‘Run Program without Help’)

clip_image001

2. Even Though you have got all prerequisites Installed either manually or through a script, SharePoint Server Installer still says ‘Windows Server Roles or Features required by this product are not Enabled’.

clip_image002

3. Let’s say you have passed all above barriers somehow. Still you get some other issues after installing and provisioning the farm.

3.1 Farm Configuration Wizard Fails

clip_image003

3.2 Local Farm Not Accessible via PowerShell. Again the compatibility issue.( "The local farm is not accessible. Cmdlets with FeatureDependencyId are not registered")

clip_image004clip_image005

Let’s see how we can get this done and here are the workarounds you have.

Note : None of these workarounds are officially supported by Microsoft and still the best solution for now is to have SharePoint 2010 on Windows Server 2008 R2.

If you are Installing SharePoint server 2010 on SQL Server 2012, make sure you have the media which has SharePoint 2010 SP1 included. None SharePoint SP 1 doesn’t support SQL 2012.

Workaround 01 – Automated PowerShell installer Script (This will save hours for you)

Craig Luccier has done a great job here – http://gallery.technet.microsoft.com/sharepoint/SharePoint-2010-and-dee17600. This single PowerShell monster resolves all above issues. Basically –

  1. installs all of the Windows Server 8 beta Roles/Features necessary to run SharePoint 2010
  2. Change the default IIS 8 App Pool .NET Framework to v2.0
  3. Downloads and install the SharePoint 2010 Prerequisites
  4. The SP 2010 installer doesn’t work issues

Running this script before you Install SharePoint will do everything above so nothing to be done manually. Just go ahead and install SharePoint right after this.

Workaround 02 – Get everything manually prepared your self (Time consuming but interesting !)

I didn’t go through the above PowerShell script as I needed to know each and every points basically what we fix and where. So here are steps with detailed descriptions on the manual workaround which worked for me.

1.Installing Prerequisites

Download and install these packages

Microsoft Chart Controls for Microsoft .NET Framework 3.5

Microsoft Filter Pack 2.0 (Available in PrerequisiteInstallerFilesFilterPack as well)

Microsoft SQL Server 2008 Native Client

Microsoft SQL Server 2008 R2 ADOMD.NET

Microsoft Sync Framework 1.0

Enable Windows features and roles via Server manager. To do this, Direct to Server manager –> Manage –> Add roles and features and Select below roles.

clip_image006

Go Forward and select Windows identity Foundation 3.5 for .Net framework 3.5 under features. It’s good so you don’t have to download It anymore as Serer 2012 contains the feature out of the box.

clip_image007

Below List of services need to be selected under IIS Role.

clip_image008clip_image009clip_image010

clip_image011clip_image012

Go ahead and install them and that’s all from the Prerequisites side.

2. Installing SharePoint

Go and run the Setup.exe and you will get the issue no 2 I have mentioned above ‘Windows Server Roles or Features required by this product are not Enabled’. Don’t worry, one guy out there has done a great job. It’s all about just Downloading Hand.ServerManagerCmdEmul – Binaries from here and copy ServerManagerCmd file in to – C:\Windows\system32 in your SharePoint Server. Additionally from there you can get the Hand.ServerManagerCmdEmul – Sources project file as well.

Boom ! You wont see that error now. So Go ahead and get the product installed.

clip_image013

Once you complete the installation you will notified for product configuration wizard. Go ahead and get your farm configured. End of the wizard, again the next issue will pop up. Yes the issue number 3.1 which I have mentioned above, ‘Configuration failed’. This is because SharePoint 2010 needs .Net farmework 2.0 in IIS App Pools.

At this stage, all the app pools and sites has been created under IIS. Let’s go there and have a look. Yes they are !

But all are having .Net v4.0 and this has to be changed in to 2.0

clip_image014

Right click on each pool –> advanced settings –> and set the .Net version to 2.0 (ignore the .Net v4.5 and .Net v4.5 Classic) it should look like this once you done.

clip_image015

Now Run the Product Configuration Wizard again and it should complete successfully.

Here we go.. ! Your Central Admin loaded.

clip_image016

3. Fixing SharePoint Management Shell Issue

In order to make use of the powershell commands with sharePoint 2010 on Server 2010, we need to switch the powershell version back to version 2.

Note: This will not uninstall version 3, it will simply launch a new powershell instance that uses version 2.

Right click on SharePoint Management Shell –> Go to File Location –> Get the properties of the Shell Shortcut –>

replace the Existing Target value in to – C:\Windows\System32\WindowsPowerShell\v1.0\PowerShell.exe -version 2.0 -NoExit " & ‘ C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\POWERSHELL\Registration\\sharepoint.ps1 ‘ "

clip_image017

Let’s go and try now. Yeah Now the Shell back to Rock !!

clip_image018

Everything on it now.. Enjoy,

image

Configuring a Virtual SAN Using ISNS in Windows Server 2012

    Yet Another very useful and free tool from Microsoft. If you remember the earlier version of this feature, it was an downloadable application where you can install separately but now with latest version of windows server 2012 it has been bundled in as a feature under roles and features.

    I was heavily using iSCSI software target for my testing purposes where I needed an Virtual SAN such as on SQL/Windows Clustering etc.. I loved this because I got the real SAN Experience without any hardware or software cost. You can read my previous article if you are a pre windows 2012 user.

    Note: This Tool only for Testing purpose and not recommended to propose for production environments.

    Windows 8 Doesn’t Support this Feature anymore, you cannot install iSCSI software target 3.0 nor the ISNS server. This has been detached from client Operating systems.

    Alright, Here is the scenario, I have two servers where I need this to be configured with.

    Server 01 (Host) – ISNS Target Server which is the Central place where holding all the Disks

    Server 02 (Initiator-Client) – Initiator servers where my SQL Instance about to host

    Setup steps falls in to two levels as

  • Server Configuration (Host Server/Target)
  • Client Configuration (Initiators)

So Let’s get configured this server.

  • Run this power shell command on Target Server – Add-WindowsFeature FS-iSCSITarget-Server (This will install the feature for you so nothing to be done through roles and features)
  • clip_image001[5]

  • Just hold on few seconds
  • clip_image002[4]

  • Now direct to Server manager of Target Server and in to iSCSI tab like shown below. Basically this is the interface you manage your SAN here after. Looks pretty nice huh ? !!
  • clip_image003[5]

  • So the next thing is to get our virtual disks created which should include in to our Target. Two methods to get it done, Either From the above tab simply click on Tasks and say New virtual Disk and completing that steps will create your disk/s else as usual go to disk management and right click on Disks and say Create VHD as shown below so it does the same.
  • clip_image004[4]

  • Then to attach the disk we got created. Server manager again and under iSCSI click on Import Virtual disk
  • clip_image005[4]

  • Browse and locate your disk here and click next.
  • clip_image006[4]

  • Now to assign Target. This simply means the configuring of our Target Server. Choose New Target and hit next.
  • clip_image007[4]

  • Specify the Name as you desire, make it a tricky one
  • clip_image008[4]

  • Yes the important part now, specifying server which are will be accessing this target server. In my case it’s my SQL Servers that I’m about to cluster. Click Add.
  • clip_image009[4]

  • Select the method to identify the initiators here.
  • clip_image010[4]

  • Specify the Initiators here. Either you can easily provide the IP address/s or else the IQN (which is an unique identifier of particular node that you can get from the initiator servers by just launching iSCSI initiator and then through configuration tab [Eg- iqn.1991-05.com.microsoft:db01.testlab.int] )
  • clip_image011[4]

  • Authentication is optional so can be ignored.
  • clip_image012[4]

  • Have a look at the summary and hit Import to proceed.
  • clip_image013[5]

  • Just few seconds to import
  • clip_image014[5]

  • Everything gone perfectly. Cool result UI huh !
  • clip_image015[4]

  • Direct again in to Server Manager and check the result. of course you can expand your SAN by adding more disks in to pool.
  • clip_image016[4]

  • Let’s configure the Initiator Servers now. Just type iSCSI on search and launch it (iSCSI initiator – readily available on windows servers). Say yes to the massage to start the service.
  • clip_image017[4]

    clip_image018[4]

  • Provide the target address here and hit Connect (your Host Server where we configured SAN before)
  • clip_image019[4]

  • So we are success here. Say done to close this.
  • clip_image020[4]

  • Direct to Volumes and devices and click auto configure so whatever the available disks of SAN storage pool will be mapped in. say ok for this window.
  • clip_image021[5]

  • Let’s see the real thing through disk management. Wow !! So my disks are attached automatically
  • clip_image022[4]

       So it’s ready to play with and up to you. will be back in Clustering part with another post Smile