How to Install Office Web App 2013

Installation guide

The process step of installing Office Web App 2013 are as follows:

  1. Identity the server that will install Office Web App has meet the hardware, OS and software requirements (For more details read section 1, 2, 3 & 4 below)
  2. Check that the server has met the firewall requirements (For more details read section 5)
  3. Download the Office Web App installation file, any SP and other software for the appropriate OS of the server (See section 6 below)

1. Software, hardware, and configuration requirements for Office Web Apps Server

You can install Office Web Apps Server as a:
  • single-server Office Web Apps Server farm, or as
  • a multi-server, load-balanced Office Web Apps Server farm.
  •  physical servers or virtual machine instances, but can’t install other server applications (such as SharePoint 2013 or SQL Server) on the same server as Office Web Apps Server.

In environments that contain actual user data, we always recommend that you use HTTPS, for which you’ll have to obtain a certificate. If you’re using multiple servers in your farm, you’ll have to configure a hardware or software load-balancing solution. You can learn more about these scenarios in the following sections.

2. Hardware requirements

Office Web Apps Server uses the same minimum hardware requirements as SharePoint Server 2013. You can find the full set of SharePoint 2013 requirements in Hardware requirements—web servers, application servers, and single server installations.

3. Operating System requirements

Can run Office Web Apps Server on the following operating systems:

  • The 64-bit edition of Windows Server 2008 R2 Service Pack 1 (SP1) Standard, Enterprise, or Datacenter with the Update for Windows Server 2008 R2 x64 Edition installed
  • The 64-bit edition of Windows Server 2012 Standard or Datacenter
  • The 64-bit edition of Windows Server 2012 R2. To use this operating system, you must use Office Web Apps Server Service Pack 1 (SP1).

4. Other software requirements

  • Don’t install any other server applications on the server that’s running Office Web Apps Server. This includes Exchange Server, SharePoint Server, Lync Server, and SQL Server. If you have a shortage of servers, consider running Office Web Apps Server in a virtual machine instance on one of the servers you have.
  • Don’t install any services or roles that depend on the Web Server (IIS) role on port 80, 443, or 809 because Office Web Apps Server periodically removes web applications on these ports.
  • Don’t install any version of Office. If it’s already installed, you’ll need to uninstall it before you install Office Web Apps Server.
  • Don’t install Office Web Apps Server on a domain controller. It won’t run on a server with Active Directory Domain Services (AD DS)

Install bellow additional software which are prerequisites for Installation of Office Web App Server.

5. Firewall requirements

Make sure the following ports aren’t blocked by firewalls on either the server that runs Office Web Apps Server or the load balancer:

      • 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)

6. Downloads, server roles, and features that are required for Office Web Apps Server

From this blog, Office Web App server installer file is no longer availiable as a FREE download from Microsoft site. Instead it is availiable for download from Volume Licensing Service Center (VLSC) below:

Download, server role, or feature If you’re installing on Windows Server 2008 R2 If you’re installing on Windows Server 2012 If you’re installing on Windows Server 2012 R2
Download: Office Web Apps Server Office Web Apps Server Office Web Apps Server Office Web Apps Server
Download: Office Web Apps Server SP1 Recommended Recommended Office Web Apps Server SP1
Download: Correct version of .NET Framework .NET Framework 4.5 .NET framework 4.5 is already installed .NET Framework 4.5.2
Download: Update for Windows Server 2008 R2 x64 Edition Update for Windows Server 2008 R2 x64 Edition Not applicable Not applicable
Download: Windows PowerShell 3.0 Windows PowerShell 3.0 Already installed Already installed
Server role: Web Server (IIS) Here are the minimum role services required for the Web Server (IIS) server role.

Common HTTP Features

  • Static Content
  • Default Document

Application Development

  • .NET Extensibility
  • ISAPI Extensions
  • ISAPI Filters
  • Server Side Includes


  • Windows Authentication
  • Request Filtering

Management Tools

  • IIS Management Console

The following options are recommended but not required:


  • Static Content Compression
  • Dynamic Content Compression
Here are the minimum role services required for the Web Server (IIS) server role.

Management Tools

  • IIS Management Console

Web Server

  • Common HTTP Features
  • Default Document
  • Static Content


  • Request Filtering
  • Windows Authentication

Application Development

  • .NET Extensibility 4.5
  • ASP.NET 4.5
  • ISAPI Extensions
  • ISAPI Filters
  • Server Side Includes

The following services are recommended but not required:


  • Static Content Compression
  • Dynamic Content Compression
Here are the minimum role services required for the Web Server (IIS) server role.

Management Tools

  • IIS Management Console

Web Server

  • Common HTTP Features
  • Default Document
  • Static Content


  • Request Filtering
  • Windows Authentication

Application Development

  • .NET Extensibility 4.5
  • ASP.NET 4.5
  • ISAPI Extensions
  • ISAPI Filters
  • Server Side Includes

The following services are recommended but not required:


  • Static Content Compression
  • Dynamic Content Compression
Feature: Ink and Handwriting Services Ink and Handwriting Services

  • Ink Support
Ink and Handwriting Services

  • Ink Support is not required.
Ink and Handwriting Services

  • Ink Support is not required.

7.Installing Office Web App Server

Perform these procedures on all servers that will run Office Web Apps Server.

Figure: The steps to prepare servers for Office Web Apps Server

The three main steps to prepare servers for Office Web Apps Server.

7.1 Follow instructions about running PowerShell commands at “Prepare servers to run Office Web Apps Server” on the OS that is relevant for the server.

7.2 Restart the server after running the PowerShell cmdlet.

7.3 Run the setup.exe file of the download Office Web App Server file that was downloaded in step 6

7.4 After install of Office web apps  and before creating the new Office web apps server, then apply the following patch update MUST be done in the following order to be completely current with updates. Patched SP1 > April 2014 PU > May 2014 PU > June 2014 CU:

For the complete list of patch CU, see below table:

Build Number Build Name Information Link Download Link
15.0.4420.1007 RTM Download
15.0.4481.1005 March 2013 PU KB2760445 Download
15.0.4481.1508 April 2013 CU KB2810007 Download
15.0.4505.1001 April 9 2013 Hotfix KB2799821 Download
15.0.4517.1003 June 2013 CU KB2817350 Download
15.0.4535.1000 August 2013 CU KB2817521 Download
15.0.4551.1003 October 2013 CU KB2825686 Download
15.0.4551.1508 December 2013 CU KB2850013 Download
15.0.4551.1515 MS14-001 Security Update KB2863879 Download
15.0.4569.1000 Service Pack 1 KB2817431 Download
15.0.4569.1000 Service Pack 1 – Mark 2 Re-release KB2880558 Download
15.0.4605.1001 April 2014 CU (hot fix) KB2863899 Download
15.0.4615.1001 May 2014 KB2880453 Links in KB
15.0.4623.1001 June 2014 CU KB2881051 Download
15.0.4631.1000 July 2014 CU KB2883003 Download
15.0.4641.1001 August 2014 CU KB2883093 Download
15.0.4659.1001 October 2014 CU KB2889898 Download
November 2014 CU None None
15.0.4673.1000 December 2014 CU KB2899574 Download
January 2015 CU None None
15.0.4693.1001 February 2015 CU KB2956101 Download
15.0.4701.1001 March 2015 CU KB2956158 Download
15.0.4711.1000 April 2015 CU KB2965306 Download
15.0.4719.1002 May 2015 CU KB3039748 Download
15.0.4727.1001 June 2015 CU KB3054863 Download
15.0.4737.1001 July 2015 CU KB3054930 Download
15.0.4745.1001 August 2015 CU KB3055003 Download
15.0.4753.1001 September 2015 CU KB3085487 Download
15.0.4763.1000 October 2015 CU KB3085571 Download
15.0.4771.1000 November 2015 CU KB3101367 Download
December 2015 CU No Updates
January 2016 CU No Updates
15.0.4797.1001 February 2016 CU KB3114338 Download
15.0.4805.1000 March 2016 CU KB3114821 Download
15.0.4815.1000 April 2016 CU KB3114934 Download
15.0.4823.1003 May 2016 CU KB3115022 Download
15.0.4833.1003 June 2016 CU KB3115170 Download
15.0.4841.1000 July 2016 CU KB3115289 Download
15.0.4849.1000 August 2016 CU KB3115446 Download

7.5 Download and install language packs for Office Web Apps Server.

8. Deploy Office Webs Server Farm

The next step is to create Office Web Apps Server farm that uses either HTTP or HTTPS with certification.

NOTE: Use HTTP if the farm is a test\development server. Otherwise always use HTTPS on production server farm with certificate install.

The steps are below assuming that certificates has been installed, deployed and configure.

  • Create Office Web Apps Server Farm (See section 8.1)
  • Verify Farm is working OK (See section 8.2)
  • Configure the host

8.1 Create the Office Web Apps Server Farm
Use the New-OfficeWebAppsFarm command to create a new Office Web Apps Server farm that consists of a single server, as shown in the following example for HTTP for a test/dev server:

New-OfficeWebAppsFarm -InternalURL “http://servername” -AllowHttp -EditingEnabled


  • –InternalURL is the name of the server that runs Office Web Apps Server, such as http://servername.
  • –AllowHttp configures the farm to use HTTP.
  • –EditingEnabled enables editing in Office Web Apps when used with SharePoint 2013. This parameter isn’t used by Lync Server 2013 or Exchange Server 2013 because those hosts don’t support editing.

The PowerShell cmdlet for creating new Office Web Apps server farm using HTTPS on production server with trusted certificate already installed and configured on the farm:

New-OfficeWebAppsFarm -InternalUrl Https:// -ExternalUrl Https:// -CertificateName WacCert -AllowHttp


In the above command, would be the Office Web App URL that we will be using (using same for internal and external, however this can be changed as per requirement)

  • InternalURL Refers to URL that will be used by Lync 2013 Clients connected to Lync server internally.
  • ExternalURL Refers to URL that will be used by Lync 2013 Clients connected to Lync server externally.
  • CertificateName is set to ‘WacCert’ which is the friendly name of the certificate that we created earlier.

8.2 Verify Office Web Apps Server farm was created successfully
To verify Office Web Apps server was created in step 3.2.1, open IE browser and go to: http://servername/hosting/discovery , where servername is the name of the server farm that had office Web App installed.

At the end of this step, we have installed office web app server, created an Office Web App Server Farm and have associated valid certificate that was created earlier, Office Web App Server is now ready to be used with SharePoint 2013 host.

9. Configure the SharePoint host

The farm is now ready to provide Office Web Apps functionality to host over HTTP. To configure Office Web apps for hosting SharePoint 2013, follow the steps below. For more information, go to:

  1. Logged into the SharePoint 2013 server farm
  2. Right-click SharePoint 2013 Management Shell to display the app bar.
  3. In the app bar, click Run as administrator.
  4. Create the binding between SharePoint 2013 and Office Web Apps Server:

4a . In a test SharePoint environment that uses HTTP, type the following:

New-SPWOPIBinding -ServerName <WacServerName> -AllowHTTP

4b. In a production SharePoint environment that uses HTTPS, type the following:

New-SPWOPIBinding -ServerName <WacServerName>

<WacServerName> is the fully qualified domain name (FQDN) of the URL that you set for the internal URL. This is the point of entry for Office Web Apps Server traffic. For this test environment, you need to specify the –AllowHTTP parameter to allow SharePoint 2013 to receive discovery information from the Office Web Apps Server farm by using HTTP. If you don’t specify –AllowHTTP, SharePoint 2013 will try to use HTTPS to communicate with the Office Web Apps Server farm, and this command won’t work.

5. View the WOPI zone for SharePoint bindings, by typing the following PowerShell cmdlet: Get-SPWOPIZone

Office Web Apps Server uses zones to determine which URL (internal or external) and which protocol (HTTP or HTTPS) to use when it communicates with the host, in this case, SharePoint 2013. By default, SharePoint Server 2013 uses the internal-https zone.If SharePoint was configured to use externally, then you use internal-https. If SharePoint was configured to be used internally, then you use internal-http. The WOPI zone displayed by this cmdlet should be internal-http. So if it’s displayed wrongly go to step 6. Otherwise go to step 7.

6. Change the WOPI zone to internal-http – If the result from Step 3 was internal-https, run the following command to change the zone to internal-http. You need to make this change because the zone of SharePoint 2013 must match the zone of the Office Web Apps Server farm. Type this PowerShell cmdlet:  Set-SPWOPIZone -zone “internal-http”

Verify that the new zone is internal-http by running Get-SPWOPIZone again.

7. Change the AllowOAuthOverHttp settings in SharePoint to True – To use Office Web Apps with SharePoint 2013 over HTTP in a test environment, you need to set AllowOAuthOverHttp to True. Otherwise Office Web Apps won’t work. You can check the current status by running the following example: (Get-SPSecurityTokenServiceConfig).AllowOAuthOverHttp

If this command returns false, run the cmdlet below to set this to true:

$config = (Get-SPSecurityTokenServiceConfig)

$config.AllowOAuthOverHttp = $true


Run the following command again to verify that the AllowOAuthOverHttp setting is now set to True: (Get-SPSecurityTokenServiceConfig).AllowOAuthOverHttp

9.1  Verify that Office Web Apps is Working

Further Information

For more information, read the following resources in this order:


Getting Started with Git

What is Git and GitHub?

Git is a repository version source control system that keeps track of files (of any format) and folder changes that are physically kept on the computer hard drive file (e.g. C drive) or shared network drive structure on Windows or Mac OS.

Meanwhile,  GitHub is an online repository source control on the cloud where it host  unlimited public repository  to individual registered users who sign up fora GitHub account. Once users have a GitHub account, they can begin to upload and publish open source code projects and solutions that are shared to the community.

GitHub also host private repository for individual or as an organization at a monthly price that users have to pay if interested.  Thus GitHub does NOT offer any free online private repository, except for Visual Studio Online that offers private repository for up to the first 5 users.

The starting pricing model (at the time this blog was published) for an organization to host private repository is:

  • $9 / month for the first 5 users hosted at GitHub; or
  • From $21/month for a pack of 10 users hosted on SMS private cloud like Windows Azure.

To get started using Git, follow the steps below:

  1. Download and install Git from this site for either Windows or Mac OS. Accept the default settings in the installation wizard dialog box
  2. Download and read eBook Pro Git by Scott Chacon and Ben Straub that is available to read online for free.
  3. Create a new folder on the desktop hard drive
  4. Right mouse click on the folder and “Git Bash Here”. This will open an Git command prompt window starting on the folder that you have just created in step 3
  5. Create a Git repository under the current working area folder. This is done by going into Git command prompt window,  type: get init
  6. Step 5 will create an invisible “.git” folder inside the current working folder. To display a list of files and folder under current working area, type cmdlet: ls -la

How to add a  file/folder into Git?

The process of adding a file into Git is to add it to a staging area. Then commit (check in) the file in staging area

  1. To add a file to staging areal,  type: git add <file name/folder name> This cmdlet will add individual file or add bulk of files (inside the folder) into the staging area.
  2. Type: git status   This will get the status list of all  files under the working folder area. The status messages are:
  • New files – Recently new files added to staging environment (green font)
  • Untrack files – Files that are not yet committed to Get repository (red font)
  • Changes to be committed – Files that has been added into the staging environment but not yet committed (yellow/orange font)

3. Now you are ready to commit (check-in) the file into Git repository, by typing: git commit -m “revision 1”

4. To verify that the comments was stamp onto the committed files, Type: git log

Other Git cmdlets:

  • Git add .  = Add all the list of untrack files to be ready for commitment in the staging environment area.
  • Git commit -m “add comments here” = Commit all the files in staging. Parameter -n means to add the comments and display message during commit process.
  • Git config -global = Add your profile into the committed files
  • Git config -global “David Liong”
  • Git log = Display the last commit process transactions
  • Git checkout <file name> = Undo pending changes made to a file in the current working area $. All save changes made to a file in the current working area will be lost and will be reverted back to the last committed changes in version history
  • Git checkout –<file name> =  Discard files that were deleted in working directory folder. Typically undo deleted file to restore file back from last committed change in  version history. Alternatively use: git checkout <file name> command
  • Get reset HEAD <file name> = Unstage from commit, meaning remove files out of staging environment back and revert file to current working.

Recommended Links

The next step is learn how to get started using GitHub

Office 365 Developer PnP PowerShell Cmdlets

The OfficeDev PnP Cmdlets are a set of cmdlets specifically designed to provision and modify artifacts in SharePoint Online. In this way they differ a bit from the PowerShell cmdlets provided by Microsoft which are mainly focused on administrative tasks. In this post I will introduce you to the basics of the cmdlets.

The cmdlets utilize CSOM behind the scenes, which means that you can run them on any computer that has access to your server over HTTP / HTTPS.

If you want to see the cmdlets in action, please check out this video on Channel 9.


First you need to determine if you want to use the Cmdlets towards SharePoint Online / Office 365, or if you want to use them on-premises. There are two different builds of the cmdlets:

PnPPowerShellCommands15.msi for SharePoint 2013 On-Premises

PnPPowerShellCommands16.msi for SharePoint Online / Office 365.

You can download the releases here:

Download the appropriate package and run the install.


Accept the license agrement and click ‘Install’. The Advanced option allows you to pick if the cmdlets should be installed only for you or if you want to install them for all users on your computer (the latter requires that you have administrative rights with the account you are logged in with).

The install shouldn’t take more than a few seconds.

Using the cmdlets

The cmdlets are using CSOM behind the scenes. CSOM stands for Client Side Object Model and is the default SDK that developers use to build addins for SharePoint. A requirement to use this SDK is that the developer creates a so-called ‘context’ object. Think of a context object as a connection point to the server. In PowerShell we have to do something similar. We ‘connect’ the PowerShell session to your remote server with the Connect-SPOnline cmdlet:

When you enter the command, obviously with a functional url to your server and or Office 365, you will be prompted to enter your user credentials.

After you entered the Connect-SPOnline cmdlet you can execute all the other cmdlets available in the PnP Cmdlets module to perform various tasks.

For instance, to retrieve all the lists in the site:

To retrieve a specific list:


To view a property of the list:

Or to get an overview of all the properties available in the list:

Notice that not all properties might be ‘loaded’ yet. CSOM tries to be efficient when it comes to retrieving data from a SharePoint Server, and this means it will only retrieve those properties that have been explicitely requested. It will for instance never automatically retrieve values of a collection. Let me explain this with an example:

This will return an error as shown in the following screenshot:


This means that while the $list  object has a property called Views, you need to explicitely request it from the server (notice, there is also a Get-SPOView  cmdlet, which returns all the views for a list, but in this case we’re going to retrieve the views the ‘hard way’).

In order to explicitely show the views we need to tell the server to retrieve the collection, and for that we need a ClientContext object. Look at the following PowerShell snippet:


Whats commands are available?

Currently there are over 135 cmdlets available each focused on a specific tasks. It goes to far to describe them all, especially because we have built-in help in PowerShell for the cmdlets after all. To get an overview of all available cmdlets after you installed them, open PowerShell and enter:

This will list all available cmdlets.

If you want more details about a specific cmdlet, for instance about the Get-SPOList cmdlet, enter:

This will return an overview of the supported parameters, a short description per parameter and one or more examples (notice, not all PnP Cmdlets show examples, but most of them do).

If you want you to have a look at all the available cmdlets with your browser, head over here:


Missing functionality or want to contribute?

The cmdlet sourcd code is available in the following github repository: This is a sub repository for the PnP Repository available at In the latter repository you will find a wiki page at that should get you up and running with a pull request, which is the github way of proposing an addition and/or change.

Further Information

Introduction to Office 365 PnP

Getting Started with Office 365 PnP

What is Office 365 PnP (Practice and Pattern)? It is about providing a site provisioning engine to create sites and site collections within a SharePoint Online tenant or a on premise SharePoint farm base on a given definition. The definition of a site provisioning engine is an object describing the provisioned components like list, libraries and features. But also SharePoint security groups, users, site property bags entries and Composed Looks. O365 PnP is also about rising initiatives awareness to the public community about training, best practices and guidance.

With the template provider, the definition object can be transformed to JSON or XML. This works in both ways, so you can transform a XML definition into an object. Therefore you are able to define the structure of a site or site collection in a XML template. The definition object will be referred to as PnP template. Few classic site provisioning techniques is best explain with the blog author Vesa Juvonen who explains these techniques in more detail.

The modern way of site provisioning is remote provisioning. Remote provisioning uses the Client Side Object Model (CSOM) or the REST API to create a site and fill this site incrementally with CSOM/REST requests. This model is suitable for both on-premises and Office 365 online in the cloud, since we control the customizations outside of the SharePoint farm in an independent solution.

To improve the experience using remote provisioning, the Office Dev PnP team created PnP Provisioning. As mentioned earlier, a really great part of PnP Provisioning is defining a site template in a XML using the PnP Provisioning Schema.


Component of PnP

All components of office dev pnp are placed on github. It started in a single repository, but soon the volume of the program became so large, the office dev pnp team decided to split the individual components in separate repositories.

Pnp partner pack
contains the pnp partner pack, a starter kit for customers and partners and combines numerous patterns and practices demonstrated in the pnp samples to one reusable solution, which can be deployed and used in any office 365 tenant.

Pnp sites core
contains the core library and the pnp provisioning engine. The pnp provisioning engine helps to deploy customizations to remote sharepoint environments.

Pnp powershell
contains powershell wrappers to the functionalities of pnp core.

Pnp guidance
contains the documentation and guidance of the program. The contents of the master branch are published to dev.Office.Com and msdn.

Pnp office add-ins
contains samples of how to work with the html and javascript based office add-in model.

Pnp tools
contains more tools, code packages and scripts for the on-premises and hybrid setup, than purely for the office 365 operations. Using classic terminology, this could be considered more targeted for it pro’s, architects and administrators in on-premises deployments.

Pnp transformation
contains the farm solution to add-in model transformation tooling and guidance.

Pnp provisioning schema
contains the provisioning schema for pnp provisioning in XML format, a community driven effort for designing one schema which can be used to define elements in the office 365.

To get started with Office 365, below are some top useful links to begin with:

1. Watch this video title “How to get started with Office 365 PnP” webcast from Channel 9 video blog. You can download the presentation slide for this video here


2. Visit the O365 PnP home page at: 
From this homepage go to the trainining section and watch the videos:

* To find and download the Power Point presentation slides for each video, go to and search for the video title.
* Each training video also contains its sample source codes which can be found at this GitHub site:


3. Visit the O365 PnP GitHub open repository site to explore sample codes and other useful links.


4. To find and search for relevant sample codes and documentation guide on using O365 PnP, go to


5. Install the following tools:


6. Create a Console application project in VS to provision a document library into O365 SharePoint site. For sample code watch the video title “How to get started with Office 365 PnP
Other useful links of sample codes for  specific project needs are:

Introducing PnP Core Component

Site collection and sub site provisioning:

PnP Partner Pack:

Further information

Using AutoSPInstaller To Install SharePoint 2013

This section talks about the software you should have ready on your system before starting the installation and configuration process of your SharePoint 2013 farm using AutoSPInstaller.

Step 1 – Software Download
  1. Login to your SharePoint Server as your domain\sp2013setup local administrator account
  2. Download SharePoint 2013 Server (w/ SP1 preferably) –
  3. Download latest Cumulative Update –
  4. Download lastest AutoSPInstaller –
  5. Download latest AutoSPInstallerGUI –
  6. Download latest AutoSPSourceBuilder –

  7. Extract contents of AutoSPInstaller to C: drive (i.e. C:\SP)

  8. Mount your SharePoint 2013 Media File to a drive

  9. Optional (steps 9-12) – Slipstream install any cumulative updates and download prerequisites for an offline install by extracting AutoSPSourceBuilder to C:\SP  Ensure that the SharePoint farm has internet connection to do step 9-12

  10. Open Windows PowerShell as administrator

  11. Change directory to C:\SP (“CD c:\sp“) and run “Set-ExecutionPolicy ByPass

  12. Choose cumulative update (when prompted) and set parameters for an offline prerequisite install by running “.\AutoSPSourceBuilder.ps1 -GetPrerequisites $true

  13. Extract AutoSPInstallerGUI to C:\SP

  14. Ensure that C:\SP\AutoSPInstaller\AutoSPInstallerInput.xml file is not marked as read only


Step 2 – Farm Configurations and Installations

This step guides you through some of the basic configuration options that AutoSPInstaller and AutoSPInstallerGUI give you when configuring your farm. More advanced configurations are described on the AutoSPInstaller and AutoSPInstallerGUI CodePlex sites, which is now depreciated. So ignore the next steps below and go to the online GUI at to create a configuration XML file for the SharePoint farm

  1. Run AutoSPInstallerGUI.exe from C:\SP

    NOTE: Alternatively AutoSPInstallerGUI is out of date and there is now an online version of GUI where you can upload the AutoSPInstallerInput.xml file

  2. Go to File -> Load XML and point to the C:\SP\AutoSPInstaller\AutoSPInstallerInput.xml configuration file

  3. On the Install tab, fill in the necessary components and how you would like your install to be configured
    1. Set the Environment
    2. Optional – Set it to offline install because you ran AutoSPSourceBuilder and auto slip streamed the cumulative updates and downloaded the pre-reqs
    3. Enable Auto Admin with the setup account (sp2013setup in my case) password so you don’t have to keep logging in after reboots to continue the process
    4. Change the search Index Data Directory to a different drive if possible
    5. Set your PID key (product key) and SKU version

  4. On the Farm tab, populate all the appropriate settings for each sub-tab
    1. Ensure you put in a Passphrase so that you can easily add more servers to the farm
    2. Create a database alias in case you ever need to move the SQL Server
    3. Set the DB Prefix with the environment name to easily identify your databases

    Recommend changing all log file locations to a separate drive

  5. Leave or customize the defaults in the web application tab

  6. Set the Service Application tabs properties


  7. Configure the enterprise service apps if required

  8. Configure Other properties if required

  9. Go to File -> Save to save your XML file and close AutoSPInstallerGUI
  10. In C:\SP\AutoSPInstaller, right click and run the AutoSPInstallerLaunch.bat file as admin


And voila! Once the script has been run, you should have a semi-running SharePoint farm.

Uninstalling SQL Server 2012

Before You Uninstall
  1. Back up your data. Although this is not a required step, you might have databases that you want to save in their present state. You might also want to save changes that were made to the system databases. If either situation is true, make sure that back up the data before you uninstall SQL Server. Alternatively, save a copy of all the data and log files in a folder other than the MSSQL folder. The MSSQL folder is deleted during uninstallation.

    The files that you must save include the following database files:

    • Master.mdf
    • Mastlog.ldf
    • Model.mdf
    • Modellog.ldf
    • Msdbdata.mdf
    • Msdblog.ldf
    • Mssqlsystemresource.mdf
    • Mssqlsustemresource.ldf
    • Tempdb.mdf
    • Templog.ldf
    • ReportServer[$InstanceName] (This is the Reporting Services default database.)
    • ReportServer[$InstanceName]TempDB (This is the Reporting Services default temporary database.)
  2. Delete the local security groups. Before you uninstall SQL Server, delete the local security groups for SQL Server components.
  3. Stop all SQL Server services. We recommend that you stop all SQL Server services before you uninstall SQL Server components. Active connections can prevent successful uninstallation.
  4. Use an account that has the appropriate permissions. Log on to the server by using the SQL Server service account or by using an account that has equivalent permissions. For example, you can log on to the server by using an account that is a member of the local Administrators group.


To Uninstall an Instance of SQL Server 2012
  1. To begin the uninstall process, go to Control Panel and then Programs and Features.
  2. Right click Microsoft SQL Server 2012 and select Uninstall. Then click Remove. This starts the SQL Server Installation Wizard.

    Setup Support Rules runs to verify your computer configuration. To continue, click Next.

  3. On the Select Instance page, use the drop-down box to specify an instance of SQL Server to remove, or specify the option to remove only the SQL Server shared features and management tools. To continue, click Next.
  4. On the Select Features page, specify the features to remove from the specified instance of SQL Server.

    Removal rules runs to verify that the operation can complete successfully.

  5. On the Ready to Remove page, review the list of components and features that will be uninstalled. Click Remove to begin uninstalling
  6. Immediately after you uninstall the last SQL Server 2012 instance, the other programs associated with SQL Server 2012 will still be visible in the list of programs in Programs and Features. However, if you close Programs and Features, the next time you open Programs and Features, it will refresh the list of programs, to show only the ones that are actually still installed.



Isolate Service Interruption – Lesson 6.3



Mock Exam Question Samples

E-mail clients are used with Office 365 to access and manage e-mails and calendars. Like other applications, there are instances where issues may arise and these issues need to be identified and resolved. A client program is available that can be used to detect connectivity issues between the email clients and Office 365. E-mail users can use this tool to locate common issues. What tool can be used by the e-mail users to identify these issues? Choose the best option(s) from those listed below.

A: Microsoft Connectivity Analyzer

B: Microsoft Online Services Diagnostics and Logging

C: Microsoft Office 365 admin center

D: Transport Reliability IP Probe

The Microsoft Connectivity Analyzer tool is used to detect connectivity issues between the e-mail clients and Office 365. It can be used by e-mail users to find common issues or by administrators to help resolve issues that could be affecting the Exchange Server deployment. It functions by using a simulated scenario such as client logon. If issues exist, error messages will be displayed that can provide helpful tips to resolve the issues.

Correct Option(s): A: Microsoft Connectivity Analyser  tool


Incorrect Option(s):

  • B: Microsoft Online Services Diagnostics and Logging – The Microsoft Online Services Diagnostics and Logging (MOSDAL) tool can be used to diagnose a network and also gather system and network configurations, and logging information which is used to connect to Office 365. It is not the tool used to identify connectivity issues between the e-mail clients and Office 365.  
  • C: Microsoft Office 365 admin center – The Microsoft Office 365 admin center is used to configure, manage, and monitor Office 365 products. It is not the tool used to identify connectivity issues between the e-mail clients and Office 365.  
  • D: Transport Reliability IP Probe – The Transport Reliability IP Probe (TRIPP) tool is typically used to test the quality of an Internet connection to a Microsoft Online Service such as Lync Online. It is not used to identify connectivity issues between the e-mail clients and Office 365.  

Continue reading Isolate Service Interruption – Lesson 6.3

Monitor Service Health – Lesson 6.2



Mock Exam Sample Questions

With Office 365, an admin center is available that allows administrators to manage and administer Office 365. Navigation sections such as Dashboard, Setup, Users & Groups, Service Settings, Service Health, and Reports are available. If an Office 365 administrator needs to view when planned maintenance is scheduled for some services, which section will include this information? Choose the best option(s) from those listed below.

A: Service Settings

B: Service Health

C: Reports

D: Setup

You access the Service Health area section of the Office 365 admin center to view planned maintenance that is scheduled for services. The Service Health area includes a dashboard view of the services running in Office 365. It enables you to see a historical view of issues that affected the service and also any planned maintenance that is scheduled on services. The Rich Site Summary (RSS) feed feature can also be configured to obtain real-time access on service incidents and maintenance that is planned.

Correct Option(s): B: Service Health  


Incorrect Option(s):

  • A: Service Settings – The Service Settings section allows you to access service settings such as Exchange Online service settings, sites, user software, passwords, and mobile. Service Settings would not include information on planned maintenance that is scheduled on services.  
  • C: Reports – The Reports section allows you to access reports that show how the organization is using Office 365 services. For example you can view mail, protection, rules, and Data Loss Prevention (DLP) reports. The Reports section will not include information on planned maintenance that is scheduled on services.  
  • D: Setup – The Setup section allows you to access and configure the Office 365 setup options, which include basic and custom. The Setup section will not include information on planned maintenance that is scheduled on services.  

Continue reading Monitor Service Health – Lesson 6.2

Analyse Reports – Lesson 6.1



Mock Exam Sample Questions

Organizations that use Office 365 often want to view information that shows how Office 365 is being used. Information such as active and inactive mail boxes, received mail, application sharing and web, and dial-in conferences. Which area of the Office 365 admin center would you access to view information on malware detections in received-mail? Choose the best option(s) from those listed below.

A: The Reports section

B: The Support section

C: The Service Health section

D: The Dashboard section

The Reports section of the Office 365 admin center allows you to view information on malware detections in received-mail. The available reports show how the organization is using the Office 365 services. These reports can be used to locate and resolve issues and filter data. Custom reports can also be created using the Office 365 reporting web services. The available reports are based on the services that your organization is subscribed to. Some of the available reports that you may have access to are malware detections in received email, active and inactive mailboxes, mailbox usage, received and sent email, application sharing and web, and dial-in conferences.

Correct Option(s): A: The Reports section  

Incorrect Option(s):

  • B: The Support section – The Support section of the Office 365 admin center allows you to search for answers, view solutions to issues, and access troubleshooting tools. The Support section is not used to view information on malware detection in received-mail.  
  • C: The Service Health section – The Service Health section in the Office 365 admin center is used to view service interruptions or outages in the service that affects the service and planned maintenance information. The Service Health section is not used to view information on malware detections in received-mail.  
  • D: The Dashboard section – The Dashboard section of the Office 365 admin center is typically what you will see by default when you access the admin center. It displays a quick overview of the service health and usage and allows you to access help resources. The Dashboard section is not used to view information on malware detections in received-mail.  

Continue reading Analyse Reports – Lesson 6.1

Setting up First Domain Controller in Windows 2012


In Windows Server 2012, dcpromo has been deprecated.


Using Server Manager (UI):

In order to make the windows server 2012 domain controller we will install ADDS (Active Directory Domain Services) role from the server manager on Windows Server 2012.

All the Latest security updates must applied before installing the Role.

First we will change the server name let say DC01 and the IP address (try to avoid using default


Installing the AD DS role

“Before You Begin” screen provides you basic information such as configuring strong passwords, IP addresses and Windows updates.


On Installation Type page, select the first option “Role-based or Feature-based Installation“.

Scenario-based Installation option applied only to Remote Desktop services.


On the “Server Selection” Page, select a server from the server pool and click next.


To install AD DS, select Active Directory Domain Services in turn it will pop-up to add other AD DS related tools. Click on Add Features.


After clicking “Add Features” above, you will be able to click “Next >” as shown in the screen below.


On the “Select Features” Page, Group Policy Management feature automatically installed during the promotion. Click next.


On the “Active Directory Domain Services” page, it gives basic information about AD DS. Click Next.


On the “Confirmation” Page, You need to confirm this to continue with this configuration. It will provide you an option to export the configuration settings and also if you want the server to be restarted automatically as required.

After clicking “Install” the selected role binaries will be installed on the server.

After “Active Directory Domain Services” role binaries have been installed and now it is time to promote the server to a Domain Controller.


TechNet Article:


To create a new AD forest called “ArabITPro.local”, select add a new forest.

Type the name ArabITPro.local

Specify the FFL, DFL, whether or not it should be a DNS Server and also the DSRM administrator password. As you can see, it has selected the GC option by default and you cannot deselect it. The reason for this is that is the very first DC of the AD forest and at least one needs to be a GC.

DNS delegation warning.

Checks the NetBIOS name already assigned.

Specify the location of the AD related folders and then click next.

Summary Of All Installation Options/Selections.


Click View script for single command line PowerShell script for dcpromo.


Before the actual install of AD, all prerequisites are checked. If All prerequisite checks are passed successfully then click Install.

When you click Install, DNS and the GPMC are installed automatically.


After the promotion of the server to a DC finished server restart automatically.

Once the server is booted and you logon to it, click on Server Manager | Tools , will notice that following have been installed:

  • Active Directory Administrative Center
  • Active Directory Domains and Trusts
  • Active Directory Module for Windows PowerShell
  • Active Directory Sites and Services
  • Active Directory Users and Computers
  • ADSI Edit
  • DNS
  • Group Policy Management



Setting up SharePoint 2013 Dev Box on Hyper-V

SharePoint 2013 service-pack 1 is officially out bringing with it support for Windows Server 2012 R2. This is most excellent news for SPDevs because finally SharePoint can be used on generation-2 virtual machines which for developer boxes is a much needed improvement due to the much improved integration for the standard VM viewer. Think remote-desktop type integration; this has been sorely lacking before R2 as Hyper-V is a server-room technology first & foremost so client-side integration has had to take a back-seat for the beginning of Hyper-V’s lifetime at least. Regardless, we now have it finally but it does involve rebuilding the entire virtual machine from scratch as generation 1 VMs can’t be converted or upgraded.


Setup Steps

This environment will just consist of x2 VMs for now to try and save on memory/hard-disc:

  • Domain controller box
    • DNS services
    • Active Directory services
    • Certificate Authority services if needed later on
  • SharePoint box
    • SharePoint 2013 with all roles
    • SQL Server – core database engine only

SharePoint just isn’t supported on AD servers as domain controllers have no concept of local security groups – something SharePoint uses a lot. Lots of SharePoint does work on AD machines; more than does not in fact but there’s plenty of functionality that just won’t work unless it’s on a standard member-server so that’s what we’re going to do too.

This guide will run through setting up the environment in the following stages:

  • Configure Hyper-V + virtual networks
  • Install Windows
  • Prepare the AD + add SharePoint machine.
  • Install software – SQL + SharePoint.
  • Install developer apps.
  • Update/tweak SharePoint VM ready to start developing.

Pre-requisitie- Create an Active Directory/Domain Controller Server

SharePoint needs an AD to work properly; either use an existing AD box or build a new one by repeating the process for the SharePoint machine but with a starting memory allocation of 2 GB & x2 CPUs when you edit the machine. Read my blog here for more details on how to create an AD Domain Controller server.

Ensure service, admin/setup accounts with necessary machine and Active Directory permissions (an example of my setup below):

1. Download ISOs

You’ll want to download the Windows Server R2 image, from MSDN most likely as this is just for development:


Also if possible, use the SP1 slipstream ISO for SharePoint.


Both RTM + SP1 install methods are documented below.

2. Configure Hyper-V + Virtual Networks

For our setup we’re going to have a private network and a public one. The private network will be so the VMs can communicate directly. Create a private network (not “internal”; we don’t want the VM host on the private VM network).


Connect an external network to one of your physical network adapters so machines can see out to the internet when necessary.

Create new Generation 2 Virtual Machine(s)

Now create a new VM in your local Hyper-V. Hyper-V can be installed on Windows 8.1 or Windows 2012 R2 – for simple development environments you’ll not notice any difference between the two.


Call it whatever you fancy really. Make sure you select “generation 2” – this is the new option that Hyper-V in Windows 8.1/2012 R2 gives us and it provides a much cleaner virtual machine over generation 1.


Give your VM 8GB (Maximum) or 4GB minimum of memory with the option to grow. Once everything’s running it’ll consume up-to 16 GB easily; SharePoint development isn’t for developers on a shoe-string-budget for hardware that’s for sure.


8 GB is a nice starting amount of RAM – with dynamic memory enabled (not supported for SharePoint normally) Hyper-V will shrink the memory allocation if it’s not needed, which until SharePoint is on & configured will very likely happen. Setting it too low will cause of lot of disc thrashing once SharePoint’s installed and configured due to how quickly memory grows on start-up. This would likely cause various timeouts on a cold boot with an initial allocation of 8 GB at least; remember that SQL Server’s on this machine too. Don’t save money on memory for SPDev – that’s something everyone learns quickly if they fall short.

As for networking, select the internal network for now. Later we’ll add an external adapter too.

Next, put a disk somewhere local to the host machine; somewhere that has decent read/write speeds as it’ll be pretty disk intensive (hint: not a USB drive). Also give it up-to 200 GB of space (or more), not the default 127 GB as by the time we’ve installed all the tools & bits it’s going to get quite full. You can expand the disk later if necessary of course, and if you’ve got bags of actual hard-disk space it’s preferable to not use dynamically expanding disks if possible.


Finally, select the ISO to install from – pick your downloaded Windows 2012 R2 ISO as the install source.

3. Edit Virtual Machines to Add More Hardware

The “new VM” wizard for some reason doesn’t ask about CPUs or any other extras for that matter – presumably for simplicity’s sake. SharePoint at least needs at least 4 physical cores so be functional, especially given it’s an “all-roles-in-one” box + developer tools on-top installation so we need to go back and edit each VM to give them more CPU power.


For networking, you might want to also add an external adapter too so the machine can see out to the big-wide-world when needed. When we don’t we can disable the adapter in the VM so as to avoid re-configuring Hyper-V again.

5. Install Windows Server

Next up; a good old clean Windows install. Being generation-2 machines, this won’t take long at all. It’s so fast in fact I’ve seen gen-2 VMs install quicker than some real servers boot up, but I digress – start the ball rolling…


I’m based in Spain so I need a Spanish keyboard layout; get the right layout here so you don’t get keyboard rage later.

Click next; you want a GUI install. Server core is the preferred install generally but SharePoint doesn’t support it, not to mention this is a dev environment so unless you’re a PowerShell master you’ll be wanting a nice & easy GUI to get things done.

Select “advanced” setup so you can partition the virtual disc etc, and start the process. After a couple of reboot you’ll need to set a local administrator password and you’re done!

Enable New Virtual Machine Integration

At some point, you’ll see this window pop-up which you might not’ve seen before:


This is basically the new integration tools kicking in now Windows is fully loaded and the generation-2 interfaces kick-in. Think RDP for Hyper-V – you can connect host discs, copy/paste freely, play sounds, etc. It’s just much friendlier than the traditional integration. Configure this now – I’d highly recommend you connect up local discs (show options; local resources; more)


Make sure you select “drives” to connect your local disks to the VM for file-copying – a very convenient improvement in generation-2. Once you confirm the integration settings, the VM viewer tool will reconnect. To edit these settings again you need to close the viewer, right-click on the VM in Hyper-V manager and click “Connect…” and which point the viewer will re-open and allow you to change the integration configuration.


I have to admit this wasn’t so obvious to me either but there you go.

Configure Local Network & Join to Domain Controller Server

At some point you’re going to have to setup the private network for your SharePoint + AD + any other boxes you want for testing (Office Web Apps server for example). Static IP allocation is the way to go; To get SharePoint dev box server to join to the Domain Controller virtual machine, that was created here, follow this instruction from Microsoft

5. Prepare the SharePoint VM Machine.

Prepare SharePoint VM – Add to Domain

Now all the system prep is done we want to add our new SharePoint machine to our domain. As ever it’s in system-properties:


If your SharePoint VM DNS settings are correct you should see this when you click “OK” and enter a domain admin credentials:


Good times. Reboot to complete the configuration.


6. Install Local SQL Server + SharePoint

SQL Server

After domain-joining the SharePoint VM you should now log in with a domain account; an administrator preferably. Remember the login is “domain\Administrator” not just “Administrator” as there’s a local account with that name too.

Get hold of SQL Server 2012 with SP1 integrated. Install a standalone instance – install the SQL setup files (let the installed find and install the newer setup files)


Anyway, follow the rest of the wizard – install just the database engine & management tools, use the default instance name (MSSQLSERVER) & add your current domain user to the list of DBAs when prompted. We’re going for a skinny SQL install because that’s all SharePoint needs for the most part.


Next step is to install SharePoint bits after running the prep-tool. At the time of writing there’s no slipstreamed SharePoint 2013 + SP1 install yet so we’re going to have to work around the fact the pre-requisites installer just doesn’t work very well on 2012 R2 – just running it will fail.

Install SharePoint 2013 + SP1 Prerequisites

If you have SharePoint 2013 installer with SP1 slipstreamed this is definitely the easiest way because the prerequisite installer actually works.


If however that’s not an option…

Install SharePoint 2013 RTM Prerequisites

What we need to do is manually what the installer would do; download & install the prerequisites. We need to configure the server roles and then install the list of packages that would normally happen automatically.

Install the roles needed with:

Import-Module ServerManagerAdd-WindowsFeature NET-WCF-HTTP-Activation45,NET-WCF-TCP-Activation45,NET-WCF-Pipe-Activation45 -Source D:\Sources\sxsAdd-WindowsFeature Net-Framework-Features,Web-Server,Web-WebServer,Web-Common-Http,Web-Static-Content,Web-Default-Doc,Web-Dir-Browsing,Web-Http-Errors,Web-App-Dev,Web-Asp-Net,Web-Net-Ext,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-Health,Web-Http-Logging,Web-Log-Libraries,Web-Request-Monitor,Web-Http-Tracing,Web-Security,Web-Basic-Auth,Web-Windows-Auth,Web-Filtering,Web-Digest-Auth,Web-Performance,Web-Stat-Compression,Web-Dyn-Compression,Web-Mgmt-Tools,Web-Mgmt-Console,Web-Mgmt-Compat,Web-Metabase,Application-Server,AS-Web-Support,AS-TCP-Port-Sharing,AS-WAS-Support, AS-HTTP-Activation,AS-TCP-Activation,AS-Named-Pipes,AS-Net-Framework,WAS,WAS-Process-Model,WAS-NET-Environment,WAS-Config-APIs,Web-Lgcy-Scripting,Windows-Identity-Foundation,Server-Media-Foundation,Xps-Viewer,Windows-Identity-Foundation -Source D:\Sources\sxs

The software packages to be installed are as follows:

Install SharePoint Server

Now we can install SharePoint 2013 by running “setup.exe” to launch the normal setup program. Select “complete” installation as we already have SQL Server ready (plus management tools).


When this finishes, do not run the wizard if this is RTM! We’ll do that once it’s all patched-up to SP1, which if your install isn’t slip-streamed will need to be done separately.

For more details about installing SharePoint 2013 and SQL Server, read below As-Built documentation

7. Install Development Tools and Office Apps

Next we want to get all our development tools & dependencies installed. First up; Visual Studio. 2013 now comes with the Office tools built-in which is nicer than before as they were separate. Install Visual Studio first.

Then we want to get Office + Visio + Project + SharePoint Designer on at the same time because installing new Office components requires the service-packs & some patches to be reapplied afterwards. Yes, SharePoint Designer is technically a part of Office so if you install SPD after patching Office to SP1 for example you’d have to re-apply SP1 again.


Configure Farm

Obviously we need to create a new farm at some point soon. Some people have all-singing, all-dancing scripts to do it (and even me too) but for developer environments I tend to prefer a more practical approach of just creating stuff as it’s needed. Everything will run under the one service-account which is a local admin (and thus breaking every best-practise in the book) but as we’re in dev-land we don’t care for now. Add your farm account to the local admins group:


Then fire up the wizard and create a new farm.


Make it clear this is a development farm.

I’ll not go into the ins’ & outs of configuring a developer “farm”; needless to say on a dev-box most good practices go out the window anyway. Just make sure your testing/staging/production environments do not in any way mirror the lazy setup that’s fine in development. Seriously don’t; minimum security practices are essential for security but we don’t need it in dev.


8. Updates, Tweaks, and Tools

Once you’ve got everything installed, the system will need patching. Start by installing Office 2013 service-pack 1 – as that covers a multitude of sins.

After that, run Windows Update too to bring everything up-to-date too


You’ll probably have lots to update; leave it updating overnight to reduce patch-stress.

Final Touches – Make Your VM Nice to Develop With

This is going to be a development environment which means maximum convenience 1st; security and correct architecture 2nd. The machine can die and it won’t matter in other words so we’re going to make it all cosy to use, which servers by default aren’t. This next bit is completely subjective – what’s comfortable to me might not be to someone else but I thought I’d jot it down anyway.

Install Useful Tools

I have a standard set of SPTools I like to use on dev machines and even some production machines. These are:

  • My very own ULS Studio for capturing ULS logs in real-time. It’s a work in progress and there are other tools out there but my version isn’t bad either (not that I’m biased at all, honest). There is of course also ULS Viewer too which most people seem to use. For now ;)
  • Fiddler – for HTTP tracing. Very useful.
  • Network Monitor for taking lower-level traces & not just HTTP.
  • SMTP4Dev – SMTP server for testing alerts. It shows just a log of messages received; perfect for development.
  • Telnet Windows component – useful for probing firewalls & raw network responses. Installable via Server Manager (Windows Features).
  • Process monitor – kernel-level troubleshooting for access denied issues.
  • Firefox + Firebug add-on for alternative browser testing. Firebug is a great HTTP debugging tool if you don’t want to use the IE11 tools (which have had a major overhaul since IE10).
  • SharePoint Manager – great for traversing the SharePoint object-model from farm to individual list items.
  • WinRAR – archiving tool.
  • ILSpy – handy for peeking inside any assembly quickly.
  • LINQPad – execute C# directly against SharePoint, PowerShell style.
Disable Overly Protective Security

Start by turning off UAC and the IE lock-down mode. Don’t do either of these in production of course; they’re there for a good reason. In server manager, under “local server” you’ll see a link called “IE Enhanced Security Configuration”. Click it and disable IE ESC for both types of users. To disable UAC, search on the start screen for “UAC” and you’ll see “Change User Account Controls setting” – open and move setting to “Never notify” – a dangerous move normally as UAC is a great help in making sure nothing wants to sneakily change your system configuration (for better or worse) but on this development environment there’ll be nothing of any real value running except our code.

Again, this security is normally pretty useful as humans don’t do such a good job of checking files for threats but I digress…



Building SharePoint 2013 BI Demo Environment (Part 1 to 10). This series consists of the following parts:

Installing SharePoint 2013 Using AutoSPInstaller (4 part series):


The links to these parts will be updated when the series progresses.

Plan Requirements for AD Federation Services – Lesson 5.1



Mock Exam Samples

Continue reading Plan Requirements for AD Federation Services – Lesson 5.1

Manage AD Users Group with DirSync – Lesson 4.3


Continue reading Manage AD Users Group with DirSync – Lesson 4.3