It’s been a while since I posted about the evolution of the corporate intranet I am working on for the last 2 years. Because these posts cover only a few things that happened over time and are spread across these 2 years, I’ll try re-cap the most important steps of the evolution here:
0 – Start
We started building our first Sharepoint services server 2 years ago. We are an office that is part of a major IT Services Company and the Global Intranet did not serve it’s purpose in many way’s:
Site was too head-office centred, Most of the available information was not applicable to oversees users.
Site was too corporate. Staff does not want to log on every morning, open their browser and read the same story from the director. Staff needs information that is applicable to them.
Centralised Ownership. This cause a small team of administrators to have too much work to be able to maintain the site. the result was that a lot of information was out of date and updates took too long to be published.
With the above points as the main ones, we took the decision we needed an intranet tool to manage our information. Since the company decided around that time to stop using Lotus Notes and Domino servers for our Email and switch to exchange, we had the opportunity to have a look at Microsoft’s options.(The original Idea was to build the intranet on a Lotus Domino 7 server).
A very convenient side-effect was, that while I was working as a technical Lead and was not really line-managed by anyone, after 2 weeks in this situation, I started looking into this out of boredom. This to my managers’ credit 
Since this was not something coming from the main organisation, there was a very limited budget available. After investigation of the different flavours we could go for, we found that we could get most of the required functionality or value for money from the Microsoft Windows Sharepoint Services, that is included for free with a Windows Server licence.
1 – First Intranet server launched
Shortly after making the decision, we drafted a layout, checked in with the different teams and departments for their requirements and started building.
We had a virtual Windows 2003 server set-up, completely standard. Then we ran the manage this server wizard and turned it in to a Application server running Windows Services. Bang!, we had an Intranet.
The site grew very fast. Mainly (I Like to believe) due to the empowerment we implemented on site-ownership and the lack of a communication platform for the last years.
2 – First Crash
And Bang! 2 months after we lost the intranet. Our Networking team pushed a set of updates causing the server to reboot. This happened right in the middle of a backup I scheduled.
Result: Server Unreachable, Backup Corrupted. “Of course, resilience!” There was a lot to learn and improve here.
3 – Second Server
From the previous lesson, we’ve learnt a lot:
These are the core lessons we learned from this exercise. When we started re-building we actually had no map or plan whatsoever. This made this lesson even more valuable.
It took me about a month to have the site rebuilt. More or less as it was before. We ordered a second server to work as a failover and made sure our backups are copied to a remote location.
4 – Site will go Global
We are now almost 2 years away from all the previous. In the meantime we did quite some spectacular things with our Intranet. Especially if you take in account that we did not have anything in place before.
Most of these things are things that help us as employees on a daily basis or workflows that automate manual tasks for us. We started looking into the processes and managed to make most of them quite a bit. Because we used WSS out of the box on a small VM Server, we decided that document storage should not be used yet. Basically because of lacking processes and policies and the 4GB size limitations on the SQL express database.
As a result from this, more and more people from other parts of the company started to take interest in our site. Communication, Cooperation , Automation where things that was quite new to them.
I was approached by different business units from within the company to set-up similar sites to ours for their teams and eventually link them through in a main portal sites.
In the meantime, somewhere else in the company a new intranet environment was being developed….
Read the rest of this entry »
Possibly Related:
Technorati Tags: Intranet, MOSS, WSS