MSFT_SIPGlobalFederationSetting class
Microsoft Office Live Communications Server 2005 with SP1 |
MSFT_SIPGlobalFederationSetting
The MSFT_SIPGlobalFederationSetting class defines the default route and port used by internal servers to route to an Access Proxy. This class also provides a way to disable communication with the Access Proxy for all internal users.
The following syntax is simplified from MOF code and includes all inherited properties.
class MSFT_SIPGlobalFederationSetting { boolean EnableRouteToEnterpriseEdge; [key] string InstanceID; string RouteToEnterpriseEdge; uint32 RouteToEnterpriseEdgePort; };
Methods
This class does not define any methods.
Properties
The MSFT_SIPGlobalFederationSetting class has the following properties.
EnableRouteToEnterpriseEdge
Data type: booleanA switch to enable or disable federation for all internal users.
Value Description False Internal users cannot connect to an Access Proxy. True Internal users can connect to an Access Proxy. The default value is
false
. This property cannot be NULL.InstanceID
Data type: [key] stringA GUID value that uniquely identifies the global federation setting. The GUID must be encapsulated between the "{" and "}" braces; for example: "{01234567-0123-4567-89AB-CDEF01234567}".
This property cannot be updated.
RouteToEnterpriseEdge
Data type: stringThe FQDN (fully qualified domain name) of the Access Proxy. This property can be NULL, but only if EnableRouteToEnterpriseEdge is false. Default value is NULL.
RouteToEnterpriseEdgePort
Data type: uint32The port number of the Access Proxy. The valid range of values is 1 to 65535. This property can be NULL, but only if EnableRouteToEnterpriseEdge is
false
. The default value is NULL.
Remarks
Instances of this class can only be updated. For PutInstance operations only WBEM_FLAG_UPDATE_ONLY flag is supported.
Requirements
Server: Installed on Windows Server 2003 with Live Communications Server 2005 with SP1.
Namespace: Defined in \root\cimv2.
See Also
cc165092(v=office.11).md, Live Communications Server WMI Reference
What did you think of this topic? |
© 2008 Microsoft Corporation. All rights reserved. |