Using LWA and lync to simulate external test edge free single front end environment

Finish the preparatory work , So we can plug in a test machine Lync Client virtual machine , Because we have routers , So we just VLAN And virtual network is consistent with our router environment , We don't need to configure IP Address, etc , Just install Lync The client can . Let's first take a look at IP Whether the address has been obtained automatically .

And then we PING once meet.contoso.com, Note that contoso.com, No ADDS Domain contoso.local.

And then we start Lync Client input created Lync User's credentials .

If it is right, we will be prompted that we will connect to lfe.contoso.local, instead of lfe.contoso.com, It's because of our SIP Domain and our ADDS You will see this prompt when the domain is different .

We can simply test the various functions after we log in , We don't have the functions of deploying enterprise voice here , So it's a little bit empty .

And then we're in the lower right corner shift Right click Lync Icon , And then look at the configuration . We can see the internal and external configuration , Although we Lync External has been set up URL by contoso.com, But why are we still connected to contoso.local Well ？ Because we only have the front end , There is no edge , And here it is URL It's not the address we're connecting to , It's an internal and external function URL Address , Like the address book , It's not what actually carries us URL, What actually carries us should be a server FQDN, Instead of a URL.

We scroll down to see , Our connection state is internally TRUE, It shows that we are an intranet user , But actually we do log in outside .

that Lync How to judge whether we are connected internally or externally ？ It's very simple , It's through the edge server , If we load edge servers , Then the internal state in the configuration will be False, Instead, connect directly to the front end , It must be inside . in addition , In this environment , Because of our ADDS Domain and SIP Different domains , So we have to be able to parse our... Outside lcontoso.local Medium lfe, in other words Lync Front-end FQDN It has to be resolved , This is needed both internally and externally without edge servers A Records of the .

If we don't have this A Record , So whether we manually configure the login address or automatically configure the login address , We were never able to log in . Because when Lync When we find out that we don't find the edge but the front end ,Lync Will judge that we are intranet users , And intranet users can parse contoso.local All records in the domain , Naturally it includes Lync Front end server FQDN, In our environment, this is lfe.contoso.local.

So if we can't parse this address , So we can still automatically discover the login server address , Prompt us to enter the password , But no matter our password is right or wrong, we can't log in successfully .

Let's try logging in on the web again , Let's test both cases , The first case is that it can be resolved from the outside lfe.contoso.local, First, let's start with a whiteboard , It can be in the client or browser .

Then we share the desktop , There is no problem .

Next , We don't have a client installed on another one , And the lfe.contoso.local Of A Record clearing , We open the browser client again , We can still share desktops and programs , But at this moment Lync The browser client will prompt us that we can't demonstrate whiteboard due to network problems 、 Voting, etc .

We can't share whiteboards , And you can't see the whiteboard shared by others , But we can still see shared desktops and programs , And basically IM The function is OK .

stay ADDS Domain and SIP In the case of different domains , We must ensure that the outside can at least resolve to ADDS Domain front end server FQDN, Otherwise, in the borderless Lync Some functions in the environment are limited . Of course , There are many functions that can also be used in browser clients , Including audio and video 、IM、 desktop 、 The functions such as program sharing can be used directly . But the best thing is that we can still unify SIP Domain and ADDS Domain , This can be used better without increasing cost and complexity Lync, Of course, what we're talking about here is a borderless environment , If there are edges, you don't have to SIP Domain and ADDS The domain is consistent . Today's content is here , Thank you for your support , Any questions are welcome , Because my environment is limited , Maybe the test wasn't very thorough , If a friend can do a detailed and comprehensive test , So much the better .