Outlook 2003 Terminal Server Error
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: Cannot open outlook 2003 on terminal server Windows Server > Group Policy Question 0 Sign in to vote rdp this computer can't connect to the remote computer I'm using outlook 2003 on a windows 2003 server with Terminal Services installed. When opening windows 2003 rdp not working outlook 2003 logged in as a user I immediatly get "Cannot start Microsoft office outlook" If I log on as the local this computer can't connect to the remote computer server 2008 admin or a user with local admin rights it works fine. I guess my question is what rights/permissions do the users need to have to use outlook with out giving them administrative rights to the whole machine. Thank because of a security error the client could not connect to the remote computer 2008 you. Friday, September 25, 2009 5:12 PM Reply | Quote Answers 0 Sign in to vote Hi, This issue may be caused by incorrect permission. Please first try to uninstall Outlook and reinstall it to different location (Important) to test. If the issue persists, try the steps below: 1. Open regedt32. 2. Select the root of HKLM, select the Registry menu and select the menu option "Load Hive" 3. Browse to where the users NTUser.dat
This Computer Can't Connect To The Remote Computer Server 2003
file is stored and select it. 4. Regedit will ask you to type in a key name. Just type User Name as the Key name. 5. Select the users hive that you just loaded, Select Permissions menu option. 6. Make sure that the users account has Full Control. If they do not, add them in and then unload the hive and logon the user to test. Thanks. This posting is provided "AS IS" with no warranties, and confers no rights. Marked as answer by Mervyn ZhangModerator Monday, October 05, 2009 2:30 AM Wednesday, September 30, 2009 7:19 AM Reply | Quote Moderator 0 Sign in to vote I gave the user group full control of the microsoft key and it seams to work working fine now. Marked as answer by Palmolive Tuesday, October 06, 2009 12:30 PM Tuesday, October 06, 2009 12:30 PM Reply | Quote All replies 0 Sign in to vote Are you loggin in the domain? Is the OL2003 configured for MAPI or RPC over HTTPS ? try to configure the the outlook once again with MAPI connection (machine should be in the domain) or else take the machine out of the domain and then try to configure RPC over HTTPS.Raj Friday, September 25, 2009 6:48 PM Reply | Quote 0 Sign in to vote HiYou receive an error
360 games PC games
Windows Server 2003 Remote Desktop Connection Limit
Windows games Windows phone games Entertainment All Entertainment windows 2003 rdp service Movies & TV Music Business & Education Business Students & educators this computer can't connect to the remote computer 2012 r2 Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet https://social.technet.microsoft.com/Forums/windowsserver/en-US/1e6ae0f5-b9fa-431d-94e0-a082f5192695/cannot-open-outlook-2003-on-terminal-server?forum=winserverGP Explorer Microsoft Edge Skype OneNote OneDrive Microsoft Health MSN Bing Microsoft Groove Microsoft Movies & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC accessories Xbox & games Microsoft Lumia All https://support.microsoft.com/en-us/kb/2735060 Windows phones Microsoft HoloLens For business Cloud Platform Microsoft Azure Microsoft Dynamics Windows for business Office for business Skype for business Surface for business Enterprise solutions Small business solutions Find a solutions provider Volume Licensing For developers & IT pros Develop Windows apps Microsoft Azure MSDN TechNet Visual Studio For students & educators Office for students OneNote in classroom Shop PCs & tablets perfect for students Microsoft in Education Support Sign in Cart Cart Javascript is disabled Please enable javascript and refresh the page Cookies are disabled Please enable cookies and refresh the page CV: {{ getCv() }} English (United States) Terms of use Privacy & cookies Trademarks © 2016 Microsoft
your account only takes a few minutes. Join Now Unable to open your default email folders. The information store could not be opened. Setup: SBS 2011 on our main server. Server 2008 r2 terminal server (where the https://community.spiceworks.com/topic/171461-unable-to-open-outlook-on-terminal-server problem is happening). The account doesn't matter. It happens for admins or reg users. Terminal services are working ok, most everything is going great actually but outlook wont open and gives that same error. Have some some searching http://www.jonathanmedd.net/2010/10/running-outlook-2003-in-ts-or-citrix-and-planning-an-upgrade-to-exchange-2010.html already but figured I would post and see if someone has experienced this. Another terminal server of the same type is working just fine. Difference is that this one we switched from the old network while the one that connect to works is a new load. Hoping I dont need to make it from a fresh load as that would make the move trouble. Reply Subscribe RELATED TOPICS: Outlook for Terminal Server Outlook on Terminal Server Access-based app slow on Terminal server, blazingly fast on local PC   17 Replies Mace OP Sosipater Nov 21, 2011 at 3:37 UTC When you said "this one we switched from the old network while the one that works is connect to the a new load" are you running two logical networks now, e.g. 192.168.0.0 and 192.168.1.0? 0 Serrano OP Cody Nail Nov 21, 2011 at 3:52 UTC It is a completely separate network both physically and logically. A test network for a projected infrastructure change. If it can be fully set up and shown working well it will likely have data and users imported in and go live. This thing is basically the last area before it is rocking 100%. Weird thing is this happens on a live server also. (I wanted to see if I could get it to happen elsewhere) Deleting old mapi files to get it to rebuild them doesn't work. Rebuilding the profile doesn't work. Reinstalling the Office Program doesn't work (and I mean a deep uninstall where the registry is wiped out too). The type of user account doesn't change the outcome. Another server in this network functions just fine. This one is basically a clone of a live server so there is something specific to this server that is causing this. I am going to go to volume keys on 2010 soon and just forget the problem but 2003 would be cheaper. 0 Chipotle OP Warren.Wagener Nov 21, 2011 at 3:53 UTC More info needed, is this a cache copy - migration? or a new standalone mail server? The infor
2010citrix, exchange 2010Jonathan Medd Outlook 2003 is listed as a supported client for Exchange 2010 with the following caveats: Clients running Outlook 2003 don’t use RPC encryption, which RPC Client Access requires by default. You will either need to turn off the RPC encryption requirement or configure Outlook 2003 to use RPC encryption. However, Outlook 2007 and later versions are automatically compatible with the change to RPC Client Access because they support RPC encryption by default. For more information, see Understanding RPC Client Access. On clients running Outlook 2003, you may notice that folder updates don't occur automatically in a timely manner. This situation occurs because User Datagram Protocol (UDP) notifications aren't supported in Exchange 2010. For more information about resolving this issue, see Knowledge Base article 2009942, In Outlook 2003, e-mail messages take a long time to send and receive when you use an Exchange 2010 mailbox. However, Outlook 2007 and Outlook 2010 are automatically compatible with this change. Having now witnessed the impact of the second issue it could cause you a big issue if you are running Outlook 2003 in Terminal Services or Citrix. The KB article 2008842 suggests two options: Make a registry interval to reduce the polling time from 60 seconds to a lower value, 10 is the minimum Use Outlook's Cached Exchange mode Having made the registry change down to 10 seconds the phrase from above ‘…..folder updates do not occur in a timely manner' is pretty diplomatic! I think most people could live with an email sitting in the Outbox for a few seconds or being delivered within seconds rather than instantaneously. However, deleting an email and it then not dissapearing for up to 10 seconds is a real issue. It feels like it didn't work, so naturally you press the delete key again and this time you are presented with an error because that item no longer exists. The whole experience with this refresh issue is pretty poor. Whilst Outlook's Cached Exchange mode is a very common deployment method for laptops and desktops (if not the standard these days) you cannot use it when running Outlook 2003 in Terminal Services or Citrix. The final option is an upgrade to Outlook 2007 / 2010 which might not be a big deal in some organisations, in others it will involve significant work and planning. It appears that there is unlikely to be a better fix either. Further