In this blog post, I'll discuss on how to update the alert custom fields based on the extended windows computer class properties.

Please refer below blog for the steps to create the command line notification to run PowerShell script.

https://blogs.msdn.com/b/steverac/archive/2010/08/17/updating-custom-alert-fields-using-subscriptions-and-powershell.aspx

I wrote small PowerShell script for our scenario from previous blog link, you can use this script along with the steps mentioned in above blog.

Param(

[parameter(mandatory=$true)][GUID] $alertID

)

Import-Module OperationsManager;

$alertID = $alertID.toString();

$newAlert = Get-SCOMAlert -Criteria "Id = '$alertID'";

$srv= $newAlert.PrincipalName;

$class = Get-SCOMClass -Name 'ExtendedWindowsComputer';

If (!$newAlert.CustomField1 -AND !$newAlert.CustomField2)

{

$objClass= Get-SCOMClassInstance -Class $class | Where-Object{$_.'[Microsoft.Windows.Computer].PrincipalName' -like "$srv"}

$app = ($objClass).'[ExtendedWindowsComputer].ServerType'

$srvType=($objClass).'[ExtendedWindowsComputer].Application'

$newAlert.CustomField1=$srvType;

$newAlert.CustomField2=$app;

$newAlert.Update("")

}

Note: Test this in your lab first and make necessary changes according to your environment.

Enjoy!

In this blog post, I will walk you through the steps to extend the windows computer class using Visual Studio Authoring Extension (VSAE).

Scenario : CONTOSO company has implemented SCOM 2012 R2 to monitor 1000+ servers and have many applications like SQL, Exchange, SharePoint and few third party applications. Every application has few development and few production servers. They have application teams who supports the application and needs to have access to the alerts    (different views for Dev. and Prod. Servers for every application). They don’t have any way to differentiate the servers between the production or development like by OU or by the Sites.

   Creating computer group is one of the option but if we create too many groups then it isn't a good option as a group is a singleton class hosted by the Management Servers, and Management Servers performs the group calculation for each group on a regular basis. 

Please refer the blog for more details on the groups https://blogs.technet.com/b/kevinholman/archive/2009/02/05/what-is-a-group-anyway.aspx

High level steps:

    A. Overview

    B. Extend the windows computer class and add two properties (ServerType & Application)

    C. Create the discovery to discover the values for the properties.

    D. Create the folder and views structure.

    E. Import Management Pack and verify.

A. Overview

1. Overview of VSAE

Link to download VSAE: https://www.microsoft.com/en-sg/download/details.aspx?id=30169

https://social.technet.microsoft.com/wiki/contents/articles/7562.visual-studio-authoring-extensions-visual-studio-features.aspx

https://social.technet.microsoft.com/wiki/contents/articles/5236.visual-studio-authoring-extensions-for-system-center-2012-operations-manager.aspx

2. Classed & Relationships:

Please refer this link for more details :

https://social.technet.microsoft.com/wiki/contents/articles/14256.operations-manager-management-pack-authoring-classes-and-relationships.aspx

3. Discovery:

Please refer this link for more details :

https://social.technet.microsoft.com/wiki/contents/articles/14260.operations-manager-management-pack-authoring-discovery.aspx

There are four types of discoveries.

  1. Registry :

           Accessing the registry on the local computer is a preferred method of discovery because of the small overhead required. The registry frequently contains lots of easy to access configuration information for many applications. A discovery can check whether a particular key or value exists, or it can collect the data from any value. Collected values may be either only collected for a property or compared to some known value to determine whether discovery data should be created.

  2. WMI :

           WMI can provide lots of information about a computer or Windows operating system components. It can also be the source of information for any application that includes a WMI provider exposing parts of the application through a WMI interface. A discovery can run a WMI query to determine whether instances of a particular WMI class exist and to collect the properties from any returned instances.

For example, a particular management pack might collect information from the computer BIOS, that can be obtained by using the WMI32_BIOS WMI class.

  3. Script :

         If a discovery requires data inaccessible from the registry or WMI, or if the discovery needs more complex logic than those discoveries provide, a discovery script must be used. A discovery script can be written in any language that can access the MOM.ScriptAPI COM object that is installed with the Operations Manager agent. The most typical scripts are written either in a language supported by Windows Script Host (VBScript or Jscript by default) or Windows PowerShell.

  4. WSMan :

          Used to access Unix/Linux resources.

Let's start with the authoring MP for our scenario using registry based discovery.

First, define the registry keys and path that we will use for the discovery.

B. Extend Windows Computer Class:

 1. To create a new management pack, you first have to create a new management pack project. A project is the Visual Studio term for the collection of code that will be compiled into a finished form – often an executable, but in this case, a management pack.

 2. From the Visual Studio Start Page, select the New Project… link, or click File → New → Project. The New Project dialog box appears.

 3. Select the correct management pack version. I'm authoring MP for SCOM 2012 R2 so I selected Operations Manager 2012 R2 Management Pack.

 4. Create the folders under the project. These folders are used for arranging code in more structured way.

 5. Right click on Project -> Add -> New Folder

6. Add MP fragment for the class.

    Right click on Classes folder -> Add -> New Item

   This will add the class syntax with the basic XML structure.

 7. Make necessary changes to the class definition like ID, base, Accessibility etc.

 8. I'll use Microsoft.Windows.Computer class as a base and it is defined in the Microsoft.Windows.Library MP. 

  9. This will be part of default MPs added when we create the project. If you need to add mp reference here, then right click on the references -> Add reference … -> Browse and select the .mp file which you have downloaded.

 10. Remove the default base class added. Move the cursor between the double quotes (Base = "") and press Control + Space (use this to find the next element or value for the element)

11. Select Windows --> Microsoft.Windows --> Computer

 12. Now, add properties

13. Select property --> then press Space to get the next element.

14. Select ID and enter the value for ID element and press space

15. Select Key and set value to false

16. Class definition will look like this

 <ClassType ID="ExtendedWindowsComputerClass" Base="Windows!Microsoft.Windows.Computer" Accessibility="Public" Abstract="false" Hosted="false" Singleton="false">
    <Property ID="ServerType" Key="false" Type="string"/>
    <Property ID="Application" Key="false" Type="string"/>
</ClassType>

Both the properties have key="false" as we already have the key property in the class hierarchy.

You can check the key property for the class from the MP.

Run this query against the Operations Manager DB to get the mpxml

SELECT convert(xml,mpxml) FROM ManagementPack WHERE MPFriendlyName like '%Microsoft Windows Library%'

17. Define the Language Pack.

  <DisplayStrings>   

        <!-- This is the string users of the Operations Console and Web Console will see. Descriptions are also helpful when the user is doing a search in the Console. -->

        <DisplayString ElementID="ExtendedWindowsComputerClass">

           <Name>Extended Windows Computer Class</Name>

           <Description>Windows Computer Class with additional properties</Description>

       </DisplayString>

         <!-- Uncomment the below section if you need to add a user friendly string for each property. -->

       <DisplayString ElementID="ExtendedWindowsComputerClass" SubElementID="ServerType">

          <Name>Server Type</Name>

          <Description></Description>

        </DisplayString>

        <DisplayString ElementID="ExtendedWindowsComputerClass" SubElementID="Application">

          <Name>Application</Name>

          <Description></Description>

        </DisplayString>

 </DisplayStrings>

C. Design Discovery:

Let's create the discovery to discover the values from registry.

Steps to create the Discovery:

1. Right click the name of the solution and select Add and then New Item. 
2. Select Discovery.
3. In the Name box, type Discoveries.mptg and click Add.

Configure the Discovery Properties:

1. Right click the entry for NewDiscovery and select Properties Window.
2. Change the ID to Discovery.ExtendedWindowsComputer.
3. Change the Display Name to Discover Extended Windows Computer.

Select the Discovery Target:

1. Select Target and click the ellipse (...) button on the right of the field. 
2. Select Microsoft.Windows.Computer and click OK.

Discovery Targets : The target of a discovery determines where the discovery will run. Any agent managing an instance of the target class will run the discovery. In order to minimize overhead, the target for a discovery should represent the most specific class where the class being discovered may potentially be found.

Select and Configure the Discovery Data Source

      1. Select Data Source Type ID and click the ellipse (...) button on the right of the field. 

      2. Select Microsoft.Windows.FilteredRegistryDiscoveryProvider and click OK.

         The Microsoft.Windows.FilteredRegistryDiscoveryProvider module is a discovery data source module type that queries the Windows registry at a scheduled frequency and returns filtered results as System.Discovery.Data data.

         Usage : Use this module when you want to query the Windows registry inside a discovery workflow. This module supports retrieving any key or value from the HKEY_LOCAL_MACHINE hive of the registry only. For multi-string values, only the first string is returned. This module allows you to specify a filter on the returned registry data before it is mapped to discovery data.

      3. Select Data Source Configuration and click the ellipse (...) button on the right of the field.

      4. Type < and select the tag (ComputerName)

    5.Registry based discovery always starts with the computer name and value will be in the format

      $Target/Property[Type="Windows!Microsoft.Windows.Computer"]/PrincipalName$ -- $Target variable resolves to the computer name of the target agent.

      For authoring variables refer to this link https://social.technet.microsoft.com/wiki/contents/articles/15300.operations-manager-management-pack-authoring-variables.aspx

      For registry base discoveries this table is very important.

     6.The following code example of type RegistryAttributeDefinitions returns a registry value:

  <RegistryAttributeDefinition>

      <AttributeName>ServerType</AttributeName>

      <Path>SOFTWARE\CONTOSO\ServerType</Path>

      <PathType>1</PathType>

      <AttributeType>1</AttributeType>

    </RegistryAttributeDefinition>

   But if you need to check if registry key exists.

 <RegistryAttributeDefinition>
  <AttributeName>ApplicationExists</AttributeName>
  <Path>SOFTWARE\CONTOSO\ApplicationExists</Path>
  <PathType>0</PathType>
  <AttributeType>0</AttributeType>
</RegistryAttributeDefinition>

 7. Define the frequency, choose as per your environment requirement. For my test lab, I'm using 1800 secs.

  <Frequency>1800</Frequency>

  Note: This value is in seconds

 8. Define the class id

 <ClassId></ClassId>  This is the class id for the class which we are going to discover and syntax will be $MPElement[Name="Name of the Class"]$

 You can use the $MPElement variable when you need to retrieve the GUID of any Management Pack element or sub-element of a Management Pack element. Some elements, such as the Discovery element, have to distinguish between several objects that are instances of a class, and each instance of a discovered class is assigned a GUID.

 9. <InstanceSettings>

 This will populate the values for the properties and key property of the class or any of its parent in the hierarchy

 For each property format will be

 <Setting>

                <Name>$MPElement[Name="ExtendedWindowsComputerClass"]/ServerType$</Name>

                <Value>$Data/Values/ServerType$</Value>

</Setting>

 For registry based discoveries values collected will be always in the $Data/Values/NameOftheAttribute

 And if you are checking if key exists or not. We need to create the expression after the instance settings (This is not required for our scenario)

 This expression will start after the </InstanceSettings> tag

 For below example

 <RegistryAttributeDefinition>
  <AttributeName>ApplicationExists</AttributeName>
  <Path>SOFTWARE\CONTOSO\ApplicationExists</Path>
  <PathType>0</PathType>
  <AttributeType>0</AttributeType>
</RegistryAttributeDefinition>

 Expression will be

 <Expression>

    <SimpleExpression>

      <ValueExpression>Values/ApplicationExists</ValueExpression>

      <Operator>Equal</Operator>

      <ValueExpression>true</ValueExpression>

    </SimpleExpression>

  </Expression>

 In our scenario expression tag will be empty

 <Expression></Expression>

D. Create Views:

 For our scenario, I'll create the folder and view structure

 https://social.technet.microsoft.com/wiki/contents/articles/15310.operations-manager-management-pack-authoring-views.aspx

All Servers

  --> SQL Application

        PROD (Alert View)

        PROD (State View)

        Dev  (Alert View)

        Dev  (State View)

  --> VMM Application      

         PROD (Alert View)

         PROD (State View)

         Dev  (Alert View)

         Dev  (State View)

1.Right click on Views - > Add -> New item 

 <Folders>     

      <Folder ID="ExtendedWindowsComputerClass.AllServers" Accessibility="Public" ParentFolder="SC!Microsoft.SystemCenter.Monitoring.ViewFolder.Root" />

      <Folder ID="ExtendedWindowsComputerClass.AllServers.SQL" Accessibility="Public" ParentFolder="ExtendedWindowsComputerClass.AllServers" />

      <Folder ID="ExtendedWindowsComputerClass.AllServers.VMM" Accessibility="Public" ParentFolder="ExtendedWindowsComputerClass.AllServers" />

    </Folders>

2.Now let's create the views, right click on view folder and select property window

Display Name : SQL PROD State View

ID: State.SQLPROD

Target : ExtendedWindowsComputerClass

View Folder : ExtendedWindowsComputerClass.AllServers.SQL

View Type ID: Microsoft.SystemCenter.StateViewType

View Configuration:

Select PropertyCriteria

 <PropertyCriteria>

      <PropertyName>ServerType</PropertyName>

      <Value>PROD</Value>

    </PropertyCriteria>

    <PropertyCriteria>

      <PropertyName>Application</PropertyName>

      <Value>SQL</Value>

    </PropertyCriteria>

  </Criteria>

 Same way we can create all the other state views.

  For Alert view

        Display Name : SQL PROD State View

        ID: Alert.SQLPROD

        Target : ExtendedWindowsComputerClass

        View Folder : ExtendedWindowsComputerClass.AllServers.SQL

        View Type ID: Microsoft.SystemCenter.AlertViewType

  For filtering we can use custom field values as property criteria is not available.

 <Criteria>

     <ResolutionState>

      <StateRange Operator="NotEquals">255</StateRange>

    </ResolutionState>

    <SeverityList>

      <Severity>Error</Severity>

    </SeverityList>

    <CustomField1>PROD</CustomField1>

    <CustomField2>SQL</CustomField2>

  </Criteria>

Please refer this blog for updating alert custom fields.

https://blogs.technet.com/b/babulalghule/archive/2014/11/30/how-to-update-custom-alert-fields-using-command-line-notification-and-powershell.aspx

https://blogs.msdn.com/b/steverac/archive/2010/08/17/updating-custom-alert-fields-using-subscriptions-and-powershell.aspx

E. Generate the Management Pack and Import

To Seal the mp, first create the .snk file. (https://msdn.microsoft.com/en-us/library/k5b5tt23(v=vs.110).aspx)

Right click on project ->Properties -->Build and Select "Generate sealed and signed management pack"

Provide the .snk file path.

To Build the project, select Build → Build Solution. The solution will be verified with various Visual Studio tools and the MP Verify tool. If any errors are found, an error list will be generated. If there are no errors, the Output window will be displayed, indicating that the build was successful. Depending on the configuration you set in the properties, the .xml or .mp file will be found in the directory you set.

We can directly deploy the MP from VSAE or we can copy the .mp file created and import it.

Import Management Pack and verify the views 

Here is the view that we designed.

Enjoy!

We get frequent requests from customers on how to create notification workflow to notify if assigned to user filed is empty for Incident or Service Request. Currently this is not possible out of the box but this can be done using XML magic.

For this blog post, I'll create the notification workflow which will notify helpdesk every 10 mins until the Incident/Service Request is assigned.

So lets start,

For detailed steps on creating notification workflow in Service Manager, please refer this TechNet link https://technet.microsoft.com/en-us/library/hh519719.aspx

Step 1: Create notification template.

Refer this TechNet https://technet.microsoft.com/en-us/library/hh519719.aspx

Step 2: Create notification workflow (periodic subscription)

I selected the target class as Incident but if you want to notify for Service Request then select Service Request.

 Add 'First assigned date' in the criteria. This field will be updated with the date time when Incident/Service Request is assigned to user. So if this field is empty then incident is not assigned to any user yet. So we need to check if this field isNull or isEmpty but we don't have these operators in the UI. Add any temporary criteria here like "is less than or equal" to '05/05/2013' as UI will not allow to click next until we specify something here. We will modify this MP and add isNull operator from XML.

 We can also add additional criteria's here based on the requirement, like if you have multiple helpdesks (ex. Network, SQL). make sure that you add all the criteria that you need here along with first assigned date as we will not be able modify this workflow form UI after we do the changes in XML.

  In recurring notification section, specify the criteria that suits your requirement for recurring notifications. For this scenario, I want to notify helpdesk every 10 mins until the incident is assigned to analyst. If you want to notify once then you can set 'End after number of occurrences' = 1.  This workflow will run every 10 mins if criteria is true. This criteria will be false when incident has assigned to user.

 Select the notification template and add required recipients on the next screen.

 So we are done with creating notification workflow from UI, now its time to modify it from XML. Export management pack and open it in XML editor.

Locate the <Criteria> section in the MP for "First assigned date" as below.

<Criteria> 

<Expression>
       <SimpleExpression>
               <ValueExpressionLeft>
                <Property>$Context/Property[Type='CustomSystem_WorkItem_Library!System.WorkItem']/FirstAssignedDate$</Property>
               </ValueExpressionLeft>
                <Operator>LessEqual</Operator>
                 <ValueExpressionRight>
                <Value>2013-04-27T18:30:00</Value>
                </ValueExpressionRight>
          </SimpleExpression>
</Expression>

</Criteria>

We need to replace the lines between the tag <Expression> </Expression> with below code.

<UnaryExpression>
       <ValueExpression>
            <Property>$Context/Property[Type='CustomSystem_WorkItem_Library!System.WorkItem']/FirstAssignedDate$</Property>
       </ValueExpression>
       <Operator>IsNull</Operator>
</UnaryExpression>

So this will look like as below.

<Criteria>
  <Expression>
      <UnaryExpression>
        <ValueExpression>
              <Property>$Context/Property[Type='CustomSystem_WorkItem_Library!System.WorkItem']/FirstAssignedDate$</Property>
        </ValueExpression>
           <Operator>IsNull</Operator>
      </UnaryExpression> 
   </Expression>
</Criteria>

Save the management pack and re-import it back and you're done with XML code changes.

Note: Once you modify and re-import the MP, do not modify it from the UI as it will break the XML code.

I have attached sample MP with this post.

Hope this helps!

ManagementPack.3bef2f9daf4e454ba542aa8e44e4786a.xml

In SCSM 2010, we used xml mp to create notification for action log/user input updates but in 2012 we have new classes which we can use for the notifications.

 https://blogs.technet.com/b/servicemanager/archive/2010/08/30/notifying-the-affected-user-when-the-analyst-has-updated-the-action-log.aspx

In this post we will cover below scenarios. 

       1. Notify Analyst when user adds comments from portal on the Incident or Service Request.

       2. Notify End User when Analyst updates the action log from console on the Incident or Service Request.

If you are using Exchange connector to create and update incident from emails. 

      3. Notify Analyst when end user reply to email notifications with comments (or provides new information) for incident or Service Request.

      4. Notify End User when analysts reply to emails requesting more information (reply to assigned to user notification or analyst notification which will be logged as Analyst
comments on the Incident or Service Request)

     5. Service Request assignment/re-assignment workflow

       We will modify assignment/re-assignment management pack to notify for assignment re-assignment of Service Request.

 Let’s start with the process of creating notifications.

 For detailed steps on creating notifications in Service Manager, please refer this TechNet link https://technet.microsoft.com/en-us/library/hh519719.aspx

 This is a good blog post on creating Notification templates https://blogs.technet.com/b/servicemanager/archive/2009/09/28/creating-notification-templates-in-system-center-service-manager.aspx

 A) Scenario 1 & 3

This notification workflow will cover both the scenarios for Incident and Service Request.

Step 1: Create notification template

• Select the target class “Trouble Ticket Analyst Comments” (Click on Browse and Select All Basic classes), this contains the analyst comments for Incident and Service Request class.

 If you are sending notification for incidents,

•  To get incident ID: Select ‘Has Analyst Comment ‘-> WorkItem ->ID

If you are sending notification for Service Request,

•  To get SR ID: Select ‘Work Item Has Comment  Log‘-> WorkItem -> ID

 Same way you can get the Title, Status fields from respective classes as mentioned above.

•  To get the Assigned to user for Incident/Service Request

• To get the Analyst comments for Incident/Service Request. (Note: This will only include latest comment)

•  Do not forget to select “Send as HTML”

Step 2: Create Notification workflow (subscription)

•  Select “When Object of selected class is created” and Target class as “Trouble Ticket Analyst Comments”

• Select the template that we created.

• Add related Recipients

 For Incident

 For Service Request

We are done with the creating the subscription/template for an action log update.

 B) Scenario 2 & 4

 Same way we can create the notification subscription/template but target class will be “Trouble Ticket User Comments”

C) Scenario 5:

 This blog provides the instruction to create the notification workflow for Incident assignment/re-assignment

https://blogs.technet.com/b/servicemanager/archive/2009/12/15/custom-notification-workflow-on-incident-assignement-or-re-assignment.aspx

 We will modify this so that it will notify for Service Request assignment/re-assignment.

First let’s understand how this MP works.

This MP has two main sections that we need to understand before we make modification.

 1. When to notify (criteria section)

  <Rule ID="IncidentAssignmentChanges" Enabled="true" Target="SystemCenter!Microsoft.SystemCenter.SubscriptionWorkflowTarget" ConfirmDelivery="false" Remotable="true" Priority="Normal" DiscardLevel="100">     
<Category>Discovery</Category>       
<DataSources>         
<DataSource ID="DS" TypeID="SystemCenter1!Microsoft.SystemCenter.CmdbInstanceSubscription.DataSourceModule">

   <Subscription>

              <RelationshipSubscription RelType="$MPElement[Name='WorkItem!System.WorkItemAssignedToUser']$" SourceType="$MPElement[Name='CoreIncident!System.WorkItem.Incident']$" TargetType="$MPElement[Name='System!System.Domain.User']$">

                <AddRelationship>

                </AddRelationship>

              </RelationshipSubscription>

 Only change will be SourceType.

  <Rule ID="ServiceRequestAssignmentChanges" Enabled="true" Target="SystemCenter!Microsoft.SystemCenter.SubscriptionWorkflowTarget" ConfirmDelivery="false" Remotable="true" Priority="Normal" DiscardLevel="100">       
<Category>Discovery</Category>       
<DataSources>         
<DataSource ID="DS" TypeID="SystemCenter1!Microsoft.SystemCenter.CmdbInstanceSubscription.DataSourceModule">

            <Subscription>

              <RelationshipSubscription RelType="$MPElement[Name='WorkItem!System.WorkItemAssignedToUser']$" SourceType="$MPElement[Name='WorkItem_ServiceRequest!System.WorkItem.ServiceRequest']$" TargetType="$MPElement[Name='System!System.Domain.User']$">

                <AddRelationship>

                </AddRelationship>

              </RelationshipSubscription>

2.   Whom to notify.

 This will decide whom to send the notification. This we can change based on the requirement.

<WorkflowArrayParameter Name="UserAliasOrRelationships" Type="string">

<Item>$MPElement[Name='WorkItem!System.WorkItemAssignedToUser']$</Item>

</WorkflowArrayParameter>

</WorkflowParameters>

I have attached 2 MPs with this blog for all 5 scenarios.

Have fun!

MPs.zip

In this blog post, I walk you through the steps to install Service Manager 2012 SP1 with a SQL 2012 AlwaysON Availability Groups.

First, let’s understand the two scenarios for using SQL AlwaysON availability Groups for Service Manager.

1. Service Manager is already installed.
2. New installation of Service Manager.

In first scenario, we need to create availability group for already installed Service Manager Database and follow the Service Manager Database movement process (link) and use availability group listener as new SQL server name.

For second scenario, create availability group and use availability group listener name as SQL server name for installing service manager.

Here are the high level steps:

1. Install two node windows server 2012 cluster.
2. Install SQL Server 2012 on both the nodes.
3. Create and configure AlwaysON Availability Group.
4. Pre-requisite for Service Manager 2012 SP1 install on SQL AlwaysON.
5. Install Service Manager.
6. Test failover.

Let’s start with brief overview of SQL AlwaysON Availability Groups

An availability group supports a failover environment for a discrete set of user databases, known as availability databases that fail over together. An availability group supports a set of primary databases and one to four sets of corresponding secondary databases. Availability groups leverage Windows Server Failover Clustering (WSFC) functionality and enable multiple features not available in database mirroring.

Please refer this (link) TechNet for the details on SQL AlwaysON Availability Groups.

Step 1:  

Setup windows Server 2012 cluster, I recently wrote a blog on installing windows cluster on virtual machines.

https://blogs.technet.com/b/babulalghule/archive/2013/02/16/how-to-configure-two-node-windows-server-2012-cluster-on-virtual-machines-for-testing.aspx

Step 2:

Install SQL Server 2012 on both the nodes with SQL Service running on domain account.

For detailed pre-requisite for SQL AlwaysON Availability Groups refer this link.

Step 3:

Enable SQL alwaysON feature on both the nodes.

• SQL Server Configuration Manager -> SQL Server Services -> Open properties of the SQL Service
• Click on “AlwaysON High Availability” tab and check “Enable AlwaysON Availability Groups” and restart SQL Service for changes to take effect.

Create SQL AlwaysON Availability Group

Pre-Requisite:

• Need minimum one database to create availability group.
• Any databases that you are planning to add to availability groups should have “Full” recovery mode.
• Take the full backup of database which you are adding to the availability groups.
• Need shared network location which is accessible to both the nodes.

We will create sample database in order to create availability group for Service Manager Installation.

• Create Sample database with full recovery mode and take the full backup of the database.
• Create shared network location

I’m using same windows cluster setup which is described on this blog post.

• Created share (\\iSCSITarget\SQLAlwaysON) on my iSCSI target server from Server Manager -> File and Storage Services -> Shares.

Create Availability Group (Refer this link for details)

• Open SQL Management studio on any of the SQL Server node.
• AlwaysON High Availability -> right click on Availability Groups  and select “New Availability Group Wizard”.

• Specify Availability Group Name.

• Select SampleDB on databases selection tab.

• Add secondary SQL node on Specify Replicas tab.

• Select the options on each of the four tabs (Replicas, Endpoints, Backup preferences and listener) which suit your requirement. This TechNet link has very good explanations on all four tabs and options available.

• On Listener tab select Create an availability group listener.

 Listener DNS Name: Specify the network name of the listener. This name must be unique on the domain and can contain only alphanumeric characters, dashes  (-), and hyphens (_), in any order. When specified by using the Listener tab, the DNS name can up to 15 characters long.

 This DNS Name will be used as SQL Server Name for Service Manager Installation.

 Port: Specify the TPC port used by this listener.

 This port will be used as SQL Server port for Service Manager Communications with database.

• On Initial Data Synchronization page, select option (Full, Join Only and Skip initial data synchronization) which suits your requirement. This TechNet link has very good explanations on all three options available.

• On Validation page, see if all success.

• Click on Finish on Summary page and then click on Close to finish the availability group creation.

          In SQL Management studio, this availability group and listener will look like as below.

On Failover cluster Manager, it will appear under Roles.

Now, it’s time to install Service Manager

• Follow the planning and deployment guides for all the standard Service Manager installation pre-requisite.
• During the installation specify the Database server as Availability Group listener DNS name.

• And complete the installation steps as per the service manager deployment guide.

Configure Service Manager Database for Availability Groups

• Service Manager Installation using the SQL availability group listener does not configure Service Manager Database in availability groups.
• To configure Service Manager database in availability group, change the recovery model (refer this link for details on Recover Model) from Simple to Full
• Take full backup of Service Manager Database.
• Right click on Availability Databases ->  Add Database wizard and follow the instruction on wizard to add Service Manager Database to the Availability Databases.

• Verify that if you see the Service Manager database on secondary node.

Now, it’s time to test Service Manager Database failover

• Open failover cluster manager and verify the owner node.

• Right click on availability group and move to secondary node.
• If you are using immediate failback option then this will immediately failback to primary.

In my case I’m using prevent failback.

• Open Service Manager Console and verify if everything is working fine after failover.
• After failover I got few errors in the OpsMgr logs, first thing I provided permission for Service Manager SDK service account on SM database on secondary node.
• Restarted the SDK restart and got the below error.

Log Name:      Operations Manager

Source:        DataAccessLayer

Date:          16-02-2013 12:37:17

Event ID:      33333

Task Category: None

Level:         Warning

Keywords:      Classic

User:          N/A

Computer:      SCSMSP1.monlab.com

Description: Data Access Layer rejected retry on SqlError:  Request: ObjectTemplateByCriteria --
(LanguageCode1=ENN), (LanguageCode2=ENU), (TypeID0=4b1e00f8-1f3d-ad95-acdb-5587b3cf7147), (LastModified0=16-02-2013
19:43:53)

 Class: 16

 Number: 6263

 Message: Execution of user code in the .NET Framework is disabled. Enable "clr enabled" configuration option.

• Executed below query on secondary node

            sp_configure 'clr
            enabled', 1

           go

           reconfigure

           go

I forgot to run this SQL query on secondary node before attempting to failover.

Now everything works as expected.

Hope this helps!

To start with, we need 3 windows server 2012 virtual machines. Out of 3, one will be used as an iSCSI target (details on iSCSI target) and other two will be part of the two node windows cluster.

Step 1: Configure iSCSI target

Pre-requisite

• Created Virtual Machine with Windows Server 2012 OS
• Joined to my test lab domain
• Added extra virtual hard disk (100 GB) to this machine which I will use as shared storage

Install the iSCSI Target Server feature

• Add Roles and Features Wizard -> Server Roles -> File and Storage Services -> File and iSCSI Service
• Select iSCSI Target Server and then click on Add Features

• Restart the virtual machine to complete the feature installation.

 Start iSCSI Initiator on the two Cluster nodes

• Server Manager -> Tools -> Click on the iSCSI Initiator
• Click on yes to start the iSCSI service and then click on OK on iSCSI Initiator property window

Configure iSCSI Target Server

• Server Manager -> File and Storage Services -> iSCSI

• Click on “To Create an iSCSI virtual disk, start the new iSCSI virtual Disk Wizard”.

This disk will be used as a shared disk on the two cluster nodes.

• Select the storage location and click Next

• Provide the name for this iSCSI virtual disk
• Specify iSCSI virtual disk size

• Create the iSCSI target

• Provide the suitable name for iSCSI target, I’m using server name as iSCSI target name
• Add the servers who can access this iSCSI storage

• Click Next on Enable Authentication
• Click create on Confirmation tab and on successful completion, you will see below screen

Configure iSCSI initiator on both nodes

• Server Manager -> Tools -> iSCSI initiator
• Type the target server name and click on Quick Connect

• If connection successful, you will see below screen

Configure the Disks on the iSCSI initiators i.e. Cluster Nodes

• Server Manager -> Computer Management -> Disk Management
• Select the disk and make it online and then initialize it.

• Create the simple volume
• Also on other node, make the disk online
• Now this disk will be visible on both the nodes

Installing Windows Cluster

• On Both the nodes install Failover Clustering feature from Server Manager -> Add Roles and Features -> Features
• Login to one of the node and open the Failover cluster Manager (Server Manager -> Tools)
• Click on Validate configuration
• Add both the node names and run the validation test.

• After validation tests are successful, click on finish to create the cluster

• Provide the suitable name for your cluster

• Click Next on Confirmation and Create New Cluster tabs and click on finish once the creation is complete.

Now cluster is ready to use, have fun!

First, let’s understand how self-service portal works.

 The flow of data is as follows: 

1. The client accesses the Self-Service Portal with a browser by specifying the URL for the SharePoint server.
2. The SharePoint server returns Silverlight code that creates a web page containing the basic framework of the Self-Service Portal and also the URL for the web content server computer. The URL for the web content server computer was defined when you installed the Self-Service Portal.
3. The client computer, which is now running the Silverlight code, makes a connection to the web content server computer using the URL in step 2.
4. The web content server computer reads and writes data to the Service Manager database. The computer name for the Service Manager Database was defined when you installed the web content server.
5. The web content server computer returns the data that makes up the center pane on the Self-Service Portal page.

 If you install Self-Service Portal (SSP) with SSL, things to remember.

• The certificates that you use for the Self-Service Portal must be issued from a Certification Authority that is trusted by the client.
• The name on the certificate for the SharePoint website server must match the URL that your users enter into the browser. For example, if the user types the URL https://ServiceDesk/SMPortal, then the certificate must have been issued to ServiceDesk and not to FQDN, for example, ServiceDesk.woodgrove.com.
• The name on the certificate for the web content server must match the name that you entered when you deployed the SharePoint website server.

 If you are deploying both the SharePoint website server and web content server on the same computer, you need only one certificate. That one certificate will work for both ports. If you are deploying the SharePoint website server and web content server on different servers (which is recommended in a production environment), you will need one certificate for each computer.

Please refer these TechNet links for more details

https://technet.microsoft.com/en-us/library/hh914195.aspx

https://technet.microsoft.com/en-us/library/hh667343.aspx

Ok, let’s continue with our scenario.

I will install the WCS and SharePoint on two different servers and will use https://ServiceDesk/SMPortal as my portal URL and not the https://<ServerName>/SMPortal.

Step 1:

We need to create the DNS record for ServiceDesk and point it to Service Manager Portal Server (in this scenario to the server where we will install SharePoint web parts).

Step2:

Here, we need to create two certificates one for WCS and other for alias name (Sharepoint server)

1. Create the certificate for this alias name.

For our scenario, I’ll create it from IIS -> Server Certificates -> Create Domain Certificate

On next page you need to select CA.

When you create the certificate it will look like this

Note: Issued to name should be same as URL

 2. I'll use same method to create the certificate for WCS server (this certificate issued to name will be same as URL in the application settings on the SharepointServer)

Sharepoint Server -> IIS -> Service Manager Portal -> Application Settings

Note : WCS certifcate issued to name and name in this URL should match.

Step 3: Install SSP

Install WCS, refer this link for details https://technet.microsoft.com/en-us/library/hh524264.aspx

and then Install Sharepoint WebPart, refer this link for details https://technet.microsoft.com/en-us/library/hh495676.aspx

Step 4: Configure the Alternate Access Mappings (AAM)

Alternate Access Mappings (AAM) allows you to modify results URLs based on the access URLs for a site. For SSP we are using the URL as ServiceDesk and not server name so to allow this in SharePoint we need to configure AAM.

 Steps to configure it: https://technet.microsoft.com/en-us/sharepoint/ff679917.aspx

SharePoint Central Administration -> Application Management -> Configure Alternate Mappings -> Select the Service Manager Portal URL -> Edit Public URLs -> and update the alternate URL

Hope this helps!