locked
External Farm FQDN RRS feed

  • Question

  • Is there a way to look up what my External (and Internal, for that matter) Farm FQDN's are? I can't remember what I used during setup, and was wondering if there's a way to reference that info after the installation is done.
    Friday, May 29, 2009 1:17 PM

Answers

  • Hi,
    My recommendation, when all else fails, is to use wbemtest.  This KB article walk you through the process of querying WMI directly. http://support.microsoft.com/kb/938288. Under "resolution 1" it shows you how to change the externalwebfarm FQDNs - but at a minimum you'll be able to see what is null & what has a value.

    Don't be scared off by some of the crazy sounding steps; take your time and you'll end up really being able to see & understand all the settings. I've come to really rely on WBEMTEST lately.

    Regards,
    Matt

    Matt McGillen, PointBridge - https://blogs.pointbridge.com/Blogs/mcgillen_matt/default.aspx
    • Proposed as answer by sharadsharma2k5 Monday, June 1, 2009 10:55 PM
    • Marked as answer by paulbrown83 Tuesday, June 2, 2009 2:20 PM
    Monday, June 1, 2009 1:55 PM

All replies

  • Hi

      Please check this:
    http://technet.microsoft.com/en-us/library/bb803611.aspx

    To list the external Web farm FQDNs

    1. Log on to the Standard Edition server or Enterprise Edition server in the pool with an account that is a member of RTCUniversalServerAdmins group or has equivalent permissions.

    2. Open a command-line prompt.

    3. Navigate to the \Program Files\Common Files\Microsoft Office Communications Server 2007 directory.

    4. To list the external URLs for the Web farm, type the following command. This command creates a remote of WMI setting values and will output the location of the report.

      Lcscmd /web /action:ListWMISettings /poolname:<poolName>

      For example:

      Lcscmd /web /action: ListWMISettings /poolname:pool2
    5. Open the file using Internet Explorer or another Web browser and look up the values for the external URLs.

      Lcscmd /web /action:ListWMISettings /poolname:<poolName>

      For example:

      Lcscmd /web /action: ListWMISettings /poolname:pool2


    Thanks

    Friday, May 29, 2009 4:40 PM
  • You can also just run a validation on your front end if you want to stay in the UI.
    Mike Stacy | Evangelyze Communications | http://www.evangelyze.net/cs/blogs/mike
    Friday, May 29, 2009 4:41 PM
    Moderator
  • thanks for the tips. I did both suggestions here, and I'm wondering where I can find the web farm fqdn after running these. Maybe I'm just missing it, but I searched the resulting XML files and couldn't find it.

    Another interesting point... when I ran the ListWMISettings command, the resulting xml file stated that my pool is not ready. Most everything is working fine, so is this something I should be worried about?
    Friday, May 29, 2009 5:57 PM
  • Hi

    You must have mistyped your poolname on the commandline. If you do this you will get:

    ERROR (0xC3EC7814): Pool is not ready.

    You should use
    Lcscmd /web /action:ListWMISettings /poolname:<poolName>

    as a command. fill in the proper values for your environment and things should work fine.

    Thanks


    Friday, May 29, 2009 6:46 PM
  • cool, i had just added the domain info to the end of it (pool.domain.local) instead of just pool. It's a success now.

    Now, I remember the installation wizard a long time ago had a place to put an internal and external web farm fqdn. It was a while back, though, so where in this xml output file can I find what info I put into the wizard? this is probably simple, i'm just missing it.
    Friday, May 29, 2009 6:55 PM
  • To answer your earlier question, run the validation against the Web Components role and you'll see the URLs listed in the output.


    Mike Stacy | Evangelyze Communications | http://www.evangelyze.net/cs/blogs/mike
    Monday, June 1, 2009 3:11 AM
    Moderator
  • Mike,

    when i run that validation, I get the following results in the xml output file. Is this a problem?

    Execute Action    Error: Exception of type 'Microsoft.Rtc.Internal.Wmi.UnableToDetectMachineFullyQualifiedDnException' was thrown.
       Failure
    [0x80131500] 

    Initialize   Machine FQDN: atatlisdocsr2.core.gtri.test
    WMI Repository Path: \\.\root\cimv2
       Success
    Monday, June 1, 2009 12:18 PM
  • Actually, I take that back. On Friday I moved the DC's in this test environment over to a new subnet, and I'm still getting around to changing the static IP settings on my servers. I fixed this server's network config and reran the validation on the web components server. In the results I see a Machine fqdn, which is just the server's fqdn, but I don't see anything that might represent what I filled out during the installation. The reason I want to find this is because I think I left the external one blank, and I'd like to know where to find that info as I'm rolling out my edge server.

    Other curious things I found in this validation result... In the Check Connectivity section, I get a 401 unauthorized for both the Check GroupExpansion and the Checking Address Book Server configuration items.
    Monday, June 1, 2009 12:43 PM
  • Hi,
    My recommendation, when all else fails, is to use wbemtest.  This KB article walk you through the process of querying WMI directly. http://support.microsoft.com/kb/938288. Under "resolution 1" it shows you how to change the externalwebfarm FQDNs - but at a minimum you'll be able to see what is null & what has a value.

    Don't be scared off by some of the crazy sounding steps; take your time and you'll end up really being able to see & understand all the settings. I've come to really rely on WBEMTEST lately.

    Regards,
    Matt

    Matt McGillen, PointBridge - https://blogs.pointbridge.com/Blogs/mcgillen_matt/default.aspx
    • Proposed as answer by sharadsharma2k5 Monday, June 1, 2009 10:55 PM
    • Marked as answer by paulbrown83 Tuesday, June 2, 2009 2:20 PM
    Monday, June 1, 2009 1:55 PM
  • Matt,

    That kb article got me what i needed. and now I found the info in the xml output file from the lcscmd command as well. One more quick question though.. Does Resolution 2 on that article do the exact same thing as Resolution 1? Has anyone used resolution 2 and had the same results?

    Paul
    Tuesday, June 2, 2009 2:23 PM
  • Paul,

    Both resolutions in that article have the same end result.  Typically it's much easier to just use LCSCMD, but both options are available.
    Jeff Schertz, PointBridge | MVP | MCITP: Enterprise Messaging | MCTS: OCS
    Monday, June 8, 2009 6:29 PM
    Moderator