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

Labels:

Comments

Post a Comment

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
11 comments
more »

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
3 comments
more »

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
3 comments
more »