Skip to main content

misc: dsquery vs powershell...

as a part of trying to familiarize myself with powershell, i figured converting some of my favorite dsquery commands to it would be as good of a measure as any. the problem was, i had a hell of a time figuring it out! thankfully, hal was nice enough to help out... in order to get displayname and streetaddress from dsquery, you'd use a command like this:
dsquery user -samid myUser | dsget user -display
oh wait a second... there is no switch for streetaddress. all you'll get is something like this:
  display
  My User (Test)
let's try that again...
dsquery * -filter "(&(objectcategory=person)(samaccountname=myUser))" -attr displayname streetaddress
in my case, i have multiple lines in my streetaddress attribute, which throws off the entire format. this is something i wanted to avoid so i seeked powershell as the answer (instead of writing a vbscript to handle it.)
  displayname                 streetaddress
  My User (Test)              2000 My Test Avenue
Suite 200
here's how you'd pull the information from powershell (providing you use the quest add-ons)...
get-qaduser testdomain\myUser | format-table displayname,streetaddress

DisplayName                                  StreetAddress
-----------                                  -------------
My User (Test)                               2000 My Test Avenue...
already much better. however, the street address is truncated. so let's try again.
get-qaduser testdomain\myUser | format-table -wrap displayname,streetaddress
now we get the full street address, but as you can see, the cr/lf is carried over. to get rid of it, we'll insert a replace statement.
DisplayName                                  StreetAddress
-----------                                  -------------
My User (Test)                               2000 My Test Avenue
                                             Suite 200
get-qaduser testdomain\myUser | format-table -wrap displayname,@{label = "StreetAddress";expression = {$_.streetaddress -replace "`n",", "}}
resulting in this much nicer formatted version...
DisplayName                                  StreetAddress
-----------                                  -------------
My User (Test)                               2000 My Test Avenue, Suite 200

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