locked
UAG 2010 SP2 access for iPad and Android tablets RRS feed

  • Question

  • Can anyone point me to any documentation which tells me how to provide access to my UAG 2010 SP2 portal for iPad and/or Android tablet devices.  I have had a look at policies and I can see that there are Windows, MacOS, Linux and Other.  Do these devices fall under "Other" and, if so, what do I need to set up as a basic policy to provide safe/secure access?  Any tips appreciated.
    Monday, October 8, 2012 5:07 AM

All replies

  • Hello,

    You could follow this to achieve your goal: http://technet.microsoft.com/en-us/library/gg274293.aspx

    Regards,


    Follow me on Twitter http://www.twitter.com/liontux | My Blog (French/English) : http://security.sakuranohana.fr/

    Monday, October 8, 2012 9:31 AM
  • Thanks Lionel,

    I got part way through that set of instructions.  Where I get stuck is this bit:

    "If you publish applications that have specific application policies and you want to allow mobile devices to access these applications, you must also modify the application specific policies. For example, if you publish Microsoft SharePoint Server 2010, you must change the SharePoint policies."

    What I really want to provide is Remote Desktop access for an iPad or Android user. 

    But when I go into the settings for the Remote Desktop application, the options "[  ] premium mobile portal" and "[  ] non-premium mobile portal" are greyed out and cannot be selected.

    Does this mean that it just isn't possible to deliver Remote Desktop services to an iPad or Android client?

    Tuesday, October 9, 2012 12:13 AM
  • Does this mean that it just isn't possible to deliver Remote Desktop services to an iPad or Android client?


    Yes, because it's based on the Windows Remote Desktop client call. Here's the offcial scenario supported by browser/OS/mobile terminal : http://technet.microsoft.com/en-us/library/dd920232.aspx

    Follow me on Twitter http://www.twitter.com/liontux | My Blog (French/English) : http://security.sakuranohana.fr/

    Tuesday, October 9, 2012 7:28 AM
  • I'd pretty much reached that conclusion just before I read your last post.  Thanks for confirming!  I guess my only option then would be to publish port 3389 directly to the 'Net and I definitely don't want to do that.
    Wednesday, October 10, 2012 12:47 AM