I just inherited a Lync 2010 admin job at my company.  (Never used Lync before)

When I open the Topology builder, it asks to pic a topology file..

How do I find which one is in use?    I have found about 10 different files. 

Obviously I dont want to open and use the wrong one.

So, you're not PICKING a topology.   The topology builder is an app that is going to DOWNLOAD the current topology from your Lync environment.   It's going to SAVE that to a local file though.   So, just choose 'todays_date_LyncTopology.xml" and then save it somewhere.  The topology will then load and you'll be faced with even more questions to post...

Good luck!!  :)

-G

• Proposed as answer by Anthony CaragolMVP 14 hours 21 minutes ago
• Marked as answer by JohnFLi1 13 hours 40 minutes ago

Here is the first screen ... DOWNLOAD the topology ...

Then, TB requires you to save that topology locally.  In case you screw something up, you can OPEN the one that you  just saved and you can publish it back and 'role back' you changes.  It's a great fail safe feature ... 

• Edited by Greg Seeber 14 hours 31 minutes ago
• Proposed as answer by Anthony CaragolMVP 14 hours 21 minutes ago
• Marked as answer by JohnFLi1 13 hours 40 minutes ago

AWESOME!!!!

Thank both of you!!

Lets see if you're as good with my next question in a new post   ;)

So, you're not PICKING a topology.   The topology builder is an app that is going to DOWNLOAD the current topology from your Lync environment.   It's going to SAVE that to a local file though.   So, just choose 'todays_date_LyncTopology.xml" and then save it somewhere.  The topology will then load and you'll be faced with even more questions to post...

Good luck!!  :)

-G

• Proposed as answer by Anthony CaragolMVP Wednesday, March 18, 2015 5:00 PM
• Marked as answer by JohnFLi1 Wednesday, March 18, 2015 5:40 PM

So, you're not PICKING a topology.   The topology builder is an app that is going to DOWNLOAD the current topology from your Lync environment.   It's going to SAVE that to a local file though.   So, just choose 'todays_date_LyncTopology.xml" and then save it somewhere.  The topology will then load and you'll be faced with even more questions to post...

Good luck!!  :)

-G

• Proposed as answer by Anthony CaragolMVP Wednesday, March 18, 2015 5:00 PM
• Marked as answer by JohnFLi1 Wednesday, March 18, 2015 5:40 PM

So, you're not PICKING a topology.   The topology builder is an app that is going to DOWNLOAD the current topology from your Lync environment.   It's going to SAVE that to a local file though.   So, just choose 'todays_date_LyncTopology.xml" and then save it somewhere.  The topology will then load and you'll be faced with even more questions to post...

Good luck!!  :)

-G

• Proposed as answer by Anthony CaragolMVP Wednesday, March 18, 2015 5:00 PM
• Marked as answer by JohnFLi1 Wednesday, March 18, 2015 5:40 PM

So, you're not PICKING a topology.   The topology builder is an app that is going to DOWNLOAD the current topology from your Lync environment.   It's going to SAVE that to a local file though.   So, just choose 'todays_date_LyncTopology.xml" and then save it somewhere.  The topology will then load and you'll be faced with even more questions to post...

Good luck!!  :)

-G

• Proposed as answer by Anthony CaragolMVP Wednesday, March 18, 2015 5:00 PM
• Marked as answer by JohnFLi1 Wednesday, March 18, 2015 5:40 PM

So, you're not PICKING a topology.   The topology builder is an app that is going to DOWNLOAD the current topology from your Lync environment.   It's going to SAVE that to a local file though.   So, just choose 'todays_date_LyncTopology.xml" and then save it somewhere.  The topology will then load and you'll be faced with even more questions to post...

Good luck!!  :)

-G

• Proposed as answer by Anthony CaragolMVP Wednesday, March 18, 2015 5:00 PM
• Marked as answer by JohnFLi1 Wednesday, March 18, 2015 5:40 PM

Here is the first screen ... DOWNLOAD the topology ...

Then, TB requires you to save that topology locally.  In case you screw something up, you can OPEN the one that you  just saved and you can publish it back and 'role back' you changes.  It's a great fail safe feature ... 

• Edited by Greg Seeber Wednesday, March 18, 2015 4:50 PM
• Proposed as answer by Anthony CaragolMVP Wednesday, March 18, 2015 5:00 PM
• Marked as answer by JohnFLi1 Wednesday, March 18, 2015 5:40 PM

Here is the first screen ... DOWNLOAD the topology ...

Then, TB requires you to save that topology locally.  In case you screw something up, you can OPEN the one that you  just saved and you can publish it back and 'role back' you changes.  It's a great fail safe feature ... 

• Edited by Greg Seeber Wednesday, March 18, 2015 4:50 PM
• Proposed as answer by Anthony CaragolMVP Wednesday, March 18, 2015 5:00 PM
• Marked as answer by JohnFLi1 Wednesday, March 18, 2015 5:40 PM

Here is the first screen ... DOWNLOAD the topology ...

Then, TB requires you to save that topology locally.  In case you screw something up, you can OPEN the one that you  just saved and you can publish it back and 'role back' you changes.  It's a great fail safe feature ... 

• Edited by Greg Seeber Wednesday, March 18, 2015 4:50 PM
• Proposed as answer by Anthony CaragolMVP Wednesday, March 18, 2015 5:00 PM
• Marked as answer by JohnFLi1 Wednesday, March 18, 2015 5:40 PM

Here is the first screen ... DOWNLOAD the topology ...

Then, TB requires you to save that topology locally.  In case you screw something up, you can OPEN the one that you  just saved and you can publish it back and 'role back' you changes.  It's a great fail safe feature ... 

• Edited by Greg Seeber Wednesday, March 18, 2015 4:50 PM
• Proposed as answer by Anthony CaragolMVP Wednesday, March 18, 2015 5:00 PM
• Marked as answer by JohnFLi1 Wednesday, March 18, 2015 5:40 PM

Here is the first screen ... DOWNLOAD the topology ...

Then, TB requires you to save that topology locally.  In case you screw something up, you can OPEN the one that you  just saved and you can publish it back and 'role back' you changes.  It's a great fail safe feature ... 

• Edited by Greg Seeber Wednesday, March 18, 2015 4:50 PM
• Proposed as answer by Anthony CaragolMVP Wednesday, March 18, 2015 5:00 PM
• Marked as answer by JohnFLi1 Wednesday, March 18, 2015 5:40 PM

Hey Greg, 

I have related question to Topology Builder. Am I able to edit properties and settings on my current Lync deployment, e.g. the SIP access port and URL on my Edge server, through the Topology Builder tool? And if I screw something I can load back a previous topology (.xml) file?

Thanks!

yeah. you can.  There is outbound ports that replicate policy from the FE (TCP/4443) to the edge.  From lync management CLI you can "get-csmanagementreplicationstatus" and see if replicate is happening.  Note that your edge servers are in tehre.  

Yes, from the time that you save the topology - you can publish ... you can role back to any previous topology if somethings goes terribly wrong.

There are certain things that you may, if you run into problems, need to run step-2 of the wizard OR run an 'enable-cscomputer' - like, IIS changes that lync may need to do under the hood.  Typically not, just watch out for it if something isn't doing what you tell it do to.  (after, of course, verifying replication and waiting around several minutes.  

• Edited by Greg Seeber 12 hours 41 minutes ago

yeah. you can.  There is outbound ports that replicate policy from the FE (TCP/4443) to the edge.  From lync management CLI you can "get-csmanagementreplicationstatus" and see if replicate is happening.  Note that your edge servers are in tehre.  

Yes, from the time that you save the topology - you can publish ... you can role back to any previous topology if somethings goes terribly wrong.

There are certain things that you may, if you run into problems, need to run step-2 of the wizard OR run an 'enable-cscomputer' - like, IIS changes that lync may need to do under the hood.  Typically not, just watch out for it if something isn't doing what you tell it do to.  (after, of course, verifying replication and waiting around several minutes.  

• Edited by Greg Seeber Monday, March 23, 2015 6:41 PM

yeah. you can.  There is outbound ports that replicate policy from the FE (TCP/4443) to the edge.  From lync management CLI you can "get-csmanagementreplicationstatus" and see if replicate is happening.  Note that your edge servers are in tehre.  

Yes, from the time that you save the topology - you can publish ... you can role back to any previous topology if somethings goes terribly wrong.

There are certain things that you may, if you run into problems, need to run step-2 of the wizard OR run an 'enable-cscomputer' - like, IIS changes that lync may need to do under the hood.  Typically not, just watch out for it if something isn't doing what you tell it do to.  (after, of course, verifying replication and waiting around several minutes.  

• Edited by Greg Seeber Monday, March 23, 2015 6:41 PM

yeah. you can.  There is outbound ports that replicate policy from the FE (TCP/4443) to the edge.  From lync management CLI you can "get-csmanagementreplicationstatus" and see if replicate is happening.  Note that your edge servers are in tehre.  

Yes, from the time that you save the topology - you can publish ... you can role back to any previous topology if somethings goes terribly wrong.

There are certain things that you may, if you run into problems, need to run step-2 of the wizard OR run an 'enable-cscomputer' - like, IIS changes that lync may need to do under the hood.  Typically not, just watch out for it if something isn't doing what you tell it do to.  (after, of course, verifying replication and waiting around several minutes.  

• Edited by Greg Seeber Monday, March 23, 2015 6:41 PM