SharePoint Platform Guidelines

A collection of SharePoint platform guidelines.

EICAR Standard Anti-Virus Test File

Recently a customer was testing antivirus scanning software, both on trafic and on servers/clients. This had to be tested on several environments, including production and really didnt want to use a real infected file. The following showed up, didn’t know about it, chances are there are others that doesnt know about this.

“The EICAR Standard Anti-Virus Test File or EICAR test file is a computer file that was developed by the European Institute for Computer Antivirus Research (EICAR) and Computer Antivirus Research Organization (CARO), to test the response of computer antivirus (AV) programs. Instead of using real malware, which could do real damage, this test file allows people to test anti-virus software without having to use a real computer virus.

Anti-virus programmers set the EICAR string as a verified virus, similar to other identified signatures. A compliant virus scanner, when detecting the file, will respond in exactly the same manner as if it found a harmful virus. Not all virus scanners are compliant, and may not detect the file even when they are correctly configured.

The use of the EICAR test string can be more versatile than straightforward detection: a file containing the EICAR test string can be compressed or archived, and then the antivirus software can be run to see whether it can detect the test string in the compressed file.”

EICAR test file – Wikipedia, the free encyclopedia

Steps to use it:
Create a .txt file on your drive, open your AV scanner software and create an exclusion on this file and location. Update the contents of the file with the referenced. Scanner software will not quarentine it with that name and location, however anywhere you move it, it should be detected and removed.

SharePoint Solution Design Specification

Finally got the last hands on the solution design I wanted to match up with the infrastructure design. I wasn’t to sure on this, as this is not an area I usually work with, but having used it two times it seems to hold proof. As with the Infrastructure design, remove any unused components.
This design takes a bit more work to fill out, as it needs to hold the descriptions on how the customer is intended to use the solution. Each service application comes out with a rich descriptions as well as the authentication model. Especially for those federated identity solutions.

I expect this design to be updated with more content, as I embrace more of the solution architecture. In order words, while not being as definitive as the infrastructure design, it should provide a good baseline for the solution design activities.

Feel free to use, give any credit you can 🙂

SharePoint Solution Design Specification (located on Google drive)

SharePoint Infrastructure Review

To aid others in correcting their SharePoint farm and to make the right choices, or simply to review their farm compared to standards, i’ve shared some of the most frequent issues / misconfigurations / things to consider whenever implementing a SharePoint farm.

This document contains the most frequent sources of issues in regards of a SharePoint infrastructure.
Each consequence of observation has been explained and recommended action stated, furthermore the type of observation has been set. The type classification is based on the authors experience and knowledge and should be challenged were project requirements state differently.
This infrastructure review is focused on SharePoint, IIS, SQL and partly Windows Server. This review does not include or only very limited to Hardware, NLB or network.

I expect to update the document when new items appear.
SharePoint Infrastructure Review (located on Google drive)

SharePoint Infrastructure

What is SharePoint Infrastructure

The question is valid and probably not many people would or could answer it appropriately.

In broad terms, SharePoint infrastructure is the composition of all those components that lie underneath your SharePoint web applications. That is; databases, user directories, web server sites and application pools, file shares, routing, switching, firewalls, ports, authentication mechanisms etc. It is also patching, monitoring and backup.

SharePoint Infrastructure (Location on Google Drive)

SharePoint Platform – Soft design considerations

Internet wearing ”Intranet skin”

Sometimes words don’t mean the same, however every once in a while, they do. In this case I’d say that intranet and internet are the same, or at least they should be the same.

For some reason people regard the intranet as a completely different technology, a completely different world – when in fact they are very closely related! People implementing intranets are not really looking at all the experiences gathered from the internet 10 years back. For some reason people designing intranets are insisting on reinventing the wheel – when they are designing their intranet solution.
They are still designing long chains of nested clicking about to find content. They are still pretending to know exactly what the end users want to look at – all of them – with just one page!

They insist that whatever they thought of, is the right thing for the user. Typically designs are made static, with high costs in order to change it. Users are not allowed to manage their own stuff, their own sites, their own colors. – And they don’t even pay for it!

All right, what have we actually learned from the internet so far that could or should be implemented in the intranet.

1: Financing – One of the driving factors of the internet is that anyone could post anything, anywhere, in any way they like (at least until someone decided they couldn’t). Usually, and I’m not saying all the time, but a lot of times intranets are implemented as a single solution that a single entity is paying for. It becomes a large expense for that entity, which assumes all responsibility and is also considered the driving factor for the solution.

Intranets are usually a web service, each page representing parts of an entity within your organization. Be strong in your implementation and make sure anyone, can do anything within your intranet. Consider it a joint-stock company, you pay to get in.

Bottom-line: there is a reason that basically every company has a web page.

2: Implementation – The internet is not created by one person, one department, one organization. It was created by many. There are still expert organizations maintaining it, but unlimited amounts of users. Just remember that not everybody has the same ambitions, skill level or requirements.

3: Navigation – The internet changed completely with the invention of search engines. People no longer typed in www addresses. They were no longer forced to navigate and click to find it. No, they opened their favorite search engine and 7 seconds later they got the information they were looking for, and related objects they didn’t even know they needed..

Usually tons of time is spent designing and implementing a beautiful navigation. When time should be spent on optimizing search.

4: Usage – When are your users using the internet and when are they using the intranet?  This question should raise enough questions and answers to keep your intranet, I mean internet, solution running the next few years 🙂

The above is somewhat oversimplified, however it does hold a grain of truth. Not every scenario can be set up so simply, not every implementation is so straight forward. However keep the above in mind when you’re buying, implementing or designing the next intranet solution and you should get some wheels of steel for free.

SharePoint Platform Maintenance Guide

Introduction and purpose

In regards to daily operations of the SharePoint platform there is a set of tools available in order to support this. To give the best possible foundation to operate your SharePoint 2010 farm with as little and as short operational disturbance as possible, the below guide defines the most important elements in relation to this.

This guide describes the GUI-based Central Administration, its tools and options as well as Microsoft’s command-line shell named Powershell. All this with reference to daily operational challenges that occur on the SharePoint Farm.

First this guide contains the most important elements from the respective tools, thereafter examples of usage is with real life issues.

Covers SharePoint 2010 and 2013.

SharePoint Maintenance – English (Location on Google Drive)

SharePoint Vedligeholdelse – Dansk (Placeret pĂĄ Google Drev)

SharePoint Platform – Backup & Restore Guide

To ensure continual operation of the implemented SharePoint Server 2010-solution, all the supported elements have to be secured in regards to reestablishing functionality and data in the event of a random element’s breakdown.

This guide describes how backup and restore of the SharePoint Server 2010-platform should be done as per Microsoft’s recommendations. This includes associated elements like Site Collections, Web Applications and the product Project Server 2010.

The guide begins with important considerations, before moving on to recommendations. It is important to emphasize that the actual implementation always has to be based on the physical setup and the customer specific demands for backup/restore level and time.

SharePoint 2010 Backup & Restore – English (Location on Google Drive)

SharePoint 2010 Backup & Restore – Dansk (Placeret pĂĄ Google Drev)