SPS2010 – Server Farm install avec local accounts… again
So we continue our journey of configuring our development farm on a standalone machine.
This time we attempt to register a new managed account which is a local account, the results:
Again we turn to PowerShell, this time using the new-spmanagedaccount cmdlet to get around the issue.
SPS2010 – Server Farm install avec local accounts
SharePoint knows what's best for you, and setting up a server farm with a local account is bad news bears.
If you select a farm install and then use a local account as your farm account when running through the configuration wizard, you get this:
Solution: Use the SharePoint 2010 Management Shell and the new-spconfigurationdatabase cmdlet. Then it's just a matter of running through the configuration wizard to connect to your new farm.
MOSS: BlobCache corruption
So here's the setup:
- Web application with disk based caching enabled for PDFs
(web.config - <BlobCache location=.. gif|jpg|...pdf)
- Accessing a PDF
- Result is the error below or PDF does not load in browser
Server 2008: Applying user settings…
This is a fun one.
9:05am - Applying SPS2010 October update.
9:15am - Prompt to reboot (stop your services before applying updates kids!)
9:20am - Try connecing to server through remote desktop, not working
9:25am - Try connecing to server through remote desktop, not working
9:30am - Try connecing to server through remote desktop, not working
9:40am - Try connecing to server through remote desktop, not working
9:45am - Try connecing to server through remote desktop, not working
10:00am - Try connecting to console (using vSphere client), see this:
10:10am - Still on 'Applying user settings...'
10:15am - Still on 'Applying user settings...'
10:20am - Still on 'Applying user settings...'
10:25am - Still on 'Applying user settings...'
10:30am - Coffee break! and, still on 'Applying user settings...'
Eventually... http://support.microsoft.com/kb/2379016
The article mentions SSL as a culprit, I take it this is due to the SharePoint Web Services web application in SPS2010.
SPS2010 – Host Header Site Collection
This is a nice improvement from WSS3.0/MOSS2007. SharePoint 2010 provides the ability to create host header site collections, simplifying the implementation of vanity URLs in the enterprise.
- This requires a DNS record for the name you're looking to use (A or CNAME work equally). In this example I'm going to use http://SharePointRocks
- Some keyboard work avec PowerShell OR a community solution (http://officetoolbox.codeplex.com/releases/view/42507)
We'll be using the PowerShell method.
SharePoint Summit 2011
If you didn't make it out to the Toronto SharePoint Summit, shame on you 
http://www.sharepointsummit2011.com/Toronto/conference_day2.htm#session_9_1
I've included my presentation here for your enjoyment. Enjoy!
Download - 24mb
NetMon parser for SharePoint
Cool new release from Microsoft. To get started do the following:
Install Netmon 3.4 if you don't already have it.
(http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=983b941d-06cb-4658-b7f6-3088333d062f)
Install updated NetMon parsers from CodePlex
(http://nmparsers.codeplex.com/releases/)
Install Office and SharePoint Products Network Parsers
(http://www.microsoft.com/downloads/en/details.aspx?FamilyID=568e2d62-cc97-401d-bc77-e22b8556235a&displaylang=en)
You might also want to check out the SQL parsers from CodePlex: (http://nmparsers.codeplex.com/releases/)
Personally I prefer Wireshark when looking at a network capture. http://www.wireshark.org/
SPS2010 – Server2K8 IIS7 Prep
Before you can even begin the SPS2010 install wizard you need to prep the box with certain Roles and Role Services.
The PrerequisiteInstaller.exe can take care of this for you; however it removes some control over the install and can leave a new administrator in the dark in terms of what is happening under the hood.
We will use ServerManagerCmd in this example. Please note that this command is only available in Windows Server. (Sorry 7!)
This post will demonstrate how to script out the install of the required server Roles and Role Services.
SPS2010 – Default Database Recovery Models
This is a brief post to update on Jeremy Jameson's post on the default recovery models for MOSS 2007 databses. Below is a simple table with the default recovery models for MOSS 2007 from Jeremy's post, and below that are the default recovery models for SharePoint Server 2010. Simply a reference. #4mr
MOSS 2007
| Database Name | Default Recovery Model |
|---|---|
| SharePoint_AdminContent_{GUID} | Full |
| SharePoint_Config | Full |
| {SSP name}_DB | Simple |
| {SSP name}_Search_DB | Simple |
| WSS_Content | Full |
| WSS_Content_{SSP name} | Full |
| WSS_Search_{server name} | Simple |
SharePoint Server 2010
| Database Name | Default Recovery Model |
|---|---|
| SharePoint_AdminContent_{GUID} | Full |
| SharePoint_Config | Full |
| {Help Search} | Simple |
| WSS_Content | Full |
| {Search Service Application}_CrawlDB | Simple |
| {SearchServiceApplication}_DB | Simple |
| {SearchServiceApplication}_PropertyStoreDB | Simple |
| ProfileDB | Simple |
| SocialDB | Simple |
| SyncDB | Simple |
| {BDC Service}DB | Full |
| {Managed Metadata Service}DB | Full |
| {PerformancePoint}DB | Full |
| {Secure Store}DB | Full |
| {State Service}DB | Full |
| {WebAnalytics}_Reporting | Full |
| {WebAnalytics}_Staging | Full |
| {WordAutomation}DB | Full |
| WSS_{Usage Application} | Simple |
SPS2010 – Install via answer file (config.xml)
Scripting an entire SharePoint farm is G.T's! (good times)
Today I found myself putting together a rather silent farm install. I started with the OOB provided config.xml file found in the Files directory of the install media for SharePoint Server 2010.
It provides a good base, but is missing quite a bit. Lord TechNet has a reference guide for the config.xml here: http://technet.microsoft.com/en-us/library/cc261668.aspx which provides some additional configuration elements.
While putting this together I continously ran into this error:
Setup Error
The Setup configuration file X:\whatever\my\file\config.xml is not valid. Run Setup again without using a Setup confguration file, or fix the configuration file.
This post provided some input into what may be happening. Turned out that if using the DATADIR and INSTALLLOCATION elements the word 'value' next to it must be as so: 'Value'. (Capital 'V', everything else lower case) The example provided in the TechNet article uses all capital letters for VALUE.
