Bitcoin hardware

bitcoin cloud mining

Elementary URLs Numerous Pools

I looked around on the top related threads before posting and they don’t seem to reaction my question downright.

Presently, I have three lync 2013 EE pools, one being a test pool that is going away. and the other two are going into production. Presently, meet, dialin, and admin all point to the one server ter the test pool.

Swtiching to a dual pool deployment, can I still run a single plain url for each (meet, dialin, admin) and just have it round robin the pool url pointed to the VIP on the HLB or do I need a seperate url for each pool?

Meet, Admin, Dialin DNS URLS

Does this make sense or am I downright wrong?

Answers

Yes. the users te 2nd pool can create the conference, but no one will be able to join. 🙂

I think based on the discussions so far, the best way forward for you is to have a headache now by creating Two different webpagina level URL’s. Provided you have redundant HLB’s – otherwise you will be having several headache’s each time the HLB goes / is taken offline.

If you see a postbode that helped you please click ",Vote spil Helpful", and if it answered your question, please click ",Mark spil Answered.

  • Proposed spil response by Murali Krishnan – Friday, November 22, 2013 9:35 AM
  • Marked spil response by LyncDude Tuesday, November 26, 2013 9:29 PM

All replies

Does both thesis pools belong to a single Lync central webpagina ? or is it part of central webpagina, but geographically entirely seprate locations (for e.g. one ter Europe and 1 ter the US ? ) and also are the pools served by Two different switch sides proxies ?

Because it is best to keep one set of elementary URL’s with a global scope. But if you want separate URL’s, that is fine spil well and can have MeetUS.domain.com and MeetEU.domain.com etc. but need to keep te mind about extra SAN names.

Having said that, since the ordinary URL’s are normally set at an organisation level rather than webpagina level te Lync topology builder, the URL can remain the same even if you add more pools. just point it to the VIP of the HLB.

Hope that helps.

If you see a postbode that helped you please click ",Vote spil Helpful", and if it answered your question, please click ",Mark spil Answered.

ordinary URL’s are primarily used for joining meetings. So does your deployment have a primary (large no of users) and secondary datacentres by any chance ? If so, send it to the primary pool VIP. If it finds that the meeting is located at the other pool, it will redirect itself. will save a lotsbestemming of hassle te creating Two sets of webpagina level URL’s.

Also DNS loadbalancing will not work with ordinary urls if you point them to Two different VIP’s. Spil you’ll have to use round robin and this could point you to an HLB’s which is offline and the request would fail.

If you see a postbode that helped you please click ",Vote spil Helpful", and if it answered your question, please click ",Mark spil Answered.

Murali and Iain,

Thank you for your replies. I am using two datacenters. 1/Trio of our users will be on one and Two/Three on the other, just to ensure that there are no issues with the redundant one overheen time. I’m basically looking for a DR/Hectare solution for plain URLS. What would toebijten if the primary datacenter that the URLs are pointed to went down, if it’s pointed to the VIP for the webpagina that went down? What you guys are providing mij is fine and I think I am beginning to understand. Apologies for being complicated.

ahh yes, sorry, left behind to mention that.

If the primary pool fails, spil part of the failover process, there will be a manual process of moving the elementary URL’s spil well.

Based on your situation, there are Two options.

1. point elementary url’s to the pool with Two/Trio of the users (unless 1/Trio of the users te the other pool uses conferencing services the most).

Two. use dns roundrobin for elementary url’s.

But if you don’t have redundant HLB’s (HLB pairs) at both sites then I wouldn’t use it, purely because you mentioned ‘Lync Pool’. so I’m assuming LYnc Enterprise edition servers which has Hectare built te and the chances of gegevens centre / Pool failure is much less than a single HLB failure.

Hope I’m making sense. :

If you see a postbode that helped you please click ",Vote spil Helpful", and if it answered your question, please click ",Mark spil Answered.

I’m looking for automatic redundancy spil much spil possible with out getting my other admins involved, spil far spil Lync is worried. It’s embarking to sound like I might have to go with two sets of ordinary urls to get the utter DR/Hectare support I’m looking for, that way when user’s are transfered overheen to the secondary pool I don’t have to mess with DNS settings. I am running Lync EE, two pools, and two seperate HLB.

If you are looking for resiliency spil far spil the Plain URL’s are worried, then yes. But I think the reaction lies ter the central webpagina question I asked before. Within Lync topology, are both thesis pools under the same central webpagina ? Because it can only either be Global scope’d or sile level ordinary url’s.

If you see a postbode that helped you please click ",Vote spil Helpful", and if it answered your question, please click ",Mark spil Answered.

For the best disaster recovery abilities ter Lync Server 2013, deploy pairs of Vuurlijn End pools across two geographically dispersed sites. Each webpagina contains a Gevelbreedte End pool which is paired with a corresponding Gevelbreedte End pool te the other webpagina.

Check more information about Pui End Pool Pairing at

TechNet Community Support

haha.. I cannot agree more spil I’m the worst when it comes to leaving behind things.. 🙂

Agree about logical &, physical sites, but with lync, the idea of Central sites and branch sites are a bit different.

Ter LSMS, if you run

will give you the number of sites and its type. My guess is that you’ll only see one te there, and if so, you can only have one set of plain URL’s.

If you see a postbode that helped you please click ",Vote spil Helpful", and if it answered your question, please click ",Mark spil Answered.

You are juist, several sites (Test, OCS, Primary, Secondary) and one webpagina type. The way I see it I have two options:

Point my elementary urls to my most active vip and hope for the best, if a disaster occurs I would need to call my domain admin to repoint the elementary urls to the backup webpagina VIP.

Create two sets of elementary urls, have a headache now, and potentially save a headache straks.

The punt is that ter the event of my primary datacenter going down, my users that are now te my secondary datacenter don’t have the capability of creating a conference because the URLS were pointed to the primary pool which te this example is down and inaccessible.

Yes. the users ter 2nd pool can create the conference, but no one will be able to join. 🙂

I think based on the discussions so far, the best way forward for you is to have a headache now by creating Two different webpagina level URL’s. Provided you have redundant HLB’s – otherwise you will be having several headache’s each time the HLB goes / is taken offline.

If you see a postbode that helped you please click ",Vote spil Helpful", and if it answered your question, please click ",Mark spil Answered.

  • Proposed spil reaction by Murali Krishnan – Friday, November 22, 2013 9:35 AM
  • Marked spil reaction by LyncDude Tuesday, November 26, 2013 9:29 PM

Microsoft is conducting an online survey to understand your opinion of the Technet Web webpagina. If you choose to participate, the online survey will be introduced to you when you leave the Technet Web webpagina.

Related movie: What Is Bitcoin – A Plain Explanation



Leave a Reply

Your email address will not be published. Required fields are marked *