Skip to main content

how to properly target machines with the dfs management pack

Bull's-eye

Image by GravitysAppleNZ via Flickr

if you’re planning to install the microsoft windows dfs 2003 management pack (yes, the converted one), you should be certain to target properly.  if you don’t, you’ll end up with some trash data coming from other dfs sources (e.g. domain controllers) that you may not want in your dfs views.

i spent a disproportionate amount of time on this to figure out all the ins and outs of targeting inside of this mp.  i would love to say it was for my edification, but in actuality, it was because the agents apparently didn’t work right until they were restarted.  :|

anyway, so the bottom line is, it was much easier than what i describe in this post on system center central.  it may still be confusing to others however so i’m posting it here.

the first thing you’ll want to do is create a new group.  there isn’t much to do here except target your members properly.  i used something like this to target a few of my dfs servers.  specifically, i’m using the mom 2005 backward compatibility windows server target since this is the target that one of the discovery rules uses later.

image

 

once that’s setup, open the object discoveries section.  to make it simpler, change your scope to microsoft windows 2003 servers with distributed file system service installation.

you should find this discovery -

Microsoft.Windows.Server.DFS.Microsoft_Windows_2003_Servers_With_Distributed_File_System_Service_Installation.Discovery

- targeting the mom 2005 backward compatibility windows computer object.

image

 

this is the rule that you want to override.

  • right-click the rule
  • go to overrides > override the object discovery > for all objects of class: mom 2005 backward compatibility windows computer
  • once open, choose override on the enabled parameter and change the override value to “false”.
  • be sure to add this to your own, custom management pack.

image

 

now we’ve effectively blocked the discovery from executing against the class above (which subsequently includes damn near everything).  before you go anywhere, let’s create another override. 

  • overrides > override the object discovery > for a group…
  • choose the group that you created prior.  the override value probably shows up as “true” already so this may appear counterintuitive.
  • select the override anyway.
  • again, add this to your own custom mp.

image

 

if done right, you should only see the dfs servers you targeted in the custom group you created.  here’s how mine looks:

image

 

hope this helps!

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