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

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
192.168.1.101
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 …