Search Application Topology

hey folks,

just recently i have implemented Search topology  with PowerShell so i thought i should share with you. there is no more UI options to set the search topology on different servers as we used to do in SharePoint2010, in SharePoint2013 you have to do it with PowerShell cmdlet , my current  scenario is that i have 3 servers and i have divided all component on these servers as you can see in the picture of After movement.

1 App Server

2 Web Front-end Servers.

SharePoint farm environment usually the Application Server will host all the Services including the Search Application services. The Search Application consists of several Search components like

  • Admin
  • Crawler
  • Content Processing
  • Analytics processing
  • Query Processing
  • Index

   Before Movement

Untitled

   After Movement 

search topology

 

below is the PowerShell cmdlet through these commands you can move the search Component.


$ssa = Get-SPEnterpriseSearchServiceApplication
$active = Get-SPEnterpriseSearchTopology -SearchApplication $ssa -Active
$clone = New-SPEnterpriseSearchTopology -SearchApplication $ssa -Clone –SearchTopology $active

$Srv2 = Get-SPEnterpriseSearchServiceInstance -Identity "Server Name Here"
New-SPEnterpriseSearchQueryProcessingComponent -SearchTopology $clone -SearchServiceInstance $Srv2
New-SPEnterpriseSearchAnalyticsProcessingComponent -SearchTopology $clone -SearchServiceInstance $Srv2
New-SPEnterpriseSearchContentProcessingComponent -SearchTopology $clone -SearchServiceInstance $Srv2
New-SPEnterpriseSearchCrawlComponent -SearchTopology $clone -SearchServiceInstance $Srv2

Start-SPEnterpriseSearchServiceInstance -Identity $Srv2
Set-SPEnterpriseSearchTopology -Identity $clone
—————-
<em>Clone again to remove original</em>

$ssa = Get-SPEnterpriseSearchServiceApplication
$active = Get-SPEnterpriseSearchTopology -SearchApplication $ssa -Active
$clone = New-SPEnterpriseSearchTopology -SearchApplication $ssa -Clone –SearchTopology $active

Get-SPEnterpriseSearchComponent -SearchTopology $clone  — to get the component id for the subsequent commands

Remove-SPEnterpriseSearchComponent -Identity  <strong><span style="text-decoration: underline;">COMPID</span></strong> -SearchTopology $clone -confirm:$false
Set-SPEnterpriseSearchTopology -Identity $clone

—–

COMPID is the component id of the search component to be removed. You can get all component running on the server by using the command

Get-SPEnterpriseSearchComponent -SearchTopology $clone

 

thanks

Hope this help

Happy sharePointing 😉

 

Advertisements

Convert VHDX to VHD format in Hyper-V

Hi guys,

i was importing windows 8.1 Virtual Machines in Windows server 2008 r2 Hyper-V environment so i have faced many issues in importing the VMs, so i experienced that you can not directly import windows 8.1 or windows server 2012 Virtual Machine into windows server 2008 r2. you have to convert the VHDX into VHD then you will be able to import in windows server2008 r2, i was wondering to write a blog  post on this topic. Please follow these steps to convert it into VHD.

Open your Hyper Server

2

Right click on the virtual machine which you want to export and click on setting option

2

Click on  hard drive option on your left and then click on edit button.

2

once located and selected click on next

you will new be prompt with 3 options

1). Compact

2). Convert

3). Expand

Select convert

1

now select what version you want to convert in my case i wan to export in VHD. click next

2

when you initially created the virtual machine if you accidentally dynamic instead of fixed here id one way to change that. if you want to keep it the same in this case dynamically available just click next

2

Select the path where you want to save this VHD

2

now click on finish to start the process

2

now wait for a while it will save your VHD in your given path. after complete this process you can import this VHD in Windows server 2008 R2.

Thanks and Regards

Ready to use Exchange 2013, Lync 2013 and SharePoint 2013 Demo and evaluation Virtual Machines

Microsoft has published a complete set of virtual machines ready to use with Exchange 2013, Lync 2013 and SharePoint 2013.

These VM’s can be used for demo and evaluation.

You can use all or part of these VM’s depending of the scenario you want to evaluate, including unified messaging.

The VM’s are set to be available for 180 days.

If you want to run the full environment, you need to host the VM’s on a server which has 24 Gb of RAM and 150 Gb of disk space.

Download the VM’s here:

Thanks and Enjoy

Happy SharePointing 🙂