SfB Default AD Containers

Scenario

You know how those tin-foil-hat types are…

If it can be changed to “enhance” security, then by golly!  Let’s do it!  The problem, of course, is the rule of unintended consequences.  You know, what happens to something else because of action A, that is totally unplanned, and no one knows about it.

And, while I am mentioning it… have you ever noticed that the same team YOU have to run everything through for approval never asks your team if it is OK if they make a change?  They just do it?  Odd how that works out, eh?

Adelante.

The Oops!

It turns out that about 6 weeks ago, the aforementioned team instituted a change to the default AD containers.  To whit, they changed the default computer container to be something other than the OOBE.

Turns out that breaks SfB big time.  As in no more publishing the topology.  A Get-CsAdDomain fails.  But that is the clue to the fix.

The Fix

Simply run the SfB Domain prep again.

YMMV

Technical Consulting

Something went through both of my brain cells today. And to keep a long story short, it centers on your approach to the question – whatever the question might be at the moment. But, let’s confine the definition to work, where we spend a goodly portion of our life, and how we would like that portion of life to be as good as possible.

I was listening to a hotshot answer what I narcissistically thought was a great question when the light bulb lit. His answer was not only covering the technical aspects that I needed to hear that he knew, but he was (quite cleverly) also feeding in the business angle aspects to the answer formula. In essence, he was answering my follow-on questions of “what is the business reason for taking this action and does this action resolve the situation with the minimum staff adjustments in terms of time and skill set and did you cover the hidden costs as well as storage, cpu, ram, racks, et cetera.”

In short, he was doing really well answering my question. And I know he was the same in front of the customer. Everyone needs to have this guy on the team.

At any rate, the light bulb lit up on the concept of technical v consulting answers. Mr. Hotshot could have stuck with the pure techno-babble, with lots of numbers, specifications, descriptions of how to do it, and all of that fun stuff. Surely, there is great value in having someone know exactly how to do whatever it might be right off the top of his or her head. I wish I could do that sometimes. I usually revert to being able to point them right at some reference work. Works for me. And reserves my spare brain cell for other things.

Details are critical to our success. Mr. Hotshot was clearly in the right spot – he can bang out the details like no-one’s business. And he knows what he does not know. And he knows how to defer the question to an issue parking lot for follow-up. Perfect.

Mr. Hotshot could also have just gone the technical route and ignored the consulting aspects until asked. All the logistics questions and staff and culture type stuff could have waited. There is some tremendous value in knowing all of that stuff even if at first glance it does appear to out of scope for our project. After all, “how is lunch served around here?” is an important project scheduling point.

But more to the point, what about using those consulting skills to identify architectural detail about the environment, impact to the project (and affecting the defining business goals/requirements) and perhaps dredge up more business? Gees. That sounds awful salesy huh? How about the idea that the design might need to change in mid-project? There is a benefit to having your very own in-house consultant, eh?

We have two approaches to doing what we do. You can be deep technical. You can dive in deep. I know a guy that you can call at almost any hour and pose some bizarre Active Directory or Registry question. Just be prepared to scribble fast because there is no way you will remember the details the forthcoming answer will encompass – but it is going to answer your issue. He knows some serious technical depth stuff.

But you can go too deep and lose your audience. What we do must be tailored to the audience. If a business decision maker is in the room, then you better be including that person in your audience profile. The technical team can wait a bit while you fill in their boss with the business details stuff and make his staff look like they were all over it from the beginning.

In our work, I see a real-life need for a consultant who can get into the technical errata, be able to walk and talk at the same time, and discuss business to the extent of your understanding; all of that without getting into even minor prevarication or truth stretching.

And here is our intrepid Mr. Hotshot fieldling my question tree with answers that meld the technical with the consulting. “Choices made for these reasons which tie to this technical answer and so on to this business requirement.” Or “we discussed the need for expanded storage” and “I expressed my concern that the network might not support the technical solution.” I know he gave those same answers to the customer and guess who was in the room? The customer’s CIO. And Mr. Hotshot is giving me answers like that. The conclusion should be obvious.

We have more work coming from that customer. That makes your work life better.

YMMV

Elevator Pitches

There I was eating dinner. A popular activity in my house. This evening was more involved as my wife had a friend in from out of town; this results in the whole event being more structured than the normal goat rope that passes for a meal. Ribs. Check. Mac n Cheese (homemade you clowns, not that box stuff). Check. Corn on the cob. Check.

Sit down, make some small talk while dishing stuff up. Our guest had a strap-hanger so I am trying to be nice (Yes, me, being nice. And no Matilda, hell did not freeze over). Eventually you get past weather, drive times, fashion, weather (again), and food; the conversation needs to address larger items in life like “…and what do you do?”

When that question comes up, and it ALWAYS does, are you prepared? Actually, there are several levels to this question. The first is the concept of “initial impressions” which unfortunately for some of us makes and breaks things. Sometimes there is simply no getting over that first impression. My econ prof used to say “corporate America does not hire Beavis and Butthead” – and while I think that needs to be modified for portions of the west coast, that statement is mostly true. I encourage reflection on how you present yourself and how that presentation might be affecting your life. OK, back to dinner.

Remember that we are chowing down on some good eats, generally having a great time. Do you really know who is who in your initial circle, and possibly the next few layers out? Do you understand the concept of six degrees of separation (and here also)? I will wait right here for you to read up on that.

We are at the moment of truth; out comes The Question. Communications Engineer says I. I get the expected response which is “what is that” and I get to give my little spiel about helping companies envision, design, architect, and implement collaboration solutions [Note: not a word about Microsoft or Cisco, or whoever at this point]. This gets me several questions about the difference between design and architecture; how long have you been doing this, et cetera. Around this point in time I start wondering whether or not this person is simply bright, engaging, and well-rounded, or is simply great at small talk.

Or it could be the OTHER ANSWER. In MY house and at MY dinner table. I will wait while you go back and re-read the six degrees thing up there.

Now it is MY turn to ask The Question. Oh my. It was the OTHER ANSWER. Sitting at my table was the executive admin to a notable international private investment firm. Oh man. I sure hope I did not do anything. This person has the private ear of the entire executive staff – you know, those folks who make business decisions. For like 16 years. Clearly this person swings a big bat. What I did and said might well result in either a welcome reception or locked doors for our sales team.

Let’s review the bidding. Initial impressions count more than you think. Maybe not fair, but it is what it is. You need to have an “elevator pitch” prepared (and practiced!). You need to be thinking through follow-on questions. You may need several versions to cover various life situations. I have the social version and the 9-5 version. You can guess as to which one I used at dinner.

Everything we do counts. We are all in sales at one point in time or another. Everyone we meet and communicate with (any medium) forms an opinion about you, your work, family, and overall value. Bottom line? Be prepared. I learned long ago (1975) that you are always on, and that you can never tell when you might need to turn it up a notch.

YMMV