P
Ребята,может кто-то вводил мониторинг принтеров Canon и HP через SCOM? можете подсказать что и куда? Интересует мониторинг количества напечатанных страниц и количество тонера, хотя б такое
Size: a a a
2021 August 10
2021 August 11
V
есть православный JetAdmin
V
бесплатный
V
с веб-мордой
D
О, кстати
D
Норм темка
D
Юзал его лет 5 назад
ВЗ
Как не надо писать пакеты управления. HP в этом мастера.
ВЗ
Эти козлы еще и лог Operations Manager засирают. Такое ощущение, что дискавери запускается один раз раз в секунду.
V
эйчпи, эйчпи... делловский MP я с первого раза вообще запустить не смог
k
Может в сторону snmp глянуть?
V
чтобы трахаться с мибами ?
k
Ну почему сразу так жестоко?) Получать удовольствие 😁
V
тут с вендорскими MP бывает, без бутылки результата нет... не хватало еще и мибов
V
я как-то пыталси длинки мониторить... плюнул на это дело и заббикс прицепил
D
snmp в скоме вообще изи же
D
главное дохулиард оидов не хотеть прикрутить
ВЗ
Посоны, у кого нить есть дистриб SCOM 2012 или 2012 SP1?
MS
нашел только такое
MS
This error is logged when a configuration file has been downloaded by a management server or agent and some further validation checks are being carried out.
For this particular error, it is checking the DnsNameOrIp property for the Child Health Services is correctly populated.
To help identify the invalid HealthService entry, run the following SQL.
USE
OperationsManager
SELECT * FROM MT_Computer WHERE NetworkName = ''
If this does not help identify a machine with an empty string for its computer name then you will need to capture a copy of the bad configuration file which you can do with the following steps on a second managment server which is reporting the same issue. To do this use the following method
On your second Management Server, stop the healthservice/System Center Management service.
Rename the Health Service State folder to Health Service State.old.
Then restart the service, watching the OpsMgr event log until you see an event like this
Log Name: Operations Manager
Source: OpsMgr Connector
Date: 04/02/2011 08:38:37
Event ID: 21023
Task Category: None
Level: Information
Computer: <ServerName>
Description:
OpsMgr has no configuration for management group <ManagementGroupName>and is requesting new configuration from the Configuration Service.
Then stop the healthservice once more on this management server.
If you time this well, the configuration file for the management server will be left in the \System Center Operations Manager 2007\Health Service State\Upload Files directory on the Root Management Server after a few seconds/minutes, and that should have the detail you need.
Collect the configuration file, which will be a numbered file without a file extension and open it in an XML editor and examine the Child section for any anomolies.
Resolution
Once you have identified the rogue agent from the configuration file or SQL query above, remove this agent from the managment group and wait for the data to groom out (+48 hours) before reinstallation.
For this particular error, it is checking the DnsNameOrIp property for the Child Health Services is correctly populated.
To help identify the invalid HealthService entry, run the following SQL.
USE
OperationsManager
SELECT * FROM MT_Computer WHERE NetworkName = ''
If this does not help identify a machine with an empty string for its computer name then you will need to capture a copy of the bad configuration file which you can do with the following steps on a second managment server which is reporting the same issue. To do this use the following method
On your second Management Server, stop the healthservice/System Center Management service.
Rename the Health Service State folder to Health Service State.old.
Then restart the service, watching the OpsMgr event log until you see an event like this
Log Name: Operations Manager
Source: OpsMgr Connector
Date: 04/02/2011 08:38:37
Event ID: 21023
Task Category: None
Level: Information
Computer: <ServerName>
Description:
OpsMgr has no configuration for management group <ManagementGroupName>and is requesting new configuration from the Configuration Service.
Then stop the healthservice once more on this management server.
If you time this well, the configuration file for the management server will be left in the \System Center Operations Manager 2007\Health Service State\Upload Files directory on the Root Management Server after a few seconds/minutes, and that should have the detail you need.
Collect the configuration file, which will be a numbered file without a file extension and open it in an XML editor and examine the Child section for any anomolies.
Resolution
Once you have identified the rogue agent from the configuration file or SQL query above, remove this agent from the managment group and wait for the data to groom out (+48 hours) before reinstallation.