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!

Labels:

Comments

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
11 comments
more »

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
3 comments
more »

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
3 comments
more »