O R G A N I C / F E R T I L I Z E R: 12.11

Dec 28, 2011

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

a long time ago, I posted about this stuff...


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

Dec 27, 2011

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. :)

  1. understanding the “ad op master is inconsistent” alert
  2. how to retrieve your ip address with powershell...
  3. sccm: content hash fails to match
  4. executing batch files remotely with psexec …
  5. sccm: client stuck downloading package with bit .tmp files in cache directory
  6. misc: netstumbler in vista...
  7. outlook 2010 does not successfully book a resource
  8. sccm: integrating dell warranty data into configmgr
  9. writing event log entries with powershell
  10. using preloadpkgonsite.exe to stage compressed copies to child site distribution points
  11. list domain controllers with powershell
  12. using powershell to replace “find” or “findstr”
  13. how to synchronize sticky notes in windows 7
  14. sccm: custom data discovery records (DDRs) using powershell
  15. preloadpkgonsite generates failed to get specified package in database errors

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:

  1. Click Start, Run, type explorer and click OK.
  2. Navigate to: C:\Program Files\McAfee\Host Intrusion Prevention\
  3. Double-click McAfeeFire.exe.
  4. Click Task, Unlock User Interface.
  5. Type the unlock code, and select Administrator Password.
    NOTE: By default, the unlock code is abcde12345
  6. After the user interface is unlocked, click the IPS Policy tab. 
  7. Deselect Enable Host IPS and Enable Network IPS. (The Firewall Policy can be disabled on its own tab.)
  8. Select Task, Exit.
    Credit: Knowledge Management IT for you: How to disable the Host Intrusion Prevention(IDS) Mcafee disable self-protect mode
    Under Creative Commons License: Attribution

after following those steps, i was able to remove the hips agent!


removing the mcafee agent

while attempting to remove the mcafee agent, it kept telling me that "other products are still using it." uh no. I removed all other products! here's how you force it:

  1. open up a cmd prompt.
  2. navigate to the directory where frminst.exe is located. generally this is in the "common framework" directory of mcafee.
  3. run the following:

frminst.exe /forceuninstall

now, smile happily as you have slain the hideous beast!