I recently [a week ago] joined another company to take their SharePoint practice to the next level (but more on that in a later post). One of my first missions at the company is to get a brand spanking new sandbox environment up and running. I’m not going into great detail in this post on how we put it together as it has a lot of little notes on how to install SharePoint 2010, SQL Server 2008 SP1 (with cumulative update 1).
After completing the SharePoint 2010 environment our attention turned to SharePoint 2007. After joining the VM (Windows Server 2008) to the domain, we fired up the installation wizard for MOSS 2007 and after entering the various details for DB Server, Default Accounts etc, we received with the following error message – “account must be a local account or a global domain account”. We scratched our heads a little, tried some quick fixes and finally came up with the resolution (after a couple of minutes):
- Remove the machine from the domain;
- Rename machine;
- Re-add machine to the domain;
After completing the steps above, the installation worked just fine. The account we used had access to SQL with dbcreator and securityadmin access. We did not give the account “local admin” rights as so many administrators do in error. :)
Hope this helps.
While installing CRM 4.0 on Windows Server 2008 I was faced with the following error message during the installation:
To resolve this issue, ensure that you select Network Service when asked to configure the service account for the installation.
Here is the full article from Microsoft: http://support.microsoft.com/kb/950100
We are currently busy with a pilot roll out in Europe and while deploying the farm with various updates I came across the fact that not a lot of information on Windows Server 2008 and Language Packs are available. In any event, I soldiered on and eventually got it to work thanks to lots of trial and error and a colleague from home.
Now most if not all websites I consulted prior to installing the language packs simply mention that you need to install the MOSS Language Packs if you are running SharePoint and there is no need for the WSS Language Packs. Well, thanks to a colleague that figured this out the hard way, we installed the WSS language packs after the MOSS language packs (yes I frowned as well) and badaboomtish, the language features started working.
I find it very odd that this isn’t well documented on the net, but ja, here is the installation path I took to get our server farm up and running language packs, infrastructure updates included:
- Scripted MOSS Installation (Not slipestreamed as I’ve read about some issues with it)
- WSS and SPS SP1
- Infrastructure Update (read more here)
- All necessary updates (August Cumulative et al, read more here)
- WSS / MOSS Language Packs (order does not matter)
- Language Pack Service Packs
Note: If you are busy with a particular update, complete that on all the servers in the farm before moving to the next. For example, don’t install WSS language packs and move onto the MOSS language packs without installing them on all and executing the configuration wizard.
Pay special attention to each step and if the wizard fails to update (Configuration Failed) there is a 99% chance that your server is not on the same patch level (one or two behind) as the other servers. Trust me, spending an extra hour on a large farm will save you days in the long run.
I’ve seen posts where people are asked to add missing files to 12 hive directories and dll’s to the bin directory and honestly, if it gets to that, it’s time to re roll.
If I come across any other funky workarounds I will be sure to update this post.
If you are reading this post, you have more than likely hit the same brick wall as what I did some time ago. Yes, you tried to install MOSS 2007 on Windows Server 2008 without SP1. FAIL!
Microsoft do not allow the installation of MOSS 2007 without SP1 on Windows Server 2008 without the SP1 as a result of a number of known compatibility issues. Good idea, but is still annoying I guess.
Anyway, here are some links that will help you through the process:
“As of Windows SharePoint Services 3.0 with Service Pack 1 (SP1), you can install Windows SharePoint Services 3.0 and Office SharePoint Server 2007 on Windows Server 2008. You cannot install Windows SharePoint Services 3.0 or Office SharePoint Server 2007 without service packs on Windows Server 2008.”
Go to the Windows Server 2008 Resource Center for SharePoint Products and Technologies for detailed information on this topic.
Well, the short answer is no.
A colleague of mine recently ran some tests to see whether one could successfully host SharePoint 2007 on Windows Server 2008 Core Edition. Here’s what he said:
“I have done some research lately on the different configurations for MOSS on Windows 2008 and was very interested to see if MOSS can be run on Windows 2008 Core edition.
Now for those who don’t know what Windows 2008 Core edition is, it is an installation that contains the core components of Windows 2008 with no GUI. So, it is command line driven. The reasoning for wanting to use this is that, without all the extra fluffiness of Windows 2008 GUI, the operating system delivers its platform applications at a much higher speed.
But ALAS after some research it’s shown that MOSS 2007 is not supported on Windows 2008 Server Core Edition.“
SharePoint 2007 is supported on the following Windows 2008 Servers:
- Windows Server 2003/2008, Standard Edition
- Windows Server 2003/2008, Enterprise Edition
- Windows Server 2003/2008, Datacenter Edition
- Windows Server 2003/2008, Web Edition