Automating WSS v3/MOSS 2007 development environment setup: part IX – Setup your farm with minimum settings


Hi,

To remove the message, you need to follow the steps described in the “Administrator Tasks” that have the order “1”.

You can skip the “Read … bla bla bla” step.

Then, you need to add servers to the farm: in our case, we also skip.

Now, we need to “Assign services to servers”. We have only 1 server, so it’ll run all the services.

The services we need to launch are listed here, with their respective “stsadm.exe “instructions:

  • Search Services : you’ll need a place to store the index. I usually create and manage the index location. Here, I chose “C:\Index”, created with “mkdir "C:\Index"”. Now, we can set the search services:
    • Windows SharePoint Services search :
      • stsadm -o spsearch -action start -farmperformancelevel PartlyReduced -farmserviceaccount ad\MOSS_Search_Acct -farmservicepassword moss -farmcontentaccessaccount ad\MOSS_Crawl_Acct -farmcontentaccesspassword moss -indexlocation C:\Index -databaseserver DEV2008 -databasename MOSS_DEV2008_WSS_SearchDB
    • Office SharePoint Search :
      • stsadm -o osearch -action start -role IndexQuery -farmcontactemail administrator@ad.contoso -farmperformancelevel PartlyReduced -farmserviceaccount ad\MOSS_Search_Acct -farmservicepassword moss -defaultindexlocation C:\Index

 

  • Document Conversion Service : we’ll need to put some settings in the registry of the server. To achieve this, I use a reg file, that contains :

      Windows Registry Editor Version 5.00

      [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\12.0\LoadBalancerSettings]
      "Port"=dword:00001f9d

      [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\12.0\LauncherSettings]
      "Port"=dword:00001f92
      "LoadBalancerUrl"=
      http://DEV2008:8093/HtmlTrLoadBalancer

    • Then, you stop the services (in case they were running – you never know!), apply the registry hack, and restart the services. Here’s the result:
      • stsadm -o provisionservice -action stop -servicetype "Microsoft.Office.Server.Conversions.LoadBalancerService, Microsoft.Office.Server.Conversions, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" -servicename DCLoadBalancer
      • stsadm -o provisionservice -action stop -servicetype "Microsoft.Office.Server.Conversions.LauncherService, Microsoft.Office.Server.Conversions, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" -servicename DCLauncher
      • iisreset
      • regedit.exe /s "Z:\DevEBSources\Scripts\MOSS_Doc_Conv_registry.reg"
      • stsadm -o provisionservice -action start -servicetype "Microsoft.Office.Server.Conversions.LoadBalancerService, Microsoft.Office.Server.Conversions, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" -servicename DCLoadBalancer
      • stsadm -o provisionservice -action start -servicetype "Microsoft.Office.Server.Conversions.LauncherService, Microsoft.Office.Server.Conversions, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" -servicename DCLauncher
      • iisreset

  • Excel Services : launch the service on the server you want it:
      • stsadm -o provisionservice -action start -servicetype "Microsoft.Office.Excel.Server.ExcelServerSharedWebService, Microsoft.Office.Excel.Server, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c"

 

  • Now the SSP : To create the SSP, you need 2 web applications, running with a domain account in their Application Pools. Once created, you can create the SSP. Here’s the instructions:
      • stsadm -o extendvs -url http://DEV2008:101 -ownerlogin ad\MOSS_Setup_Acct -owneremail admin@ad.moss -databasename MOSS_SSP_AdminWebApp_ContentDB -exclusivelyusentlm -description "WebApp SSP Admin (101)" -apidname SSP_AppPool(101) -apcreatenew -apidtype configurableid -apidlogin ad\MOSS_SSP_AppPool_Svc -apidpwd moss
      • stsadm -o extendvs -url http://DEV2008:102 -ownerlogin ad\MOSS_Setup_Acct -owneremail admin@ad.moss -databasename MOSS_SSP_MySites_ContentDB -exclusivelyusentlm -description "WebApp SSP MySites (102)" -apidname SSP_MySites_AppPool(102) -apcreatenew -apidtype configurableid -apidlogin ad\MOSS_SSP_AppPool_Svc -apidpwd moss
      • stsadm -o createssp -title "MOSS Farm SSP" -url http://DEV2008:101 -mysiteurl http://DEV2008:102 -indexserver DEV2008 -indexlocation "C:\Index" -ssplogin ad\MOSS_SSP_Acct -ssppassword moss -sspdatabasename MOSS_SSP_SspDB -searchdatabasename MOSS_SSP_SearchDB

 

  • To finish these nice scripts, I always create a “useful” site, to see the work:
      • stsadm -o extendvs -url http://DEV2008:80 -ownerlogin ad\MOSS_Setup_Acct -owneremail admin@ad.moss -databaseserver DEV2008 -databasename MOSS_WebApp80_ContentDB -exclusivelyusentlm -sitetemplate SPSPORTAL -description "MOSS Portal Home Page" -apidname "MOSS_WebApp_80"  -apidtype configurableid -apidlogin ad\MOSS_AppPool_Svc -apidpwd moss

And here you are. No more annoying messages in Central Administration.

You just need now to move on the more “developer” specific setup tasks.

<Emmanuel />

Note: as you may see, I changed the server name again: I started the posts series with SVR2003, then switched to MSDN (in January posts) and now DEV2008. Its’ not a trick, just that I replay the scripts on different Virtual Machines, depending on my customer engagements.


Comments (3)

  1. Hi, This long post series raised interest from many of you. Thanks for that. I was asked few times to

  2. Un petit post rapide pour linker une excellente série faite par Emmanuel Bergerat sur son blog : Automating