OWA UAG 2010 sp2 endpoint detection not installed

All replies

• 

  

  0

  Sign in to vote

  Hi,

  Thanks for your post

  As far as I know, endpoint component is not related to your issue.

  UAG endpoint components are not required for the following scenarios:

  Publishing- Publishing Web applications via UAG, including Exchange services or RDS

  Authentication- Authenticating end-users does not require UAG endpoint components.

  In general, you can troubleshooting publishing issues through 5 steps like this:

  http://technet.microsoft.com/en-us/library/gg315322.aspx

  As you mentioned, internal OWA can be accessed successfully but not external. I doubt that if there is something wrong about your publish rule. So please double confirm your publishing step by the link:

  http://technet.microsoft.com/en-us/library/ee921443.aspx

  Additionally, do you see any article describe the TCP offload may result in this issue? Since I do not find any information about this, so if you have already saw some articles, please share with us.

  Best Regards

  Quan Gu  

  ---

  We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time.
  Thanks for helping make community forums a great place.
  

  
  

  • Edited by Quan Gu Monday, October 28, 2013 7:45 AM

  Monday, October 28, 2013 6:00 AM
• 

  

  0

  Sign in to vote

  Hi,

  I verify the suggested owa publisher, I have the same configuration

  I am working with UAG sp1 up1 TMG sp2

  My problen is that it connect but it doesn't give login screen, it gives the reporter error  

  When a user connect to owa, it open  a sessión. 

  -----------------------------------------------------------------------------------------------------------------

  Severity	Time	ID	Type	Category	Trunk	Nodename	Description
  Information	10/28/2013 22:13:52	60	Session Started	Session	exchange (S)	servername	Session 88B6A9EA-1ED2-4768-98E7-7769B2B9844B was started on trunk exchange (secure=1).

  ---------------------------------------------------------------------------------------------------------------------------------

  General Session Details
  Session Started At	28/10/2013 22:13:52
  Session Duration	00:00:32
  Session Authenticated
  Privileged Session
  Endpoint computer was not checked for policy compliance

  ------------------------------------------------------------------------------------------------------

  I have installed the Microsoft ForenFromt UAG endpoint components V4.0.0 in personal computer
  I have conetd to owa but with the same error

  I removed the program a restart computer
  When I  connect with owa it doesn't download the program to personal computer.

  I tried it from several computers with windows 7

  It was working the last week

  How can I  Know the issue?

  
  
  

  • Edited by Luimamt Monday, October 28, 2013 9:35 PM

  Monday, October 28, 2013 3:14 PM
• 

  

  0

  Sign in to vote

  Hi,

  Thanks for your post.

  Do you have another TMG server?

  Is the publishing rule created on UAG? What is the TMG used for here?

  In addition, please test：

  1. Access OWA from internal client to see if the problem is directly related to exchange server
  2. Try to access URL:https://xxxx/ecp (original URL should be https://xxxx/owa , please replace owa with ecp and then try to access. )
  3. Disable endpoint functionality on client to see if owa can work without endpoint on UAG.

  Best Regards

  Quan Gu   

  ---

  We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time.
  Thanks for helping make community forums a great place.
  

  Tuesday, October 29, 2013 6:33 AM
• 

  

  0

  Sign in to vote

  We have a one UAG 2010 server
  I have published the owa in UAG,
  The TMG is using to Microsoft Exchange edge transport, access rule for netbios and NDP for remote management. No problem with the TMG
  The Access owa from internal works fine

  https://xxxx/ecp gives  https://xxx/uniquesig160e99a22f6a31672b4be5cdbe8f0b56/uniquesig0/InternalSite/InternalError.asp?site_name=exchange&secure=1&error_code=109

  I Have tried to disable/enable Component installation and detection

  The authetication in Client Access Server for ecp and owa are anonymous,basic true

  Tuesday, October 29, 2013 9:46 PM
• 

  

  0

  Sign in to vote

  I have found this error

  [15:17:47.200] GET https://XXXX/owa [HTTP/1.1 302 Object moved 1186ms]
  [15:17:48.814] GET https://XXXX/uniquesig160e99a22f6a31672b4be5cdbe8f0b56/uniquesig0/InternalSite/InitParams.aspx?referrer=/InternalSite/InstallAndDetect.asp&resource%5Fid=7C77165D96BE4A83820E07277F6DE620&login%5Ftype=8&site%5Fname=exchange&secure=1&orig%5Furl=https%3A%2F%2FXXX%2Fowa [HTTP/1.1 302 Found 390ms]

  [15:17:48.883] GET https://XXXX/uniquesig160e99a22f6a31672b4be5cdbe8f0b56/uniquesig0/InternalSite/InternalError.asp?site_name=exchange&secure=1&error_code=109 [HTTP/1.1 200 OK 234ms]

  
  [19:42:22.973] GET https://XXXX/ [HTTP/1.1 302 Object moved 78ms]

  [19:42:23.044] GET https://xxxx/uniquesig160e99a22f6a31672b4be5cdbe8f0b56/uniquesig0/InternalSite/InitParams.aspx?referrer=/InternalSite/InstallAndDetect.asp&resource%5Fid=2&login%5Ftype=8&site%5Fname=exchange&secure=1&orig%5Furl=https%3A%2F%2ForXXX/uniquesig160e99a22f6a31672b4be5cdbe8f0b56/uniquesig0%2FSecureExchangePortalHomePage%2F [HTTP/1.1 302 Found 31ms]

  
  [19:42:23.078] GET https://XXXX/uniquesig160e99a22f6a31672b4be5cdbe8f0b56/uniquesig0/InternalSite/InternalError.asp?site_name=exchange&secure=1&error_code=109 [HTTP/1.1 200 OK 47ms]

  
  [19:44:53.866] GET https://XXXX/owa [HTTP/1.1 302 Object moved 62ms]

  [19:44:53.930] GET https://XXXX/InternalSite/InitParams.aspx?referrer=/InternalSite/InternalError.asp&site%5Fname=exchange&secure=1&error%5Fcode=25&policy%5Fid=Hybrid%5FNoPolicy%5FExp&ErrorType=HTMLErrorPage [HTTP/1.1 302 Found 31ms]

  [19:44:53.958] GET https://XXXX/uniquesig160e99a22f6a31672b4be5cdbe8f0b56/uniquesig0/InternalSite/InternalError.asp?site_name=exchange&secure=1&error_code=109 [HTTP/1.1 200 OK 141ms]

  
  

  • Edited by Luimamt Thursday, October 31, 2013 6:33 PM

  Wednesday, October 30, 2013 7:47 PM
• 

  

  0

  Sign in to vote

  Hi,

  I have did some research for error code 109. I suggest you to upgrade your UAG to SP3 Rollup 1.

  http://blogs.technet.com/b/brettcr/archive/2012/07/03/forefront-uag-2010-service-pack-update-rollup-and-version-number-reference.aspx

  Best Regards

  Quan Gu  

  ---

  We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time.
  Thanks for helping make community forums a great place.
  

  Thursday, October 31, 2013 2:05 AM
• 

  

  0

  Sign in to vote

  Hi

  Thak you for your suggetion but why it was workining fine and now it doesn't

  The error code 109 is generic,it is the problem 

  With intenet explore tool it gives redirect loop detected but I can find the redirection

  My problem is that I am remote working and the upgrade can't do remote

   

  Thursday, October 31, 2013 2:54 PM
• 

  

  0

  Sign in to vote

  I have update the UAG to SP3 but it gives the same error

  I don't kwon how i can find the problem.

  The UAG don`t give enough information

  I have imported a configuration that worked  fine but now it doesn't work, Why ?

  If I  import a configuration it must work fine.

  are There something that doesn't change after import ? how I can remove it ?

   

  Thursday, November 7, 2013 9:38 PM