Lync Edge 2013 Service Publish With TMG 2010

Hello Experts,
I have a question for Lync edge and having issue in desktop sharing and program sharing with federated partners if logged in on internal as well as external (internet) network... setup is like below.
TMG with 3 leg architecture ; 1 internal IP, 1 DMZ IP and 4 public IP's (1 for sip access, 1 for web conf, 1 for av and last one for web services)
edge pool with 1 edge server having 2 NIC and 1 Intenal IP and 3 DMZ IP on second NIC ( GW for DMZ  is IP of TMG DMZ NIC card)
No Firewall.
so if all NAT rules and firewall rules configured properly on TMG should have any issue for desktop sharing/program sharing with federated partners. However some partners are working fine? Is desktop sharing / program sharing go through edge always for federated
partners?
Any information would be very helpful.
Many Thanks,
Ankur

Hello Ankur,
Desktop Sharing use the AV link to work. I already had some issues with TMG, check this http://technet.microsoft.com/en-us/library/ee796231.aspx
After deployed ARR to lync , I don't have more problems. Try this.
“Vote As Helpful” and/or “Mark As Answered” - Thiago Mendes da Silva - MCSE Communication - ITIL v3 Foundation - http://www.ucsteps.com/

Similar Messages

  • Exchange 2010/2013 coexistence published in TMG 2010

    Environment:
    Two Windows 2008 R2, Exchange 2010 SP3 servers, currently holding all mailboxes
    Two Windows 2012 R2, Exchange 2013 SP1 servers, setup in progress
    Two Windows 2008 R2, TMG 2010, V7.0.9193.540 publishing both Exchange 2010 servers.
    Scenario:
    I need to continue having Exchange 2010 setup in TMG as is as the mailbox migration to 2013 will take weeks if not months and I have a project requirement to have Exchange Database Availability Group (DAG) functionality for all mailboxes throughout the project,
    so 4 servers are an absolute must. So I need to add Exchange 2013 in TMG and not just replace the 2010 setup with the 2013 setup and I cannot run one 2010 and one 2013 server. 
    Questions:
    1. I currently only have 2 public IP addresses available to SMTP, mapped to the external interfaces of TMG, to allow my environment to be able receive emails on 4 Exchange servers (two 2010 and two 2013) I need to have 4 public IP addresses, is that correct?
    2. Does anyone have a good general guide/blog for doing this (setting up Exchange 2013 in TMG in a coexistance scenario)? 
    This is nice, but doesn't really approach it from a coexistance scenario:
    http://blogs.technet.com/b/exchange/archive/2012/11/21/publishing-exchange-server-2013-using-tmg.aspx
    Thanks!

    Hi Trana,
    In TMG you can use single IP address to publish multiple Web address and below are the options which you can explore.
    Hope your OWA ECP etc are Https
    You need a SSL certificate which has all the URL SAN entry of both old and new Exchange server.
    Create a listener and select the IP address (Say public IP address 195.219.x.x)
    Link the SSL certificate
    Public DNS entry
     A record , Single IP
    195.219.x.x 
    Point to           
    Owa1.exchange1.com   - Old Server
    195.219.x.x 
    Point to           
    ECP1.exchange1.com     - Old Server
    195.219.x.x 
    Point to           
    ECP2.exchange2.com      - New Server
    195.219.x.x 
    Point to           
    Owa2.exchange2.com     - New Server
    Create a Web publishing rule as below
    Old server Exchange 1
    Owa1.exchange1.com  
    ECP1.exchange1.com    
    One Web publishing Rule with all the URL added on it and link the Rule with the listener we created
    Point the Web publishing to Exchange1.com server which is old
    New server Exchange 2
     Web publishing Rule with all the URL added on it and link the Rule with the listener we created
    Point the Web publishing to Exchange2.com server which is New
    ECP2.exchange2.com     
    Owa2.exchange2.com    

  • Lync Edge 2013 Certificate Assign (again!)

    Hi,
    I recently posted a similar topic on the forum (Lync
    Edge 2013 Certificate Assign). The issue was related to certificate assignation. I solved it, but I needed later to change my certification authority, and so change the certificate assigned to the public Edge interface. Trying this, I encountered a new
    (different) problem with my new certificate, so I am back here to try to find a solution.
    As said, I am trying to assign a Certificate to my Lync 2013 Edge Server on the Internet edge.  This certificate is signed by a recognized authority (Comodo).
    Whenever I imported the certificate in the store via the Lync wizard and proceed on to the Assign Certificate step, the Certificate that i have imported does not appear in the List of certificates on the Lync deployment tool interface, so that I cannot assign
    it to the External Edge interface.
    I tried to import it with Digicert (which allow me to solve my previous importation problem, but not this time...) with no more result.  I tried to import it from cer format, or crt format, results are the same.
    I launched the MMC on the computer and add the Computer Certificate Snap-In. If I look at the certificate icon, I see the little key in the icon, so it sounds like I have the private key available.
    Any help would be greatly appreciated!
    Thank you very much for your help.
    EDIT: when running the digicert tool "Test Key", the result is the following : " the private key was successfully tested" and "revocation check for certificate chain failed". Does it give any clue ?

    I had the feeling I did everything fine too...!  This is maybe a silly question, but I try anyway: do you think it be possible that I cannot choose the imported certificate by the Lync Deployment assistant because the assistant does not recognize the
    public name of the computer? I mean, I could add the internal interface certificate because the computer recognized its local name (edge.local.domain). But it seems he doesn't know its Internet FQDN (lync.mydomain.com) which is mentionned in the topology.
    It does not explain why I could previously add the wilcard certificate, so I think my remark is silly, but I am kind of lost....
    Thank you anyway for your messages.
    EDIT: when I try to use powershell to assign manually my certificate, i got an error message telling that the command execution failed because [my certificate thumbprint] is not in the store or not approved. It is true that I had some intermediate certificate
    provided by Comodo, but I installed all of them in the store via mmc>Certificate, both in trusted root CA and intermediate CA. Maybe I miss a location ?

  • Exchange 2013 with TMG 2010 and Go Daddy

    Hi all;
    actually I'm new to exchange server 2013 and I need some help:
    recently I installed exchange 2013 in our domain with contains TMG 2010
    what I need is sending emails out.
    currently I can send emails internaly
    I have static IP and TMG and registered domain in Go daddy.
    could someone help me by steps what to do?
    in TMG?
    in Exchange administration?
    in Go Daddy?what records needed and how?
    and should I do any configurations in my DNS?
    please I'm stuck in this.
    Thanks

    Sorry, my fault. Try these links:
    http://blogs.technet.com/b/exchange/archive/2012/11/21/publishing-exchange-server-2013-using-tmg.aspx
    http://www.isaserver.org/articles-tutorials/configuration-general/publishing-exchange-2013-outlook-web-app-forefront-threat-management-gateway-tmg-2010.html
    CRM Advisor

  • Lync 2013 Cumulative updates with coexistence 2010

    Hello 
    I am pretty new lync admin, i have successfully done a coexistence with 2010 and 2013
    I just need clarification on the steps for a 2013 standard edition cu updates. 
    From the site http://support.microsoft.com/kb/2809243  I am seeing that I need to 
    1) run LyncServerUpdateInstaller.exe
    2)run Install-CsDatabase -ConfiguredDatabases -SqlServerFqdn SE.FQDN -Verbose
    3) Do not run Install-CsDatabase -CentralManagementDatabase until after full 2013 migration 
    4) Enable the Mobility service, run the following cmdlet:
    Enable-CsTopology
    5) Run %ProgramFiles%\Microsoft Lync Server 2013\Deployment\Bootstrapper.exe
    Just need those steps confirmed and..
    1) Just to confirm that I dont need to worry about output of Get-CsPoolUpgradeReadinessState command
    2) We dont have Mobility service, do I still need to run Enable-CsTopolgy for Standard edition?
    Thanks !

    Thank Iain 
    Just to confirm it is lync 2013 CU updates I am trying to perform on standard pool 
    When i run the CsPoolUpgradeReadinessState 
    I get State:insufficientActiveFrontEnds and IsReadForUpgrade True
    According to the update notes, they only speak of running cspoolupgradereadiness on Enterprise edition pool. 
    So i just wanted to know if the output of cspoolupgradereadinessState can be ignored or concerned about for the updates. 

  • Is Lync 2013 perfectly compatible with Office 2010?

    Microsoft Office 2010 and Lync 2013 are two diferrent instances, but they use some common elements.
    In our company we have over a hundred MS Office 2010 licences and we dont need/afford to change them all to 2013. Now we want to install Lync 2013 and I wonder if there could be compatibility issues or, if Lync 2013 can modifiy the common files they use,
    so that certain functions in Office 2010 will not be available or not work properly.
    Is there a risk of this happening or they can work together "in complete harmony"? This is very important to me and I cannot afford to make a mistake. I would appreciate any help. Thank you.

    Hi Cristi,
    Checkout these Lyncs on compatibility and interoperability:
    Lync 2013 Compatibility http://technet.microsoft.com/en-us/library/gg412817.aspx
    Client Interoperability http://technet.microsoft.com/en-us/library/jj204672.aspx
    As far as having Lync 2013 & Office 2010 on the same PC, largely it SHOULD be ok and I've not had many issues. The exception to this was on a recent Citrix deployment, where for some reason running Lync 2013 was causing the Office 2010 instance to rerun
    everytime it was started. All desktops were ok though.
    My suggestion is to make sure you thoroughly test with every scenario that you can think of before rolling out to the masses.
    If this helped you please click "Vote As Helpful" if it answered your question please click "Mark As Answer" | Blog
    www.lynced.com.au | Twitter
    @imlynced

  • Lync Edge 2013 NOT Replicating config data with CMS / NOT up to date

    I have recently installed my Lync 2013 Edge pool (1 edge server).
    all services are UP and public & internal certificates deployed successfully.
    BUT i keep seeing an X sign in the Replication Status field in the "Lync Control Panel->Topology" page.
    even running the "Get-CsManagementStoreReplicationStatus" gives:
        UpToDate           : False
        ReplicaFqdn        : internalEDGEFQDN.domain.com
        LastStatusReport   :
        LastUpdateCreation : 06/08/2013 10:09:41 AM
        ProductVersion     :
    telnet from my front-end to edge over port 4443 works
    all edge services are UP
    browsing [https://internalEDGEFQDN.domain.com:4443/ReplicationWebService] returns a special page
    there is a file called "data.zip" placed on the FileStore destined to my edge replica   \\filestorefqdn\lync2010files\1-CentralMgmt-1\CMSFileStore\xds-master\replicas\internalEDGEFQDN.domain.com\to-replica
    I dont know what might be causing the replciation to NOT get initiated. the edge server needs to be replicated so to be functional.
    thanks in advance,

    Hi,
    Please also run the Invoke-CsManagementStoreReplication cmdlet and allow time for the replication to complete before running the Get-CsManagementStoreReplicationStatus again.
    Would you tell us more details about certificate you used for Lync edge internal and external interface, and front end server? If you assigned a wildcard certificate to front end server, this may cause the replication issue between front end and edge.
    Please check event viewer if there is any relevant error message. In addition, you can refer to the blog you pasted how to check the CMS replication traffic.
    http://ocsguy.com/2011/09/07/troubleshooting-cms-replication/
    Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make
    sure that you completely understand the risk before retrieving any suggestions from the above link.
    Kent Huang
    TechNet Community Support

  • Error the service FWSRV of TMG 2010 on Windows server 2008 R2 Enterprise

    Please help me about a issue of TMG 2010:
    My company installed TMG 2010 on Windows server 2008 R2 Enterprise but it happen error " Due to an unexpected error, the service fwsrv stopped responding to all requests. Stop the service or the corresponding process if it does not respond, and
    then start it again. Check for related error messages."
    and " The Firewall service stopped because an application filter module C:\Windows\SYSTEM32\ntdll.dll generated an exception code C0000005 in address 0000000077A72F86 when function CompleteAsyncIO was called. To resolve this error, remove recently
    installed application filters and restart the service."
    I have reinstall but there error also appear again. My company use about 2000 clients access through TMG 2010.
    i have try update windows and TMG latest but can not solved this issue.
    i hope everyone help me as soon as. thank you so much.

     
    HI Luis,
    Not sure whether this will fix your issues however give it a try and let us know so that other can also provide suggestion.
    Disable
    Antivirus
    Monitoring Tools / Hardware Diagnostics tools which comes with Server vendor
    Try -
    http://support.microsoft.com/kb/2649961
    http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=2649961&kbln=en-us
    Ensure you have enough space for Log to be stored

  • Lync Edge Server Service Not Starting

    i am having an issue with starting the "Lync Server Audio/Video Edge" service on my lync edge server. when i try to start the service it throws the following error..
    "The Lync server audio/video edge service on local computer started and than stopped. some services stop automatically if they are not in use by other services or programs."
    than in the event viewer logs there are 2 specific errors i can see that look like the following..
    what is stopping me from fixing this right away is that i havent changed anything in my configuration, seems to have broke on its own. i can post more errors i have found in other places as well if needed. any help is greatly appreciated

    hey sean, thanks for your response. all things point to something else using port 443 right now.. however from what i can see from a netstat command it doesnt look like anything new is running on it. here is a copy/paste of my most recent netstat command..
    Active Connections
      Proto  Local Address          Foreign Address        State           PID
      TCP    0.0.0.0:80             0.0.0.0:0              LISTENING       4
      TCP    0.0.0.0:135            0.0.0.0:0              LISTENING       756
      TCP    0.0.0.0:443            0.0.0.0:0              LISTENING       4
      TCP    0.0.0.0:445            0.0.0.0:0              LISTENING       4
      TCP    0.0.0.0:3389           0.0.0.0:0              LISTENING       2804
      TCP    0.0.0.0:4443           0.0.0.0:0              LISTENING       4
      TCP    0.0.0.0:47001          0.0.0.0:0              LISTENING       4
      TCP    0.0.0.0:49152          0.0.0.0:0              LISTENING       468
      TCP    0.0.0.0:49153          0.0.0.0:0              LISTENING       844
      TCP    0.0.0.0:49154          0.0.0.0:0              LISTENING       896
      TCP    0.0.0.0:49338          0.0.0.0:0              LISTENING       1400
      TCP    0.0.0.0:56483          0.0.0.0:0              LISTENING       572
      TCP    0.0.0.0:56966          0.0.0.0:0              LISTENING       564
      TCP    0.0.0.0:56967          0.0.0.0:0              LISTENING       2824
      TCP    192.100.100.84:139     0.0.0.0:0              LISTENING       4
      TCP    192.100.100.84:444     0.0.0.0:0              LISTENING       1768
      TCP    192.100.100.84:5061    0.0.0.0:0              LISTENING       1908
      TCP    192.100.100.84:5061    68.34.170.246:52296    CLOSE_WAIT      1908
      TCP    192.100.100.84:5061    68.34.170.246:52297    CLOSE_WAIT      1908
      TCP    192.100.100.84:5061    68.34.170.246:53570    CLOSE_WAIT      1908
      TCP    192.100.100.85:5061    0.0.0.0:0              LISTENING       1908
      TCP    192.100.100.85:5062    0.0.0.0:0              LISTENING       1844
      TCP    192.100.100.85:5062    192.100.100.83:53701   ESTABLISHED     1844
      TCP    192.100.100.85:5062    192.100.100.83:53967   ESTABLISHED     1844
      TCP    192.100.100.85:8057    0.0.0.0:0              LISTENING       1768
      TCP    192.100.100.85:8057    192.100.100.83:56612   ESTABLISHED     1768
      TCP    192.100.100.85:8057    192.100.100.83:56617   ESTABLISHED     1768
      TCP    192.100.100.85:8057    192.100.100.83:56618   ESTABLISHED     1768
      TCP    192.100.100.85:8057    192.100.100.83:56619   ESTABLISHED     1768
      TCP    192.100.100.85:8057    192.100.100.83:56620   ESTABLISHED     1768
      TCP    192.100.100.85:8057    192.100.100.83:56628   ESTABLISHED     1768
      TCP    192.100.100.85:8057    192.100.100.83:56629   ESTABLISHED     1768
      TCP    192.100.100.85:8057    192.100.100.83:56670   ESTABLISHED     1768
      TCP    192.100.100.85:57577   192.100.100.146:5357   TIME_WAIT       0
      TCP    192.100.100.85:57579   192.100.100.175:5357   TIME_WAIT       0
      TCP    192.100.100.85:57583   192.100.100.159:5357   TIME_WAIT       0
      TCP    192.100.100.85:57584   192.100.100.147:5357   TIME_WAIT       0
      TCP    192.100.100.85:57585   192.100.100.242:3911   TIME_WAIT       0
      TCP    [::]:80                [::]:0                 LISTENING      
    4
      TCP    [::]:135               [::]:0                 LISTENING      
    756
      TCP    [::]:443               [::]:0                 LISTENING      
    4
      TCP    [::]:445               [::]:0                 LISTENING      
    4
      TCP    [::]:3389              [::]:0                 LISTENING      
    2804
      TCP    [::]:4443              [::]:0                 LISTENING      
    4
      TCP    [::]:47001             [::]:0                 LISTENING      
    4
      TCP    [::]:49152             [::]:0                 LISTENING      
    468
      TCP    [::]:49153             [::]:0                 LISTENING      
    844
      TCP    [::]:49154             [::]:0                 LISTENING      
    896
      TCP    [::]:49338             [::]:0                 LISTENING      
    1400
      TCP    [::]:56483             [::]:0                 LISTENING      
    572
      TCP    [::]:56966             [::]:0                 LISTENING      
    564
      TCP    [::]:56967             [::]:0                 LISTENING      
    2824
      TCP    [2002:c064:6454::c064:6454]:4443  [2002:c064:6453::c064:6453]:54033  ESTABLISHED     4
      TCP    [2002:c064:6454::c064:6454]:57581  [2002:c064:64ab::c064:64ab]:445  ESTABLISHED     4
      TCP    [2002:c064:6454::c064:6454]:59957  [2002:c064:640c::c064:640c]:445  ESTABLISHED     4
      UDP    0.0.0.0:123            *:*                                   
    948
      UDP    0.0.0.0:500            *:*                                   
    896
      UDP    0.0.0.0:1434           *:*                                   
    1976
      UDP    0.0.0.0:4500           *:*                                   
    896
      UDP    0.0.0.0:5355           *:*                                   
    140
      UDP    127.0.0.1:51664        *:*                                   
    1172
      UDP    127.0.0.1:56155        *:*                                   
    2924
      UDP    127.0.0.1:59005        *:*                                   
    964
      UDP    127.0.0.1:62503        *:*                                   
    1680
      UDP    127.0.0.1:62786        *:*                                   
    572
      UDP    127.0.0.1:62788        *:*                                   
    140
      UDP    127.0.0.1:64531        *:*                                   
    896
      UDP    127.0.0.1:65160        *:*                                   
    1844
      UDP    192.100.100.84:137     *:*                                   
    4
      UDP    192.100.100.84:138     *:*                                   
    4
      UDP    [::]:123               *:*                                   
    948
      UDP    [::]:500               *:*                                   
    896
      UDP    [::]:1434              *:*                                   
    1976
      UDP    [::]:4500              *:*                                   
    896
      UDP    [::]:5355              *:*                                   
    140

  • Project Professional 2013 Installations Fails with Office 2010 installed on Windows 7 x86

    When attempting to install Project Professional 2013 Pro (x86) on Windows Professional x86 PC that has Office 2010 ProSp2 installed client getting an error message at the end of the installation "Project 2013 has encountered an error during setup".
    I have gotten the installer to work on x64 PC with Office 2010 installed. (Something worth noting that even thought I set the reboot to prompt its automatically reboots without warning but, appears to be working.)  I also tried using the OTC, custom XML
    file and just running setup.exe and get the error no matter what. When looking in the logs I there are MSI installer error with an error: Product:
    Microsoft Project Professional 2013 - Update '{A6FFA77F-C1C1-43D3-A2C7-6A5B68138D9F}' could not be installed. Error code 1603. Windows Installer can create logs to help troubleshoot issues with installing software packages. Use the following link for
    instructions on turning on logging support: http://go.microsoft.com/fwlink/?LinkId=23127
    Without having to uninstall Office 2010 what do I need to modify in the installer to get it to Project 2013 Pro to install on the x86 machine?
    Thanks

    Hi,
    Your environment will support 32 bit of Project professional 2013 (x86) as you have Windows and Office of (X86).
    You try to modify registry then you wont face issue.
     The issue when you hit a "1653" is that Windows
    Installer "DisableRollback" is set. Office 2013 requires that "rollback" be enabled. If you are getting a "1653"
    error in your logs as Ken did then the solution is to delete the "DisableRollback" (or set to '0') at the following registry keys:
    HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows\Installer
    HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer
     these are the issues I've seen:
    Scheduler service was stopped. At a cmd window typing "net start schedule" resolves the problem.
    CMD.exe was customized via the following registry key. Solution was to temporarily disable the customization by changing autorun value to autorun_old. 
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Command Processor
    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Command Processor
    Permission issues - seems some custom permissions affected Ingram's install which he explained in his previous post.
    Environment variable "ComSpec" had been modified (semicolon added). Fix was to remove the added semicolon (there should be no semicolon).
    The way to identify you are hitting this specific issue is if in the %temp%\OfficeSetup.log there is a mention of "Office64MUI.msi" failing to install with return value of 1603
    If you want to enable verbose logging via the following key, rerun your failed install, and collect all the setup and MSI* logs that will give more information.
    [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer]
    "logging"= "voicewarmup"
    kirtesh

  • Excel 2013 VBA Compatible with Excel 2010

    Hello,
    I am new at working with VBA and have a question regarding an excel sheet with a VBA macro inserted.
    The sheet was created in Excel 2013 by another user, and my laptop runs Excel 2010.  I get script errors when I run it, however on Excel 2013 it works fine.
    My question is: Is there a way to make Excel 2010 work with Excel 2013 VBA scripts? Perhaps importing the library from Excel 2013 VBA to E-2010?  Or perhaps a way to save a VBA script in E-2013 to be backwards compatible with E-2010?
    Thank you all for your support.

    Open the workbook.
    Select Tools > References...
    The references that are in use have their check box ticked. They are all at the top of the list. Do any of those start with MISSING?
    Regards, Hans Vogelaar (http://www.eileenslounge.com)

  • Lync edge server for site with 2500 users

    Dear All,
    I have a question with regards to the implementation of lync edge server deployment.
    One of our client having lync deployment with 4000 users in a central site with 3 FE EE and  edge pool with 2 Edge servers, there are planning for a new site with 2500 users.
    what will be the best method for the site implementation , shall we deploy a SE Fe server and all the external communication through the Central site Edge server?
    or is it required to have a separate pool for site?
    please help me 

    Agree with the others.  So, there's two questions, "what will be the best method for the site implementation?" and "is it required to have a separate pool for site?".
    The best method I'd suggest is use Enterprise Edition Lync so you can perform pool pairing for resiliency, and have a local edge pool as the others suggested.  You have enough users to support this, and with growth you might want to be able to scale
    up anyway.
    Is it required? Not at all.  You can send them all through the central site edge server, it's possible and fully supported.    It's up to you, but I'd suggest the separate pool.
    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
    SWC Unified Communications

  • Exchange 2013 OWA published through TMG: Unable to preview documents with Office Web App server

    We configured our Exchange 2013 servers to use Office Web App for document previews on OWA. Everything works fine internally, and externally also when we access OWA directly. But when from an outside network we open a OWA session through TMG and try to preview
    a document, we get the error "Sorry we cannot open this document, an error occured . . ."
    Did anyone experience such an issue ?
    Thanks,
    Antonio

    Hello,
    Since directing accessing OWA from CAS is fine and the issue only occur when involving TMG, I think the issue is more related to TMG settings. Please find more efficient support
    via our TMG forum:
    http://social.technet.microsoft.com/Forums/en-US/Forefrontedgegeneral/threads
    Thanks,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Simon Wu
    TechNet Community Support

  • Can't open Project Server 2013 word documents with office 2010 installed

    hello forum members,
    we having issues opening a word document in a Project Server 2013 . we have Office 2010 on our computers installed. 
    when I click on a document link, i get a message "The webpage cannot be displayed".  the only way to open a document is to right click on link and select "Open". 
    Does Project Server 2013 require Office 2013 installed? If not, is there a way to open documents in Project Server 2013 without right clicking on links?
    tatiana
    tatiana

    Hi Tatiana,
    This is the know issue. I have experienced this issue with one of our client. The cause of issue as below -
    Scenario
    You have 2007 Microsoft Office installed on a computer.
    On the same computer, you also have a Microsoft Office 2013 application installed, such as Microsoft Lync 2013 or Microsoft Word 2013.
    SOLUTION
    To work around this issue, remove the Microsoft SharePoint Foundation Support program component from the Office 2013
    installation on the affected computer or computers. To do this, follow the “Install or remove individual Office program components” section of the following Microsoft Office website:
    Install or remove individual Office
    programs and components
    (http://office.microsoft.com/redir/HA010354261.aspx)
    After you complete these steps, repair 2007 Office. For more information about how to repair the installation, click
    the following article number to go to the article in the Microsoft Knowledge Base:
    924611
    (http://support.microsoft.com/kb/924611/ )
    How to install the individual 2007 Office features or to repair the installed 2007 Office programs
    Note When
    you follow these steps, set the Microsoft SharePoint Foundation Support
    component within Office Tools to Not Available.
    This solution doesn't apply to scenarios in which SharePoint Designer 2013 is installed on the affected computer.
    You can find further details here at Microsoft support site -
    http://support.microsoft.com/kb/2888015
    Hope this helps you.
    Cheers, Badal

  • Exchange 2013 co-existence with Exchange 2010 proxying issue.

    Hello,  
    I am testing Exchange 2010 and Exchange 2013 co-existence in my test lab at the moment, with
    a view to migrating our production environment to 2013 later in the year.  
    The lab is setup, and the problem I'm having is that internal Outlook clients cannot open
    their respective mailboxes once the 2013 CAS server is introduced into the mix.  
     The
    setup is listed below:  
    EXCHANGE 2010 Servers  
    TESTLABEXCH01 - CAS,HT,MBX - Exchange 2010 SP3  
    TESTLABEXCH02 - CAS,HT,MBX - Exchange 2010 SP3  
    Both servers are part of a CAS Array - casarray01.testlab.local  
    Both servers are part of a DAG - DAG01.testlab.local  
    RpcClientAccessServer on all 2010 databases set to casarray01.testlab.local  
    The A record for casarray01.testlab.local points to the IP of the VIP of a load balancer.  
    The loadbalancer serves
    the following ports: 25,80,443,143,993,110,995,135,60200,60201  
    OutlookAnywhere is enabled on both servers:  
    ClientAuthenticationMethod : Ntlm  
    IISAuthenticationMethods   : {Basic, Ntlm}  
    Internal and external mail flow works without issue before the 2013 server is introduced. 
    Internal and external client access works without issue before the 2013 server is introduced. 
    Part Two to follow.....
    Matt

    EXCHANGE 2013 Servers :
    TESTLABEXCH03 - CAS,MBX - Exchange 2013 SP1  
    OutlookAnywhere is enabled on the server:  
    ClientAuthenticationMethod : Ntlm  
    IISAuthenticationMethods   : {Basic, Ntlm}  
    RpcClientAccessServer on all 2013 databases set to casarray01.testlab.local
    (This an inherited setting I assume from the pre-existing 2010 organization)  
    Split DNS is in place and all internal/external URL's point to either:  
    autidiscover.external.com  
    mail.external.com  
    The A record for the mail.external.com points to the IP of the load balancer VIP  
    The CNAME record for autodiscover.external.com points to mail.external.com  
    When the TESTLABEXCH03 is added to the load balancer config,
    and given highest priority this is when the Outlook clients stop working.  
    Any existing profiles in Outlook 2010/Outlook 2013 can no be opened as there is a persistent
    credentials prompt.  
    Upon trying to create a new profile, the process errors when reaching the "Log onto server"
    stage and again prompts for credentials.  
    Running the test-outlookconnectivity cmdlet from
    either of the 2010 servers produces the following results.  
    [PS] C:\Windows\system32>Test-OutlookConnectivity -Protocol:http  
    ClientAccessServer   ServiceEndpoint                         
    Scenario                            Result  Latency  
    TESTLABEXCH02  autodiscover.external.com    Autodiscover:
    Web service request.  Success  343.20  
    TESTLABEXCH02  casarray01.testlab.local       RpcProxy::VerifyRpcProxy.  
    Success    0.00  
    TESTLABEXCH02  casarray01.testlab.local         RFRI::GetReferral.                 
    Failure   -1.00  
    TESTLABEXCH02  casarray01.testlab.local        NSPI::GetProfileDetails.           
    Failure   -1.00  
    TESTLABEXCH02  casarray01.testlab.local        
    Mailbox::Connect.                   Failure   -1.00 
    TESTLABEXCH02  casarray01.testlab.local        
    Mailbox::Logon.                     Skipped   -1.00  
    If remove the 2013 CAS server from the loadbalancer config and
    all connections go directly to the 2010 servers again, all of the above tests pass and Outlook connectivity is also restored.  
    IIS has been reset on all 3 servers incidentally, following any changes made whilst troubleshooting. 
    I'm struggling to see what I'm missing here, if anyone can assist in troubleshooting this
    matter further, or point out any errors in my setup it would be greatly appreciated.  
    Regards  
    Matt 
    Matt

Maybe you are looking for