Take a look at http://technet.microsoft.com/en-us/library/cc179062.aspx and see if you are following the procedures there for Outlook 2010.

Thanks for the response Terry.  I have used the Customazation tool to create the PRF file.  I am using the /importprf switch when launching Outlook.  That seems to work fine.  I need the mail profile to be available for another application without Outlook being open.  Any ideas?  I think I have Metaprofiles setup to copy out the registry for Windows Messaging System and Office14.  But that doesn't seem to be working right.  My session gets disconnected instead of logged off and I am not sure why.

Just to verify, the MAPI profile is located at HKEY_CURRENT_USER\Software\ Microsoft\Windows Messaging Subsystem and if the application is MAPI-based then persisting this entry is correct. However, the vWorkspace MetaProfile agent only writes profile information back to the storage server at logoff and only when those designated profile entries have CHANGED.  If you are disconnecting, then the profile agent isn't being given the opportunity to save your profile information. Make sure you terminate the application by using the menu EXIT and properly LOGOFF of the session.

Additionally, in the vWorkspace console, ensure that the profile configurations are assigned to the user or group; Ensure the storage server is configured; and verify that the necessary registry keys are configured and assigned.

Sorry, I was trying to do the reg entry from memory.  But yes.  That is what I have set in the User Profiles.  I am doing a FILE | EXIT off of the Outlook screen.  And although the application closes my session goes disconnected. The only time I actually log off is when I use the Quest Remote Desktop Client.  Going through the web access page all sessions disconnect and then the profile is locked until a reboot.

I have tried this on both Windows Server 2008 and 2008 R2 servers and the behavior is the same. 

Hi Slklos,

You should find that you are fully logged off when you close the last application for a session. If this is not happening for you when connecting via web access then it is likely there is an application or process that is holding the session open. You may be able to identify this by looking in the vWorkspace Console, and checking the Processes tab of the associated Terminal Server. Look to see what processes are running for the user whose session you are monitoring. You can then add these to the Session Auto-Logoff List to see if this is able to correct the behaviour.

Regards

David

Hi David,

I have made sure that I am starting off with my user (which is me) with no profile or logged in session on the TS. I log into Web Access, open Outlook 2010 and wait for it to finish loading.  I do a FILE | EXIT then wait until the session is no longer in my Quest Session Status window on my WIndows 7 x64 bit client.  When I go into the TS my session shows as disconnected.  There are still process running in the Quest vWorkspace Console for my session.  I have added all of those onto the Auto-Logoff List.  I logged off the session, and removed the user profile from the TS server and did the above steps again.  Samething.  I really appreciate any insights in this issue.

Thanks,

Shareen

Shareen,

When adding the files to the Session Auto-logoff list, you don’t need to add all of the executables. Can you try performing the following?

1. Open the vWorkspace Management Console (ensure you have a running session to the Terminal Server)
2. Expand “vWorkspace_Farm” | “Locations” | “Location1” | “Terminal Servers” and connect to the terminal server
3. Expand your running session to view the processes
4. Close Outlook and wait for outloo.exe to close
5. If the session is still running, right click on each process one at a time and select “End Process” until you discover the process that is preventing your session from closing.
6. Once you know what specific process is causing the issue, add this file to the Session Auto-Logoff list.

Thanks,

-Roman