1. Is Your SharePoint ReallyHealthy?What’s the Right Prescription? Presented By: Richard Harbridge #SPTechCon @rharbridge

2. Who am I? I

3. Why does this topic matter? We find the issues in SharePoint typically when SharePoint upgrades, new third party components, new solutions and significant changes are made to SharePoint. This results in high costs and greater delays than if many of those issues had been discovered earlier.

4. What we will be talking about… What is a SharePoint Prescription? SharePoint Preventative Care SharePoint Palliative Care SharePoint CurativeCare SharePoint Incident Reporting SharePoint Health Assessments

5. Our Goal Today… From Here To Here

6. What is a SharePoint Prescription?

7. Why do you need a Prescription?

9. They typically contain orders to be performed by patients, caretakers, nurses, pharmacists or othertherapists.

11. It’s a technology-care program implemented by an expertthat governs the plan of care for a SharePoint implementation.

12. It typically contains orders to be performed by patients, caretakers, nurses, pharmacists or othertherapists.

13. It typically contains orders to be performed by system, administrators, developers, architects or other experts.

14. It indicates that the prescriber takes responsibility for the clinical care of the systemand in particular for monitoring efficacy and safety.

16. What to watch out for… Even with an effective prescription you must follow it in order for it to be effective.

17. SharePoint Preventative Care

18. What is Preventative Care? Measures taken to prevent diseases (or injuries) rather than curing them or treating their symptoms. In SharePoint Terms? The pro-active actions you plan for, schedule and execute to mitigate or prevent issues from occurring in your SharePoint implementation.

19. SPDisposeCheck

20. Sandboxed Solutions

21. Deployment Processes

23. Improves search and navigation.

24. Provides consistent application of site and content access permissions.

27. The Outcome You are able to prevent many potential SharePoint issues through careful planning.

28. What to watch out for… No one wants to do preventative care or pay for it. “It won’t happen to me.”

29. SharePoint Palliative Care

30. What is Palliative Care? Any form of medical care or treatment that concentrates on reducing the severity of disease symptoms, rather than striving to halt, delay, or reverse progression of the disease itself. In SharePoint Terms? Targeting and fixing symptom like issues within your SharePoint implementation without targeting or solving the root cause.

32. You are under artificial constraints that make the potential solutions for the underlying issue infeasible until a later time.

33. Budget/Time/Scope

34. Awaiting Technology Improvements (Upgrade)Cynefin (Dave Snowden Explains)

35. SharePoint Example A site collections content database is 60GB in total size. Preventative Action: Set alert to warn if the content database goes beyond 80GB in size and schedule reports on storage space and database growth. The content database grows quickly to 100GB in total size. The warnings have been sent out. Palliative care would be to either split the content database up or to adjust processes so that the content DB can continue to grow beyond 100GB.

36. The Outcome Symptoms of an underlying SharePoint issue are resolved to decrease the impact of the underlying SharePoint issue.

37. What to watch out for… When a symptom is treated it doesn’t cure the underlying issue.

38. SharePoint Curative Care

39. What is CurativeCare? Actions that seek to cure the existing disease or medical condition. In SharePoint Terms? Solve the underlying issue/problem so that it no longer exists in your implementation.

40. There is no magic pill.

44. Effort needs to be taken to determine an automated synchronization solution for the HR Employee Directory and Active Directory data or one of the systems for managing employee information should be retired so that it can be contained and managed from one source identity/profile. This is because some people are updating user profiles in SharePoint. Some are contacting help desk or HR to get their information updated when addresses or phone numbers change. There are several known challenges. When a user updates their information in SharePoint it does not update Active Directory resulting in updates to the contact information in Exchange. When Help Desk updates user information they do it in Active Directory. When HR updates user information they do it in the HR Employee Directory (Custom/Not Active Directory).

45. Do I Need To? Before you go through a medical procedure the doctor would explain the procedure and the risks, options and alternativesallowing the patient to make an informed decision about whether the risk was worth it. We must do the same with SharePoint solutions – the risk is theirs to take, not ours. Not if there are no known or identified issues.

48. What to watch out for… We cannot cure something if we don’t know enough about it.

49. Incident Reports An incident report or accident report is a form that is filled out in order to record details of an unusual event that occurs at the facility, such as an injury to a patient. The purpose of the incident report is to document the exact details of the occurrence while they are fresh in the minds of those who witnessed the event. In SharePoint Terms? If something unusual happens as a result of ‘preventative’, ‘curative’, or ‘palliative’ measures being taken it must be documented with as much detail as possible while it’s still fresh in the minds of those who were participants or effected. Note this is also important to perform assessments aftercurative care has been provided to better understand it’s impact.

50. SharePoint Incident Reporting

51. SharePoint Health Assessments

52. When to Assess When not scheduled it’s still important to perform assessments after any “curative” action is performed. “It indicates that the prescriber takes responsibility for the clinical care of the system and in particular for monitoring efficacy and safety.” Additionally it may be best to perform one after significant palliative or preventative measures are taken.

53. Mental or Physical? Physical health without mental health is not ‘healthy’. In a SharePoint Implementation: Physical Health = Technical Health Mental Health = Business or Non-Technical Health If you have business or non-technical issues you may not have a healthy SharePoint implementation.

55. What are we currentlyusing SharePoint for within our Enterprise?

56. What are the future uses for SharePoint within our Enterprise?

57. How is SharePoint helping us achieve our business goals?

58. What are our SharePoint objectives and their priority?

59. What are our SharePoint initiatives and their priority?

60. How do our SharePoint initiatives align with our SharePoint objectives?

61. What are ways we can reduce inefficiencies and duplication?

62. What groups are doing similar initiatives and how can we help?

63. What are the related systems, applications and services we have within our enterprise?

64. How is the business prioritizing SharePoint initiatives?

65. Who are the people or key areas of the business involved in setting the strategic direction for our SharePoint implementation?

66. What areas of the business offer the most opportunity for growth?

67. How are you communicating strategic changes or initiatives related to SharePoint in your organization?

69. Are we using it to meet external web content management needs?

71. What are the known future SharePoint initiatives?

72. Am I using all the features our organization is paying for?

73. Are we using any of the features incorrectly?

74. What are the related business applicationsandservices?

75. Do any contain duplicate features/functionality?

76. Are any being retired/eliminated in the future?

77. What are the technical objectives for SharePoint within the organization?

78. How are these technical objectives prioritized?

79. What are our current and future licensing plans with SharePoint?

80. Do you have a communication plan?

81. When do communications occur?

82. What must the communications contain?

83. Who are the contacts for key responsibilities?

86. What are people searching for and what are they not able to find?

88. Do you know how complex the SharePoint Designer workflows are in your environment?

90. Are the roles and responsibilities of the membership clearly defined?

91. Is all of the membership engaged?

92. Does the membership rotate?

93. How often are your members getting together?

94. What are the reasons your Governance teams, committees or boards get together?

95. Are the outcomes of these meetings actionable?

96. Do you have a Governance Site (and Governance Plan)?

98. Initiatives/Technical Strategy Team

99. Tactical Teams:

100. Tactical Operations Team

101. Tactical Development Team

104. Do they have a backup?

105. Do they have the knowledge and training they need?

106. Have you ever deviatedfrom the default settings? Why and when?

107. How are you monitoring SharePoint?

108. Do you know when a content DB’s size is approaching it’s recommended limit?

109. Do you know when the site count of a site collection is approaching it’s recommended limit?

110. Do you know when the site collection count in a content database is approaching it’s recommended limit?

111. What quotashave you configured for SharePoint?

112. How do you handle requests for a larger quota?

113. What is the maximum quota?

114. Do you have errors in your event logs?

115. Do you have errors in your SharePoint logs?

116. Have you changed the default settings for storing logs?

117. Do you have errors in your SQL logs?

119. What quotas have you configured for SharePoint?

120. How do you handle requests for larger quotas?

122. How many web applications do you have in your farm?

123. How many site collections do you have?

124. How many databases do you have?

125. How large are your databases?

126. How many SQL Server Instances do you have?

127. How many users are using your SharePoint site collections?

128. How many requests per second are you seeing?

129. How many sites do you have?

130. How many documents do you have?

131. What is the highest document size?

132. What is the average document size?

133. What are your resource throttling settings?

134. What other technologies are you using with SharePoint?

135. Are you using ISA or Forefront?

136. Are your users using Micrsoft Groove or SharePoint Workspace?

137. What is the current version of Microsoft Office you are using?

138. Are you using Office Communication Server or Lync?

140. Where are the problems?

141. What are the solutions for these problems?

142. Awesome Tip?

144. What Timer Jobs are Running?

145. What Timer Jobs have Run Successfully or Failed?

146. Server

147. Web App

148. Duration

150. How do you keep Environments within SLAs?

151. How do you reduce downtime?

152. How do you validate and benchmark codeDownload the Latest SharePoint Admin Toolkit

154. Do you perform a fire drills based on your plan? When was the last one and how often do you do them?

155. How do you provide single file recovery? (version control, recycling bin, DPM, etc)

156. How do you provide single or multiplesite recovery?

157. How do you provide server recovery?

158. How do you provide data center recovery?

159. Are you storing excess or unnecessary (unused) data in your SharePoint farm?

160. What are the costs of this storage?

162. What are the bandwidth costs associated with SharePoint?

163. What are the costs associated with transferring redundant data around your farm?

164. What are my slowest performing pages?

165. How heavy are my SharePoint pages?

166. Are you using caching in your SharePoint implementation?

167. Are you using Output Caching?

168. Are you using Disk Based Caching?

169. Are you using Object Caching?

170. Are you using IIS compression?

171. Are you monitoring SQL Server Latency?

172. Is your latency 10 milliseconds or less for the Temp Database?

173. Is your latency 10 milliseconds or less for the Search Database?

174. Is your latency 20 milliseconds or less for the Database Log File?

176. What lists or sites are becoming very large?

177. Two Key SharePoint 2007 Tips:

178. Look at the reports available in SharePoint Designer.

180. If you are upgrading to SharePoint 2010 this is also important to understand as the default throttling limits may impact user experience.

181. SQL Scripts (Read Only) and API calls can help identify what lists you do have over the default throttle settings, and which have a larger lookup count.

184. Do you provide help material such as Manuals, Course Guidebooks, Workbooks, How To, Tutorials, or Demonstrations?

185. How do you train users on SharePoint?

186. How do you currently provision your sites?

187. How do you determine where each site should live?

188. Who owns the site and who supports the site?

189. How do you communicate new features, initiatives, or changes to SharePoint to your users?

190. How many SharePoint support requests do you currently get?

191. How are these categorized?

192. How are these assigned and escalated?

193. How many are effectively responded to?

194. How many are closed with success?

195. Do you leverage/contribute to an internal knowledgebase for SharePoint support?

196. Do you have clearly defined SLAs for support and problem resolution?

197. Do you offer face to face learning or unstructured/semi-structured environments for learning? (Lunch and learns, after hours discussions, communities etc)Support Assessments

198. Multiple Tiers for Escalation (You can’t know everything)

199. Measure Support Learn and use data to be proactive.

201. Online

202. MSDN

203. TechNet

204. Blogs

205. Cheat Sheets

206. One on One

207. Classroom Training

208. Forums

209. Help

211. Does this clearly indicate recommended containment hierarchy?

212. Do you have a site map that defines future site structures?

213. Are you using Content Types?

214. Are you using metadata to help make content easier to organize and find?

215. Are you using site columns?

216. Are you using and managing Term Sets?

217. Do you have tagging guidelines?

218. Are you managing keywords?

219. Are you using and managing Site Directories?

220. Do you have classifications based on type of use?

221. Communications based (publishing) portal/sites/collections?

222. Team based collaboration sites/collections?

223. Application/services based sites/collections?

224. Are you checking for dead links?

225. How well is your site structured?

228. Do you have PII (Personally Identifiable Information) in your environment? Is it secured and audited?

229. How well are permissions managed in your SharePoint environment?

230. Have you ever deviated from SharePoint’s default security levels?

231. In what site collections?

232. What was the reasoning/need behind creating your own security levels?

233. How can security be improved in your SharePoint environment?

234. How can you more effectively monitor, manage, and maintain security in your SharePoint environment?

236. What third party products are we using in our SharePoint environment?

237. Where are they available? Who can use them?

238. What is the status of these non-Microsoft products?

239. Are there newer versions available?

240. How is custom code performing within our SharePoint environment?

241. Are you disposing of SharePoint objects correctly?

242. Are you using best practices when querying or working with SharePoint objects?

243. Do you know how many workflows have been created within your SharePoint environment?

244. Do you know what they do?

245. Do you know who owns them?

246. Do you know what they were developed using? (SharePoint Designer? Visual Studio? Third Party Product?)

247. Who is using SharePoint Designer?

248. How do you test your SharePoint environment when an update is made to it?

249. When new code is added or a third party product?

250. How are you storing older versions of configurations, code and compiled components?Development Assessments

252. What are the current systems and applications in place?

253. What are the application and system lifecycles?

254. Is there duplicated content that is contained in other systems or applications and not just within SharePoint?

255. How is this content kept synchronized when updates are made to it?

256. Can data stored in other systems provide additional value to your SharePoint business solutions?

257. Can it give added context to SharePoint content?

258. What are already integrated?

259. How are they integrated?

260. What are not integrated?

261. Why haven’t they been integrated?

263. Does this include user built SharePoint solutions?

264. What is the SharePoint skill level of your users?

265. Do you have user stories on how people are currently using SharePoint successfully?

266. Have you performed interviews or surveys to help understand how people are using SharePoint or how specific SharePoint solutions can be improved?

267. How many people are using your SharePoint implementation?

268. Are you reviewing SharePoint Usage Statistics on a Regular Basis?

269. How many are using a specific site?

270. How many are using specific documents?

271. What times of the week are they using specific sites or documents?

272. Are there patterns that can be identified to help in determining the best time for updates or additions?

273. Is your SharePoint accessible externally or via mobile devices?Usage and Adoption Assessments

275. Have you performed usability assessments?

276. How has your SharePoint implementation been branded?

277. Does it have a unique name for referencing?

278. What are your theme and styling guidelines?

279. How does your SharePoint implementation work across browsers?

280. What about upcoming browsers?

281. What are the accessibility concerns in your current SharePoint implementation?

282. How can this be improved?

283. Do you have usage policies defined?

284. Have your users signed off or acknowledged these policies?

285. Do you enforce these policies?

286. How often are these usage policies assessed and updated?Usage and Adoption Assessments

288. Is your SharePoint accessible externally?

289. Is your SharePoint being used on mobile devices?

290. How is the user experience?

291. How has your SharePoint implementation been branded?

292. What are your theme and styling guidelines?

293. How does your SharePoint implementation work across browsers?

294. What about upcoming browsers?

295. What are the accessibility concerns in your current SharePoint implementation?

296. How can this be improved?

297. How do you make navigation changes in your SharePoint implementation?

298. Is your current navigation effective?

299. Have you performed card sorting exercises?

301. Make it easier to work with Powerful Columns You Probably Didn’t Know About

302. Make it easier to work with Why Leveraging SharePoint Blog Features for News is a Great Idea

304. Are you using people search?

305. Are you checking what queries resulted in failure (no click through or 0 results)?

306. Are you using best bets?

307. Have you defined synonyms?

308. Do you allow users to search non SharePoint data from within SharePoint? If so what data?

309. Are you using hit highlighting?

310. Have you made organizational enhancements to the noise words file and/or the thesaurus file?

312. How timely and up-to-date is the information you are reporting on and using to support decisions?

313. Are users empowered to create their own reports or analysis on key business information metrics?

314. Forcasting?

315. Predictive Analytics?

317. What are acceptable tags?

318. Are negative tags allowed?

319. Are there examples of effective tags available?

320. When should a user tag and when shouldn’t they?

321. If content has already been tagged is it valuable to tag it again?

322. Is it okay to tag content if that content already has a column (or metadata) value that represents that tag?

323. Are you using Status Updates?

324. What are acceptable status updates?

325. Are there examples of effective status updates available?

326. What is acceptable About Me information for a user profile?

327. Are there examples of effective About Me descriptions available?

329. Are you using Robots Exclusion Standard (robots.txt)?

330. Are you placing your content higher up in the page (to improve search engine processing).

331. Are you ensuring alt and titletags are always filled on things like images?

332. Are you using descriptive text in your hyperlinks?

333. Are you using descriptive page titles?

334. Are you automatically updating the sitemap (helps search engines crawl or discover pages on the site).

336. Don’t expect a vendor to tell you that SharePoint has been implemented poorly. You should perform your own assessment based on your own environment, culture and challenges. This is a starting point.

337. Assessment Breakdown

338. Categorized Assessment Approach

339. Specific Assessment Approach

340. Phase the Assessments

342. Microsoft/Community ToolsSharePoint Diagnostics (2007, 2010), ULS Viewer, SharePoint DocGen, Log Parser, Visual Studio 2010 Ultimate (Load Testing) etc.

344. The Diagnosis Diagnosis is used to help determine the causes of symptoms, mitigations for problems, and solutions to issues.

345. What to watch out for… “Prescription without Diagnosis is Malpractice.” “Prescription of a SharePoint Tool/Solution/Implementation without Diagnosis is Malpractice.” Please Share This!

346. What we talked about… The Plan of Care for SharePoint PreventativeCare is critical and cost effective. Palliative Care targets side effects and is expensive. Curative Care is difficult without clear diagnosis. Record and Learn from Results Assess Often, Target Assessments, Act on Results What is a SharePoint Prescription? SharePoint Preventative Care SharePoint Palliative Care SharePoint Curative Care SharePoint Incident Reporting SharePoint Health Assessments

348. Blog: www.rharbridge.com

349. LinkedIn: www.linkedin.com/in/rharbridge

350. Email me at: rharbridge@Allin.com

351. My company: www.Allin.com

352. Assessments: www.SharePointDiagnostics.com