Changing number of NSPI connections on Windows 2008 Global Catalogs


hi

we looking change maximum number of nspi connections on windows 2008 global catalog servers 50 (default) 10,000 based on article below:

http://www.blackberry.com/btsc/viewcontent.do?externalid=kb17325&sliceid=1

"as of windows server 2008, microsoft has changed default behavior of domain controller regards named service provider interface (nspi) connections. nspi interface allows messaging application programming interface (mapi) interact global catalog server use microsoft® exchange address book , perform name resolution tasks requiring information stored in global catalog. prior windows server 2008, individual mapi client make virtually unlimited numbers of nspi connections global catalog without consequence. in order more appropriately manage these connections mapi clients, windows server 2008 introduced limit of 50 nspi connections per user. more details, see microsoft knowledge base article 2019948 @ microsoft support web site.

this limit has little no impact on single user mapi client; however, blackberry enterprise server has monitor mailbox each blackberry smartphone user added , requires more nspi connections client, such microsoft® outlook® would.

the number of nspi connections required blackberry enterprise server can vary based on number of blackberry smartphone users , frequency of calendaring activity. recommended configure value based on maximum possible concurrent connections blackberry enterprise server possibly make, rather typical average.

it suggested account 1000 nspi connections per 1000 blackberry smartphone users on blackberry enterprise server, rounded nearest thousand. example, blackberry enterprise server 0-1000 blackberry smartphone users use 1000 nspi connections. blackberry enterprise server 1001-2000 users use 2000 nspi connections.

it important note above method of determining number of required nspi connections on per server basis. limit on nspi connections on per user basis. if there multiple blackberry enterprise servers in environment running same service account, number of nspi connections blackberry enterprise servers require must added together.

for example, in environment 5 blackberry enterprise servers averaging 1500 blackberry smartphone users each blackberry enterprise servers run under same service account, maximum number of concurrent nspi connections required 10000. in environment same 5 blackberry enterprise servers each server runs under different service account, maximum number of concurrent connections required 2000."

can see potential problems changing value on our gc servers? mean, i'm sure ms changed reason?

regards

hi john,

 

this behavior occurs because windows server 2008 allows default maximum of 50 concurrent nspi connections per user domain controller. additional nspi connections rejected mapi_e_logon_failed error code.

 

please check resolution described in following kb article:

 

949469  nspi connections windows 2008-based domain controller may cause mapi client applications fail error code: "mapi_e_logon_failed"

http://support.microsoft.com/default.aspx?scid=kb;en-us;949469

 

regards,

wilson jia


this posting provided "as is" no warranties, , confers no rights. please click "mark answer" when correct reply question.


Windows Server  >  Directory Services



Comments

Popular posts from this blog

WIMMount (HSM) causing cluster storage to go redirected (2012r2 DC)

Failed to delete the test record dcdiag-test-record in zone test.com

Azure MFA with Azure AD and RDS