Skip to main content

comparing home directories to user names with powershell

aside from just enjoying scripting, i particularly love scripting requests that start with something like -- “i want to know if this is possible…”.  my coworker put it best about why scripting is enjoyable.  it has a definite start and (usually) a definite end.  it comes with a sense of accomplishment when you’re done.  that’s nice.  kind of like… building a birdhouse or something.

anyway, the request was to compare a user’s home directory value to the user id to see if the user has the correct mapping.  sometimes while cloning accounts, this process may carry over something undesirable.  pretty simple stuff right?

let’s pretend you have a user named “Reimer Davies”.  his properties are as follows:

  • user id: “ReDavies”
  • home directory: \\myfileserver\redavies$

(yes, i know the mapping is old school home path.  this is what i had to deal with so bear with the example.  you can always change around the text manipulation statements to make it do what you want.)

anyway, here it is.  i wrote it (hopefully verbosely enough) for the requester to follow along.  all i did was split the home directory on the “\” and the “$” to get the exact user id out of it.  the user id itself was simple since it’s just as the value sits.  in the comparison, i dropped both to lowercases to processes it through.  your preference on whether you want to use if/then like i did or switch.  the best part was kicking it out to a custom object so i could push it into a gridview.  the reason this is cool is that i don’t have to write it once to kick out a list of “true” results and then later revise to kick out a list of “false” results.  you know how it goes.  sometimes you don’t know what you want until you see what you don’t want.

pushing it to gridview gives the requester the ability to sort and search as required (in 2.0).  anyway, let me know what you think.

# initialize a boring array for which we will push in user list information
$userListMatches = @()

$users = Get-QADUser -AccountExpiresAfter (Get-Date) -SearchRoot "ou=me,dc=mydomain,dc=com"

foreach ($user in $users) {
$hmdirtext = $user.homedirectory
$userid = $user.samaccountname

# break the user home directory into the user name only by splitting the \
$hmdir = $hmdirtext.split("\")[3]

# user name will still be user$ at this point so break the $ out
$hmdir = $hmdir.split("
$")[0]

# create a noteproperty object so we can use it with grid view
$myUserSet = New-Object System.Object

# add the values to the object
$myUserSet | Add-Member -type noteproperty -Name User -Value $userid
$myUserSet | Add-Member -type noteproperty -Name Home -Value $hmdirtext


# now compare the values
if ($hmdir.ToLower() -eq $userid.ToLower()) {
# add this value when the match is true
$myUserSet | Add-Member -type noteproperty -Name Matches? -Value "
True"
} else {
# add this value when the match is false
$myUserSet | Add-Member -type noteproperty -Name Matches? -Value "
False"
}

# add the userset value to the userlistmatches array
$userListMatches += $myUserSet
}

# now kick out the grid
$userListMatches | Out-GridView

Comments

  1. Get-QADUser -AccountExpiresAfter (Get-Date) -SearchRoot "ou=me,dc=mydomain,dc=com" | where {$_.homedirectory.tolower() -ne "\\myfileserver\" + "$_.samaccountname.tolower() + '$'}

    For a quick count if needed.

    ReplyDelete
  2. Perfect, exactly what I was looking for.

    Thanks for putting this together Marcus!

    ReplyDelete

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

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