Configure People Picker for Multi-Domains(or Cross Domains), Forests Environments

If you have SharePoint environment in new domain(example: Main) and also have old sharepoint in other domain(example: Constco) and want to bring Old sharepoint users into new SharePoint then follow the below steps

Open Two way/ One way Trust between Two Domain controllers (i.e. Old and New)

1)  Open the proper ports between SharePoint 2019 servers (except Database servers) and Old Domain  Controler (Constco)

2) exectue the below command in all servers in New sharepoint environment

           stsadm -o setapppassword -password Test$123   

            replace Test$123 to your own passowrd 

3)  exectue the below command in web servers only in New sharepoint environment

    stsadm -o setproperty -pn peoplepicker-searchadforests -pn peoplepicker-searchadforests -pv "forest:Main.Corp;forest:constco.corp,constcoDomain\loginname,'password'" -url "SharePoint web URL"

Note: Replace Main to your new domain 

           constcoDomain to old domain

           loginname to old domain login name 

           password to Old domain password 

4) excecute all web servers

     stsadm -o setproperty -pn peoplepicker-searchadforests -pv "domain:Newdomain.CORP; domain:OldDomain.CORP" -url "web url"

5) Reset IIS


Note: Replace Red color text to your labels 


Proper ports list:

  • TCP/UDP 135 (RPC)
  • TCP/UDP 389 (LDAP default port)
  • TCP 636 (LDAP SSL default port)
  • TCP 3268 (LDAP Global Catalog)
  • TCP 3269 (LDAP SSL Global Catalog)
  • TCP/UDP 53 (DNS)
  • TCP/UDP 88 (Kerberos)
  • TCP/UDP 445 (Directory Services)

    Optional Ports:
  • TCP/UDP 749 (Kerberos-Adm)
  • TCP port 750 (Kerberos-IV)
-------------------------------------------------
Please use the below article for reference:

https://aarohblah.blogspot.com/2016/02/my-notes-on-sharepoint-2013-user.html
http://sharepoint-talk.blogspot.com/2011/09/sharepoint-people-picker-and-active.html

Comments

Post a Comment

Popular posts from this blog

SharePoint 2016 and 2019 Ports

http://sharepoint2016server.blogspot.com/2016/10/sharepoint-2016-ports-list.html SharePoint 2019: Distributed Cache : TCP Port 22233, 22236 : UDP Port N/A : Protocols ICMP Type 0 (ping) People Picker : TCP Port 53, 88, 135, 137–139, 389, 445, 636, 749, 750, 3268, 3269 : UDP Port N/A 53, 88, 137–139, 389, 445, 749 : UDP Port N/A : Protocols N/A Sandbox Service : TCP Port 32846 : UDP Port N/A : protocols N/A Search Crawler : TCP Port Web Application Ports Used (e.g., 80, 443) : UDP Port N/A : Protocols N/A Search Index : TCP Ports 16500–16519 : UDP Port N/A : Protocols N/A Service Applications : TCP Port 32843, 32844 : UDP Port N/A : Protocols N/A SQL Server : TCP Port 1433 (default) : UDP Port 1434 (default) : Protocols N/A WCF Services : TCP Port 808 : UDP Port N/A : Protocols N/A User Profile Service : TCP Port 53, 88, 389, 5725, 1025–5000, 49152–65536 : UDP Port 53, 88, 389, 464 : Protocols N/A SMTP : TCP Port 25 (default), 587 (TLS default) : UDP Port N/A : Protocols
Read more

PsConfig step by step /Configuration Wizard. “Upgrade Available” vs “Upgrade required”

Image
The "Upgrade available" simply means that there is a newer patch available at the SharePoint Updates page than the one installed on your SharePoint farm. We checked the Farm version and made sure its the latest available version. Getting "Upgrade Required" error message in SharePoint 2013? Well, Ideally, We have to run the SharePoint Products Configuration Wizard on the server(s) right after installing the service pack/patches. In Windows Server 2012, SharePoint updates are part of Windows Server Update. It installs patches but never runs Products configuration wizard automatically! You still have to run psconfig wizard to complete patching! ----------------------------------------------------  https://www.sharepointdiary.com/2014/02/upgrade-available-server-status-after-sharepoint-patching.html https://www.sharepointdiary.com/2015/03/upgrade-required-status-in-sharepoint-central-admininstration.html https://blog.stefan-gossner.com/2015/08/20/why-i-prefer-psconfigui
Read more

Clear fields based on drop-down values in PowerApps

Clear current selection from drop down when another drop down value changes 1) Parent drop-down is States 2) Child drop-down is City We can hide and show the City drop-down based on States Value changes NOTE: Please use your DataCardValues and  lv_dpclear is local variable Select City data card and go to the Advanced properties for DataCard Look for the Visible property and write the below code If(DataCardValue3.Selected.Value="VA",true,false) For clearing the City dropdown selected value based state changes. Select the State drop-down (first drop-down) and go to Advanced use the below code in OnChange  UpdateContext({lv_dpclear: true}); UpdateContext({lv_dpclear: false})  In the Reset property of the second dropdown(City), add the below code       lv_dpclear -------------------------------------------------------------------- Clearing text box and Date Control values based on dropdown selection: Add below code in drop-down OnChange 
Read more