Skip to main content

ATLSMUG Meeting 07/22/2016

http://www.atlsmug.org/events/register-now-july-22

 

Hi everyone.

If you’re familiar with Atlanta TechStravaganza, you’re probably used to having seen an announcement by now. Well, we had some logistical challenges this year so it looks like we have to push back until later this summer.

This is typically where we hold our 2nd quarter meetings for ATLSMUG. In the absence of that event, we are moving forward with our own meeting to keep things going. I hope you will find yourself available to join us.

We’ll be back at the Microsoft Alpharetta campus (thank you Microsoft – Jim & crew are great!) looking to start our first presentation at 10 AM and ending around 3 PM. Hopefully this will solve the traffic challenges that I know many of you face getting to the event.

We’ve got some good stuff cooking up – Orchestrator, ConfigMgr, etc. However, if you have any urgent topics, we might still have time to work them in. Just drop us a note at leaders@atlsmug.org. Any other comments, suggestions, topics, etc are welcome, too.

And of course, if you want to be a presenter, we’re always looking for people. It’s a great environment for it! Round-table style presentations, open forum. Get your ideas heard and validated in a meeting of your peers. Great way to practice for larger venues for those of you wanting to break into the presentation circuit.

Where else in Atlanta are you going to get a day of systems management learning for free? With free lunch? And a prize giveaway? Only here, everyone. :)

Hope to see you there!

 

More details and registration -- http://www.atlsmug.org/events/register-now-july-22

 

P.S. Thank you Flexera for sponsoring us!

Comments

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 …