juillet 2009 - Posts
Presque deux mois après la disponibilité de la RTM de la R2 de notre produit de supervision préféré, j’ai le plaisir de vous annoncer sa disponibilité publique par le biais de vos canaux de distribution habituels : revendeurs ou portails de téléchargement (TechNet, MSDN, MVLS etc..)
Pour les impatiens qui auraient déjà installé la version d'évaluation de cette R2, n’ayez aucune crainte puisque la mise à jour de vos infrastructures est pleinement supportée et de surcroit en quelques clics.

Une exellente initiative des développeurs de pack d'administration ! Rentrouvez de nombreuses video et présentation ppt sur leur site:
Le code sources des providers utilisés par les agents CrossPlatform sont disponibles sur Codeplex. Voici de quoi faire vos agents ;).
Rob Kuehfus, nous rappelle les différences possibilités en la matière:
|
Use Case |
Command |
|
Fresh Install and set specific action account |
msiexec.exe /i \\path\Directory\MOMAgent.msi /qn /l*v %temp%\MOMAgentinstall.log USE_SETTINGS_FROM_AD=0 MANAGEMENT_GROUP=<MG_Name> MANAGEMENT_SERVER_DNS=<MSDNSName> ACTIONS_USE_COMPUTER_ACCOUNT=0 ACTIONSUSER=<AccountUser> ACTIONSDOMAIN=<AccountDomain> ACTIONSPASSWORD=<AccountPassword> USE_MANUALLY_SPECIFIED_SETTINGS=1 SET_ACTIONS_ACCOUNT=1 |
|
Fresh Install and use local system as action account |
msiexec.exe /i \\path\Directory\MOMAgent.msi /qn /l*v %temp%\MOMAgentinstall.log USE_SETTINGS_FROM_AD=0 MANAGEMENT_GROUP=<MG_Name> MANAGEMENT_SERVER_DNS=<MSDNSName> ACTIONS_USE_COMPUTER_ACCOUNT=1 USE_MANUALLY_SPECIFIED_SETTINGS=1 SET_ACTIONS_ACCOUNT=1 |
|
Fresh Install with AD Integration and set specific action account |
msiexec /i \\path\Directory\MOMAgent.msi /qn /l*v %temp%mominst.NoGroupSpecified.log USE_SETTINGS_FROM_AD=1 USE_MANUALLY_SPECIFIED_SETTINGS=0 ACTIONS_USE_COMPUTER_ACCOUNT=0 ACTIONSUSER=<AccountUser> ACTIONSDOMAIN=<AccountDomain> ACTIONSPASSWORD=<AccountPassword> SET_ACTIONS_ACCOUNT=1 |
|
Fresh Install with AD Integration and use local system as action account |
msiexec /i \\path\Directory\MOMAgent.msi /qn /l*v %temp%\ mominst.NoGroupSpecified.log USE_SETTINGS_FROM_AD=1 ACTIONS_USE_COMPUTER_ACCOUNT=1 USE_MANUALLY_SPECIFIED_SETTINGS=0 SET_ACTIONS_ACCOUNT=1 |
|
Upgrade from SP1 |
msiexec /i \\path\Directory\MOMAgent.msi SET_ACTIONS_ACCOUNT=0 /qn /l*v %temp%\MOMAgentUpgrade.log |
|
Upgrade from R2 Beta |
msiexec /i \\path\Directory\MOMAgent.msi SET_ACTIONS_ACCOUNT=0 /qn /l*v %temp%\MOMAgentUpgrade.log |
|
Upgrade from R2 RC |
msiexec /i \\path\Directory\MOMAgent.msi SET_ACTIONS_ACCOUNT=0 /qn /l*v %temp%\MOMAgentUpgrade.log |
|
Change Management server name |
MsiExec.exe /i \\path\Directory\MOMAgent.msi /norestart /qn /l*v %temp%\MOMAgentReinstall.log MANAGEMENT_GROUP= <SameManagementGroup> MANAGEMENT_GROUP_OPERATION=ModifyConfigGroup MANAGEMENT_SERVER_DNS=<NewManagementServerName> REINSTALL=ALL |
|
Add new MG |
MsiExec.exe /i \\path\Directory\MOMAgent.msi /norestart /qn /l*v %temp%\MOMAgentAdd.log MANAGEMENT_GROUP=<NewManagementGroup> MANAGEMENT_GROUP_OPERATION=AddConfigGroup MANAGEMENT_SERVER_DNS=<NewManagementServerName> REINSTALL=ALL Note: If fresh install is already AD enabled, then re-homing configuration is set by AD |
|
Remove old MG |
MsiExec.exe /i \\path\Directory\MOMAgent.msi /norestart /qn /l*v %temp%\MOMRemove.log MANAGEMENT_GROUP=<OldManagementGroup> MANAGEMENT_GROUP_OPERATION=RemoveConfigGroup MANAGEMENT_SERVER_DNS=<OldManagementServerName> REINSTALL=ALL
Note: If this is the last MG assigned to this agent the agent will also be uninstalled. Note: If fresh install is already AD enabled, then re-homing configuration is set by AD |
|
Re-Home (remove old MG\MS, redirect to new MG/MS) |
Step 1: Add new management group \ Management server MsiExec.exe /i \\path\Directory\MOMAgent.msi /norestart /qn /l*v %temp%\MOMAgentAdd.log MANAGEMENT_GROUP=<NewManagementGroup> MANAGEMENT_GROUP_OPERATION=AddConfigGroup MANAGEMENT_SERVER_DNS=<NewManagementServerName> REINSTALL=ALL Step 2: Remove old management group \ management server MsiExec.exe /i \\path\Directory\MOMAgent.msi /norestart /qn /l*v %temp%\MOMRemove.log MANAGEMENT_GROUP=<OldManagementGroup> MANAGEMENT_GROUP_OPERATION=RemoveConfigGroup MANAGEMENT_SERVER_DNS=<OldManagementServerName> REINSTALL=ALL
Note: Make sure to add the new management group first before removing the old one. If you remove the old management group first and it’s the last management group assigned to the agent the agent will be uninstalled. Note: If fresh install is already AD enabled, then re-homing configuration is set by AD |
|
USE_SETTINGS_FROM_AD=0 |
Indicates that management group settings properties will be set on the command line. |
|
MANAGEMENT_GROUP=MG1 |
Sets the management group the computer will be managed by to MG1. |
|
MANAGEMENT_SERVER_DNS=MS1.Domain1.net |
Sets the management server fully qualified domain name (FQDN) to MS1.Domain1.net (). To use a gateway server, enter the gateway server FQDN as MANAGEMENT_SERVER_DNS.
|
Important |
|
If the computer's DNS and Active Directory names differ, the MANAGEMENT_SERVER_AD_NAME property also needs to be set to the fully qualified Active Directory Domain Services name. |
|
|
USE_MANUALLY_SPECIFIED_SETTINGS=1 |
Indicates that management group settings properties will be set on the command line. |
|
SET_ACTIONS_ACCOUNT=1 |
Indicates that the default action account will be set on the command line. |
|
SECURE_PORT |
Sets the health service port number. |
|
ACTIONS_USE_COMPUTER_ACCOUNT=0 |
Sets the Agent Action account to a specified user account, instead of to Local System. |
|
ACTIONSUSER=AgentAction |
Sets the Agent Action account to AgentAction. |
|
ACTIONSDOMAIN= Domain1 |
Sets the Agent Action account domain to Domain1. |
|
ACTIONSPASSWORD= Password#2007 |
Sets the Agent Action account password to Password#2007. |
Note: L'ordre des paramètres n'a pas d'importance
Voici une vidéo réalisée lors du dernier MMS dans la halle Ask The Expert, au menu une démonstration des intéractions avec Service Manager le future outil/portail de gestion des incidents.
L'un des scénarios supportés par le nouveau pack d'administration Exchange (natif) est de le faire cohabiter avec l'ancien pack d'administration !
L'idée est de conserver les données collectées par ce dernier. De plus, afin de ne pas être polué il est nécessaire de désactiver l'ensemble de ses règle.
Pour y parvenir, l'equipe produit vous fournit ce pack d'administration non-scéllé.