Quantcast
Channel: Remote Desktop Services (Terminal Services) Forum
Viewing all articles
Browse latest Browse all 27656

Establish Outlook Profile When Using Published Remote App

$
0
0

We have a RDP server where we publish Microsoft Dynamics AX 2012 R3 via remote app. When a user uses the remote app Dyanamics AX it will spawn a PDF file which will open with Adobe Acrobat reader that is installed on the RDP server with the DAX client. Microsoft Office 2016 is also isntalled on the RDP server. When the PDF file is open the user will click the Mail icon in Adobe Reader that looks for the users Outlook Profile and will tell the user they need to configure their Outlook profile in order to send the PDF via e-mail. We have configured Group Policy to auto configure each users outlook profile on the RDP server. The problem is that the Outlook profile isn't actually created until Outlook is opened under the user profile. Remember this is a published app they are using not a full RDP session so they do not have access to launch the Outlook Client. We don't need them to have access to Outlook, we just need the Outlook profile created so that the Adobe reader app will detect it and use that profile to send e-mail.

 Is there any way we can establish the Outlook profile, transparently to the user? Logon script, or any other technology?

I know that once the profile is established by opening Outlook then the mailing function of Adobe Reader works. I tested this out by trying to mail from adobe only using the Published App, DAX. Adobe wouldn't detect the Outlook profile. I then logged onto the RDP server using a full RDP session as the same user, opened Outlook, the profile autoconfigured as expected, then closed Outlook. Kicked my remote app session, and logged off. I relaunched the Published app DAX and when the PDF spawned Adobe was able to detect the Outlook profile.

RDP Server is WS2012 Datacenter


Viewing all articles
Browse latest Browse all 27656

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>