SCOM 2016 – Install System Center Operations Manager 2016 – Part 6

Standard

In this series off blog post I am going to take you true the steps I took to install System Center Operations Manager 2016. The Environment will be installed using the following software:

  • Microsoft Windows Server 2016 – Download from here
  • Microsoft SQL Server 2016 – Download from here
  • System Center Operations Manager 2016 – Download from here

My Test environment consist of the following servers,

  • DC01 – Domain Controller
  • SQL01 – Microsoft SQL 2016 server
  • DATA01 – Data Server
  • MS01 – Scom Management Server 01
  • MS02 – Scom Management Server 02
  • MS03 – Scom Management Server 03 | Audit Collection Service
  • SQLRPS01 – SQL Reporting Service 01
  • WEB01 – Scom Web Console Server,
  • WAP01 – Web Applications Proxy.

 

Here you can find the previous blogposts

In this part we are going to install System Center Operations Manager Audit Collections Services. I installed a third management server in my environment. On how to install a management server please have a look at Part 2.

When the management server is installed. Let’s start by installing audit collection service.

  1. On the “Operations Manager” page, click “Audit Collection Services
    acs01

  2. On the “Audit Collection Services Collector Setup” page, in the “Welcome to the audit collection Service setup Wizard” section click “Next
    acs02

  3. On the “Audit Collection Services Collector Setup” page,  in the “Microsoft Software License Terms” section click “I accept the license terms” and click “Next
    acs03

  4. On the “Audit Collection Services Collection Setup” page in the “Database Installation Options” section select “Create a new database” and click “Next
    acs04

  5. On the “Audit Collection Services Collection Setup” page, in the “Data Source” section click “Next
    acs05

  6. On the “Audit Collection Services Collector Setup” page, In the “Database” section select “Remote database Server” and enter the name of you SQL server. In my configuration it looks like this:
    acs06

  7. On the “Audit Collection Services Collector Setup” page, in the “Database Authentication” section select “Windows Authentication” and click “Next
    acs07

  8. On the “Audit Collection Services Collector Setup” page, in the “Database Creation” section select “Use SQL Servers default data and log file directories” and click “Next
    acs08

  9. On the “Audit Collection Services Collector Setup” page, in the “Event Retention Schedule” section click “Next
    acs09

  10. On the “Audit Collection Services Collector Setup” page, in the “ACS Stored Timestamp Format” section, select “Local” and click “Next
    acs10

  11. On the “Audit Collection Services Collector Setup” page, in the “Summary” section click “Next
  12. On the “Audit Collection Services Collector Setup” page, in the “Audit collection services has been successfully installed” click “Finish
    acs11

When you start the System Center Operations Manager Console and you expand Microsoft Audit Collection Services, Collector and click the state view you should see something like this:

acs12

Next we need to deploy the ACS reporting Services.

  1. On your reporting server in my case "SQLRP01" create a temporary folder "C:\ACS"
  2. On the Installation Media browse to “ReportModels\acs” and copy all the files and directories to the above created directory
  3. Open a command prompt window by using "Runs as Administrator" and change the directory to the "Acs" directory
    acs13
  4. Enter the following command “UploadAuditReports “SQLRP01\MSSQLSERVER” “http://sqlrp01/ReportServer$MSSQLSERVER” “D:\ACS”
    acs14

When finished the results should look something like this:

acs16

This completes this part off the series installing System Center Operations Manager 2016. In the next part we are going to install the Gateway

SCOM 2016 – Install System Center Operations Manager 2016 – Part 5

Standard

In this series off blog post I am going to take you true the steps I took to install System Center Operations Manager 2016. The Environment will be installed using the following software:

  • Microsoft Windows Server 2016 – Download from here
  • Microsoft SQL Server 2016 – Download from here
  • System Center Operations Manager 2016 – Download from here

My Test environment consist of the following servers,

  • DC01 – Domain Controller
  • SQL01 – Microsoft SQL 2016 server
  • DATA01 – Data Server
  • MS01 – Scom Management Server 01
  • MS02 – Scom Management Server 02
  • SQLRPS01 – SQL Reporting Service 01
  • WEB01 – Scom Web Console Server,
  • WAP01 – Web Applications Proxy.

Here you can find the previous blogposts

In this part we are going to install System Center Operations Manager Reporting Service.

Before we can start installing the reporting service module we need to make sure that our SQL reporting server is member of SQL group “SG – SQL2016” that we created in part 1 

First we need to install “Active Directory Module for Windows PowerShell” this can be done using the following steps:

  1. Start the "PowerShell" command line ad administrator and enter the following command:
     Install-WindowsFeature RSAT-AD-PowerShell

    The result should look something line this:

    reporting01

  2. In the “Powershell” command line enter the following command:
      Get-ADServiceAccount Sql2016Report

    The result should look something line this: 
    reporting02

If the values are true then its time to install the SQL Server Reporting Services. I took the following steps:

  1. In the "SQL Server Installation Center" wizard on the "Planning" page click "Installation"
  2. In the "SQL Server Installation Center" Wizard on the "Installation" page, click "New SQL Server Stand-Alone installation or add features to an existing installation"
  3. In the “SQL Server 2016 Setup” Wizard on the “Product key” page, enter a product key and click “Next
  4. In the “SQL Server 2016 Setup” Wizard, on the “License Terms” page check “I accept the license terms” and click “Next
  5. In the “SQL Server 2016 Setup” Wizard, on the “Microsoft Update” page click “Next
  6. In the “SQL Server 2016 Setup” Wizard, on the “Product Update” page click “Next
  7. In the “SQL Server 2016 Setup” Wizard, on the “Install Setup files” page click “Next
  8. In the “SQL Server 2016 Setup” Wizard, on the “Install Rules” page click “Next
  9. In the “SQL Server 2016 Setup” Wizard, on the “Feature Installation” select “Report Services Native” and click “Next

    reporting03

  10. In the “SQL Server 2016 Setup” Wizard, on the “Instance Configuration” page, click “Next
  11. In the “SQL Server 2016 Setup” Wizard, on the “Service Account” page add managed service account and click “Next

    reporting04

  12. On the “SQL Server 2016 Setup” Wizard, on the “Reporting Service Configuration” page, click “Next
  13. On the “SQL Server 2016 Setup” Wizard, on the “Ready to Install” page, click “Install
  14. On the “SQL Server 2016 Setup” Wizard, on the “Complete” page click “Close

Now we need to configure the reporting service

    1. On the “SQLRP01 server” start the “Report Service Configuration Wizard

      reporting05

    2. On the “Reporting Services Configuration Connection” page, click “Connect
    3. On the “Reporting Services Configuration Manager” page, click “Database” and connect to your SQL server. In my case “SQL01”. The end result should look something like this:

      reporting06

Now its time to install the reporting Services for System Center Operations Manager

  1. On the "System Center Operations Manager 2016" install page click "Install"
  2. On the “Operations Manager Setup” page, in the “Select Features to Install” section select “Reporting Server” and click “Next

    reporting07

  3. On the “Operations Manager Setup” page in the “Select Installation location” section change the location to where you want to install the reporting Service and click “Next

    reporting08

  4. On the “Operations Manager Setup” page, in the “Proceed with Setup” section, click “Next
  5. On the “Operations Manager Setup” page, in the “Please read the License terms” section, check “I have read, understood, and agree with the license terms” and click “Next

    reporting09

  6. On the “Operations Manager Setup” page, in the “Specify Management Server” section enter the management server you want to use and click “Next

    reporting10

  7. On the “Operations Manager Setup” page, in the “SQL Service for reporting Services” section, make sure that the right reporting server is selected and click “Next

    reporting11

  8. On the “Operations Manager Setup” page, in the “Configure Operations manager Accounts” section enter the data reader account and password and click “Next

    reporting12

  9. On the “Operations Manager Setup” page, in the “Diagnostic and Usage Data” section click “Next
  10. On the “Operations Manager Setup” page, in the “Installations Summary” section click “Install
  11. On the “Operations Manager Setup” page, in the “Setup is Completed” section click “Close

    reporting12

When you start the System Center Operations Manager Console the end result should look something like this

reporting14

In the next part we are going to install Audit collection services.

SCOM 2016 – Install System Center Operations Manager 2016 – Part 4

Standard

In this series off blog post I am going to take you true the steps I took to install System Center Operations Manager 2016. The Environment will be installed using the following software:

  • Microsoft Windows Server 2016 – Download from here
  • Microsoft SQL Server 2016 – Download from here
  • System Center Operations Manager 2016 – Download from here

My Test environment consist of the following servers,

  • DC01 – Domain Controller
  • SQL01 – Microsoft SQL 2016 server
  • DATA01 – Data Server
  • MS01 – Scom Management Server 01
  • MS02 – Scom Management Server 02
  • WEB01 – Scom Web Console Server,
  • WAP01 – Web Applications Proxy.

Here you can find the previous blogposts

In this part we are going to install the System Center Operations Manager web-console and going to publish it using the Web Application Proxy Server.

I took the following steps to install the Web Application Proxy Service. Before you can start installing you need to make sure that you have a Certificate. I bought mine wildcard certificate using Xolphin. Also make sure that on you firewall you forward 443 traffic to you Web Application Proxy server and create a DNS entry web01.domain.com

  1. Start the “Server Manager” and click “Manage” and click “Add Roles and Features
  2. On the “Add roles and Features wizard” page, in the “Before you begin”  section,  click “Next
  3. On the “Add roles and Features Wizard” page in the “Select Installation type” section, select “Role-based or feature-based installation” and click “Next
  4. On the “Add Roles and Features Wizard” page, in the “Select Destination Server” section, select the server where you want to install Web Application Proxy and click “Next
  5. On the “Add Roles and Features Wizard” page, in the “Select Server Roles” section select “Remote Access” and click “Next
    wap01
  6. On the “Add Roles and Features Wizard” page, in the “Features” section click “Next
  7. On the “Add Roles and Features Wizard” page, in the “Remote Access” section click “Next
    wap02
  8. On the “Add Roles and Features Wizard” page, in the “Role Services” section, select “Web Application Proxy”. In the popup “Add Roles and Features” click “Add Features”. In the “Add Roles and Features Wizard” page, in the “Role Services” section click “Next
    wap03
  9. On the “Add Roles and Features Wizard” page, in the “Confirm Installation Selection” section, check “Restart the destination server automatically if required” and click “Install
    wap04
  10. On the “Add Roles and Features Wizard” page, in the “Installation process” section, click “Close” when completed
  11. Login into your Active Directory Federation Server and start the Microsoft Management Console using the command “MMC
  12. On the “Console1 – [Console Boot]” screen go to “File”,  “Add/Remove Snap-ins” select “Certificates” then click “Add
    wap05
  13. On the “Certificate Snap-in” page, select “Computer account” and click “Next
    wap06
  14. On the “Select Computer” page, select “Local Computer (The computer this Console is running on)” and click “Finish
    wap07
  15. On the “Add Remove Snap-in” page click “OK
  16. On the “Console1 – [Console Root\Certificates (Local Computer)\Personal\Certificates]” page, expand “Certificates (Local Computer)”, “Personal”, “Certificates” right click the certificate you used to setup you Active Directory Federation Server and go to “All Tasks”, “Export
    wap09
  17. On the “Certificate Export Wizard” page click “Next
  18. On the “Certificate Export Wizard” page select “Yes, Export Private Key”and click “Next
  19. On the “Certificate Export Wizard” page, select “Personal Information Exchange – PCKS #12 (.pfx) ” and check “Include all Certificates in the certification path if possible” and click “Next
  20. On the “Certificate Export Wizard” page, in the “Password” section enter a password and click “Next
  21. On the “Certificate Export Wizard” page click Browse and find a location to save the .pfx file to. Type in a name such as "mydomain.pfx" and then click Next.
  22. On the “Certificate Export Wizard” page and click “Finish
  23. Login into your Web Application Proxy Server and start the Microsoft Management Console using the command “MMC
  24. On the “Console1 – [Console Boot]” screen go to “File”,  “Add/Remove Snap-ins” select “Certificates” then click “Add
  25. On the “Console1 – [Console Root\Certificates (Local Computer)\Personal\Certificates]” page, expand “Certificates (Local Computer)”, “Personal” right click the certificate you used to setup you Active Directory Federation Server and go to “All Tasks”, “Import
    wap10
  26. On the “Certificate Import Wizard” page click “Next
  27. On the “Certificate Import Wizard" page, Browse to the Certificate you exported. and click “Next
    wap11 
  28. On the “Certificate Import Wizard” page, Enter the “password” and click “Next
  29. On the “Certificate Import Wizard” page, leave the default certificate store as Personal. Click Next 
  30. On the “Certificate Import Wizard” page, click “Finish” The end result should look something like this
    wap12
  31. In  “Server Manager” under ”Notifications” click the message “Open the Web Application Proxy Wizard
  32. On the “Web Application Proxy Configuration Wizard” screen in the “Welcome” section, click “Next
    wap13
  33. Optional Configuration if you have ADFS Running On the “Web Application Proxy Configuration Wizard” page, in the “Federation Server ” section enter the “adfs.ms-opsmgr.eu” and the Service Account you created during AD FS setup. Click Next:
    wap14
  34. On the “Web Application Proxy Configuration Wizard” page, in the “AD FS Proxy Certificate” section on the drop down menu select the certificate you imported from your AD FS server. Click Next:
    wap15
  35. On the “Web Application Proxy Configuration Wizard” page, in the “Confirmation” section click “Configure
    wap16
  36. On the “Web Application Proxy Configuration Wizard” page, in the “Results” section click “Close
    wap17
  37. When you start the “Remote Access Management Console” result shoulld look something like this:
    wap18

Now that we have the Active Directory Federation Server and Web Application Proxy installed we can start installing the System Center Operations Manager Web Console.

Before we can install the System Center Operations Manager Web Console we must install the following Software. Report viewer which can be downloaded from here and the Microsoft System CLR Types for SQL Server 2014 which can be downloaded from here. Il be using the Group Policy’s to deploy the software I already wrote down the steps you need to take to accomplish this in “SCOM 2016 – Install System Center Operations Manager 2016 – Part 3” which can be found here. Also make sure you imported your certificate.

    1. On server “Web01 ” start “PowerShell” command line utility as administrator to install the IIS-Components that are needed for the web-console. I ran the following command:
      Add-WindowsFeature Web-Server, Web-WebServer, Web-Common-Http, Web-Default-Doc, Web-Dir-Browsing, Web-Http-Errors, Web-Static-Content, Web-Health, Web-Http-Logging, Web-Log-Libraries, Web-Request-Monitor, Web-Performance, Web-Stat-Compression, Web-Security, Web-Filtering, Web-Windows-Auth, Web-App-Dev, Web-Net-Ext45, Web-Asp-Net45, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Mgmt-Tools, Web-Mgmt-Console, Web-Mgmt-Compat, Web-Metabase, NET-Framework-45-Features, NET-Framework-45-Core, NET-Framework-45-ASPNET, NET-WCF-Services45, NET-WCF-HTTP-Activation45, NET-WCF-TCP-PortSharing45, WAS, WAS-Process-Model, WAS-Config-APIs -restart

                   

    2. On Server “Web01” start “PowerShell” command line utility as administrator to install the NET components that are needed for the web-console. I ran the following command:

      Add-WindowsFeature NET-WCF-HTTP-Activation45

      Web02

    3. Check of the "Report Viewer" and the "Microsoft System CLR Types for SQL Server 2014" are installed
    4. On server “WEB01” start the “Internet Information Services (IIS) Manager” console and expand “WEB01 (ms-opsmgr\administrator)”, “Sites” and click “Default Web Site

      IIS01

    5. On server “WEB01” in the “Internet Information Services (IIS) Manager” select the “Default Web Site” and from the “Actions” pane click “Bindings
    6. On server “WEB01” on the “Bindings” screen click “Add
    7. On server “WEB01” on the “Add Site Bindings” screen change type to “https” and select certificate you imported. When finished click “OK” The result should look something like this:

      IIS02

    8. On server “WEB01” on the “Bindings” screen click “Close
    9. On server “WEB01” in the “Internet Information Services (IIS) Manager” select the “Default Web Site”  and double click the “SSL Setting” and check “Require SSL” and click “Apply” 
      IIS03

    10. On server “WEB01” start the “Setup.exe
    11. In the “Operations Manager” Screen click “Install

      Web03

    12. On the “Operations Manager Setup” page in the “Select Features to Install” section select “Web Console” and click “Next

      Web04

    13. On the “Operations Manager Setup” page in the “Select Installation Location” section click “Next

      Web05 

    14. On the “Operations Manager Setup” page in the “Proceed whit Setup” section click “Next

      Web06

    15. On the “Operations Manager Setup” page in the “Read License Term” section select “I have read, understood and agree whit the license terms” and click “Next

      Web07

    16. On the “Operations Manager Setup” page, in the “Specify a management Server” section enter a management server that will be used for the web console and reporting features only I entered my first management server “ms01.ms-opsmgr.eu” and click “Next

      Web08

    17. On the “Operations Manager Setup” page, in the “Specify a website for use whit the web console” section check “Enable SSL” and click “Next 
      Web09
    18. On the “Operations Manager Setup” page, in the “Select an authentication mode for use whit the web console” section select “Use Mixed Authentication (Forms Authentication)” and click “Next

      Web10

    19. On the “Operations Manager Setup” page, in the “Diagnostic and Control” section click “Next

      Web11

    20. On the “Operations Manager Setup” page, in the “Microsoft Update” section select “Off” and click “Next

      Web12 

    21. On the “Operations Manager Setup” page, in the “Installation Summary” section click “Install

      Web13

    22. On the “Operations Manager Setup” page, in the “Completed” section click “Close

      Web14blis

    Now that the System Center Operations Manager Web Console is installed its time to publish the web console using the Web Applications Proxy.

    1. On the "WAP01" server, start the “Remote Access Management Console
    2. On the “WAP01” server from the “Remote Access Management Console” from the “Task” pane click “Publish

      wap19

    3. On the “Publish New Application Wizard” screen in the “Welcome” section click “Next

      wap20

    4. On the “Publish New Application Wizard” screen in het “Preauthentication” section click “Pass-Through” and click “Next

      wap21

    5. On the “Publish New Application wizard” screen in the “Publishing Settings” enter the following settings and click “Next

      • Name: "Web01"
      • External URL: "https://web01.ms-opsmgr.eu/"
      • External Certificate: "Select the certificate you installed on de Web Application"
      • Check "Enable Http to Https redirection"

      The result should look something like this:

      wap22

    6. On the “Publish New Application wizard” screen in the “Confirmation” section click “Publish

      wap23

    7. On the “Publish New Application Wizard” screen in the “Results” section click “Close” 

    Now that the Web Application Proxy publishing rule is created we can test it using internet explorer. When we browse “https://web01.ms-opsmgr.eu/operationsmanager” you should a get an authentications challenge. When you login using your admin credentials  the result should look something like this:

    webconsolefinished

     

    This concludes Part 4 on Installing System Center Operations Manager. In the next part we are going to install and configure System Center Reporting Services.

    SCOM 2016 – Install System Center Operations Manager 2016 – Part 3

    Standard

    In this series off blog post I am going to take you true the steps I took to install System Center Operations Manager 2016. The Environment will be installed using the following software:

    • Microsoft Windows Server 2016 – Download from here
    • Microsoft SQL Server 2016 – Download from here
    • System Center Operations Manager 2016 – Download from here

    My Test environment consist of the following servers,

    • DC01 – Domain Controller
    • SQL01 – Microsoft SQL 2016 server
    • DATA01 – Data Server
    • MS01 – Scom Management Server 01
    • MS02 – Scom Management Server 02
    • WEB01 – Scom Web Console Server,

    Here you can find the previous blogposts

    In this part we are going to install the second Management Server and the System Center operations Manager Console.

    First we are going to install the System Center Operations Manager Console. The System Center Operations Manager Console will be installed on Windows 10 domain joined machine. Before we can install the System Center Operations Manger console we need to install Report Viewer Controls. These can be download from here. I am using a Group Policy to deploy the Report Viewer Controls.

    1. Start the "Group Policy Management" console
    2. Right click on the Group Policy Object that is applied to all the workstation that you want to deploy the Report Viewer and click “Edit
      CreateGPO01
    3. In the “Group Policy Management Editor” navigate to “Computer Configuration – Policies – Software Settings – Software installation” then right click on “Software installation” then click on “New” then “Packages
      CreateGPO02
    4. Navigate to the path that you placed the installation files and select “Reportviewer.msi” then click “Open
    5. On the “Deployment Screen” select “Advanced” and click “OK
      CreateGPO03
    6. On the “Microsoft Report Viewer 2015 Runtime Properties” page, click “OK
      CreateGPO04
    7. Restart the client computer that is available in the Organizational Unit that you want to use. The result should look something like this:
      CreateGPO05
    8. On the “Windows Client” where you want to install the “System Center Operations Manager Console” click “Setup.exe
    9. On the “Operations Manager” screen click “Install
    10. On the “Operations Manager Setup” page, in the section“Select feature to Install” select “Operations Manager Console” and click “Next
      ConsoleInstall01
    11. On the “Operations Manager Setup” page, in the section “Select installation location” click “Next
      ConsoleInstall02
    12. On the “Operations Manager Setup” page, in the section “Proceed with Setup” screen click “Next
      ConsoleInstall03
    13. On the “Operations Manager Setup” page, in the section “Proceed read the license terms” Screen check “I have read, understood and agree with the license term” and click “Next
      ConsoleInstall04
    14. On the “Operations Manager Setup” page, in the section “Diagnostic and usage Data” screen click “Next
      ConsoleInstall05
    15. On the “Operations Manager Setup” page, in the section “Microsoft Update” screen select “Off” and click “Next
      ConsoleInstall06
    16. On the “Operations Manager Setup” page, in the section “Installation Summary” screen click “Install
      ConsoleInstall07
    17. On the “Operations Manager Setup” page, in the section “Setup is Complete” click “Close
      ConsoleInstall08
    18. The end result should look something like this
      ConsoleInstall09

    Now we are going to install the second management server. On the server is Windows Server 2016 Core edition installed.  I used the following script to install the management server:

    First we need to install the AuthManager for Windows Server 2016 using PowerShell:

    InstallMS01

    Next we can run the following command:

    When you start the “System Center Operations Manager” Console and you to “Administration” and expand “Device Management”, “Management Servers” you should see two Management servers.

    InstallMS02

    This completes the third part of these series. In the fourth part we are going to install the web-console.

    Big thanks’ to Tao Yang and Florent Appointaire for there information on there blogs on how to install System Center Operations Manager 2016 on Windows Server Core 2016

    SCOM 2016 – Install System Center Operations Manager 2016 – Part 2

    Standard

    In this series off blog post I am going to take you true the steps I took to install System Center Operations Manager 2016. The Environment will be installed using the following software:

    • Microsoft Windows Server 2016 – Download from here
    • Microsoft SQL Server 2016 – Download from here
    • System Center Operations Manager 2016 – Download from here

    My Test environment consist of the following servers,

    • DC01 – Domain Controller 
    • SQL01 – Microsoft SQL 2016 server
    • DATA01 – Data Server
    • MS01 – Scom Management Server 01
    • MS02 – Scom Management Server 02
    • WEB01 – Scom Web Console Server,

    Here you can find the previous blogposts

    Before we can deploy System Center Operations Manager 2016 we need to create the Service accounts.

    Domain\Account Description
    ms-opsmgr\Srv-OpsmgrAction Unless an action has been associated with a Run As profile, the credentials that are used to perform the action will be those defined for the action account
    ms-opsmgr\Srv-OpsmgrDataAccess The System Center Configuration service and System Center Data Access service account is used by the System Center Data Access and System Center Management Configuration services to update information in the Operational database. The credentials used for the action account will be assigned to the sdk_user role in the Operational database.
    ms-opsmgr\Srv-OpsmgrSqlRead The Data Reader account is used to deploy reports, define what user the SQL Server Reporting Services uses to execute queries against the Reporting data warehouse, and define the SQL Reporting Services account to connect to the management server.
    ms-opsmgr\Srv-OpsmgrSqlWrite The Data Warehouse Write account is the account used to write data from the management server to the Reporting data warehouse, and it reads data from the Operations Manager database

    I also created a security group “SG – Opsmgr Administrators” where the user “Srv-OpsmgrDataAccess” and “Srv-OpsmgrAction” is added. I used the following script to create the accounts.

    You can find it here

    The next step that we need to make the group “SG – Opsmgr Administrators” local administrator on the two management Servers named “MS01” and “MS02” I am going to do this using Group Policy’s

    1. Start the “Group Policy Management Console
    2. On the Organization Unit where you moved the Management Server to right click “Create a GPO in this domain, and link it here

      InstallMSPrereq01

    3. In the “New GPO” windows enter the name that you want to give the GPO. I named mine “Default Opsmgr Policy
    4. Right click on the “GPO” and click “Edit

      InstallMSPrereq02

    5. In the “Group Policy Management Editor” browse tot the following location “<Gpo Name>\Computer Configuration\Policies\Windows Settings\Security Settings\Restricted Groups

      InstallMSPrereq03

    6. In the “Group Policy Management Editor” select “Restricted Groups”. Right click on “Restricted Groups” and click “Add Group

      InstallMSPrereq04

    7. On the “Add Group” page. browse to the above create group. In my case “SG – Opsmgr Administrators” and click “Ok

      InstallMSPrereq05

    8. In the “Ms-opsmgr\SG – Opsmgr Administrators properties” screen in the “This group is member is off” click “Add” and add a Local “Administrators” group. and click “Ok

      InstallMSPrereq06

    9. Close the “Group Policy Management Editor
    10. On the clients “MS01” and “MS02” run the command “Gpupdate /force” and restart the Computer. The result should look something like this:

      InstallMSPrereq07

    Now that al prerequisites are installed it’s time to install the first management Server.

    1. Log in to the first management server "MS01" that is member of the "SG – Opsmgr Administrators"
    2. Run "Setup.exe"
    3. On the “Operations Manager” screen click “Install

      ScomInstallMS01-1

    4. On the “Operations Manager” screen, in the “Select features to install” section select “Management Server” and click “NextScomInstallMS01-2
    5. On the “Operations Manager” screen, in the “Select Installation location” section click “Next

      ScomInstallMS01-3

    6. On the “Operations Manager” screen, in the “Proceed with setup” section click “Next

      ScomInstallMS01-5

    7. On the “Operations Manager” screen, in the “Specify an installation option” section, select “Create a first management server in a new management group” and enter “Management group name” in my case I entered “Ms-opsmgr” and click “Next

      ScomInstallMS01-6

    8. On the “Operations Manager” screen, in the “Please read the license term” section, check the “I have read, understood, and agree with the license terms” and click “Next

      ScomInstallMS01-7

    9. On the “Operations Manager” screen, in the “Configure the Operational Database” enter the “Server Name and Instance” press “Tab”. When the connection is made click “Next

      ScomInstallMS01-8

    10. On the “Operations Manager” screen, in the “configure the data warehouse database” section enter the “Server name and instance name” and click “Next

      ScomInstallMS01-9 

    11. On the “Operations Manager” screen, in the “Configure Operations Manager Accounts” section enter the accounts that you created above and click “Next”. The result should look something like this: 
      ScomInstallMS01-10
    12. On the “Operations Manager” screen, in the “Diagnostic and Usage data” section click “Next

      ScomInstallMS01-11

    13. On the “Operations Manager Setup” screen, in the “Windows Update” section, check “Off” and click “Next

      ScomInstallMS01-12

    14. On the “Operations Manager Setup” screen, on the “Installation Summary” section click “Install

      ScomInstallMS01-13

    15. On the “Operations Manager Setup” screen, on the “Setup complete” screen click “Close

      ScomInstallMS01-14 

    When finished installing Systeem Center Operations Manager 2016 om MS01 its time to enter the License key. This is done by taking the following steps:

    1. Start the "Operations Manager Shell" as "Administrator"
    2. Type the following command and press "Enter":

    In the Next Part we are going to install the second management server and the console.

    Update MP: System Center Management Pack for SQL Server and Dashboards

    Standard

    On 10-October-2016 Microsoft released update for the System Center Management Pack for SQL Server and Dashboards. The version is updated to 6.7.7.0

    • Microsoft System Center Management Pack for SQL Server 2016 The features and fixes that are included in this update:
      • Feature: Updated the visualization library
      • Fix: "Set DB offline" task does not work when the database is in Availability Group
      • Fix: Always On console task does not work
    • Microsoft System Center Management Pack for SQL Server 2014 Feature overview is the same as above
    • Microsoft System Center Management Pack for SQL Server The features and fixes that are included in this update:
      • Fix: SQL Server 2012 Always On discoveries fail after stopping WSFC service
      • Fix: “Set DB offline” task does not work when the database is in Availability Group
      • Fix: user policy discovery script fails with “Invalid namespace "ROOT\Microsoft\SqlServer\ComputerManagement12"’ error
      • Fix: Always On console task does not work
      • Feature:Updated the visualization library
    • Microsoft System Center Management Pack for SQL Server Dashboards The features and fixes that are included in this update:
      • Feature: Restored the correct group order in SQL Server Summary dashboard views
      • Fix: expanding “arrow” has low-contrast color when a health group is collapsed in Instance view (High-Contrast #2 color scheme)
      • Fix: In Web console, Dashboards continuously send requests to the database
      • Fix: not the first object gets selected in the object list after drill-down
      • Fix: on Web console, Dashboards crash when drilling down from Datacenter view to Instance view
      • Fix: horizontal scroll position resets after refreshing the Instance view
      • Fix: “No Data” message is displayed on some tiles after upgrading Dashboards management pack from version 6.7.2.0 to 6.7.4.0 or later version
      • Fix: on Web console, Dashboards crash when drilling down from Datacenter view to Instance view

    Before installing in the updates in your production environment make sure that you test these updates in your test environment.

    Building a Management pack using VSAE Part 1.

    Standard

    In this blog post I’m going to take you thru the steps I took to build a management pack using Microsoft Visual Studio Community 2015 in combination whit the Visual Studio Authoring Extensions.

    You can download the Visual Studio Community 2015 from here. The Visual Studio Authoring Extensions can be downloaded from here

    The application I am going to monitor is Commvault Simpana Version 10 r2. Commvault Simpana is backup application which I use for backing up my environment. More information on Commvault Simpana can be found here.

    The application is consist of the following components:

    • CommServe: This component creates the SQL Database that communicates whit all clients and coordinates all operations whit in the CommCell   environments, such as backups, restores, copies and media management operations. Along whit the CommServe software, the following components are automatically installed.
      • CommCell Console: The console is a graphical user interface that allows you to control and manage CommCell operations.
      • Files System: The File system component enables the back-up and restore of files and folders residing on the CommServe computer.
      • Web Server and Web Console:  if the Internet Information Services (IIS) is enabled on the computer, the Web Server component is installed along whit the Web Console Component. The Web Console is a web based application that allows end-users manage their data.
      • Workflow:  Tool that allows you to automate business processes by putting together a set of tasks in a specific order.
    • MediaAgent: This component manages the transmission of data between clients and backup media. Install the MediaAgent component on a Windows or UNIX computer that is configured with the backup media. The backup media is a storage device where you want to store your backed up data.
    • Agent: The Simpana software provides a range of installable components that support the type of data that you want to protect. These components are referred to as agents.

    Now that the we know how the application works its time to create a service model for the application. My service model look something like this:

    CommVaultSimpanaManagementPackBasicComponent

    Creating the Management Pack

    1. Start the “Visual Studio 2015
    2. In the “Microsoft Visual Studio” console in the “Menu” click “File”,”New” and click “Project
      Microsoft Visual Studio - File - New - Project
    3. In the “New Project” console, expand “templates”, “Management Pack”, “Operations Manager”. From the middle click “Operations Manager 2007 r2 Management Pack”. Enter the following data:
      • "Name:" Simpana.CommVault
      • "Location:" D:\Management Pack\Simpana CommVault\
      • "Solution Name" Simpana.CommVault

      Visual Studio - New ProjectClick “Ok” to create the management pack.

    4. In the “Microsoft Visual Studio” console in the “Solution Explorer” right click “Simpana.CommVault” and click “Properties
      Visual Studio - Solution Explorer - Properties
    5. In the “Microsoft Visual Studio” console, on the “Simpana.CommVault” tab click “Build” and select “Generate sealed and Signed Management Pack” Insert the following:
      • "Company Name:" Ms-opsmgr.eu
      • "Copyright:" Copyright (c) Ms-opsmgr.eu. All rights reserved.
      • "Key File:" Simpana.CommVault.snk. If you don’t know how to create a Key File for signing and sealing a management pack take a look at the following blogpost

      Visual Studio - Simpana.Commvault Properties - Build

    6. In the “Microsoft Visual Studio” Console, on the “Simpana.CommVault” tab click “Management Group”, click “Add
    7. In the “Add Management Server….” wizard, enter the “Server Name” and click “Add Server
    8. In the “Microsoft Visual Studio” Console, on the “Simpana.CommVault” tab the result should look something like this:
      Visual Studio - Simpana.CommVault - Management Group
    9. In the “Microsoft Visual Studio” console, on the “Simpana.CommVault” tab click “Deployment”. In the “Start action” select “Deploy projects to default management group only
      Visual Studio - Simpana.CommVault - Deployment
    10. In the “Microsoft Visual Studio” console, in the “Menu” click “File”, “Save

    Create a Management Pack Fragment

    In this part we are going to create a management pack fragment to give the management pack a friendly name and description when we look in the administration of System Center Operations Manager

    1. In the “Microsoft Visual Studio” console, in the “Solution Explorer” right click “Simpana.CommVault” and click “Add”, “New Item
      VisualStudioNewFragment1
    2. In the “Add New Item – Simpana.Commvault” wizard select “Empty Management Pack Fragment” Enter the following data and click “Add
      • "Name:" Simpana.CommVault.Project

      VisualStudioNewFragment2

    3. In the “Microsoft Visual Studio” console, on the “Simpana.CommVault.Project.mpx” tab enter the following code:
    4. In the “Microsoft Visual Studio” console, in the “Menu” click “File”, “Save
    5. In the “Microsoft Visual Studio” console, in the “Menu” click “Build”, “Build Solution

      Visual Studio - Build - Build Solution

    6. In the “Microsoft Visual Studio” console, on the “Standard” menu bar click “Start” to deploy the management pack.

      Visual Studio - Deploy

    7. Start the “System Center Operations Manager” console click “Administration” and click “Management Pack” and the result should look something like this:

      VisualStudioNewFragment5

    Create the Classes whit the base class Windows Computer Roles.

    In this part we are going to create the classes that are based on the Windows Computer Role Class. The following classes are going to be created:

    • Abstract Class: CommServe
      • CommCell Console
      • File System
      • Workflow
    • Abstract Class: Media Agents
      • Agent Exchange
      • Agent SharePoint
      • Agent SQL
      • Agent File System

    Schematic it will look something like this:

    Classes Based On Windows Computer Role

    1. In the “Microsoft Visual Studio” console, in the “Solution Explorer” right click “Simpana.CommVault” and click “Add”, “New Folder

      Visual Studio - Create New Folder

    2. In the “Microsoft Visual Studio” console. in the “Solution Explorer” name the new Folder “Service Model
    3. In the “Microsoft Visual Studio” console, in the “Solution Explorer” on the folder “Service Model” Right click the folder and click “Add”, “New Folder

      VisualStudioNewFolder2

    4. In the “Microsoft Visual Studio” console, in the “Solution Explorer” name the new folder “Classes
    5. In the “Microsoft Visual Studio” console, in the “Solution Explorer” on the folder “Classes”, right click the folder and click “Add”, “New Item
    6. In the “Microsoft Visual Studio” console, in the “Add New Item – Simpana.Commvault” screen select “Class”. Enter the following data and click “Add”:
      • "Name:" ComputerRoles.mpx

      Visual Studio - Create Class - ComputerRoles.mpx

    7. In the “Microsoft Visual Studio” console, on the “ComputerRoles.mpx” tab enter the following code:

    8. In the “Microsoft Visual Studio” console, in the “Solution Explorer” on the folder “Classes”, right click the folder and click “Add”, “New Item
    9. In the “Microsoft Visual Studio” console, in the “Add New Item – Simpana.Commvault” screen select “Class”. Enter the following data and click “Add”:
      • "Name:" Commserve.mpx

      Visual Studio - Create Class - CommServe.mpx

    10. In the “Microsoft Visual Studio” console, on the “CommServe.mpx” tab enter the following code:

    11. In the “Microsoft Visual Studio” console, in the “Solution Explorer” on the folder “Classes”, right click the folder and click “Add”, “New Item
    12. In the “Microsoft Visual Studio” console, in the “Add New Item – Simpana.Commvault” screen select “Class”. Enter the following data and click “Add”:
      • "Name:" MediaAgent.mpx
    13. In the “Microsoft Visual Studio” console, on the “MediaAgent.mpx” tab enter the following code:

    14. In the “Microsoft Visual Studio” console, in the “Menu” click “File”, “Save
    15. In the “Microsoft Visual Studio” console, in the “Menu” click “Build”, “Build Solution
    16. Start the “System Center Operations Manager” console click “Monitoring” and select “Discovered Inventory” and from the “Tasks” pane click “Change Target Type

      Operations Manager Console - Change Target Type

    17. In the “Select Items to target” screen, select “View all targerts” and in the “Look for” bar enter “Simpana”. The result should look something like this: 
      Select Items to Target - Simpana Commvault

    Create the Rollups to create a Health service Rollup

    In this part we are going to create the classes that are used to create the health service rollup and create the containment relations between the rollups. The following rollups are created: 
    CommVault Simpana - Containments

    1. In the “Microsoft Visual Studio” console, in the “Solution Explorer” on the folder “Classes”, right click the folder and click “Add”, “New Item
    2. In the “Microsoft Visual Studio” console, in the “Add New Item – Simpana.Commvault” screen select “Class”. Enter the following data and click “Add”:
      • "Name:" Rollups.mpx

      VisualStudio - Rollups.mpx

    3. In the “Microsoft Visual Studio” console, on the “Rollups.mpx” tab enter the following code:

    4. In the “Microsoft Visual Studio” console, in the “Solution Explorer” on the folder “Classes”, right click the folder and click “Add”, “New Item
    5. In the “Microsoft Visual Studio” console, in the “Add New Item – Simpana.Commvault” screen select “Relationship”. Enter the following data and click “Add”:
      • "Name:" Containments.mpx

      VisualStudioContainments1

    6. In the “Microsoft Visual Studio” console, on the “Containments.mpx” tab enter the following code:

    Create the Dependencies relationships

    In this part we are going to create the depend relationships for webserver and Web console and SQL Server. The following rollups are created:

    CommVault Simpana - Dependecies

    1. In the “Microsoft Visual Studio” console, in the “Solution Explorer” Right click “References” and click “Add Reference

      Visual Studio - Add Reference

    2. In the “Add Reference” screen, click on the “Browse” tab and go to the “C:\Program Files (x86)\System Center Visual Studio Authoring Extensions\References\OM2007R2” select “Microsoft.SystemCenter.InstanceGroup.Library.mp” and click “Ok

      VisualStudio - Add Reference

    3. In the “Microsoft Visual Studio” console, in the “Solution Explorer” select “Microsoft.SystemCenter.InstanceGroup.Library.mp” and in the properties screen change  the “Alias” to “InstanceGroup

      VisualStudio -Change Alias

    4. Repeat step 2 and 3 for the “Microsoft.SQLServer.Library.mp” and change the “Alias” to “SQL
    5. Repeat step 2 and 3 for the “Microsoft.Windows.InternetInformationServices.2012.mp” and change the “Alias” to “IIS2012r2
    6. In the “Microsoft Visual Studio” console, in the “Solution Explorer” on the folder “Classes”, right click the folder and click “Add”, “New Item
    7. In the “Microsoft Visual Studio” console, in the “Add New Item – Simpana.Commvault” screen select “Relationship”. Enter the following data and click “Add”:
      • "Name:" Dependecies.mpx

      Visual Studio - Dependecies

    8. In the “Microsoft Visual Studio” console, on the “Dependecies.mpx” tab enter the following code:

            

    9. In the “Microsoft Visual Studio” console, in the “Menu” click “File”, “Save
    10. In the “Microsoft Visual Studio” console, in the “Menu” click “Build”, “Build Solution

    This concludes the first part of building a management pack using Visual studio authoring extensions. If you want to learn more I advise you to follow the training from Brain Wren on the Microsoft Virtual Academy

    Install and Configure System Center Management Pack for SharePoint Server 2013

    Standard

    In this post I’m going to take you true the steps I took to install and configure the system center management pack for SharePoint server 2013. Before installing the system center management pack for SharePoint server 2013 let’s take a look ad the environment that I want to monitor

    • 2 SharePoint Web Front-End servers
    • 1 SharePoint Application server
    • 2 Microsoft SQL 2012 server

    You can download the system center management pack for SharePoint server 2013 from here

    Before you start installing the system center management pack for SharePoint 2013 make you sure you have installed and configured the following management pack’s:

    • System Center Management Pack for Windows Server Operating System which can be downloaded from here
    • Microsoft System Center Management Pack for SQL Server which can be downloaded from here
    • System Center 2012 Management Pack for Microsoft Windows Server 2012 Internet Information Service 8 which can be downloaded from here

    I took the following steps

    1. Install the system center management pack for SharePoint 2013
    2. Import the system center management pack for SharePoint 2013
    3. Copy the configuration file
    4. Create a Run-As account
    5. Give the Run-As account full access to the SQL Servers 
    6. Give the Run-As account farm admin rights to your SharePoint environment
    7. Configure the SharePoint config file
    8. Configure the SharePoint management pack

    1. Install the system center management pack for SharePoint 2013

    1. Click "Microsoft.Sharepoint.Server.ManagementPacks.msi"
    2. In the “Microsoft.SharePoint.Server.ManagementPacks – installer” wizard, on the “License Agreement” page, select “I accept” and click “Next
      Install SharePoint Server Management Pack
    3. In the “Microsoft.SharePoint.Server.ManagementPacks – installer” wizard, on the “Select Installation Folder” page, select “Everyone” and click “Next
      Install SharePoint Server Management Pack
    4. In the “Microsoft.SharePoint.Server.ManagementPacks – installer” wizard, on the “Confirm Installation” page, click “Install
      Install SharePoint Server Management Pack
    5. In the “Microsoft.SharePoint.Server.ManagementPacks – installer” wizard, on the “Installation Complete” page, click “Close
      InstallSharePointMP4

    2. Import the system center management pack for SharePoint 2013

    1. Start the "Operations Manager Console"
    2. In the “Operations Manager Console” click “Administration
    3. Right click “Management Packs”, and the click “Import Management Packs
      Import Management Packs
    4. The “Import Management pack wizard” opens. Click “Add”, and the click “Add from Disk
      Import Management Packs
    5. The Select Management Packs to import dialog box appears. If necessary, change to the directory that holds your management pack file. Select the following files:
      • Microsoft.SharePoint.Foundation.Library.mp
      • Microsoft.SharePoint.Foundation.2013.Discovery.mp
      • Microsoft.SharePoint.Foundation.2013.Monitoring.mp
      • Microsoft.SharePoint.Server.Library.mp
      • Microsoft.SharePoint.Server.2013.Discovery.mp
      • Microsoft.SharePoint.Server.2013.Monitoring.mp
        Import Management Packs
    6. In the “Import Management Pack” wizard, Click “Install
    7. In the “Import Management Pack” wizard, Click “Close

    3. Copy the configuration file

    1. Make a RDP connection to your “Management Server
    2. From the directory “C:\Program Files (x86)\System Center Management Packs\Microsoft.Sharepoint.Server.ManagementPacks” copy the file “microsoft.sharepoint.foundation.library.mp” with the type config to the directory “C:\Program Files\System Center Management Packs

    4. Create a Run-As accounts

    1. Start the “Operations Manager Console
    2. In the "Administration" Workspace, in the Navigation pane, expand "Run As Configuration", right click "Accounts" and click "Create Run As Account"

      Create Run As Account

    3. In the “Create Run As Account Wizard”, on the “Introduction” page, click “Next
    4. In the “Create Run As Account Wizard”, on the “General Properties” page enter the following “Display Name” “SharePoint Discovery/Monitoring Account” and click “NextCreate Run As Account
    5. In the “Create Run As Account Wizard”, on the “Credentials” page enter the “Username”, “Password”, “Confirm password”, “Domain” and click “Next
      Create Run As Account
    6. In the “Create Run As Account Wizard”, on the “Distribution Security” page, select “More Secure” and click “Create
      Create Run As Account
    7. In the “Create Run As Account Wizard”, on the “Completion” page, click “Close
    8. Right click on the “SharePoint Discovery/Monitoring Account” and click “Properties
      Create Run As Account
    9. On the “Run As Account Properties – SharePoint Discovery/Monitoring Account” page open the tab “Distribution
      Create Run As Account
    10. On the “Run As Account Properties – SharePoint Discovery/ Monitoring Account” page on the “Distribution” tab, click  “Add”  to add all the SharePoint farm computers.
      Create Run As Account
    11. On the “Run As Account Properties – SharePoint Discovery/Monitoring Account” page, on the “Distribution” tab click “Apply” and the “OK

    5. Give the Run-AS accounts full access to the SQL Servers 

    1. Make a RDP connection to your “SQL Server” hosting your SharePoint databases
    2. Start the “Server Manager
    3. In the “Server Manager” in the tools menu click “Computer Management
      SQL Computer Management Local User
    4. On the “Computer Management” page, expand “Local Users and Groups” and click “Groups
    5. On the “Computer Management” page, open the “Administrators” group
      SQL Computer Management Local User
    6. On the “Administrators Properties” page click “Add” and add the user you used to create your Run As account.
    7. On the “Administrators Properties” page click “Apply” and click “OK
    8. On the SQL server start the “Microsoft SQL Server Management Studio
      SQL Full Access Database
    9. In the “Connect tot server” page enter the “Server name” your “Authentication” and click “Connect
    10. In the “Object Explorer” expand “Security”, and right click “Logins” and click “New Login
      SQL Full Access Database
    11. On the “New Login” page, on the “General” page add the above created account
      SQL Full Access Database
    12. On the “New Login” page, on the “Server Roles” page, select “Sysadmin” and click “Ok
      SQLFullAccess6
    13. Repeat the above steps on all your SQL Servers.

    6. Give the Run-As account farm admin rights to your SharePoint environment

    I am not a SharePoint  administrator so I contacted my SharePoint Administrator to give the monitoring account farm admin right to the SharePoint farm.

    7. Configure the SharePoint config file

    1. Open the “microsoft.sharepoint.foundation.library.mp.config” SharePoint configuration file from the following location: “C:\Program Files\System Center Management Packs
    2. In edit the following rule:
      <Association Account="SharePoint Discovery/Monitoring Account" Type="Agent">
          <Machine Name="" />
      </Association>
    3. add a “Machine Name” line for each server in your farm. I have 5 servers that are in my farm so my Config file looks something like this:
      <association type="Agent" account="SharePoint Discovery/Monitoring Account">
          <machine name="web01.ms-opsmgr.eu" />
          <machine name="web02.ms-opsmgr.eu" />
          <machine name="sql01.ms-opsmgr.eu" />
          <machine name="sql02.ms-opsmgr.eu" />
          <machine name="app01.ms-opsmgr.eu" />
      </association>
    4. Save and close the configuration file

    8. Configure the SharePoint management pack

    1. Start the “Operations Manager Console
    2. In the “Monitoring” workspace expand “”Microsoft SharePoint” and select “Administration” and from the administration pane select “Microsoft SharePoint Farm Group

      SharePoint Configuration

    3. From the “Tasks” pane, click “Configure SharePoint Management Pack

      Sharepoint Configuration

    4. On the “Run Task – Configure SharePoint Management Pack” click “Run

      SharePoint Configuration

    5. The result should look something like this:

      Sharepoint Configuration

      When everything is finished the result should look something like this.

      Finished

      When you want more information of installing and configuring the SharePoint Management pack please take a look at:

      Update MP: Microsoft Exchange Server 2013 Management Pack

      Standard

      On 28-April-2015 Microsoft released update for the Microsoft Exchange Server 2013 Management Pack. The version is updated to 15.0.066.20

      • Microsoft Exchange Server 2013 Management Pack The features and fixes that are included in this update:
        • Fix: preventing Exchange 2013 Mailbox Properties collection when the contents of Email Addresses field exceed the total length of more than 1024 characters.
        • Fix: alerts generated by the previous version of the Management Pack for Exchange Server 2013 have unreadable name. After upgrading of the Management Pack to version 15.0.620.19, alerts generated before the upgrade had the following name: {2}

      Before installing in the updates in your production environment make sure that you test these updates in your test environment.

      Log File MP webinar with MVP – Kevin Greene

      Standard

      This live demo session will be focused on illustrating how you can use the NiCE Log File Management Pack to effectively monitor your log files in SCOM. You will leave the session with a clear understanding of how the solution can help you in your own environment + pick up a few tips & tricks that you may not already know if you are already using the solution.

      logfileWebinar

      Kevin Greene will run through some real-life scenarios in the session to illustrate how to work with the solution to solve problems, and NiCE Product Director, Christian Heitkamp will give you a sneak preview on a future product release.

      Webinar agenda and take outs

      • Learn new best-practices on how our customer use the NiCE Log File MP
      • Popular use cases explained and demonstrated by MVP Kevin Greene
      • Download of the free solution + free examples after Webinar
      • Sneak preview of new features and road map
      • Chance to ask NiCE experts questions

      To find out more about this insightful NiCE Webinar, sign-up today!

      Webinar date: Thursday April 21st, 2016

      Webinar Location: Microsoft ‘Skype for Business’ – Online Webinar (invitation to be sent upon registration)

      Webinar Time:

      16:00-16:45 – Central Europe Time Zone

      10:00-10:45 – North American Eastern Time Zone

      14:00-14:45 –  UTC/GMT