SMS Implementation Analysis

[hectormz]

Hi all,

I'm looking for an inventory, patch management and deployment solution and everything points that SMS is the best choice for this. I've also been told that SMS can do SNMP management.

I have some doubts about buying SMS first of all because of the high (for finance) prices and in case it doesn't do SNMP management, i'll need to buy other $oftware that does the trick.

How does it works? Is it difficult to implement and mantain? Or it is really worthy buying it?

Thanks in advance,

Regards,

-Hector

 

[Yanze]

SMS is great for inventory, patch-management, remote control, software deployment, building custom software/hardware queries against your database ... but SNMP management? It can discover devices via SNMP, there is some sort of Eventlog-SNMP-thing, but that's about it i guess ... (talking about SMS 2.0)

 

[Jpoandl]

I think you talking about Event to Trap Translation. Which is a feature of SMS 2.0:

Event to Trap Translator Overview
Use the Event to Trap Translator for configuring events on Windows NT clients to translate to SNMP trap. You can browse for all the possible events that can be translated to SNMP traps on a client, and you can easily add or remove events from a client configuration. Also, you can use this tool to configure clients individually. The Event to Trap Translator gives you the option to configure one client and then export that configuration to a text file. You can then use this text file with the Remote Configuration Tool, in a package, to automatically configure many clients with the same configuration.

Specified events are translated only while the SNMP service is running (the Event to Trap Translator runs as part of this service). However, if the computer running the Event to Trap Translator is restarted, the Event to Trap Translator also restarts. After restart, the Event to Trap Translator looks at the event log to see if any new specified events have occurred between the time the computer restarted and the Event to Trap Translator restarted. If so, the Event to Trap Translator translates these events.

Added events persist between invocations of the Event to Trap Translator; once added, they remain in the configuration registry until you remove them.

Note The SNMP service must be stopped and restarted on a client after the Event to Trap Translator is installed, or the Event to Trap Translator will not function. The first time the Event to Trap Translator is started, no events are listed because none have been specified.


However, I do not believe that SMS 2003 supports this anymore.

Joseph L. Poandl
MCSE 2003

If your company is in need of experts to examine technical problems/solutions, please check out

http://www.NJCOMPUTERNETWORKS.com

(Sales@njcomputernetworks.com)