Harmjan Greving’s Blog

If you’re using Windows XP you can’t install this version of Visual Studio 2008 Extensions, because you don’t have Windows SharePoint Services 3.0 installed:

Here I read a solution to let you’re computer act as it has WSS 3.0 installed:
http://blogs.msdn.com/jannemattila/archive/2007/08/16/how-to-install-windows-sharepoint-services-3-0-tools-to-xp-or-vista.aspx

1. Start regedit

2. Add the key: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0] 

3. Add the value: “Sharepoint”=”Installed”

After that, download the software and install it:
Windows SharePoint Services 3.0 Tools: Visual Studio 2008 Extensions, Version 1.2

When you right click with you’re mouse on the desktop and choose properties, normally you will see something like:

In my situation I had no ScreenSaver tab in that window because someone hide it:

I’ve a solution to make the ScreenSaver tab appear again. This solution works only if you’re the Administrator or if you’ve write access to the registry:

1. Start the program: regedit

2. Find the key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\system

3. Set NoDispScrSavPage to 0:

For a customer we had to set  up a Microsoft Office SharePoint Server 2007 (MOSS 2007) Multiple Server Farm. The customer uses the Content Management Server (CMS) possibilities of SharePoint 2007 to manage the company’s Internet site.

Before we started setting up the servers and building the farm, web applications and sites we had to consider the company’s network architecture. This consists of an Intranet zone and a perimeter network (also called a DMZ), split into two sections: the Inner DMZ and the Outer DMZ. One of the challenges during the assignment was to keep this setup and all the security properties of the networks intact, and still make it work.

For security reasons the Internet users may not connect to any site on the Intranet directly and also it would not be a good idea to let (internal) Intranet users manage content directly on a webserver in a DMZ. Therefore we set up two farms: one Intranet Farm and one DMZ Farm. Moreso, we split the Internet Farm between a Web Frontend server in the Outer DMZ and the Database and Services (Search, SSP and Central Admin) in the Inner DMZ.  Between the two DMZs resides an ISA server for access security.

The editors work on the website inside the company’s Intranet. Content is synchronized to the Internet (DMZ farm) with Web Content Deployment Content (Paths and Jobs) and all changed and published content is sent to the DMZ every 15 minutes. You can read about Content Deployment in our next post.

So there was ‘just’ one problem. Since the DMZ Farm is a real farm (not a single server setup), it is required to use domain accounts for the service accounts. This automatically means you need a separate AD domain controller inside the DMZ. Sharing the DMZ domain with the intranet domain would be possible too, however the whole purpose of a DMZ  is not to put your authentication at risk. So we needed a separate AD Domain controller just for the service accounts. If that controller is compromised, the internal domain is not affected.

So we ended up with 4 Servers in two Farms for a minimum configuration. From this point on it’s a matter of extending Database, Services and/or Web Frontend Servers. We could start installing the software and configuring them:

Intranet Farm > Database Server

· Windows Server 2003 SE SP1
· Internet Information Services (IIS)
· SQL Server 2005 (installs also the .NET Framework 2.0)

DMZ Farm > Database and Web Server

· Windows Server 2003 SE SP1
· Internet Information Services (IIS)
· SQL Server 2005 (installs also the .NET Framework 2.0)
· .NET Framework 3.0
· Windows Server Support Tools
· MOSS 2007 with SP1 (WSS SP1 and MOSS 2007 SP1 included)
(· MOSS 2007 additional language packs)
· Run the SharePoint Configuration Wizard
(· MOSS 2007 language pack SP1)
(· WSS 3.0 post SP1 hotfix for content deployment [KB950279])

Intranet and DMZ Farm > Web Servers (2 Servers)

· Windows Server 2003 SE SP1
· Internet Information Services (IIS)
· .NET Framework 2.0
· .NET Framework 3.0
· Windows Server Support Tools
· MOSS 2007 with SP1 (WSS SP1 and MOSS 2007 SP1 included)
(· MOSS 2007 additional language packs)
· Run the SharePoint Configuration Wizard
(· MOSS 2007 language pack SP1)
(· WSS 3.0 post SP1 hotfix for content deployment [KB950279])

And also run the windows updates for the Operating System (OS), SQL Server 2005 and the .Net Framework updates etc.

There is one *really* important thing to keep in mind here: always keep all servers in the farm (f.i. all Web Front End Servers) and the software completely identical. So either install service releases on all systems, or onto none at all.

For a developer it’s easy to use a Microsoft Office SharePoint Server 2007 (MOSS 2007) in a Single Server Farm. You’ve to install the following software on a Windows Server that has WSS 3.0 on board:

1. Logon or install a Windows Server 2003 or Windows Server 2008 with an administrator account;
2. Install .Net framework 2.0;
3. Install .Net framework 2.0 SP1;
4. Install .Net framework 3.0;
5. Install SharePoint 2007 - Select the option: ”Single Server Farm installation”;
6. Install WSS 3.0 SP1;
7. Install SharePoint 2007 SP1.

The SharePoint 2007 installation includes SQL Server 2005 Express Edition.

You’re now reading the blog of Harmjan Greving. I am a Software Developer for Atos Origin. On this blog I write about my experiences with Microsoft Technologies. I hope you will find here some usefull information.