I was working with a client a little while back and we needed an easy way to setup search on the dev and test SharePoint environments. What I came up with to resolve that issue was the following script that will take a source and destination URL and it will transfer the search settings from the one environment to the other. I am publishing this with the consent of and at the request of this client because he thought it was cool enough to share. I have not used this in a while but I do remember that there were some interesting error messages that came up when trying to migrate the schema because of duplicate properties but there is an option to exclude that if you are getting those errors. Enjoy.
I tried embedding the scriptlet itself but some of the xml was getting lost so here is a zip of the ps1 file.
I was working at a client where we had to rebuild their search service to try and alleviate some issues that they were experiencing and as part of this I came to the realization that manually creating managed properties has got to stop. The problem is that there is no easy way to move service scoped properties from one server to another. Also as a developer, the fact that this is not easily deployed bugs me. I want to be able to deploy the properties consistently. I don’t want to have to go back and create them again and wait for another full crawl because I missed one or typed the name in wrong. What’s worse is there is no way of putting this configuration into version control to create a baseline configuration. Continue reading “SharePoint Search and PowerShell Automation Script”
Thanks for an awesome event. I have posted the slides to slideshare since they are rather large. Display templates are attached to this post.
I am working on getting the video onto YouTube so stay posted. It does look like however that my camera ran out of space near the end of the presentation.
Feel free to contact me if you have any questions.
I decided this week to change my demo from running on my laptop with its limited RAM and move it to Amazon’s cloud. Amazon has a pretty sweet setup where you can pay by the hour for the server time that you need. I now have a server that can handle the requirements of SharePoint 2013 without as many headaches as I had with my laptop. I looked at using cloudshare when I was prepping my demo for SharePoint Saturday Utah but I didn’t feel like paying that much for a whole month when I only needed the server to be running for a few hours.
I have the server setup after some fun oauth issues in SharePoint 2013. Now I have the fun part of transferring my demo content to this new server.
For those that are thinking of trying to run SharePoint 2013 on your own laptop. If you only have 8GB of RAM or less do not go there. You can get it working but all of the required pieces on one machine is too much. In order to do my last demo I had to turn off a bunch of services to free up memory. I had to severely trim the services for Search and the sad part was that my presentation was on search. So I had it crawl the content I needed then I turned off the crawler and indexer to free up the memory. Luckily no-one asked for live search results or changes. Now with this server that I can turn on whenever I want and only pay for the time that it is running I no longer have this problem. I love technology.