Collaboration, Search, Extranets, and Internal Communications Built on SharePoint and Microsoft 365

Author: Dave Wolf (Page 2 of 5)

"I help companies improve collaboration, knowledge management, and internal communications through systems based on Microsoft SharePoint. Do you need help making your investment in SharePoint pay off? Contact me - I can help you!"

Have a Wingman for Outages and Major Issues

“…simple truth is that you cannot troubleshoot and do the administrative stuff simultaneously. You’re good, but no one is that good.”

It’s 11:30 and you’ve dozed off in front of the TV on a Saturday night when your phone goes off – another callout.

It’s IT Operations on the horn and there’s a problem with one of your Production systems.

You think, “Oh, God, not again.”

You hook up the laptop, call in to the bridge, VPN to the network, and start sniffing around.

Definitely, the system is down and it doesn’t look like a quick fix will bring it back. This is going to be an all-nighter.

First things first – depending on your company or client, there is a notification protocol and you quickly assess you are going to need other resources to help troubleshoot and then fix the system.

The simple truth is that you cannot troubleshoot and do the administrative stuff simultaneously. You’re good, but no one is that good. You need help with the administrative aspects of managing an operations incident. You need a wingman.

Do not be bashful – engage the Operations person to help with the administrative components. Get them to take notes. Have them page out other people.  If that is not “in their contract” get another member of your team to help you.  If no one else is available, then get your Service Delivery Manager out of bed. This is an outage and whatever it takes is what is needed – all hands on deck!

As you work the issue, have your wingman send out notification emails. Ask them to call the business representatives if the outage will affect end users. Have your wingman look at things you cannot look at while you are in the thick of troubleshooting – logs on other servers; logs and reports on monitoring systems (SCOM, SPLUNK, Open View, Idera, etc.). If you need a break or your wingman has stronger skills investigating the issue at hand, trade roles.

Don’t be a hero. If you’ve been going at hit for an hour or two and haven’t gotten the system back up, take a break and let your wingman take the lead. There is no “I” in team.

Be Prepared!

The Boy Scout motto “Be Prepared!” is a good for IT problem solvers.

Be prepared for issues to occur at the least opportune of times and under the least desirable of circumstances.

If your contact lists are in SharePoint and SharePoint is down, you are in a heap of trouble, son.

Keep your information in SharePoint, sure, but also make hard copies of lists and keep them with you. Put copies in the glove compartment of the car.  Put soft copies in a secure place (OneDrive, for example) so you can get to them while traveling or enjoying an evening out.

 

Is Ignite Too Big?

 

ignite_conf_2017

Is the Ignite Conference too big?

Sure, there’s benefit by combining several different disciplines into one large conference, but there’s a big downside – especially for smaller support organizations.

You can’t have your support people at a conference and minding the store simultaneously!

If you’ve got your messaging and SharePoint and SQL and…  personnel at the conference, how deep is your bench if you run into operational issues?

What about timing with releases, patching, and such for the organization that you support?

And what if the organization (consider outsourced support) has a contingent at the conference, too?

Chicago was a logistical nightmare. A technical conference must be tightly confined for attendees to mix and match without having to grab a cab to attend a desired session.

Maybe Atlanta will be the last experiment at such large convergence. We shall see!

What do you think?

Office 365 ‘App Model’ rename cheat sheet – old booze in new flasks

Check out Jeremy Thake’s cheat sheet with new names for the confusing SharePoint and Office “apps.”

Jeremy Thake

Sophisticated solutions developed by ISVs are in a different league than a hobby project app available from the Office Store.

No question, this created problems justifying a few hundred grand for a year-long effort when the CIO sees the plethora of  ‘free’ and low-cost apps in the Office Store.

Read Jeremy’s full post for more insight and community comments.

 

Here’s the cheat sheet if you’re in a rush:

Apps for SharePoint (old) SharePoint Add-ins (new)
App Web Add-in Web
App Part Add-in Part
SharePoint App Model SharePoint Add-in Model
Apps for Office Office Add-ins
Office App Model Office Add-in Model

 

Ignite Conference Breakouts on Channel 9

ignite_2015

If you overbooked and missed a session, or that guy behind you with the post-nasal drip drowned out the speaker, here’s your chance to catch up!

https://channel9.msdn.com/Events/Ignite/2015

PLUS! Vlad Catrinescu  published a script to download and neatly organize the videos and PowerPoint decks from the conference. Thanks, Vlad.

https://gallery.technet.microsoft.com/all-the-Ignite-Videos-and-b952f5ac

« Older posts Newer posts »