Skip to main content

Posts

Showing posts from December, 2011

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

a long time ago, I posted about this stuff... http://marcusoh.blogspot.com/2010/01/listing-group-membership-of-computer-in.html http://marcusoh.blogspot.com/2010/01/listing-group-membership-of-computer-in_06.html both of which were just works in progress... and as it turns out, completely wrong! I ran into this post this morning that simplified what I was doing down to a few lines. here it is: $group = Get-MonitoringObject | Where { $_.DisplayName -eq "YourGroupName" } $MonitoringClass = Get-MonitoringClass -Name "Microsoft.Windows.Computer" $group.GetRelatedMonitoringObjects($MonitoringClass, "Recursive" ) | Select DisplayName source: http://michielw.blogspot.com/2010/12/scom-get-nested-group-members.html

my 15 most popular posts of 2011

in the interest of full disclosure, at some point, blogger or analytics did something... but I wasn't tracking page hits for the majority of the year so it's actually only about the last four months. unfortunately, blogger stats provide limited filtering for dates. I was hoping to have some good information to post something like this. oh well. it'll have to do. :) understanding the “ad op master is inconsistent” alert how to retrieve your ip address with powershell... sccm: content hash fails to match executing batch files remotely with psexec … sccm: client stuck downloading package with bit .tmp files in cache directory misc: netstumbler in vista... outlook 2010 does not successfully book a resource sccm: integrating dell warranty data into configmgr writing event log entries with powershell using preloadpkgonsite.exe to stage compressed copies to child site distribution points list domain controllers with powershell using powershell to replace “find” or “fi

moving to endpoint protection

made the switch this morning to forefront endpoint protection -- or what will be known as system center endpoint protection. most of it went okay, but there were a couple of mcafee components that made the process PAINFUL! believe it or not, the antivirus component was not it. the removal of the host intrusion prevention system (hips) and the mcafee agent itself were both more time-consuming than required, each with its own peculiarity. :/   removing hips attempting to remove the hips agent may produce an error about needing to "disable self-protect mode." I am shamelessly stealing this from the site kmit4u because the instructions are quite near perfect and don't need revising: Click Start , Run , type explorer and click OK . Navigate to: C:\Program Files\McAfee\Host Intrusion Prevention\ Double-click McAfeeFire.exe . Click Task , Unlock User Interface . Type the unlock code, and select Administrator Password . NOTE: By default, the unlock code is abcde12345