IT tutorials
 
Applications Server
 

Microsoft Lync Server 2013 Edge Server : Edge Server Administration (part 2) - Assigning External Access Policies, Managing Federation

2/7/2014 12:33:18 AM
- Free product key for windows 10
- Free Product Key for Microsoft office 365
- Malwarebytes Premium 3.7.1 Serial Keys (LifeTime) 2019

3. Assigning External Access Policies

After the new user policy is created, it must be assigned to a user account. If the external policy is created with a site scope, this step is not required.

1. Open the Lync Server Control Panel.

2. Select Users in the navigation pane.

3. Search for a user, highlight the account, click Modify, and click Assign Polices.

4. In the External Access Policy section, select the new external access policy, and click OK. An example of this configuration is shown in Figure 2.

Image

Figure 2. Assign an External Access Policy.

The Lync Server Management Shell can also be used to assign a policy to a user:

Grant-CSExternalAccessPolicy [email protected] -PolicyName "Allow all features"

4. Managing Federation

After enabling user accounts for federation, administrators can manage the organizations with which they want to federate through Lync Server. If partner discovery lookups are allowed on the Access Edge configuration, all domains are automatically allowed. Adding allowed domains can still be done to grant a higher level of trust to partners, but is not required. If partner discovery is not allowed, administrators must manually add all federated partners to the allow list.

Blocking a federated domain can be used to prevent internal users from communicating with specific partners. This is used in situations in which federation should be allowed globally, but blocked to only a few specific domain names. To allow or block a federated domain, use the following steps:

1. Open the Lync Server Control Panel.

2. Select Federation and External User Access in the navigation pane.

3. Click SIP Federated Domains.

4. Click New and then select either Allowed Domain or Blocked Domain.

5. Enter the SIP domain name of the federated domain allowed or blocked, as shown in Figure 3, and click OK.

Image

Figure 3. Adding an allowed domain for SIP federation.


Caution

When you are adding an allowed domain, the option exists to add the FQDN of the partner’s Access Edge Server. This field is not required, but when it is used it grants a higher level of trust to the domain by allowing more requests per second from the domain. Be careful when using this field because if a partner changes its FQDN later, the name will no longer be valid.


The Lync Server Management Shell can also be used to perform these tasks. To allow a new domain, use the following command. The only required parameter is the domain name, but a comment and partner’s Access Edge Server FQDN can also be specified. In addition, the MarkForMonitoring parameter can be set to enable quality monitoring to this domain by a Monitoring Server role.

New-CSAllowedDomain –Domain <SIP Domain Name> -Comment <Comment string> -ProxyFQDN <Partner Access Edge FQDN> -MarkForMonitoring <True|False>

To block a domain from sending or receiving messages, use the following command:

New-CSBlockedDomain –Domain <SIP Domain Name>

 
Others
 
- Microsoft Lync Server 2013 Edge Server : Edge Server Administration (part 1) - Editing the Global External Access Policy, Creating a New External Access Policy
- Microsoft Lync Server 2013 Edge Server : Edge Server Configuration
- Packaging and Deploying Sharepoint 2013 Apps : Packaging and Publishing an App
- Packaging and Deploying Sharepoint 2013 Apps : Anatomy of an App (part 3) - Web Deploy Package, Database Package
- Packaging and Deploying Sharepoint 2013 Apps : Anatomy of an App (part 2) - Manifest and Assets, SharePoint Solution Package
- Packaging and Deploying Sharepoint 2013 Apps : Anatomy of an App (part 1)
- Exchange Server 2013 : Exchange Clients - Design Considerations (part 3) - Network Usage, Exchange 2013 User Throttling
- Exchange Server 2013 : Exchange Clients - Design Considerations (part 2) - Client Performance
- Exchange Server 2013 : Exchange Clients - Design Considerations (part 1) - Supportability, Security
- Sharepoint 2013 : Community portals and sites - Managing your community settings
 
 
Top 10
 
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 2) - Wireframes,Legends
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 1) - Swimlanes
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Formatting and sizing lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Adding shapes to lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Sizing containers
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 3) - The Other Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 2) - The Data Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 1) - The Format Properties of a Control
- Microsoft Access 2010 : Form Properties and Why Should You Use Them - Working with the Properties Window
- Microsoft Visio 2013 : Using the Organization Chart Wizard with new data
Technology FAQ
- Is possible to just to use a wireless router to extend wireless access to wireless access points?
- Ruby - Insert Struct to MySql
- how to find my Symantec pcAnywhere serial number
- About direct X / Open GL issue
- How to determine eclipse version?
- What SAN cert Exchange 2010 for UM, OA?
- How do I populate a SQL Express table from Excel file?
- code for express check out with Paypal.
- Problem with Templated User Control
- ShellExecute SW_HIDE
programming4us programming4us