Skip to main content

Microsoft Azure Tour in Atlanta

Sometimes I wonder about the effectiveness of Microsoft’s marketing engine. At any rate, if you haven’t already heard, the Azure Tour is happening right now. Atlanta’s turn is up this week, Thursday, 1/14/2016.

Still getting caught on up Azure?
Have some burning questions you need answered from experts?

It’s not too late to attend! Details below.


The Microsoft Azure Tour provides a free one day technical training event for IT professionals and developers to help you be more successful in using cloud.

Our top engineers from Redmond and independent experts from around the world will present 12 technical sessions and 3 unique hands-on opportunities covering the breadth of the Azure platform and the wealth of developer features including security, networking, big data, storage, identity, web, mobile, hybrid, containers, DevOps, open source, management, and the Internet of Things.

Featured speaker:  James Staten – General Manager of Cloud and Enterprise Strategy, Microsoft

Date
Thursday, January 14, 2016

Venue
Hyatt Regency Atlanta
265 Peachtree Street NE
Atlanta, Georgia, USA, 30303

Meals
Continental breakfast, lunch and coffee breaks.

Registration
Registration opens at 7:30am. A reminder e-mail will be issued on December 29 with details.

https://microsoft.eventcore.com/azuretour/atlanta/auth/login#/

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