Skip to main content

Community Roadshow 3.11.2016

Doing something a little bit differently this time. We’ve partnered with Microsoft to bring you timely content on Windows 10! I don’t have a complete schedule yet as we are still bringing in speakers for the event.

Mark your calendars now though and go register so you can get the clearance to show up! March 11, 2016.

At some point, Flatiron City will be a venue which opens up and becomes available for events like these. In the meantime, we’re still hosting out of Alpharetta. All of the details are going to show up here as we put it together.


So what’s different you ask? Well, a few things. First of all, we’re being joined by the Windows Infrastructure and Virtualization User Group as well as the Atlanta PowerShell User Group. Pretty cool, right? If nothing else, you’ll get exposure to the great folks in the other communities here in Atlanta.

Secondly, we typically do a full day meetup. Instead of that format, we are opting with a 12ish to 4ish configuration. Instead of the usual breakfast/lunch scenario, we’re going to do a PIZZA & BEER event! (and maybe some wine if you really want that…)

So bring your appetite for food and knowledge! Look forward to seeing you there. Drop me a personal note if you have any questions. My UG email is


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