Skip to main content

march user group follow-up …

in case you missed it, we tried something new (to us … but of course, not to the rest of the world.)  we streamed the entire user group meeting incorporating in person attendees, in person presenters, virtual attendees and virtual presenters!

it was really cool.  as with every user group, microsoft has continued to support us by providing the facilities and equipment to make it happen.  this time, they threw in a microsoft roundtable conferencing device, which made the experience that much cooler.  not to mention, they brought a lot of awesome swag to give away.

systemcentercentral.com was instrumental in getting this show going.  they helped secure a sponsor: prowess.  many thanks to rory and pete.  prowess came in, did a short demonstration on smartdeploy, and fed everyone a trough of barbeque – which i hear was quite good. :)  o’reilly has been a long time sponsor supplying books for giveaways and for review.

anyway, this is just a post to direct you to material which we saved from 71839495 the meeting.  since we broadcasted the event, we were able to capture the entire thing.  so instead of –just- slide deck, we have the audio/video stream as well.  instead of  supplying links, we decided to take a smarter, simpler approach and place hyperlinks to the material in the original agenda.  instead of a start/end time field, you’ll find links to the livemeeting and slide deck per presentation (as they’re available).  you can find it all at www.atlsmug.org.

so what’s all this mean?  well, if you couldn’t make it physically, you had the option of being there virtually.  if you couldn’t make it virtually, you have the option now of viewing all the material you missed.

of course, if you weren’t there physically, you didn’t get to see all the giveaways.  as i was arranging things, it started getting pretty difficult 71861046to find empty space on my desk.  we had a pile of books from ed wilson.  i chased him down after his presentation to get him to sign all four of them.

he was more than happy to do it.  the funny thing was he got into a conversation with garth and was totally derailed.  i think he remembered i was standing there (eventually) with what felt like a ton of books -- about 5 minutes later.  the guy is passionate about what he does.  can’t blame him for that although it did remind me of one of my mom’s favorite forms of punishment growing up – standing in the corner, holding up a couple of encyclopedias.  <3  that’s another story.

all the books went quickly, especially the autographed ed wilson encyclopedias.  we had a couple of copies of windows 7 to give away, some office 2007 standard, and an arc mouse.  in that pile of stuff, we had money clips, courtesy of silect software, ball and paddle from securevantage, and a load of stuff from microsoft.  they really delivered on the goods!  everyone who attended got an led book light… and a green and black laptop bag.  those are the ones under my desk.  it was pretty cool.

can’t guarantee it’ll always be like that… but it’s great to share when it is.  hope you all enjoyed it as much as i did!  see you at the next one.  spread the word to your friends!

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