LeVeilleur.net » Scom 2007 http://www.leveilleur.net Thu, 03 Jun 2010 21:21:36 +0000 http://wordpress.org/?v=2.9.1 fr hourly 1 SCOM / PowerShell : Number of locked AD accounts http://www.leveilleur.net/index.php/2010/03/08/scom-powershell-number-of-locked-ad-accounts/ http://www.leveilleur.net/index.php/2010/03/08/scom-powershell-number-of-locked-ad-accounts/#comments Mon, 08 Mar 2010 12:43:17 +0000 Christopher Keyaert http://www.leveilleur.net/?p=287 Dear All,

Here a new little powershell script that creates an event 6970 in the event viewer when there is more than X accounts locked in less than Y minutes. Now, you just have to create a new rule in SCOM that collect event with the ID6970 and schedule that script to run every 10 minutes.

Thanks to that you can be alert when there is an attack attempt to your Active Directory.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
########################################################
#Get the number of lock account in less than 10 minutes
########################################################
###########################
# Param
###########################
$LockedSince = 10 #Minutes
$NumberofLockedAccount = 50 #

###########################
# FUNCTIONS
###########################
###########################
# SCRIPT
###########################
$objDomain = New-Object System.DirectoryServices.DirectoryEntry
$objSearcher = New-Object System.DirectoryServices.DirectorySearcher
$objSearcher.SearchRoot = $objDomain
$objSearcher.PageSize = 1000
$objSearcher.Filter = "(&(objectClass=User)(lockoutTime>=1))"
$colProplist = "name","samaccountname","lockoutTime"

foreach ($i in $colPropList){$objSearcher.PropertiesToLoad.Add($i) | out-null}
$colResults = $objSearcher.FindAll()

$cpt = 0
$result = $null
$result2 = $null

foreach ($objResult in $colResults) {

    $domainname = $objDomain.name
    $samaccountname = $objResult.Properties.samaccountname

    $user = [ADSI]"WinNT://$domainname/$samaccountname"
    $ADS_UF_LOCKOUT = 0x00000010
    #$objResult.Properties

    if(($user.UserFlags.Value -band $ADS_UF_LOCKOUT) -eq $ADS_UF_LOCKOUT) {
        $Sam = $objResult.Properties.samaccountname
        $Name = $objResult.Properties.name
        [String]$LockTime = $objResult.Properties.lockouttime
        [datetime] $LockTime = [datetime]::FromFileTime($LockTime)

        #We want all the account locked in the last 24h
        $DayDate = Get-Date
        $DayDateBefore = $DayDate.AddMinutes(-$LockedSince)

        if(($LockTime -gt $DayDateBefore) -and ($LockTime -lt  $DayDate))
            {
            Write-Host "************"
            Write-Host "User : $sam"
            Write-Host "Name : $name"
            Write-Host "LockTime : $lockTime"
            Write-Host "************"
            Write-Host ""

            $result2 += "************`r"
            $result2 += "User : $sam`r"
            $result2 += "Name : $name`r"
            $result2 += "LockTime : $lockTime`r"
            $result2 += "************`r"
            $result2 += "`r"

            $cpt += 1
            }
    }
}

Write-Host "************"
Write-Host "There is $cpt account(s) locked in the last $LockedSince minutes"
Write-Host "************"

$result += "************`r"
$result += "There is $cpt account(s) locked in the last $LockedSince minutes`r"
$result += "************`r"
$result += $result2

if($cpt -ge $NumberofLockedAccount)
    {
    Write-Host ""
    Write-Host "Limit reached, /!\ ALERT /!\"
    Write-Host ""
    $infoevent=[System.Diagnostics.EventLogEntryType]::Error
    }
else{
    $infoevent=[System.Diagnostics.EventLogEntryType]::Information
    }  

############################
#Var for the event creation
############################
$evt = new-object System.Diagnostics.EventLog("Application")
$evt.Source = "AD-SCOM"
$evt.MachineName = "."
$evt.WriteEntry($result,$infoevent,6970)
]]> http://www.leveilleur.net/index.php/2010/03/08/scom-powershell-number-of-locked-ad-accounts/feed/ 0 OpsMgr / SCOM : Automatic Agent Deployment With PowerShell http://www.leveilleur.net/index.php/2010/01/20/opsmgr-scom-automatic-agent-deployment-with-powershell/ http://www.leveilleur.net/index.php/2010/01/20/opsmgr-scom-automatic-agent-deployment-with-powershell/#comments Wed, 20 Jan 2010 15:06:55 +0000 Christopher Keyaert http://www.leveilleur.net/?p=281 Hello everyone,

Some weeks ago, I had to deploy SCOM Agent on more than 350 windows servers at the time. For that, I wrote a PowerShell Script where you just have to give a server list in input and the name of your RMS/MS . And that’s it, the script is performing the agent installation for you. A CSV file will be generated as output with the agent installation status of each servers.

Concerning the right management, you have to ensure that the Default Action Account using on the server that you will use for deploying the agents (MS normally), has administrative right on the servers that you want to add in SCOM. For that, and the duration of the deployment only, use a Domain Admin Account as the Run As Account of your MS/RMS.

The script :

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
###########################
# Autor : Christopher Keyaert
# Version : 1.0
# Date : 28 DEC 2009
##########################
#Getting the credential of the user
#$creds = Get-Credential

###########################
#Param
##########################
$RMS =  #don't forget to use the FQN RMS001.contoso.local
$MS  =  #don't forget to use the FQN MS001.contoso.local

$myFile = "D:\Dep\myfile.txt" #List of Servers
$ResultPath = "D:\Dep" #Folder for path output
Start-Transcript -path "$ResultPath\Transcript$(get-date -uformat '%Y-%m-%d_%Hh%Ms%S').log"

$MaintenanceModeEnable = $false

$MaintenanceModeDuration = 10 * 1440 # 1440 minutes per day
$comment = 'Global Deployment'
$reason = 'PlannedOther'

######################
#Functions
#####################
function SetToMaintenanceMode($rootMS,$computerPrincipalName,$minutes,$comment,$reason)
{
$computerPrincipalName = $computerPrincipalName + ".dir.ucb-group.com"
$computerClass = get-monitoringclass -name:Microsoft.Windows.Computer
$healthServiceClass = get-monitoringclass -name:Microsoft.SystemCenter.HealthService
$healthServiceWatcherClass = get-monitoringclass -name:Microsoft.SystemCenter.HealthServiceWatcher
$computerCriteria = "PrincipalName='" + $computerPrincipalName + "'"
$computer = get-monitoringobject -monitoringclass:$computerClass -criteria:$computerCriteria
$healthServices = $computer.GetRelatedMonitoringObjects($healthServiceClass)
$healthService = $healthServices[0]
$healthServiceCriteria = "HealthServiceName='" + $computerPrincipalName + "'"
$healthServiceWatcher = get-monitoringobject -monitoringclass:$healthServiceWatcherClass -criteria:$healthServiceCriteria
$startTime = [System.DateTime]::Now
$endTime = $startTime.AddMinutes($minutes)

Write-host " "
"Putting " + $computerPrincipalName + " into maintenance mode"
New-MaintenanceWindow -startTime:$startTime -endTime:$endTime -monitoringObject:$computer -comment:$comment -Reason:$reason
 
"Putting the associated health service into maintenance mode"
New-MaintenanceWindow -startTime:$startTime -endTime:$endTime -monitoringObject:$healthService -comment:$comment -Reason:$reason
 
"Putting the associated health service watcher into maintenance mode"
New-MaintenanceWindow -startTime:$startTime -endTime:$endTime -monitoringObject:$healthServiceWatcher -comment:$comment -Reason:$reason
Write-host " "

}

#################################
#Init the connection to SCOM srv
#################################
if(-not (Get-pssnapin | Where-Object {$_.Name -eq "Microsoft.EnterpriseManagement.OperationsManager.Client"}))
    {
    Add-PSSnapin Microsoft.EnterpriseManagement.OperationsManager.Client
    }  
new-managementGroupConnection -ConnectionString:$RMS
Set-Location "OperationsManagerMonitoring::" -ErrorVariable errSnapin ;
Set-Location $RMS -ErrorVariable errSnapin ;   

##########################
#Agent installation
##########################
#Creating the computers list
$ComputersList  = @()
$ComputersList = Get-Content $myFile

#Define a WindowsDiscoveryConfiguration
$discoConfig = New-WindowsDiscoveryConfiguration –ComputerName: $ComputersList –PerformVerification: $true -ComputerType: "Server" #–ActionAccountCredential: $creds

#Start the discovery process.
$managementServer = Get-ManagementServer | Where-Object {$_.PrincipalName -like "*$MS*"}

$discoResult = Start-Discovery –ManagementServer: $managementServer –WindowsDiscoveryConfiguration: $discoConfig

#Check that the discovery process discovered the Windows computers you specified.
$discoResult.CustomMonitoringObjects

if($discoResult.CustomMonitoringObjects -ne $null)
    {
    Write-Host "Agent installation in progress..."
    Write-Host ""
    Install-Agent –ManagementServer $managementServer –AgentManagedComputer $discoResult.CustomMonitoringObjects

    Write-host "Installation Finished, waiting for 60 secondes"
    Start-Sleep -s 60
    }
else{
    Write-Host "No servers discovered"
    }  

####################################################################
#We have to check if all the agent has been well installed + Maintenance mode
#####################################################################
Write-Host ""
Write-Host "Installation Checking"
Write-Host ""

$InstallArray = @()
foreach($srv in $ComputersList)
    {
    $Value = $null
    $Value = Get-agent | Where-Object {$_.ComputerName -like "*$srv*"}
   
    if($Value -ne $null)
        {
        Write-Host "$srv - Agent installed "
        $InstallTime = $Value.InstallTime
        $HealthState = $Value.HealthState
        $AgentInstalled = $true
       
        #Write-Host "Activation of the Maintenance Mode"
        #Put the server in Maintenance Mode
        if($MaintenanceModeEnable -eq $true){SetToMaintenanceMode $RMS $srv $MaintenanceModeDuration $comment $reason}
       
        }
    else{
        Write-Host "$srv - Agent not installed"
        $AgentInstalled = $false
        $InstallTime = ""
        $HealthState = ""
        }
   
    $obj = New-Object PSObject
    $obj | Add-Member Noteproperty -Name "Name" -Value $srv
    $obj | Add-Member Noteproperty -Name "AgentInstall" -Value  $AgentInstalled
    $obj | Add-Member Noteproperty -Name "InstallTime" -Value  $InstallTime
    $obj | Add-Member Noteproperty -Name "HealthState" -Value  $HealthState
    $InstallArray += $obj
    }

Write-Host ""  
Write-Host "Save the Result File"  

$InstallArray  | Export-Csv "$ResultPath\$(get-date -uformat '%Y-%m-%d_%Hh%Ms%S').csv"
Stop-Transcript
]]> http://www.leveilleur.net/index.php/2010/01/20/opsmgr-scom-automatic-agent-deployment-with-powershell/feed/ 0 Quoi de neuf dans SCOM R2 http://www.leveilleur.net/index.php/2010/01/14/quoi-de-neuf-dans-scom-r2/ http://www.leveilleur.net/index.php/2010/01/14/quoi-de-neuf-dans-scom-r2/#comments Thu, 14 Jan 2010 06:01:55 +0000 Christopher Keyaert http://www.leveilleur.net/?p=277 Voici une vidéo en Français expliquant les différences entre SCOM 2007 et SCOM 2007 R2 :

Source

]]> http://www.leveilleur.net/index.php/2010/01/14/quoi-de-neuf-dans-scom-r2/feed/ 0 SCOM2007R2 : not enough entropy when installed Linux Agent http://www.leveilleur.net/index.php/2009/12/03/scom2007r2-not-enough-entropy-when-installed-linux-agent/ http://www.leveilleur.net/index.php/2009/12/03/scom2007r2-not-enough-entropy-when-installed-linux-agent/#comments Thu, 03 Dec 2009 13:01:32 +0000 Christopher Keyaert http://www.leveilleur.net/?p=270 Here the error message :

1
2
3
4
5
6
7
8
9
10
Generating certificate with hostname="xxxxxxxx"
[/home/serviceb/TfsCoreWrkSpcLinux_REDHAT_5.0_x86_64/source/code/tools/scx_ssl_config/scxsslcert.cpp:198]
Failed to allocate resource of type random data: Failed to get random data - not enough entropy
error: %post(scx-1.0.4-248.x86_64) scriptlet failed, exit status 1


<DataItem type="Microsoft.SSH.SSHCommandData" time="2009-12-03T12:08:30.6908778+01:00" sourceHealthServiceId="91A3B596-F820-6A90-305C-6974DA25966D"><SSHCommandData><stdout>Generating certificate with hostname="xxxxxxx"
[/home/serviceb/TfsCoreWrkSpcLinux_REDHAT_5.0_x86_64/source/code/tools/scx_ssl_config/scxsslcert.cpp:198]
Failed to allocate resource of type random data: Failed to get random data - not enough entropy
error: %post(scx-1.0.4-248.x86_64) scriptlet failed, exit status 1

There are two ways to solve this problem, you can recreate the /dev/random file or do a manual agent install.

For both fixes, clean off the partially installed agent using the commands

  1. rpm -e scx
  2. rm -rf /etc/opt/microsoft/scx

Then if you want to make it so that discovery will work from the wizard use the commands

  1. rm /dev/random
  2. mknod -m 644 /dev/random c 1 9
  3. chown root:root /dev/random

A manual install requires copying the appropriate package from %Program Files%\System Center Operations Manager 2007\AgentManagement\UnixAgents to the Unix\Linux machine and installing it directly.

After fixing the install issue, switch the /dev/random file back to a signed random file using the commands:

  1. rm /dev/random
  2. mknod -m 644 /dev/random c 1 8
  3. chown root:root /dev/random

Source : http://blog.xplatxperts.com/xplat-xperts/2009/08/opsmgr-cross-platform-discovery-errors.html

]]> http://www.leveilleur.net/index.php/2009/12/03/scom2007r2-not-enough-entropy-when-installed-linux-agent/feed/ 1 SCOM2007 : Jalasoft Xian Io for VmWare Monitoring http://www.leveilleur.net/index.php/2008/11/26/scom2007-jalasoft-xian-io-for-vmware-monitoring/ http://www.leveilleur.net/index.php/2008/11/26/scom2007-jalasoft-xian-io-for-vmware-monitoring/#comments Wed, 26 Nov 2008 10:10:51 +0000 Christopher Keyaert http://www.leveilleur.net/?p=121

Now monitor your network devices and Unix servers directly in System Center Operations Manager 2007 with the latest version of Xian Network Manager! Advanced new features like, device update, network scan task, linkable policy templates are only a few of the many new features in Xian Io. Check out more information and download the free evaluation version to see the power of Xian yourself.

It is possible that your VC is v2.5, our Virtual Center SMP does not support that version by default, but we have developed a patch in order to provide support for this version. Just follow these steps in order to apply it:

1. Download the patch from: http://download.jalasoft.com/pub/patches/JS0176TD/Patch20080711.zip
2. Go to the server where Xian was deployed and stop the ‘Jalasoft Xian Network Manager’ service.
3. Go to the following folder: ‘[program files]\Jalasoft\Xian Network Manager Io\Plugins\Jalasoft.Xian.Plugin.VMwareVirtualCenter\resources\’
4. Replace the ‘Jalasoft.Xian.Plugin.VMwareVirtualCenter.config.xml’ file with the recently downloaded.
5. Start the ‘Jalasoft Xian Network Manager Server’ service.
6. Open the Xian console and try discovering your virtual centers. Please note that discovering a VC could take several time (depending on the amount of ESX servers hosted in it), so it is recommended to increase the ‘timeout’ and  ‘maximum number of retries’ parameters on the execution of the discovery rule.

]]> http://www.leveilleur.net/index.php/2008/11/26/scom2007-jalasoft-xian-io-for-vmware-monitoring/feed/ 0 SCOM2007 : Installation de Operations Manager 2007 http://www.leveilleur.net/index.php/2008/11/26/scom2007-installation-de-operations-manager-2007/ http://www.leveilleur.net/index.php/2008/11/26/scom2007-installation-de-operations-manager-2007/#comments Wed, 26 Nov 2008 09:13:13 +0000 Christopher Keyaert http://www.leveilleur.net/?p=87 Hello,

Comme promis, voici la suite de l’article sur l’installation de Microsoft System Center Operations Manager 2007.
Au préalable, vous devrez avoir un server Microsoft SQL Server 2005 fonctionnel.

Installation de la partie SQL pour Microsoft System Center Operations Manager 2007

Cette partie est donc à réaliser sur le Microsoft SQL Server 2005 que vous avez préalablement installé.

Installation du server Microsoft System Center Operations Manager 2007

Cette partie est quant à elle a réaliser sur le serveur que vous souhaitez utiliser pour Operations Manager 2007.

=> Install Operations Manager 2007

http://www.microsoft.com/downloads/details.aspx?FamilyID=D21C292C-368B-4CE1-9DAB-3E9827B70604&displaylang=en

=> Après l’installation de MSXML 6.0, vous devez à nouveau relancer l’installation
=> Install Operations Manager 2007

=> On se trouve donc avec une erreur, comme quoi l’on a pas réussi à passer les Prerequisite.

ASP.NET 2.0 is required.
=> Pour ce faire, il suffit de l’installer depuis le add/remove programs et après celui, il faut enregister le ASP.NET

To register ASP.NET:

1. In a command prompt, change directory to %WINDIR%\Microsoft.net\framework\V2.0.50727
2. Type « aspnet_regiis.exe -i -enable » to re-register ASP.NET 2.0

=> On peut reprendre l’installation

Et voilà votre installation terminée :)

]]> http://www.leveilleur.net/index.php/2008/11/26/scom2007-installation-de-operations-manager-2007/feed/ 0 SCOM2007 : Installation de Sql Server 2005 http://www.leveilleur.net/index.php/2008/11/24/scom2007-1-installation-de-sql-server-2005/ http://www.leveilleur.net/index.php/2008/11/24/scom2007-1-installation-de-sql-server-2005/#comments Mon, 24 Nov 2008 13:31:27 +0000 Christopher Keyaert http://www.leveilleur.net/index.php/2008/11/24/scom2007-1-installation-de-sql-server-2005/ Voici la première partie du guide d’installation de Microsoft System Center Operations Manager 2007. La première partie consiste à installer Microsoft Sql Server 2005 sur un serveur dédié.

La plupart des screenshoots ci-dessous se passe de commentaires :


 

Install -> Server components, tools, books online, and samples

 

 

 

 

Voici comment installer Microsoft Sql Server 2005.
Le second article sera quant à lui consacré à l’installation de Microsoft System Center Operations Manager 2007 en lui même.

]]> http://www.leveilleur.net/index.php/2008/11/24/scom2007-1-installation-de-sql-server-2005/feed/ 0 Scom2007 : Scripts pour Maintenance Mode http://www.leveilleur.net/index.php/2008/11/23/scom2007-scripts-pour-maintenance-mode/ http://www.leveilleur.net/index.php/2008/11/23/scom2007-scripts-pour-maintenance-mode/#comments Sun, 23 Nov 2008 16:41:21 +0000 Christopher Keyaert http://www.leveilleur.net/index.php/2008/11/23/scom2007-scripts-pour-maintenance-mode/ Hello tout le monde,

En tant qu’utilisateur de Microsoft System Center Operations Manager 2007, vous avez déjà certainement été confronté au problème ci-dessous

 A computer agent unexpectedly generates heartbeat alerts after you put it into Maintenance mode in System Center Operations Manager 2007

La description détaillée de cela se trouve sur le site de Microsoft : http://support.microsoft.com/kb/942866

En fait, pour mettre un serveur en Maintenance Mode, il faut mettre en réalité trois objets en Maintenance :

  • Computers
  • Health Service
  • Health Service Watcher

Plutot que de faire cela à la main à chaque fois que vous souhaitez mettre un odirnateur completement en Maintenance Mode, voici deux scripts que j’ai écris.


# ==============================================================================================
#
# Microsoft PowerShell Source File
#
# NAME: StartMaintenanceMode.ps1
#
# AUTHOR: Christopher Keyaert
# EMAIL: christopher.keyaert@ucb-group.com
#
# DATE  : 11/19/2008
# VERSION : 1.0
#
# COMMENT: This script will start the maintenance mode for the specified computer
#
# PARAMETERS: rootMS, computerPrincipalName, minutes, comment, reason
#
#
#
# ==============================================================================================

param($rootMS,$computerPrincipalName,$minutes,$comment,$reason)

Add-PSSnapin "Microsoft.EnterpriseManagement.OperationsManager.Client" -ErrorVariable errSnapin;
Set-Location "OperationsManagerMonitoring::" -ErrorVariable errSnapin;
new-managementGroupConnection -ConnectionString:$rootMS -ErrorVariable errSnapin;
set-location $rootMS -ErrorVariable errSnapin;

$computerClass = get-monitoringclass -name:Microsoft.Windows.Computer
$healthServiceClass = get-monitoringclass -name:Microsoft.SystemCenter.HealthService
$healthServiceWatcherClass = get-monitoringclass -name:Microsoft.SystemCenter.HealthServiceWatcher
$computerCriteria = "PrincipalName='" + $computerPrincipalName + "'"
$computer = get-monitoringobject -monitoringclass:$computerClass -criteria:$computerCriteria
$healthServices = $computer.GetRelatedMonitoringObjects($healthServiceClass)
$healthService = $healthServices[0]
$healthServiceCriteria = "HealthServiceName='" + $computerPrincipalName + "'"
$healthServiceWatcher = get-monitoringobject -monitoringclass:$healthServiceWatcherClass -criteria:$healthServiceCriteria
$startTime = [System.DateTime]::Now
$endTime = $startTime.AddMinutes($minutes)

"Putting " + $computerPrincipalName + " into maintenance mode"
New-MaintenanceWindow -startTime:$startTime -endTime:$endTime -monitoringObject:$computer -comment:$comment -Reason:$reason

"Putting the associated health service into maintenance mode"
New-MaintenanceWindow -startTime:$startTime -endTime:$endTime -monitoringObject:$healthService -comment:$comment -Reason:$reason

"Putting the associated health service watcher into maintenance mode"
New-MaintenanceWindow -startTime:$startTime -endTime:$endTime -monitoringObject:$healthServiceWatcher -comment:$comment -Reason:$reason

Le second, pour arrêter le Maintenance Mode


# ==============================================================================================
#
# Microsoft PowerShell Source File
#
# NAME: StopMaintenanceMode.ps1
#
# AUTHOR: Christopher Keyaert
# EMAIL: christopher.keyaert@ucb-group.com
#
# DATE  : 11/19/2008
# VERSION : 1.0
#
# COMMENT: This script will stop the maintenance mode for the specified computer
#
# PARAMETERS: rootMS, computerPrincipalName
#
#
#
# ==============================================================================================

param($rootMS,$computerPrincipalName)

Add-PSSnapin "Microsoft.EnterpriseManagement.OperationsManager.Client" -ErrorVariable errSnapin;
Set-Location "OperationsManagerMonitoring::" -ErrorVariable errSnapin;
new-managementGroupConnection -ConnectionString:$rootMS -ErrorVariable errSnapin;
set-location $rootMS -ErrorVariable errSnapin;

$computerClass = get-monitoringclass -name:Microsoft.Windows.Computer
$healthServiceClass = get-monitoringclass -name:Microsoft.SystemCenter.HealthService
$healthServiceWatcherClass = get-monitoringclass -name:Microsoft.SystemCenter.HealthServiceWatcher
$computerCriteria = "PrincipalName='" + $computerPrincipalName + "'"
$computer = get-monitoringobject -monitoringclass:$computerClass -criteria:$computerCriteria
$healthServices = $computer.GetRelatedMonitoringObjects($healthServiceClass)
$healthService = $healthServices[0]
$healthServiceCriteria = "HealthServiceName='" + $computerPrincipalName + "'"
$healthServiceWatcher = get-monitoringobject -monitoringclass:$healthServiceWatcherClass -criteria:$healthServiceCriteria

$endTime = [System.DateTime]::Now

"Stopping " + $computerPrincipalName + " maintenance mode"
Set-MaintenanceWindow -endTime:$endTime -monitoringObject:$computer

"Stopping the associated health service maintenance mode"
Set-MaintenanceWindow -endTime:$endTime -monitoringObject:$healthService

"Stopping the associated health service watcher maintenance mode"
Set-MaintenanceWindow -endTime:$endTime -monitoringObject:$healthServiceWatcher

Et voici comment appeller ces deux scripts

Start maintenance mode
 C:\WINDOWS\system32\WindowsPowerShell\v1.0\powershell.exe C:\MaintenanceMode\StartMaintenanceMode.ps1 –rootMS: ‘localhost’ -computerPrincipalName: 'SERVERNAME' -minutes:30 -comment: 'Maintenance Mode' -reason: 'PlannedOther'
Stop maintenance mode
 C:\WINDOWS\system32\WindowsPowerShell\v1.0\powershell.exe C:\MaintenanceMode\StopMaintenanceMode.ps1 –rootMS: ‘localhost’ -computerPrincipalName: 'SERVERNAME'

Voilà, si vous avez des questions, ne pas hésiter à les poser dans les commentaires.

]]> http://www.leveilleur.net/index.php/2008/11/23/scom2007-scripts-pour-maintenance-mode/feed/ 0 Operations Manager 2007 : Some Notification properties that may prove useful http://www.leveilleur.net/index.php/2008/11/06/operations-manager-2007-some-notification-properties-that-may-prove-useful/ http://www.leveilleur.net/index.php/2008/11/06/operations-manager-2007-some-notification-properties-that-may-prove-useful/#comments Thu, 06 Nov 2008 10:47:52 +0000 Christopher Keyaert http://www.leveilleur.net/index.php/2008/11/06/operations-manager-2007-some-notification-properties-that-may-prove-useful/  In addition to the notification properties you are able to add via Settings,Notification from the Administration space for Global notification settings or via the custom formats within your subscription, the list below list some other currently undocumented properties that may prove useful.

]]> http://www.leveilleur.net/index.php/2008/11/06/operations-manager-2007-some-notification-properties-that-may-prove-useful/feed/ 0