Collaboration, Search, Extranets, and Internal Communications Built on SharePoint and Microsoft 365
"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!"
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
Are you developing for SharePoint in a commercial organization? Eager to get coding before a well-thought-out development environment is planned and stood up?
Cool your jets! Avoid the temptation to get started early and begin creating solutions in a Stand-alone SharePoint installation!
DO NOT develop in a Stand-alone SharePoint environment if you’re doing serious work!
Wait for your project team to formalize the environmental architecture and provision real farms in which you will do development, even if a farm consists of a single SharePoint server and separate SQL instance.
I have delivered the bad news to a development team up against a tight deadline that their performance problems and some system errors are the result of the Stand-alone deployment.
For starters, if you have Visual Studio, SharePoint (with a boatload of Services enabled), SQL Express, troubleshooting tools, and the Kitchen Sink running in what is likely a 2-core, 4 GB virtual instance on an over-subscribed virtual host, you are already asking for Big Trouble.
Don’t paint yourself into a corner with a Stand-alone deployment!
Most likely you are unaware (as was I until I researched a bunch of errors) that a Stand-alone deployment will not support all ‘normal’ SharePoint functionality. If you look at the Services status page, you won’t see a clue that anything is amiss!
See these caveats from the authoritative TechNet article on single-server SharePoint 2013 installations:
Consider the following restrictions of this method of installation:
Don’t you love free stuff?
Some folks like to create and share, like Ayaz Malik. In his site Designzzz, Ayaz provides downloadable resources, links to downloads by others, and how-to advice on all things UI.
The downloads are useful for general web work and SharePoint – especially SharePoint 2013 (and SharePoint Online) with the more open design protocol.
Fonts, graphics (many in native PSD format), style sheets are generously provided with little or no strings. And I’m cautious about strings!
Plenty of ads, but all well-behaved (no annoying pop-ups) when I’ve visited his site.
Check it out – be sure to drop a note of thanks if you use any of the resources. Let me know if you found this helpful.
Good job, Ayaz.
Like the Nanny state trying to save us from ourselves, Microsoft started pushing SharePoint patching into automatic updates.
If your WinTel team and corporate governance folks are in alignment on best practice, they would avoid automatic patching like an Ebola tent without protective gear. If they do allow Windows Update to patch server OSs and applications, you might want to have a little chat with your CIO. But that’s getting off topic.
The reports from system administrators who have been victimized by automatic patching are unpleasant. Learn from them by making sure your SharePoint (and associated) servers are configured for manual patching only! Stop everything else that you’re doing and read this post from Todd Klindt NOW! Don’t Enable Automatic Updates on SharePoint Servers
“There is no such thing as a secure electronic health information system.”
This is the warning delivered by Jim Pyles in his Congress Blog post, Lessons from Anthem, from February 20 issue of The Hill.
Anthem spokespeople emphasize that our medical information wasn’t compromised, implying that there may not have been a HIPPA violation. That may keep them out of the woods with the Feds, but what about our personal information, such as Social Security and credit account numbers?
Have you received correspondence from Anthem that your information was compromised? I’m waiting to hear if our family has to perform damage control, or if we can go about our business. How can we trust them again?
Newsworthy security breaches and data theft should make us and our users challenge the integrity of our service providers. Makes no difference if our systems are on premise, hybrid, or in the cloud – if a biggie like Anthem is compromised, what are we and our vendors doing to encourage rather than erode confidence?
© 2025 Dave Wolf – SharePoint Professional
Theme by Anders Noren — Up ↑
Recent Comments