getproperty -pn peoplepicker-searchadforests返回Property Exist =" No" [英] getproperty -pn peoplepicker-searchadforests returns Property Exist="No"

查看:90
本文介绍了getproperty -pn peoplepicker-searchadforests返回Property Exist =" No"的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我遇到服务器上的peoplepicker延迟问题。 我运行了以下命令,得到了结果Property Exist ="No"。 这是正常的吗? 我们有2个应用服务器和2个wfe服务器。我在wfe服务器上运行了命令。 
我正在解决人们选择器在wfe服务器上花费超过2分钟的问题。 另一台服务器在30秒内在peoplepicker框中显示结果。

I'm having issues with a delay on peoplepicker on a server.  I ran the below command and got the result Property Exist="No".  Is this normal?  We have 2 app servers and 2 wfe servers. I ran the command on the wfe server.  I'm troubleshooting an issue in which people picker takes over 2 minutes on one of the wfe server.  The other server shows results on peoplepicker box within 30 seconds.

PS C:\ Windows \ system32> Stsadm -o getproperty -pn peoplepicker-searchadforests -url" xxxx.com"

< Property Exist =" No" /> PS C:\ Windows \ system32> $ webapp.peoplepickersettings

PS C:\Windows\system32> Stsadm -o getproperty -pn peoplepicker-searchadforests -url "xxxx.com"
<Property Exist="No" />PS C:\Windows\system32> $webapp.peoplepickersettings

Evy

推荐答案

是的,它是正常的,因为它没有设置为默认值。

Yes, it is normal as it has no value set as default.

延迟通常是SharePoint由于防火墙端口而无法联系的域控制器(例如DMZ中的DC SharePoint尝试但无法联系)或只是远程和/或高延迟连接。

A delay would typically be a Domain Controller that SharePoint either can't contact due to a firewalled port (e.g. a DC in a DMZ that SharePoint attempts to but cannot contact) or simply one that is remote and/or over a high latency connection.


这篇关于getproperty -pn peoplepicker-searchadforests返回Property Exist =&quot; No&quot;的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
相关文章
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆