Quantcast
Channel: Mavention
Viewing all articles
Browse latest Browse all 715

SP2013 installation lessons learned part 2

$
0
0

This part is about some things I ran into while installing a new search topology. In my previous blogpost (lessons learned part 1) I gave a solution when the search topology does not work. The solution was to start the WSS Usage Analytics Application Proxy.

Well, some time later I ran into another search topology that did not start either. This time it was a topology I wanted to install with PowerShell on multiple servers in a SharePoint 2013 farm. Somewhere on the technet forum I found links to 3 hotfixes that (according to the writer) have to be installed on all SharePoint servers to make it work.

The three hotfixes are (only for Windows Server 2008 R2 SP1):

http://hotfixv4.microsoft.com/Windows%207/Windows%20Server2008%20R2%20SP1/sp2/Fix402568/7600/free/447698_intl_x64_zip.exe

http://hotfixv4.microsoft.com/Windows%207/Windows%20Server2008%20R2%20SP1/sp2/Fix368051/7600/free/433385_intl_x64_zip.exe

http://hotfixv4.microsoft.com/Windows%207/Windows%20Server2008%20R2%20SP1/sp2/Fix354400/7600/free/427087_intl_x64_zip.exe

After installing these hotfixes on the two SharePoint servers (Web front End and Application) and installing the initial topology, I have configured search with the PowerShell scripts in this technet article: http://technet.microsoft.com/en-us/library/jj862356.aspx

The topology I was configuring:

Virtual machine A  (…208t)

Virtual machine B  (..206t)

Admin component

Crawl component

Content processing component

Analytics processing component

Query processing component

Index component 1 (that belongs to index partition 0)

After following the technet article this was the output:

searchcomponents

And this the final search topology:

searchadmin


Viewing all articles
Browse latest Browse all 715

Trending Articles