Thursday, October 4, 2018
Friday, September 21, 2018
How to host multiple subdomain sharepoint website under Godaddy
Scenario : I do have multiple wild card sharepoint sites need to be hosted under single domain ,
in my case i have domain name "SoftPOC.com"
1) SoftPOC.com is a static company site and hosted under different domain hosting provider freehostia.com.
x
x
2) I need to host a sharePoint site my.softpoc.com , sg.softpoc.com , I have added a "A" record and pointed this to my Loadbalncer IP or my Static IP of the sharepoint WFE azure server.
Wednesday, July 25, 2018
Change SP2016 WFE as WFE with Distributed cache (2 WFE +1SQL +1 Search)
I have 2 WFE and 1SQL and 1 Search server in single farm, As per the requirement both the WFE now needs to change the role from WFE to WFE+Distributed cache.
1) Run the below command in both the WFE
Add-SPDistributedCacheServiceInstance -Role WebFrontEndWithDistributedCache
2) Wait for few minutes and go to
go to CA -> System
Settings > Convert
server role in this farm
Select the role under New Role drop down and change this to
Front end with Distributed cache, Click Apply .
3)V erify that the Distributed Cache service is started. To do this, in the SharePoint Central Administration website, click Application Management. In the Service Applications section, click Manage services on server.
Search Service configuration to Single server under (2 WFE+1 SQL+1Search)
Run the below commands to SP 2016 Search server
$App1 = "MCMYPSPA01"
$SearchAppPoolName = "SharePoint Search Application pool"
$SearchAppPoolAccountName = "apps\svc.srch"
$SearchServiceName = "SharePoint Search Service Application"
$SearchServiceProxyName = "SharePoint Search Proxy"
$DatabaseName = "SP_Prod_AppFarmA_Search_AdminDB"
#Create a Search Service Application Pool
$spAppPool = New-SPServiceApplicationPool -Name $SearchAppPoolName -Account $SearchAppPoolAccountName -Verbose
#Start Search Service Instance on all Application Servers
Start-SPEnterpriseSearchServiceInstance $App1 -ErrorAction SilentlyContinue
#Start-SPEnterpriseSearchServiceInstance $App2 -ErrorAction SilentlyContinue
Start-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance $App1 -ErrorAction SilentlyContinue
#Start-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance $App2 -ErrorAction SilentlyContinue
#Create Search Service Application
$ServiceApplication = New-SPEnterpriseSearchServiceApplication -Partitioned -Name $SearchServiceName -ApplicationPool $spAppPool.Name -DatabaseName $DatabaseName
#Create Search Service Proxy
New-SPEnterpriseSearchServiceApplicationProxy -Partitioned -Name $SearchServiceProxyName -SearchApplication $ServiceApplication
#----------------------------------------------------
$clone = $ServiceApplication.ActiveTopology.Clone()
$App1SSI = Get-SPEnterpriseSearchServiceInstance -Identity $App1
#We need only one admin component
New-SPEnterpriseSearchAdminComponent –SearchTopology $clone -SearchServiceInstance $App1SSI
#We need content processing components
New-SPEnterpriseSearchContentProcessingComponent –SearchTopology $clone -SearchServiceInstance $App1SSI
#We need analytics processing components
New-SPEnterpriseSearchAnalyticsProcessingComponent –SearchTopology $clone -SearchServiceInstance $App1SSI
#We need crawl components
New-SPEnterpriseSearchCrawlComponent –SearchTopology $clone -SearchServiceInstance $App1SSI
#We need query processing components
New-SPEnterpriseSearchQueryProcessingComponent –SearchTopology $clone -SearchServiceInstance $App1SSI
#---------------------------------------------------------
#Set the primary and replica index location; ensure these drives and folders exist on application servers
$PrimaryIndexLocation = "E:\SharePoint\index\Data"
#We need index partitions and replicas for each partition. Follow the sequence.
New-SPEnterpriseSearchIndexComponent –SearchTopology $clone -SearchServiceInstance $App1SSI -RootDirectory $PrimaryIndexLocation -IndexPartition 0
$clone.Activate()
Monday, July 9, 2018
Wednesday, July 12, 2017
Get the Lync Server Details for Migration
Run the below command on Lync FE server
1) Get-WmiObject -query 'select * from win32_product' | where {$_.name -like "*Lync Server*"} | ft Name, Version -AutoSize >c:\version.txt
Tuesday, October 11, 2016
Server information as a wall paper utility BGINFO
https://technet.microsoft.com/en-us/sysinternals/bginfo.aspx
If you manage multiple computers you probably need BGInfo. It automatically displays relevant information about a Windows computer on the desktop's background, such as the computer name, IP address, service pack version, and more. You can edit any field as well as the font and background colors, and can place it in your startup folder so that it runs every boot, or even configure it to display as the background for the logon screen.
Subscribe to:
Posts (Atom)
HTML
Script:


