Error updating symantec endpoint protection

Now the MP XML will be checked and the output will be written to the output windows below. The output will be: When I want to add a module I could choose to create it in XML (see also my blog on how to enable the MP schema check in VS) but I could also simply use SCOM authoring console , select tools What you have to do is: 1. install the SCOM authoring console AND the Authoring tools so you can use the workflow simulator. So a webserver as frontend and a database as backend. Now we select the 2-tier Application Model and drag & drop it into the document. Now of course we have to specify the targets for the monitors. Just select the My front end role and the My Backend role and change the parameters.If any error is detected it will report also in this window so you can quickly see what’s wrong without leaving VS. Install VSS 2005 if you want to safe you’re work with revisions. The backend will be monitored with a DB watcher and the front end will be having a web site watcher and a performance monitor with an threshold. In this case this will be an discovery based on registry key availability. I want also to monitor one performance counter on the front end role.I say this is a MUST for every MP author USE A SOURCESAFE TOOL!! Of course you must create this registry keys on the servers to let the discovery do his work. We simply drag and drop a performance monitor in to the sheet … normally I hate this word because I like the deep guru stuff….

If any management packs in the Import list are dependent on this management pack, the installation of the dependent management packs will fail. MPInfra_p_Management Pack Install failed with exception: Database error. You open the unsealed MP with any plain text editor you have. Next step is to do a global replace on the text below: Save the xml file.But I think MS is never going to release a updateable version of this MP because they would have to change the internal class names too. Pretty easy stuff for you reading this blog but its not the MP but the Authoring VS extensions that have the focus here. 1) Class type for the Symantec Agent 2) Discovery rule to discover the Symantec Agent 3) Monitor rule for the NT service Check of the Symantec Agent 4) Views to display the Symantec health state. Ill think this will be replaced by an real class create template wizard soon. So said that we open the just created Class MP fragment. Since the best way to discover the Symantec agent is the registry we are going to use a registry key discovery rule. It looks a bit more work but its not so bad at all because most of the properties have filled select lists behind it. After we fill in the common properties as: Display name , ID , Description, we start with the Module – Datasource Type ID . We have to specify the folder in XML: Now we have the folder we are going to create the views.And if you do this the MP will loose its upgrade feature!! And we change the class internal / display name first. So when a windows computer has the Symantec agent on it a new class instance Symantec agent will be created and the product version number will be filled in. Good for us it is a real template so (almost) no need for XML. On the left you will see all the objects created by the templates. Templates – View (Custom) this time we have to use the properties to specify the view configurations. And we specify the View configuration and View Folder.The MP file location will be : and the MP (unsealed) file will be here: At this point you can test the MP with the already super tool Authoring Console with the Work flow simulator. Last step is to import the MP into the SCOM MNG group. If you want a sealed one you must specify in the build tab a certificate. So now you have created your first MP with the new VS authoring Extensions. Next time I will blog more about this new authoring tool. Michel Kamp Tags: Authoring, SCOM, Visual Studio Authoring Console Extensions Hi, As promised I will write 1 blog post a week.

I think I am going to take you guys on the how to create a dashboard widget tour…. This time I will describe a method I used the last 5 years for authoring my management packs.

If you are going to use this solution you have to realize that if Microsoft is updating his “front Unified Access Gateway” management pack you will not be able to upgrade ! To solve this you can uninstall your version and import the MS one. We are going to build an management pack that will discover all your Symantec Agents and monitor the running state of it. All the wizard stuff we where having in the ‘normal’ authoring console is gone. And now we have to type in the registry configuration by using XML. But the most important is of course the configuration of the module type.