After performing some trial and error with migrating the Managed Metadata Service databases and attempting to attach the databases in another farm in hopes it would just come up, I came to the conclusion that this isn’t the best option. These are my steps for migrating the Managed Metadata Service from one farm to another. In my situation, we had an ESF farm setup where several services were hosted and are primary farm connected over to those services via a remote connection. I was tasked with migrating those services over to the primary farm to simplify the architecture. So these steps involve dropping the remote connection and re-creating it in the primary farm.
In an effort to setup Enterprise Search in SharePoint 2013 using PowerShell to make sure every nook and cranny was covered, I came across a number of scripts, but none seemed to do as good of a job as this one. I’m not sure what the original source is or who put it together, but it worked flawlessly. This is probably by far the best PowerShell script I have found for setting up Enterprise Search that does a good job of setting up every component. Enjoy!
Before running, create a folder on a hard drive of your choosing where indexes will be stored. In this case, I used “C:\SPSearchIndexes” for the Index location. This has to be created beforehand, otherwise it will fail!
To test out the migration of a site from SharePoint 2010 to 2013, I needed to convert a test environment web application to claims authentication to prepare for the move. However, to prove out my methodology and make sure I had the process down, I converted the web app back to classic authentication in order to repeat my steps. I’ve found a number of sites that explain how to do this, but have yet to find it all consolidated into one post. So here’s what I’ve found.
Need to give a service account access to a web application in SharePoint 2013? Easy! Just run these two PowerShell commands as the farm service account in the SharePoint PowerShell command prompt:
$webApp = Get-SPWebApplication http://contoso.com $webApp.GrantAccessToProcessIdentity("CONTOSO\svcacct-contoso")
In SharePoint 2010, if you had other domains that you needed to lookup users on in order to give them access to a site, it just worked without having to do any further configuration.
Not so with SharePoint 2013. You must add each domain and sub-domain to each web application to be able to perform user lookups from within the people picker.
So how do you do this? Well, with PowerShell, and fortunately Microsoft has provided a nice script that performs it for you. Otherwise, it would be quite a task.
It’s important to note that you must add the default domain your SharePoint environment is currently setup in. Otherwise, you won’t even be able to do lookups in it! (Found that out the hard way)
Instructions: Open Notepad or your favorite text editor, copy and paste the code below into the file, and save it as a .ps1 file. Open the SharePoint PowerShell command window as an Administrator, and an account with farm level access, change the directory (cd C:\YourDirectory, etc.) to the place you saved the code below (as a .ps1 file), type out .\YourPowerShellScript.ps1 and hit enter.
*I provide this as is, with no guarantees it will resolve your issues. And if you muck up your environment, it’s not my fault. 🙂 Obviously you should perform this on a dev or test environment first before attempting it in production. Good luck!*
Since I had to piece together how to accomplish the migration of a host-named site collection (HNSC) I had already setup in SharePoint 2013, from one farm to another, I figured I would outline exactly how to do it. In my case, I needed the HNSC to be in its own content database, I’m targeting a particular web app with the HNSC as opposed to using a wildcard web app to handle the hostnames, and all of this is assuming you have your rights setup to be able to carry out all of this; SQL, SharePoint farm account and otherwise. With that said…
Here are some highlights from the conference. There’s a lot more detail, but this is the good stuff I’ve gathered.
- SP2013 RTM was released.
- Drag and drop documents into document folder; preview documents in pop-up window (including the ability to scroll through, it’s not just an image). Really cool.
- Drag and drop does work cross-browser. Really great news.
- One of the coolest functions for developers and designers in SP2013: automatic HTML to master page conversion.
- SP2013 is backward compatible with 2010 … in almost every way, from back-end to front-end (this was contradicted later as I’ll show, however for the most part, I believe it’s accurate)
- SP2013 central admin UI is different but structure/taxonomy is the same for the most part
- Said in keynote: custom solutions work just the same in 2013 from 2010. (Yeah, we’ll see 🙂 )
- New: Search-driven navigation. Intriguing and powerful.
- Your own profile in MySites has a news feed that looks almost like Facebook and Twitter combined. You can follow certain sites or (what were once called) document libraries and it will all show up in one feed. You can then interact with others’ posts and conversations.
- Client and server-side, they made significant reductions in I/O (on the back-end) and bandwidth (via the front-end); 40% reduction in bandwidth usage over-all; 50% reduction in SQL I/O by eliminating redundant queries and limiting the number of queries a single page makes; image compression is now 4X what it was.
- eDiscovery: not just for SP, but also Exchange and other apps (like Project Server). You can freeze a file in its existing state, without affecting the file itself (meaning changes can still be made, but it doesn’t change the copy you’ve frozen), without user knowing it, in case of audit.
- When versioning items, now only the delta is saved as opposed to the entire item each time. This significantly reduces SQL content DB growth.
- Web analytics is now rolled into search. Very cool.
- Down side: you cannot do an in-place upgrade. Only database attach. Not many people were happy about that apparently (maybe it was just me; that’s how I upgraded 2007 to 2010).
- Down side: Office Web Apps now exists on its own, you no longer install it within SP as a service application. If upgrading, you would need to install Office Web Apps on its own server(s).
- OWA bolts into Exchange now. Interesting.
For whatever reason, I got an upgraded hotel room at Mandalay Bay; a suite, very nice:
It’s amazing these are still allowed in hotels. Wonder how much longer that will last. Even Vegas still holds out hope and truth though for now.
Mandalay Bay Hotel, Luxor in the middle, and THEhotel to the left.
ClubLAX, aka ClubSPC (since M$ bought it out from 6-8pm one night); the decibel level was astounding. I’m getting old.
Bumblebee, of course.
One of the many meals where 10,000 people were served two full meals a day. Quite a serious logistical operation. Mandalay Bay pulled it off. Very impressive.
Waiting in line, for 40 minutes, with 10,000 people for Jon Bon Jovi and a lot of food; the SPC Beach Party. The lobster tacos were killer. I was too full after those to try anything else. I had to bolt early to make it to the next event …
This was the highlight for me: The @RBAConsulting Sky Party. 34th floor of the Palms Casino Resort, overlooking the strip. I overheard that this loft/suite was $40,000 a night? Good grief. Cigar rolling, drink, food, music, all overlooking Vegas. The pool went out over the edge, suspended. It was by far the coolest event I went to.
Best shot I got …
DJ, mixin’ it up! He never did get around to the Snoop Dogg song I requested though 🙂
Oh yeah, and looooots of SharePoint sessions 🙂