A list of recommended MOSS Service Accounts

Account Type
Account Name
MOSS Farm Account

Server Farm Account. This account needs some SQL permissions granting: dbcreator and security admin (do not grant this account SA!). If using ADACM this is the account used for creating objects in the OU specified – so you’ll need to delegate permissions on the OU to this user.

MOSS App Pool Identity for the any MOSS Web App Application Pool(s). A separate process identity should be used for each content Web App (this allows for greater security and auditing). Using the site name in the naming is not advisable as although this may make troubleshooting and auditing easier it reduces security by showing the relationship between App Pools and Web Apps.


SSP Service Account SSP service account svcMOSSSSP1
SSP App Pool Identity for the SSP Web App Application Pool svcMOSSSSPAppPool1
MOSS Search Account under which the Office SharePoint Server Search runs under. svcMOSSSearch1
MOSS Content Access Account used to access content sources to be crawled and indexed. Need to grant this account permission to any NON-MOSS content sources (e.g. NTFS file share, Exchange public folder, websites etc…)Separate accounts may be configured for access to specific content sources using crawl rules. svcMOSSCrawl1
User profile & Properties Access Account Account used to access Active Directory for the Profile import svcMOSSDSA1
WSS Search Account which the Windows SharePoint Services Search service runs under. Due to the fact the Office SharePoint Server Search service is running this will only index the WSS Help files. svcMOSSWSSSearch1
WSS Content Access Account used by WSS search service to crawl content. svcMOSSWSSCrawl1
MOSS Install Account Account used to install MOSS and perform all the required configuration changes.As this account will be used to install and configure the SharePoint servers it must be granted local admin on all farms members and have permissions to the SQL instance.This account can be disabled after installation and configuration is complete (it is not advised to delete it). svcMOSSInstall1
SQL Services Used to run MS SQL Services



This list is copied from Matt Grove, thanks Matt.

To make the creation of these accounts easy, I have created a VBS script that does the job.

Option Explicit
' =====================================================
' Author:        Magnus Johansson
' Create date:   12.08.2009
' Description:   Creates services acounts for the MOSS VPC
' File Name:     CreateMOSSServiceAccounts.vbs
' =====================================================
Dim strComputer
' Set the local computer name
strComputer = "."
' Run the Load method
Sub Load()
Dim strPassword
strPassword = "Pa$$word"
' Create the service accounts
CreateUser "svcMOSSFarm1", strPassword, "MOSS Farm Account"
CreateUser "svcMOSSAppPool1", strPassword, "MOSS App Pool 1"
CreateUser "svcMOSSAppPool2", strPassword, "MOSS App Pool 2"
CreateUser "svcMOSSAppPool3", strPassword, "MOSS App Pool 3"
CreateUser "svcMOSSSSP1", strPassword, "MOSS SSP Service Account"
CreateUser "svcMOSSSSPAppPool1", strPassword, "MOSS SSP App Pool"
CreateUser "svcMOSSSearch1", strPassword, "MOSS Search"
CreateUser "svcMOSSCrawl1", strPassword, "MOSS Content Access"
CreateUser "svcMOSSDSA1", strPassword, "User profile & Properties Access Account"
CreateUser "svcMOSSWSSSearch1", strPassword, "WSS Search"
CreateUser "svcMOSSWSSCrawl1", strPassword, "WSS Content Access"
CreateUser "svcMOSSInstall1", strPassword, "MOSS Install Account"
CreateUser "svcSQLSVC1", strPassword, "SQL Services SQL Server"
CreateUser "svcSQLRS1", strPassword, "SQL Services SQL Reporting Services"
CreateUser "svcSQLAS1", strPassword, "SQL Services SQL Analysis Services"
MsgBox "Complete!"
End Sub
' Create the local user
Sub CreateUser(userName, password, description)
Dim objComputer
Dim objUser
' Check to see if the user exists; if so, then skip
If NOT CheckIfUserExists(userName) Then
Set objComputer = GetObject("WinNT://" & strComputer & "")
Set objUser = objComputer.Create("user", userName)
objUser.SetPassword password
objUser.FullName = userName
objUser.Description = description
objUser.Put "UserFlags", 65600 ' Sets Password Never Expires to TRUE
' and sets User Can't Change Password to TRUE
MsgBox userName & " already exists!"
End If
End Sub
' Check to see if user exists
Function CheckIfUserExists(userName)
Dim objComputer
Dim intFound
Dim User
Set objComputer = GetObject("WinNT://" & strComputer & "")
objComputer.Filter = Array("user")
intFound = 0
For Each User In objComputer
If lcase(User.Name) = lcase(userName) Then
intFound = 1
End If
If intFound = 1 Then
CheckIfUserExists = True
CheckIfUserExists = False
End If
End Function


Then, follow a guide to install a complete MOSS setup.

How to install MOSS on Windows Server 2008 R2

First a disclaimer. Microsoft doesn’t support this scenario, so you will be on your own.

When you try to install MOSS 2007 on Windows Server 2008 R2, you will be prompted by this error message:


and you are stuck.

The only way to install MOSS 2007 on Windows Server 2008 R2 is to slipstream MOSS Service Pack 2 into the installation media. I will now run through the steps to do so.


  • MOSS 2007 installation media. (Either the .iso file from MSDN, or the DVD)
  • WSS 3.0 Service Pack 2 (Remember to get the x64 version, since Windows 2008 R2 is 64bit only)
  • MOSS 2007 Service Pack 2 (Remember to get the x64 version, since Windows 2008 R2 is 64bit only)

First, extract the contents of your MOSS 2007 media .iso file (or simply copy the files if you are using the DVD) to a temporary installation folder. In my case this will be H:\MOSS Installation Media. There is an TechNet article on how to slipstream updates into MOSS, but I will go through the steps here also.

Open a command prompt and change directory to where you have the service pack files. Extract the contents to the Updates folder of your installation folder.

First the WSS Service Pack files:

officeserver2007sp2-kb953334-x64-fullfile-en-us.exe /extract:"H:\MOSS Installation Media\x64\Updates"

Then the MOSS 2007 service pack files:


officeserver2007sp2-kb953334-x64-fullfile-en-us.exe /extract:"H:\MOSS Installation Media\x64\Updates"


Now, you will need to delete the file wsssetup.dll from the Updated folder, otherwise it will only install the WSS SP2.

You can now install WSS 3.0 and MOSS 2007 SP2 using set setup.cmd found in the installation folder.

SharePoint: Open with Windows Explorer on Windows Server 2008

If you are developing SharePoint solutions on Windows Server 2008, you may have noticed that nothing happens when you click on the Toolbar menu item Open with Windows Explorer in a Document Library ?

That is because that this feature uses the WebDAV protocol, which isn’t installed by default on Windows Server 2008. In order to install the WebDAV protocol on Windows Server 2008, you must enable the Desktop Experience feature.

After you have installed the WebDAV protocol, you can also save Office documents directly to your SharePoint site from the Windows Server 2008 client.

Start the Server Manager console.

Click on Add Feature.

Image showing the Add Feature link

Select the Desktop Experience and click Next.

Image showing the Desktop Experience checkbox

Click Install.

Image showing the Install procedure of the Desktop Experience

Image showing the installation of the Desktop Experience

Click on Close to Reboot.

Image showing the restart process after installation

An indexer is not assigned to the Shared Services Provider


If you have come across this error message, you have probably done some changes in the search settings, like stopping the search service.

An Indexer is not assigned to the Shared Services Provider_1

The solution is to re-assign the indexer to the Shared Services Provider.

Here are the steps:

Open the SharePoint 3.0 Central Administration and click on the Shared Services Administration link in the left menu bar.

Image showing the Manage this Farm's Shared Services

Right click on your default Service Provider and select Edit Properties.

Image showing the Edit Proprerties menu item

Now, select the server that you want to use in the Index Server drop down list.

Image showing the Index Server selection