This post is more than 5 years old
16 Posts
0
22255
July 21st, 2011 13:00
Trouble with Outlook 2010 when launched through Connection Broker
I am creating Windows Server 2008 R2 environment with vWorkspace 7.2 MR1. I have installed Office 2010 on the terminal server. We like to use a PRF file to configure Outlook for our users. When I launch Outlook directly from the TS server it open without issue. If I launch Outlook through Web Access (we do not use the AppPortal) or use the Quest RD client going through the Connection Broker I get the following error when it goes through the profile creation.
The Server is unavailable
All servers in the environement are inside the firewall. I can ping the exchange server from the Connection Broker.
I can launch Word from the Web Access page. So there are apps that do work.
slklos
16 Posts
1
July 22nd, 2011 11:00
To be honest I am not sure either it is coming from Outlook or vWorkspace. I have added a screenshot of the error hoping that may help. Going through the Web Access page it does start to load Outlook at when it gets to the loading profile it stops.
If I login to a console to the TS server it loads fine. It does take me through the manual setup of the mail profile but it works. Also, using the vworkspace RD client, if I RD directly into the TS it does the same as logging into the console, but if switch from Server to Application and go through the CB i get the same error that I do on the Web Access page.
DELL-David Y
228 Posts
0
July 22nd, 2011 07:00
Hi,
Are you able to post a screenshot of the error or describe the error in more detail. Is it Outlook that is reporting Server unavailable or is this a vWorkspace message? Does the connection complete and launch Outlook for you, with or without your Outlook Profile?
You say this works directly from the TS server, is this when logged in locally or via a MS RDP session?
Regards
David
DELL-Paul Fi
101 Posts
0
July 22nd, 2011 08:00
Hi,
What happens if you disable EOP Xtreme server side? To do this go to the properties of the session host (terminal) server in the vWorkspace console and (from memory) go to performance options and disable there. Make sure that the job completes by viewing the pending jobs at the top of the vWorkspace console.
Cheers
Paul
DELL-David Y
228 Posts
0
July 22nd, 2011 12:00
The server unavailable message is coming from Outlook. It is offering the option to Work Offline which confirms this is an Outlook message rather than vWorkspace.
How many servers have you published Outlook to, is it possible that the published application is logging you into a different TS from the one which you connect to directly?
I might suggest that you also disable the seamless option and then test again when launching the application as a full-desktop, this may show you more information about why it is not seeing the profile or at least give you the ability to check the user setup is correct.
slklos
16 Posts
0
July 22nd, 2011 12:00
I thought I had removed the PRF from loading. I forgot I had a script that runs a VBS script which calls the PRF file and deletes some Registry entries. I had this script working in my Server 2003 /vworkspace 7.1 environment/Outlook 2007 and so I thought I would reuse it for the new environment making the changes I thought were right, but that doesn't seem to be something I can do. When I removed the script, Outlook works like a champ. I have to go through the mail profile setup but it works.
Now I just need to figure out how to setup the PRF to work correctly.
Thank you for your help.