Skip to main content

listing the group membership of a computer in opsmgr [part 2]

yesterday, i posted an entry about retrieving a computer’s membership through a very backwards way that i cobbled together.  after talking to pete zerger for a little while, i started poking into how to make boris’ script work.  it was initially only pulling back two groups for me.

well, i managed to increase that count to six.  however, my output and boris’ still doesn’t match up.  it could be an incorrect root class, i’m using.  either way, i wanted to post it to see if you guys could direct me to a better solution.  who knows?

since you can’t seem to use an abstract class directly in boris’ script, i modified it a bit to first get the abstract class object using get-monitoringobject and then pull out the objects into an array.  afterwards, that array is fed into the get-monitoringclass cmdlet.  at that point, we should have a pretty good set of objects we can use.

those objects are sent back down the pipe to get-monitoringobject using the criteria of $computerFQDN to create a new array called $subClasses.  that array is sent down the pipe to finally run the lines in boris’ script that handles getting the related objects of $computerFQDN.

take a look over it if you have a chance, and let me know what you see.  here’s some sample output of a domain controller using my script and the edited boris script:

my script -

Agent Managed Computer Group
All Windows Computers
Windows Server 2003 Computer Group
Windows Server Computer Group
Windows Server Instances Group

 

edited boris script -

AD Domain Controller Group (Windows 2003 Server)
Windows Server Instances Group
Windows Server Instances Only Group

 

so you see?  holes.  everywhere.  more playing to do later.  here’s the script:

param($computerFQDN)

$ErrorActionPreference = "SilentlyContinue"

function GetGroupNames($computerFQDN)
{
$containmentRel = Get-RelationshipClass -name:'Microsoft.SystemCenter.InstanceGroupContainsEntities'
$abstractClass = Get-MonitoringClass -name:"Microsoft.Windows.ComputerRole"

$subObjects = Get-MonitoringObject -monitoringClass:$abstractClass
$subObjects = $subObjects | ForEach-Object {
$_.FullName.Split(":")[0]
} | Sort-Object -Unique

$subObjects | ForEach-Object {
$subObjects += Get-MonitoringClass -name:$_
}

$criteria = [string]::Format("Path = '{0}'",$computerFQDN)

$subObjects | ForEach-Object {
$subClasses += Get-MonitoringObject -MonitoringClass:$_ -Criteria:$criteria
}

$subClasses | ForEach-Object {
$relatedObjects += $_.GetMonitoringRelationshipObjectsWhereTarget($containmentRel,`
[Microsoft.EnterpriseManagement.Configuration.DerivedClassTraversalDepth]::Recursive,`
[Microsoft.EnterpriseManagement.Common.TraversalDepth]::Recursive)
}

foreach($group in ($relatedObjects | Sort-Object SourceMonitoringObject -Unique))
{
$group.SourceMonitoringObject.DisplayName
}

}

GetGroupNames $computerFQDN

Comments

Popular posts from this blog

using preloadpkgonsite.exe to stage compressed copies to child site distribution points

UPDATE: john marcum sent me a kind email to let me know about a problem he ran into with preloadpkgonsite.exe in the new SCCM Toolkit V2 where under certain conditions, packages will not uncompress.  if you are using the v2 toolkit, PLEASE read this blog post before proceeding.   here’s a scenario that came up on the mssms@lists.myitforum.com mailing list. when confronted with a situation of large packages and wan links, it’s generally best to get the data to the other location without going over the wire. in this case, 75gb. :/ the “how” you get the files there is really not the most important thing to worry about. once they’re there and moved to the appropriate location, preloadpkgonsite.exe is required to install the compressed source files. once done, a status message goes back to the parent server which should stop the upstream server from copying the package source files over the wan to the child site. anyway, if it’s a relatively small amount of packages, you can

How to Identify Applications Using Your Domain Controller

Problem Everyone has been through it. We've all had to retire or replace a domain controller at some point in our checkered collective experiences. While AD provides very intelligent high availability, some applications are just plain dumb. They do not observe site awareness or participate in locating a domain controller. All they want is the name or IP of one domain controller which gets hardcoded in a configuration file somewhere, deeply embedded in some file folder or setting that you are never going to find. How do you look at a DC and decide which applications might be doing it? Packet trace? Logs? Shut it down and wait for screaming? It seems very tedious and nearly impossible. Potential Solution Obviously I wouldn't even bother posting this if I hadn't run across something interesting. :) I ran across something in draftcalled Domain Controller Isolation. Since it's in draft, I don't know that it's published yet. HOWEVER, the concept is based off

sccm: content hash fails to match

back in 2008, I wrote up a little thing about how distribution manager fails to send a package to a distribution point . even though a lot of what I wrote that for was the failure of packages to get delivered to child sites, the result was pretty much the same. when the client tries to run the advertisement with an old package, the result was a failure because of content mismatch. I went through an ordeal recently capturing these exact kinds of failures and corrected quite a number of problems with these packages. the resulting blog post is my effort to capture how these problems were resolved. if nothing else, it's a basic checklist of things you can use.   DETECTION status messages take a look at your status messages. this has to be the easiest way to determine where these problems exist. unfortunately, it requires that a client is already experiencing problems. there are client logs you can examine as well such as cas, but I wasn't even sure I was going to have enough m