Outlook Web App didn't initialize - Exchange 2010

Desktops, Servers, and Networks, oh MY!

Outlook Web App didn't initialize - Exchange 2010

This and many other Outlook and even Microsoft Exchange related issues can be resolved remotely. With software for online desktop support, you could access desktops and servers remotely to work on issues with email clients or mail delivery from servers.  

OWA version: 14.1.355.2



Exchange 2010 Outlook Web App loads the login form page for users of OWA but after login an error page is displayed that displays an error indicating that Outlook Web App cannot initialize. This is an authentication issue.

In the case of the blogged server situation. The SSL cert was purchased form digicert.com and applied successfully. The problem was the settings in IIS and in Exchange management console for client access of Outlook Web Access (now called outlook web app) were not "matching".

Server configuration > client access > OWA properties > Authentication Tab

Select Use Forms Based, Username only. Enter your logon domain (your local internal Active Directory domain).

Next, in IIS7, go to the following spot in the tree under Default Website and set the authentication like the following image shows.



That's all I had to do on my Exchange 2010 and Exchange 2016 server to get past the OWA error message after login in of:

Outlook Web App didn't initialize.

RDP manager software can help with application issues.

RDP manager software plays a crucial role in resolving Outlook application issues by providing professionals with a centralized platform to manage and troubleshoot various aspects of the application. Firstly, this software allows IT administrators to remotely connect to desktops or servers that are experiencing Outlook problems, enabling them to quickly identify and resolve any underlying issues. Additionally, RDP manager software enhances efficiency by providing functionalities like session management, which allows multiple users to simultaneously access and work on the same session without interrupting each other's progress. OWA or Outlook is only one example of many where RDP connection management software enables a centralized platform for initiating a support experience for the end-user. Furthermore, it offers features such as file sharing and collaboration tools that facilitate seamless communication between team members, enabling them to address Outlook problems collectively. Overall, the RDP manager software streamlines troubleshooting processes by offering a comprehensive set of tools and capabilities that ensure efficient resolution of application issues in a professional setting. Similar to RDCMan, the software facilitates the creation of a list of re-usable RDP connections. RDCMan requires installation and to use on multiple computers or laptops, the list has to be exported and imported.

Online RDP Manager

Online RDP manager software, the managed and centralized list of RDP connections is available from any computer or devices independent of operating system. RDS servers enable a pseudo centralized RDP connection and desktop availability. They are commonly used to give users access to a virtual application or desktop. Software to centralize RDP connections, such as software from 4RemoteSupport.com, is designed for a single administrator or support teams presents a list of managed RDP connections to access servers or desktops that are RDP enabled. Since 4RemoteSupport's online RDP manager doesn't require installation but instead is an online RDP manager, the software user interface permits one or more administrators to modify the list of RDP connections and have access at the same time. The list of RDP connections is available to all team members. Unlike RDCMan, the list of RDP connections doesn't have to be exported to be shared.  All administrators can access the shared list of online RDP connections at the same time from any internet connected device with a browser.   

 

Citrix Session Printers Registry Key Location

Session printers created via policy

Session printers created via policy in Citrix XenApp are considered local printers. As such they are in the registry key that is common for local printer definitions. That registry key location on Windows 2008 R2 is :

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Printers

Problem with session printers such as additional printers appearing in the user's list of available printers while in a session, most often is a result of driver corruption. Once the corrupt driver has been fixed or removed, you may have printers still showing up in user sessions that do not belong.

One of the things you can check is the key in the registry where the session printers are defined.
For stuck printers, as option to get rid of them is often to delete the user's profile but that's not always the best option so removing the session printers defined for that user can be done through the registry. Be cautious when removing but when there are no users logged into the Cirix Xenapp server, there should be no session printers defined.

Similar to Citrix is RDS using RDP protocol. Similar issues are encountered when using RDP for user access to desktops or Administrator access to servers or desktops. Managing RDP connections can be time consuming and having a centralized RDP connections make administration and management easier. RDS gateway such as this one similarly to Citrix permits multiuser access.