Windows 2008 R2 Sp1 server – updated till August 2013
Office Web Apps Server 2013 – with Latest Patches.
A quick glance at this page here Formal Reading for AAG is always a good start. This post would cover some of the more technical aspects involved. To begin with setting up the Windows Failover Cluster would be the initial task to be completed. (more…)
As part of an Always On Availability Group for SQL 2012 that was being built for a SharePoint 2013, the following error was occurring when trying to create a Windows Failover Cluster : (more…)
The following post describes the installation process for Office Web Apps 2013 RTM
- Turn on the required Server side roles which are required for the installation of Office Web Apps 2013.
On Windows 2012 Server
On Windows 2008 R2 Sp1 (Remember to bring the server to have all latest patches and updates installed verify previous post http://wellytonian.com/2012/08/sharepoint-2013-and-office-web-apps/ )
- Once the above mentioned Pre requisites are installed browse to Office Web Apps 2013 RTM Installer and run through the binary installation
Enabling HTTP for the WAC Server
New-OfficeWebAppsFarm –InternalURL http://$WACServer –AllowHttp -EditingEnabled
New-SPWOPIBinding -ServerName $OffWebAppSrv -AllowHttp
Log onto your SharePoint site and browse to Documents Library and click on New Document
And there you go..
So the scenario is that I have an instance of Windows Server 2012 (Windows Server 8 Beta) running on VMware Workstation 8 on my laptop.
Adding Hyper V role to the server
The other error that has been recorded:
Shutdown the Windows Server 2012
Browse to your VM location and open the vmx file and append at the end the following two lines
hypervisor.cpuid.v0 = "FALSE"
Save and power up your VM
Let’s try that again
Now you should be able to go on and configure your Hyper- V role on the server.