Skip to main content

OpsMgr 2012 - DeleteDisabledDiscoverySources

Back again for a short post regarding a resent event I experienced. I have been tidying up my lab to prepare for an upgrade test I have been waiting to complete. Prior to the upgrade I wanted to remove some of the management packs what was targeted to IIS on some of my servers. Usually this is done by:
  1. Create a new ManagementPack (IIS7.disabled.xml)
  2. Create a new group and target it to the newly created MP (IIS7.disabled.xml)
  3. Disable the discovery rules for IIS7 and target the new Group
This should prevent the members of the group to “apply” the managementpack, however the the servers will still show up in views that target IIS7 MP. To remove these objects from the view, we need to run a powershell SCOM-cmdlet called Remove-SCOMDisabledClassInstance. So off I went and loaded the OperationsManager Module in my always open powershell console window and fired off the cmdlet. It threw the usual warning message at me:

image

I sat back and was planning to enjoy my coffee, when this message said hello:

Remove-SCOMDisabledClassInstance : Discovery data has been received from a rule targeted at a non-existent object ID.
Object ID: 172d24e6-1c99-d334-7ac2-ae0c160a4ae9
Rule ID: f6d8a11c-0585-3cc8-ecd3-3a0c34aadad0
At line:1 char:33
+ remove-scomdisabledclassinstance <<<<
    + CategoryInfo          : InvalidOperation: (Microsoft.Syste...nstancesCommand:RemoveSCDisabledClassInstancesComma
   nd) [Remove-SCOMDisabledClassInstance], DiscoveryDataFr...ObjectException
    + FullyQualifiedErrorId : ExecutionError,Microsoft.SystemCenter.OperationsManagerV10.Commands.RemoveSCDisabledClas
   sInstancesCommand


Okay, no problem. I have the IDs for the rule and object. Armed with this I went to work in powershell and came back with nothing. These were not “SCOM-GUIDs”. They are operationsmanager database GUIDs. Not prepared to do raw hacking in my operations database, I went and visited my good friend gOOgle. That didn’t really help much until I discovered this post:

http://myitforum.com/cs2/blogs/momlist/archive/2009/04/06/msmom-re-object-discovery-kj8dggiwa3.aspx

Conclution; Proceed to run the cmdlet a few times and see what happens?
Off I went, and behold after running the command 4 times, it completed successfully:

image

Comments

Post a Comment

Popular posts from this blog

Developing PowerShell modules for REST APIs – Part1

Over the years I have developed different PowerShell modules for different web APIs. I thought it would be a good idea to write a 2 series post about how you could go about to do this. This will be a 2 part blog series where we will run through the entire process of building a module for a REST API. I will try my best to keep this as simple as possible and leave more advanced stuff for a follow up post if the interest is there.What you needDepending on your experience with source control and PowerShell in general, you might want to use GIT or some other software repro for the code. In addition we are going to create a test REST API using the splendid UniversalDashboard PowerShell module created by Adam Driscoll. It is available on the PowershellGallery. Other prerequisites are built-in to Powershell. I will assume that you will be following along using at least PowerShell version 5 or greater.
What is HTTP metods for REST API.The primary or most common HTTP verbs used are POST, GET, PU…

Serialize data with PowerShell

Currently I am working on a big new module. In this module, I need to persist data to disk and reprocess them at some point even if the module/PowerShell session was closed. I needed to serialize objects and save them to disk. It needed to be very efficient to be able to support a high volume of objects. Hence I decided to turn this serializer into a module called HashData.



Other Serializing methods

In PowerShell we have several possibilities to serialize objects. There are two cmdlets you can use which are built in:
Export-CliXmlConvertTo-JSON
Both are excellent options if you do not care about the size of the file. In my case I needed something lean and mean in terms of the size on disk for the serialized object. Lets do some tests to compare the different types:


(Hashdata.Object.ps1)

You might be curious why I do not use the Export-CliXML cmdlet and just use the [System.Management.Automation.PSSerializer]::Serialize static method. The static method will generate the same xml, however we …

Developing PowerShell modules for REST APIs – Part2

This is part 2 of the REST API blogpost. In part1 we successfully setup two REST API endpoints using the UniversalDashboard PowerShell module. In this part we are going to create a simple module that support some CRUD operation against our API. As we are trying to keep things as simple as possible, we will not use any fancy framework (like Plaster) to build our module. We are also going to skip a very important step you should familiarize yourself with, Pester tests. Lets get to it.


The moduleWe will build a module called FilesAPI. The module folder will look like this:



In the functions folder I have already added the 2 helper functions from part 1, Get-AuthorizationHeader and ConvertTo-Base64. The other folders are just placeholders for important stuff like classes, private functions that you do not want to make available for the module consumer and tests for Pester tests. For such a small module that we are going to create, one could argue that it is much easier to just add the functi…