Showing posts with label SCOM2007. Show all posts
Showing posts with label SCOM2007. Show all posts

Wednesday, February 6, 2013

[OpsMgr 2007 R2][OpsMgr 2012] Generate & View SCOM reports on iOS mobile devices

Overview:

With the immense boom in the smart phone and tablet device market, many customers are moving towards accessing SCOM reports on mobile devices. They need a solution to view and generate SCOM reports on the go using their ipads and iphones. There is a solution for this and is very easy to setup. Below article will walk you through the setup process. The trick here is to access the SQL reporting services that you installed with your SCOM installation through multiple on your iOS devices.


For more details please visit : http://techordian.com/2013/02/01/scom-2007r2-2012-generate-view-scom-reports-on-ios-mobile-devices/

This posting is provided "AS IS" with no warranties.

Tuesday, April 24, 2012

[Powershell][OpsMgr 2007] Get All objects in Maintenance Mode using powershell

The need here is to be able to list all objects in Maintenance mode in a management group.

Here is also a very short powershell function you can use :

  1. function ListObjectsInMaintMode {
  2.  $criteria = new-object Microsoft.EnterpriseManagement.Monitoring.MonitoringObjectGenericCriteria("InMaintenanceMode=1")
  3.  $objectsInMM = (Get-ManagementGroupConnection).ManagementGroup.GetPartialMonitoringObjects($criteria)
  4.  $objectsInMM | select-object DisplayName, @{name="ObjectType";expression={foreach-object {$_.GetLeastDerivedNonAbstractMonitoringClass().DisplayName}}},@{name="StartTime";expression={foreach-object {$_.GetMaintenanceWindow().StartTime.ToLocalTime()}}},@{name="EndTime";expression={foreach-object {$_.GetMaintenanceWindow().ScheduledEndTime.ToLocalTime()}}},@{name="Path";expression={foreach-object {$_.Path}}},@{name="User";expression={foreach-object {$_.GetMaintenanceWindow().User}}},@{name="Reason";expression={foreach-object {$_.GetMaintenanceWindow().Reason}}},@{name="Comment";expression={foreach-object {$_.GetMaintenanceWindow().Comment}}}
  5. }
In a powershell shell, connect to a management group and just launch ListObjectsInMaintMode

Result be look like :



This can be really usefull ! :)

This posting is provided "AS IS" with no warranties.

Monday, March 5, 2012

I Love System Center Wallpaper new version in High Resolution

I Love System Center Wallpaper

New version, System Center Wallpaper. High Resolution (3840 x 2160), and in 11 Colors.







This posting is provided "AS IS" with no warranties.

Thursday, February 9, 2012

[SQL] Get SCOM Groups members using a SQL Query on OperationsManager DB

Here is a short query that is very usefull to list all member of a SCOM group. Use it on your OperationsManager DB :
  1. select DisplayName from RelationShip r with (nolock)
  2. inner join basemanagedentity bme with (nolock) on bme.BaseManagedEntityId = R.TargetEntityId
  3. Where SourceEntityId in (
  4.             select BaseManagedEntityId from basemanagedentity with (nolock)
  5.             where DisplayName LIKE '%GroupName%')
  6. Order by DisplayName

This posting is provided "AS IS" with no warranties.

Opalis Integration Server & System Center Operations Manager Extensibility Kit 2.0

source code, 12K, uploaded Nov 5 2010
documentation, 1020K, uploaded Nov 5 2010
 
Please refer to http://opalis.codeplex.com/releases/view/50751 - original post where I've found the information
 
The Opalis Integration Server (OIS) – System Center Operations Manager (SCOM) Extensibility Kit 2.0 includes examples of how to extend SCOM using both the SCOM and OIS SDKs. The C# code and compiled DLL included here offer two OIS objects which can be used to automatically create or delete notification subscriptions based on an existing Channel as well as work against existing Pending Agent Installs in the SCOM database.

Included in this Extensibility Kit:
  • Opalis Ready DLL:
  • Can be used with the “Invoke .NET” object included in the Integration Pack for “Opalis Quick Integration Kit for Microsoft .NET”
    • OpalisSCOMExtensibility.dll
    • NOTE: This DLL is dependent on some other resources, see System Requirements.
  • C# Source Code:
  • Example C# Source Code illustrating the combination of the SCOM and OIS SDKs.
    • SCOM_NoteSubcriptionCreate.cs
    • SCOM_NoteSubcriptionDelete.cs
    • SCOM_AgentInfoAdapter.cs
    • SCOM_ApprovePendingAgentInstall.cs
    • SCOM_ListPendingAgentInstalls.cs
    • NOTE: These C# files are dependent on some other resources, see System Requirements.

This Extensibility Kit (DLL to be used with the Opalis “Invoke .NET” object) adds the following object capability to Opalis Integration Server:
  • Create SCOM Notification Subscription (SCOM.SCOMSDK.SCOMNoteSubcriptionCreate)
  • Delete SCOM Notification Subscription (SCOM.SCOMSDK.SCOMNoteSubcriptionDelete)
  • List Pending Agent Installs (SCOM.SCOMSDK.SCOMListPendingAgentInstalls)
  • Approve Pending Agent Installs (SCOM.SCOMSDK.SCOMApprovePendingAgentInstall)

This DLL (and appropriate dependencies) can be rolled up into an Opalis Integration Pack (not included here) by using the QIK Wizard.

Please Refer to the OIS-SCOM Extensibility Kit 2.0 - User Guide for more information on System Requirements, Installation, Configuraiton and Usage.

This posting is provided "AS IS" with no warranties.

Friday, February 3, 2012

[SCOM 2007] Operations Manager Dynamic Group Examples by Jeanie Decker (Microsoft)

Please find on this page an article that provides example of group definitions. The examples describe the items to select in the Query Builder and the resulting formula.


First published by

This posting is provided "AS IS" with no warranties.

Wednesday, February 1, 2012

[Powershell] Playing with registry keys in powershell

I've had to read and write some registry keys from my management pack to implement a functionnality for debugging purpose - all events are created in in the Operations Manager Event log.

Here are the differents functions that can be usefull :
  • CheckIfRegistryKeyExists : create event 200 (Information or Error) depending of the result
  • ReadRegistryKey : Read the key value and write information event 200
  • WriteRegistryKey : Write the key value and write information event 200
  • Write-ErrorInfo : create error event 500
  • Write-DebugInfo : create Information event 100

Copy the code below in a  ReadRegistryKey.ps1 file for example

  1. param ($RegistryKeyPath, $KeyName, $KeyValue, $Debug)
  2. if ($debug -ne "true"){$debug = [bool]$false}else{$debug = [bool]$true}
  3. $Script:API             = new-object -comObject "MOM.ScriptAPI"
  4. $Script:Bag             = $Script:API.CreatePropertyBag()
  5. $Script:LOG_ERROR       = 1
  6. $Script:LOG_WARNING     = 2
  7. $Script:LOG_INFORMATION = 4
  8. $Script:ScriptName      = "ReadRegistryKey.ps1"
  9. $Script:Arguments       = "Received Arguments:`RegistryKeyPAth = $RegistryKeyPath `rKeyName = $KeyName `rDebug = $debug"
  10. #------------------------------------------------------------------------------------------
  11. Function CheckIfRegistryKeyExists($KeyPath,$KeyName)
  12. {
  13.  $KeytoRead = $KeyPath
  14.  $KeytoReadName = $KeyName
  15.  $a = (Get-ItemProperty -path registry::$KeytoRead).$KeytoReadName -eq $null
  16.  if ($a -eq "false")
  17.   {
  18.   $Script:API.LogScriptEvent("CheckIfRegictyryKeyExists",200,$Script:LOG_ERROR,"`r$KeyPath\$KeyName doesn't exist !")
  19.   }
  20.  else
  21.   {
  22.   $Script:API.LogScriptEvent("CheckIfRegictyryKeyExists",200,$Script:LOG_INFORMATION,"`r$KeyPath\$KeyName exists.")
  23.   }
  24. }
  25. #------------------------------------------------------------------------------------------
  26. function ReadRegistryKey($KeyPath,$KeyName)
  27. {
  28.     $Script:API.LogScriptEvent("$ScriptName",200,$Script:LOG_INFORMATION,"`r$KeyPath\$KeyName ")
  29.  $KeytoRead = $KeyPath
  30.  $KeytoReadValue = $KeyName
  31.  $a = Get-ItemProperty -path registry::$KeytoRead -name $KeytoReadValue
  32.  $ReadValue = $a.$KeytoReadValue
  33.  $ReadValue
  34. }
  35. #------------------------------------------------------------------------------------------
  36. function WriteRegistryKey($KeyPath,$KeyName,$KeyValue)
  37. {
  38.  $Script:API.LogScriptEvent("$ScriptName",200,$Script:LOG_INFORMATION,"`r$KeyPath\$KeyName with value $KeyValue is created")
  39.  $KeytoRead = $KeyPath
  40.  $KeytoReadValue = $KeyName
  41.  $Value = $KeyValue
  42.  $a = Set-ItemProperty -path registry::$KeytoRead -name $KeytoReadValue -Value $Value
  43.  $a.$KeytoReadValue
  44. }
  45. #------------------------------------------------------------------------------------------
  46. function Write-DebugInfo([string] $msg)
  47. {
  48.     if ($debug)
  49.     {
  50.         $Script:API.LogScriptEvent("$ScriptName",100,$Script:LOG_INFORMATION,"`r$Arguments`r`r$msg")
  51.     }
  52. }
  53. #------------------------------------------------------------------------------------------
  54. function Write-ErrorInfo([string] $msg)
  55. {
  56.     if ($debug)
  57.     {
  58.     $Script:API.LogScriptEvent("$ScriptName",500,$Script:LOG_ERROR,"`r$Arguments`r`r$msg")
  59.  }
  60. }
  61. #------------------------------------------------------------------------------------------
  62. # MAIN CODE START HERE
  63. #------------------------------------------------------------------------------------------
  64. # Use this line to Read the registry key
  65. ReadRegistryKey $RegistryKeyPath $KeyName
  66. # Use this line to Create the registry key with its value
  67. WriteRegistryKey $RegistryKeyPath $KeyName $KeyValue
  68. # Use this line to check if key exist
  69. CheckIfRegistryKeyExists $RegistryKeyPath $KeyName
Then is a powershell command shell, just launch the ReadRegistryKey.ps1 with the parameters like :
> C:\scripts\ReadRegistryKey.ps1 "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\
Microsoft Operations Manager\Debugging" "ForTestingPurpose" "ValueToSet" "true"

When the HKLM\SOFTWARE\Microsoft\Microsoft Operations Manager\Debugging\ForTestingPurpose key doens't exist :
  • ReadRegistryKey function will return
Case : key tested exists :

Case key doens't exist : To be implemented since the code return error in powershell or just use the CheckRegistryKey function before.

Get-ItemProperty : Property ForTestingPurpose1 does not exist at path HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\Debugging.
At C:\scripts\ReadRegistryKey.ps1:35 char:23
+     $a = Get-ItemProperty  <<<< -path registry::$KeytoRead -name $KeytoReadValue

  • Write registry key will create the key and return :

  • Checking the registry key can return 2 states :
Key doens't exist


And also Key exists :


 Hope this will be helpful.





This posting is provided "AS IS" with no warranties.

[Powershell] Get SCOM Groups members using a SQL Query

Here is a new powershell script that I had to use to develop MPs. Retieving SCOM Groups members (displayName in the exemple)by using the SCOM DB.
  1. function GetSCOMGroupMembers ($SCOMGrp, $DBServer, $DBCatalog)
  2. {
  3. $SqlServer = $DBServer
  4. $SqlCatalog = $DBCatalog
  5. $SCOMGroup = $SCOMGrp
  6. $SQLQuery = "select DisplayName from RelationShip r with (nolock)
  7. inner join basemanagedentity bme  with (nolock) on bme.BaseManagedEntityId = R.TargetEntityId
  8. Where SourceEntityId in (
  9. select BaseManagedEntityId from basemanagedentity with (nolock)
  10. where DisplayName LIKE '%$SCOMGroup%')"
  11. $SqlConnection = New-Object System.Data.SqlClient.SqlConnection
  12. $sqlConnection.ConnectionString = "Server = $sqlserver; Database = $sqlcatalog; Integrated Security = True"
  13. $SqlCmd = New-Object System.Data.SqlClient.SqlCommand
  14. $SqlCmd.CommandText = $SQLQuery
  15. $SqlCmd.Connection = $SqlConnection
  16. $SQlCmd.CommandTimeout = 120
  17. $SqlAdapter = New-Object System.Data.SqlClient.SqlDataAdapter
  18. $SqlAdapter.SelectCommand = $SqlCmd
  19. $DSet = New-Object System.Data.DataSet
  20. $SqlAdapter.Fill($DSet) | out-null
  21. $SqlConnection.Close()
  22. $DSet.Tables[0]
  23. }

How to use it :
  1. # --------- Read the SCOMDB Server and Catalog
  2. $SCOMServer = "MyServer"
  3. $SCOMCatalog = "OperationsManager" 
  4. # --------- Variable initialization
  5. $SCOMGrpName = "MyGroupName" 
  6.  # --------- Read SCOM group and get member count
  7. $GroupMembersList = GetScomGroupMembers $SCOMGrpName $SCOMServer $SCOMCatalog
The script wil return a table $GroupMembersList that can also be re-used.

This posting is provided "AS IS" with no warranties.

[Powershell] Get SCOM Groups using a SQL Query

Today, I'll add a new powershell script that I had to use for a developped MP. Retieving SCOM Groups by using the SCOM DB.
  1. Function GetSCOMGroupsInSQL ($DBServer, $DBCatalog)
  2. {
  3. $SqlServer = $DBServer
  4. $SqlCatalog = $DBCatalog
  5. $SQLQuery = "select distinct SCOMGroup = convert(varchar(100), upper(rtrim(ltrim(BME.Displayname))))"
  6. $SQLQuery += " from BaseManagedEntity BME"
  7. $SQLQuery += " left join dbo.ManagedTypeView T1 on (BME.BaseManagedEntityId = T1.Id)"
  8. $SQLQuery += " Left join dbo.Relationship R1 on(BME.BaseManagedEntityId=R1.Sourceentityid)"
  9. $SQLQuery += " left join BaseManagedEntity ME2 on (ME2.BaseManagedEntityId=R1.targetentityid)"
  10. $SQLQuery += " left join dbo.ManagedTypeView T2 on(ME2.BaseManagedEntityId=T2.id)"
  11. $SQLQuery += " where (T1.Name like 'UINameSpace%.Group' or T1.Name like '%MySpecificGroupName%')"
  12. $SqlConnection = New-Object System.Data.SqlClient.SqlConnection
  13. $sqlConnection.ConnectionString = "Server = $sqlserver; Database = $sqlcatalog; Integrated Security = True"
  14. $SqlCmd = New-Object System.Data.SqlClient.SqlCommand
  15. $SqlCmd.CommandText = $SqlQuery
  16. $SqlCmd.Connection = $SqlConnection
  17. $SQlCmd.CommandTimeout = 120
  18. $SqlAdapter = New-Object System.Data.SqlClient.SqlDataAdapter
  19. $SqlAdapter.SelectCommand = $SqlCmd
  20. $DSet = New-Object System.Data.DataSet
  21. $SqlAdapter.Fill($DSet) | out-null
  22. $SqlConnection.Close()
  23. $DSet.Tables[0]
  24. }
How to use it :
  1. # --------- Read the SCOMDB Server and Catalog
  2. $SCOMServer = $Config.Groups.SCOMDB.SCOMDBServerName
  3. $SCOMCatalog = $Config.Groups.SCOMDB.SCOMDBName
  4. # --------- Query SCOM DB to get Agent list and Group List
  5. $GroupList = GetSCOMGroupsInSQL $SCOMServer $SCOMCatalog
The script wil return a table $GroupList that can also be re-used.

This posting is provided "AS IS" with no warranties.

[Powershell] Get SCOM Agents using a SQL Query

Today, I'll add a new powershell script that I had to use for a developped MP. Retieving SCOM agents by using the SCOM DB instead of Get-Agent cmdlet.
The aim was to have a very fast answer of the script and using the Get-Agent cmdlet was really too long.

  1. Function GetSCOMAgentsInSQL ($DBServer, $DBCatalog)
  2. {
  3. $SqlServer = $DBServer
  4. $SqlCatalog = $DBCatalog
  5. $SQLQuery =  "SELECT distinct(B.displayname)"
  6. $SQLQuery += " FROM TypedManagedEntity T WITH(NOLOCK)"
  7. $SQLQuery += " JOIN BaseManagedEntity B WITH(NOLOCK)    ON B.BaseManagedEntityId = T.BaseManagedEntityId"
  8. $SQLQuery += " WHERE T.ManagedTypeId = dbo.fn_ManagedTypeId_MicrosoftSystemCenterAgent()"
  9. $SQLQuery += " order by 1"
  10. $SqlConnection = New-Object System.Data.SqlClient.SqlConnection
  11. $sqlConnection.ConnectionString = "Server = $sqlserver; Database = $sqlcatalog; Integrated Security = True"
  12. $SqlCmd = New-Object System.Data.SqlClient.SqlCommand
  13. $SqlCmd.CommandText = $SqlQuery
  14. $SqlCmd.Connection = $SqlConnection
  15. $SQlCmd.CommandTimeout = 120
  16. $SqlAdapter = New-Object System.Data.SqlClient.SqlDataAdapter
  17. $SqlAdapter.SelectCommand = $SqlCmd
  18. $DSet = New-Object System.Data.DataSet
  19. $SqlAdapter.Fill($DSet) | out-null
  20. $SqlConnection.Close()
  21. $DSet.Tables[0]
  22. }

How to use it :
  1. # --------- Read the SCOMDB Server and Catalog
  2. $SCOMServer = $Config.Groups.SCOMDB.SCOMDBServerName
  3. $SCOMCatalog = $Config.Groups.SCOMDB.SCOMDBName
  4. # --------- Query SCOM DB to get Agent list and Group List
  5. $AgentList = GetSCOMAgentsInSQL $SCOMServer $SCOMCatalog
The script wil return a table $AgentList that can also be re-used.

This posting is provided "AS IS" with no warranties.

[SCOM 2007] Overrides report per server

The reports provided with System Center Operations Manager 2007 may sometimes seem particularly poor in terms of daily operations on the product. Today, Jean-Sébastien Dûchene offers a report which lists all the overrides that have been created and applied to a given machine.

French and English page is available here :


This includes targeting overrides:
  • entities (disk, database ...) attached,
  • groups with the machine or its entities are part
  • class
 
You can then retrieve information such as the Management Pack, the type (Monitor/rule), the name of the rule or the monitor, the type of context, the target name, the setting overrided, the value, the value of Enforced option, the last modified date, the added date, or the management pack used to store the change.

 Note that :
  • The report can be long to run.
  • Do not necessarily reflect the actual configuration on the client since you can have several different values overrided affecting a class, group, and object.
Do not forget to create a datasource targeting to the operational database with security rights necessary to generate the report.

 
Thanks to Jean-Sébastien Dûchene - This report is provided "AS IS" without express or implied warranty of any kind.


This posting is provided "AS IS" with no warranties.

Tuesday, January 31, 2012

[SCOM 2007 R2] Authoring Console ask for Microsoft.SystemCenter.Library version 6.1.7221.61 for editing a MP

Article ID: 2590414 - Last Review: November 14, 2011 - Revision: 3.0
KB only applicable to if CU4 or later is installed.
 You are prompted for the latest version of the Microsoft.SystemCenter.Library management pack when you try to edit a new management pack in the Authoring Console in Microsoft System Center Operations Manager 2007 R2 after you install Cumulative Update 4 (CU4) or later versions.



Root cause : This issue occurs because new management packs that are imported or created automatically in Operations Manager 2007 R2 after you install Cumulative Update 4 or later versions have a dependency on the latest version of the Microsoft.SystemCenter.Library management pack (The latest version of the Microsoft.SystemCenter.Library management pack may be version 6.1.7221.61 or a later version).

Resolution :To resolve this issue, download the latest version of the Microsoft.SystemCenter.Library management pack from the Microsoft Download Center, then extract the management pack and copy it to the following folder:%ProgramFiles%\System Center MP Authoring Console 2007
The next time that you use the Authoring Console to edit a new management pack, you will not be prompted for the Microsoft.SystemCenter.Library management pack.


For more information please read the microsoft web page http://support.microsoft.com/kb/2590414

This posting is provided "AS IS" with no warranties.

Thursday, January 26, 2012

[Powershell] Get Rules informations and Monitors informations for a spécified MP in SCOM

Here is a short powershell function that create 2 CVS files. One with Rules informations and an other one for Monitors information for a specified MP :
  1. Function RetrieveIDs()
  2. {
  3. Param ([String] $MPName, [String]$Path)
  4. If ($Path -eq "") { $Path=("C:\Temp") }
  5. $MonitorsFile = $Path + "\MonitorsIds.csv"
  6. $RulesFile = $Path + "\RulesIds.csv"
  7. "Files MonitorsIds.csv & RulesIds.csv will be generated in : " + $Path
  8. If ($MPName -eq "") { $MPName=(Read-Host "Enter a Management Pack Name ") }
  9. $mp=Get-ManagementPack | where {$_.name -eq $MPName}
  10. if ($mp -eq $null) {
  11.       "The ManagementPack you have put in argument is incorrect or not found"
  12.       "Here is a list of available MP:"
  13.       Get-ManagementPack | sort -property Name | ft Name
  14.       break
  15.       }
  16. $mp.Getmonitors() | select DisplayName, XMLTag,Category,Name,id, @{name="Description";expression={foreach-object {$_.Description -replace "\n","-"}}}  | export-csv -noTypeInformation -path $MonitorsFile
  17. $mp.Getrules() | select DisplayName,  XMLTag,Category,Name,id, @{name="Description";expression={foreach-object {$_.Description -replace "\n","-"}}} | export-csv -noTypeInformation -path $RulesFile
  18. }
3 ways to use the function :
  •  Just launch the command with no parameter:
PS Microsoft.EnterpriseManagement.OperationsManager.Client\OperationsManagerMonitoring::> retrieveIDs

No cvs files will be created since no MP Name is given. The output of the script will be the list of available MP.

  • Launch the command with 1 parameter that should be a MP Name:
PS Microsoft.EnterpriseManagement.OperationsManager.Client\OperationsManagerMonitoring::> retrieveIDs MyMPName

The cvs files MonitorsIds.csv & RulesIds.csv will be created in the default folder that is C:\Temp. You will retrieve information for the rules and monitors for the MyMPName MP.


  • Launch the command with 2 parameter that should be a MP Name and the path where to create the files :
PS Microsoft.EnterpriseManagement.OperationsManager.Client\OperationsManagerMonitoring::> retrieveIDs MyMPName C:\MyPath

The cvs files MonitorsIds.csv & RulesIds.csv will be created in the C:\MyPath folder. You will retrieve information for the rules and monitors for the MyMPName MP.

This posting is provided "AS IS" with no warranties.

Agent Health Tips and Fixes for System Center Operations Manager 2007

Article ID: 2616936 - January 16, 2012 - Revision: 6.1 http://support.microsoft.com/kb/2616936

This article is intended to give some tips on fixes and changes for System Center Operations Manager 2007 (OpsMgr) Agent Health. There are a variety of hotfixes and registry keys listed so please be aware that these are things that may not be noticed in your environment directly but might be causing issues that you are not aware of. If you are having an issue with agents in a grey state these fixes may help, if they do not see the following: http://support.microsoft.com/kb/2288515

This posting is provided "AS IS" with no warranties.

Monday, January 16, 2012

SCOM 2012 Servers sizing for a small SCOM 2007 new deployment

For my own job, I've to create a new SCOM 2007 infrastructure (less than 250 servers to monitor - 120 servers in the same domain - 120 servers in 10 others domains).

I've also define 2 screnarios according to the Microsoft recommendations.

  • scenario given by Microsoft – small deployment

HW Mini required


Role: Root Management Server• 2 disk RAID 1
• 4 GB RAM
• Dual Proc

Role: Operations Database Server,  & Operations Data Warehouse Server (w/ SRS & Web Console Server)• 6 disk RAID 10 (147GB)
• 4 GB RAM
• Dual Proc



  • More secure scenario
The idea is to have a secure infrastructure for all monitored servers and a SCOM 2012 compliantcyto be sure if one day we have to migrate to SCOM 2012 - no new server will be needed.

So here is the minimal requisite for a small SCOM 2012 infrastructure (Minimal Hardware is given since we don't have a the moment any Microsoft recommandations):




and here is a more secure Topology Diagram :

SQL DB/DW on a cluster
SQL reporting server on the passive node since cluster is not supported
Servers outside the domain 1 will be linked to MS + RMS (failover) by using certificate
Servers in Domain 1 will be attached to 2 gateways (one for failover)
Console will be installed on a management server


This posting is provided "AS IS" with no warranties.