Quick note to let you know that SPSIndia 2012 Online Videos have been published here
I have been evaluating Windows Azure [CDN – Images on this blog] and Amazon Glacier for storage and I will most likely end up using both for
- VHD to spin up environments on the fly in Azure (need to try this and for that I must get the VHD up in Azure Blobs)
- Cheaper Storage of Data – Glacier is definitely cheap at $0.01 per GB / month
Now with multiple “cloud” storage accounts – you need one client, irrespective of the storage provider you use. For me it’s the CloudBerry S3 Backup Enterprise Edition (since I can have unlimited network locations backed up)
Per my previous blog post – Search Admin Component Not Running, it was noted that that for the search admin component to run, you would need at least 3 additional hot fixes & if that didn’t work running a windows update and installing all the missing updates would certainly fix the Search Admin Component Not Running issue.
Todd Klindt also has blogged about the 3 missing pre-requisites in his blog post.
After provisioning the SharePoint 2013 Server Preview – Search Service Application – from the Central Administration, I see this error on the Search Administration in the Search Application Topology Section
I had used correct accounts, databases were created, Search related services were running on the server – no go!
Then I deleted the Search Service Application and used the Farm Configuration Wizard – same result.
The wraps were taken off last week on SharePoint vNext aka SharePoint 2013 and Preview bits have been made available to download and play!
This is the first post on SharePoint 2013 Preview and he objective is to provision Search Service Application and Usage Service Health with PowerShell to ensure that we have Database Names without GUID, else you will have to put up with something like this under