Skip to main content

top 20 posts of 2013

these posts represent the most visited pages of 2013. i realize the year is not yet closed… but no one is in the office if our office is any indication. :)

  1. understanding the “ad op master is inconsistent” alert
  2. sccm: content hash fails to match
  3. how to retrieve your ip address with powershell...
  4. how to use dropbox to synchronize windows 7 sticky notes
  5. sccm: client stuck downloading package with bit .tmp files in cache directory
  6. executing batch files remotely with psexec …
  7. sccm: custom data discovery records (DDRs) using powershell
  8. using preloadpkgonsite.exe to stage compressed copies to child site distribution points
  9. sccm: integrating dell warranty data into configmgr
  10. search programs and files no longer works in windows 7 (only shows headers)
  11. "get computer/ip status" activity throws raw socket error
  12. sccm clients fail to apply a policy
  13. list active directory subnets with powershell
  14. dsmod bug when using the –c option?
  15. using repeat count to detect a problem in a window of time
  16. using powershell to list active directory trusts
  17. list domain controllers with powershell
  18. sccm: the required permissions for creating collections
  19. sccm: computers with names greater than 15 characters
  20. scom: overloading the consolidation module (and how to avoid it)

maybe my next post will be how to create this list from analytics. ;-)


Popular posts from this blog

how to retrieve your ip address with powershell...

update: this is how it’s performed in powershell v3 as demonstrated here.(get-netadapter | get-netipaddress | ? addressfamily -eq'IPv4').ipaddress update: this is by far the easiest.PS C:\temp> (gwmi Win32_NetworkAdapterConfiguration | ? { $_.IPAddress -ne $null }).ipaddress
are you laughing yet?  i know you probably find this topic amusing.  it's really interesting though.  whenever you get over it, i'll do this in the standard cmd.exe interpreter and then in powershell to show you what kind of coolness powershell does.done?  okay, good.  this is an interpretation of a demo that bob wells did at our smug meeting.  hope you like it.i should tell you, it's not as simple as the title would lead you to believe.  i like doing that little slight-of-hand thing since it gives the impression that i'm painting a very easy target on my back for your criticism (though it's probably true in other ways)!  the idea is that we want to retrieve just the ip ad…

understanding the “ad op master is inconsistent” alert

i use the term “understanding” loosely.  this is by far no definitive guide on this particular alert, just a few things i have picked up in my attempt to understand it.let’s look at the context of the alert:The Domain Controller's Op Master is inconsitent. See additional alerts for details.
first of all, it gives very little information.  the only particularly useful detail is that it indicates which server is having the issue.  other than that, just a spelling error as there are no additional critical alerts to look at for details.this rule, as you know, comes from a sealed mp.  therefore, we can’t modify anything in it except the overrides.  the couple i’ve tinkered with are:interval (sec) log success event to begin with, interval (sec) is just set way too high.  the default is 60 seconds.  why on earth would anyone want to know that your op master consistency may be off, every minute?  actually, i could think of a few reasons, but really, it’s overkill.  the way the script works…

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.DETECTIONstatus messagestake 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 material to …