[Index]
Title | Description | Details | |||||||||||||||||||||||||||||||||||||||||||||||
MinEndpointExpiration | When endpoints log on, they have the option of requesting an expiration timeout; this specifies the time interval that an endpoint can remain logged onto the system before it must contact the server and request an extension. The MinEndpointExpiration property represents the minimum amount of time that clients can be granted. For example, if the minimum time is set to 600 seconds and a client requests a timeout interval of 200 seconds, the client will be given the minimum allowed expiration period: 600 seconds. The MinEndpointExpiration must be between 300 (5 minutes) and 900 (15 minutes). The default value is 300. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
PoolState | Current state for the Registrar pool. Allowed values are: Active FailedOver FailingOver FailedBack The default value is Active. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
MaxEndpointExpiration | When endpoints log on, they have the option of requesting an expiration timeout; this specifies the time interval that an endpoint can remain logged onto the system before it must contact the server and request an extension. The MaxEndpointExpiration property represents the maximum amount of time that clients can be granted. For example, if the maximum time is set to 600 seconds and a client requests a timeout interval of 800 seconds, the client will be given the maximum allowed expiration period: 600 seconds. The MaxEndpointExpiration must be between 300 (5 minutes) and 900 (15 minutes). The default value is 900. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
ScopeClass |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Element |
|
||||||||||||||||||||||||||||||||||||||||||||||||
InMemory | Creates an object reference without actually committing the object as a permanent change. If you assign the output of this cmdlet called with this parameter to a variable, you can make changes to the properties of the object reference and then commit those changes by calling this cmdlet's matching Set-<cmdlet>. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
EnableDHCPServer | Indicates whether endpoints can use DHCP servers to locate a Registrar. If True, clients will send a DHCP Inform message when they first start; the DHCP server will respond by sending the fully qualified domain name (FQDN) of a Registrar that can be used to log on the user. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
DefaultEndpointExpiration | When endpoints log on they have the option of requesting an expiration timeout; this specifies the time interval that an endpoint can remain logged onto the system before it must contact the server and request an extension. The DefaultEndpointExpiration property represents the expiration timeout interval for clients that do not request a specific timeout value. The DefaultEndpointExpiration must be between 300 (5 minutes) and 900 (15 minutes). The default value is 600 (10 minutes). |
|
|||||||||||||||||||||||||||||||||||||||||||||||
EnableWinFabLogUpload | PARAMVALUE: $true | $false |
|
|||||||||||||||||||||||||||||||||||||||||||||||
WinFabMaxLogsSizeMb | PARAMVALUE: Int32 |
|
|||||||||||||||||||||||||||||||||||||||||||||||
UserCertificateReplicationThreshold | PARAMVALUE: UInt64 |
|
|||||||||||||||||||||||||||||||||||||||||||||||
MaxUserCount | Indicates the maximum number of users that can simultaneously be logged on to a Registrar. MaxUserCount can be set to any integer value between 2000 and 100000, inclusive. The default value is 12000. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Anchor |
|
||||||||||||||||||||||||||||||||||||||||||||||||
BackupStoreUnavailableThreshold | Specifies the amount of time the system will wait before determining that the backup store is unavailable; at that point, users will be placed in survivability mode. The default value is 30 minutes (00:30:00). |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Identity * | Unique identifier for the Registrar configuration settings to be created. To create settings configured at the site scope, use syntax similar to this: -Identity site:Redmond To create settings at the service level, use syntax like this: -Identity service:Registrar:atl-cs-001.litwareinc.com Note that a given site or service can only have, at most, a single collection of Registrar settings. If you try to create a new collection with the Identity site:Redmond and the Redmond site already hosts a collection of Registrar settings, then your command will fail. In addition, you cannot create new Registrar settings at the global scope. If you want to change values at the global scope, use the Set-CsRegistrarConfiguration cmdlet. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
MaxEndpointsPerUser | Indicates the maximum number of endpoints a user can simultaneously have connected to the system. (For example, a user who is logged on to Skype for Business Server 2015 with both a computer and a mobile phone would be using two endpoints.) MaxEndpointsPerUser must be set to a value between 1 and 64, inclusive. The default value is 8. Although it is possible to allow a user as many as 64 endpoints, it is recommended that the maximum number of endpoints not exceed 8. Values of 9 or more are used for backwards compatibility and, in rare cases, when suggested by Microsoft support personnel. For new deployments, the maximum number of endpoints should be no more than 8. Note, too, that the maximum number of endpoints is intended to give individual users multiple points of presence. As such, this setting is designed for individual users and not for groups of users (such as an entire department.) |
|