Outlook Keeps Prompting for Logon Credentials Office 365

Outlook Keeps Asking for Password Credentials

When Outlook is configured for Office 365, the type of authentication is Anonymous Authentication. 

For all of you that have been configuring Outlook know that this is not a normal option for Outlook authentication against an Exchange server.  We normally have, as shown below, many more options. 

Anonymous Authentication is not listed or available as an Option in Outlook 

The anonymous option is present in Outlook 2013 but Outlook 2010 and Outlook 2007 do not normally have this option listed. windows 7 is normally not a problem but since there are still many Windows XP installation out there that we need to still support, this can be an issue. 

Outlook Keeps Prompting for Credentials 

So the problem you may encounter with some XP desktop systems that still need to be supported is that Outlook 2007 or Outlook 2010 will not have this option by default. You may find on forums a repeated suggestion to update the operating system. This is not always a good option as it might break another application installed already or you have already updated but still do not have the Anonymous Authentication option in Outlook. This Outlook issue can be resolved by IT departments remotely. Software applications that give IT departments remote access to computers through the web enables faster assistance because online desktop support software creates connections to the desktop. Software for online support is designed for faster access to user desktop computers to resolve issues.  

I had a customer with XP SP3, Outlook 2007 which I upgraded to Outlook 2010 and applied SP1 but still no Anonymous Authentication in Outlook. I did not run anymore updates. Instead I found and ran the following Hotfix from Microsoft (I ran the 32bit version) : 

KB Article Number(s): 2791026 Language: All (Global) Platform: i386 Location: (hotfixv4.microsoft.com/.../462115_intl_i386_zip.exe) 

KB Article Number(s): 2791026 Language: All (Global) Platform: x64 Location: (hotfixv4.microsoft.com/.../462116_intl_x64_zip.exe) 

After running this fix, Outlook would not start until the system was rebooted. Once the system came back up, the Anonymous Authentication option was available in Outlook 2010 . 

Here is another information post regarding Outlook prompting repeatedly for user credentials. 

Using CentOS 6.4 x64 for VMware vCloud Director 5.5

Completed a complete installation of VMware vCloud Director 5.5 for a client. This was not a lab setup but the for a real cloud service.

CentOS 6.x for VMware vCloud Director

If your just starting out installing or planning your vCloud Director installation and are trying to decide whether to purchase a licensed Linux or use CentOS, I can certainly attest to the fact the CentOS operates just fine. The installation has been completed for several months now and vCloud Director has not had a single issue. I have installed two for fail-over. I do not have them in a load balance configuration. There are no caveats to using CentOS except of course it is free and thus has no profession or direct product support.

 CentOS Basic Installation for vCloud Director 5.5 

 My suggestion is to not use the basic installation option. Install CentOS with the server option and include both desktops in the installation. Or install them using YUM afterwards.

The one problem I found with CentOS 6.4 for VMware vCloud Director 5.5 was the NIC assignment. vCloud Director 5.5 requires two network interfaces. That is easy and simple enough to add. The problem comes in when there is a need to change addresses. Also, on one of the CentOS for vCloud Director installations , one of the NICs was replying for both ip addresses assigned to it.

Windows XP Login Screen - Fast User Switching

The image above is the nice login screen you get with windows XP Home or Windows XP Professional edition with fast user switching enabled. Fast user switching is usually enabled by default on windows XP but if it is not it can be enabled again. 

When windows XP Professional computer is a member of a domain, fast user switching is disabled. 

Fast user switching cannot be enabled when the computer is a member of the domain. Windows XP Home cannot be a member of a domain, only workgroup. 

Outlook Web App didn't initialize - Exchange 2010

Outlook Web App didn't initialize.

If the problem continues, please contact your helpdesk.

Request URL: https://your-server-name.domain:443/owa/auth/error.aspx
User host address: ::1
OWA version: 14.1.355.2

As you will see from the posted images this Exchange 2010 server was no lab. It was a real situation.  It was not in a sterile lab with no real issues or customer waiting to use the money they spent on new technology and hardware. How it got to this unknown but the resolution to this problem took a little time and is solid. Outlook web app issues and many other desktop computer problems can be solved with software for online computer support. These software application permit access to the user's desktop for web based screen-sharing and remote control to help the user and solve problems quickly on the web. 
This Exchange 2010 server was purchased and setup for a migration from Exchange 2003 to Exchange 2010. It was not setup for demo or lab purposes. It was setup with intend and goal to be a real Exchange server for a migration from Exchange 2003 and getting put into production. But Outlook Web App was not working, and this customer is going to need it. Hope this post helps someone out, Cheers!

The error message in OWA occurred after the login. The OWA login page displayed okay but after the login, the following error occurred.

This is most like due to an improper security setting for the OWA virtual directory. NOT the file system OWA directory under the exchange program folder.

                   

The setting I have for OWA to work are:

From within Exchange 2010 management Console

From within IIS:

The above settings solved the error. This site had a valid cert. You don't need one for this problem to be solved but be aware that in IIs you'll have to uncheck the box that says require SSL cert.

Cert errors are totally unrelated to this. This is strictly an authentication issue within Exchange 2010 OWA and IIS 7.

You can also use the following shell commands to test connectivity. 

Exchange management shell:

Create new exchange 2010 test user account. Run the following from the scripts\ directory in the exchange program folders. Use the exchange command shell with elevated privileges to create the test account if you don't have one already.

new-TestCasConnectivityUser.ps1

then:

Test-OWAConnectivity

output display was the following: 

The test couldn't sign into Outlook Web App due to an authentication failure.

The error above was displayed as output prior to the fixes noted earlier in this post.

Another Outlook web app initialization resource that might be useful to you. Outlook Web App didn't initialize. Hope it helps. 

Access servers, desktop, networks switches and even firewalls remotely. 

 

If you experience users whose outlook repeatedly prompts when configured for Office 365 online exchange this article / post might be useful. 

RDP manager software plays a vital role in resolving issues related to the Outlook application. It provides professionals with a centralized platform to effectively manage and troubleshoot various aspects of the application. This software enables IT administrators to remotely connect to desktops or servers that are experiencing Outlook problems, allowing them to swiftly identify and resolve any underlying issues.

RDP manager software 

One of the key features of RDP manager software is session management, which enhances efficiency by enabling multiple users to simultaneously access and work on the same session without interrupting each other's progress. This functionality fosters seamless collaboration and teamwork, facilitating the collective addressing of Outlook problems. Moreover, the software offers additional features such as file sharing and collaboration tools, which further streamline communication between team members.

Overall, RDP manager software streamlines the troubleshooting process by providing a comprehensive set of tools and capabilities that ensure efficient resolution of application issues in a professional setting. It serves as a centralized platform for initiating a support experience for end-users, not limited to OWA or Outlook. Similar to RDCMan, this software allows the creation of a list of reusable RDP connections. However, unlike Microsoft's RDCMan, 4RemoteSupport's RDP manager software does not require installation and can be accessed from any computer or device, regardless of the operating system. For 4Remotesupport.com's online RDP manager, an internet connection and a modern browser is needed. The online list of RDP connections is centralized, managed, and accessed using a browser.  When the RDP file downloads, the default RDP / RDC client is started and makes the connection to the server or desktop. RDP client that supports the RDP format are recommended.  

Online RDP Manager

In addition, RDS servers enable a pseudo centralized RDP connection and desktop availability. They are commonly used to grant users access to a virtual application or desktop. Software designed to centralize RDP connections, such as the one offered by 4RemoteSupport.com, is specifically designed for single administrators or support teams. It presents a managed list of RDP connections, providing a convenient and efficient solution for managing and accessing these connections. Online RDP manager Live Demo

Online RDP manager software

In conclusion, 4RemoteSupport RDP manager software is an essential tool for professionals dealing with Outlook application issues. Its centralized platform, comprehensive features, and seamless collaboration capabilities make it an invaluable asset in efficiently resolving problems and ensuring a smooth workflow in a professional environment. Centralized RDP Connections accessible from the web with only a browser permits IT teams to engage in supporting their environments more efficiently. Since the list of RDP connections are available to all members (or even a single admin), connections can be made to servers or desktops without looking up a server or desktop name. The list of RDP connections managed online and centralized can contain a description field to keep a note on the purpose of the server or desktop.  Some servers and desktop give away their purpose or function depending on the naming convention used but for those who use a more flexible naming convention, the name may not give away the purpose, so the description field is quite useful.  The server can be used in the RDP connection name or the IP address.  

Manage RDP Connections

Furthermore, RDP manager software not only enhances productivity but also improves security measures. With its advanced encryption protocols and secure remote access capabilities, professionals can confidently access and manage Outlook application issues without compromising sensitive data. The software's robust authentication methods and user access controls ensure that only authorized individuals can connect to the system, minimizing the risk of unauthorized access or data breaches. By prioritizing efficiency, 4RemoteSupprt's online RDP manager becomes an indispensable tool for professionals seeking to optimize RDP access and their Outlook application management processes. RDP Connection manager Live Demo

XenApp Session Printer Registry Key Location

Citrix XenApp Session Printer Registry Location.

Corrupt drivers in Citrix xenapp can often lead to printers repeatedly being included into user session that should not be included. They are from past connection sessions and are "stuck" in the registry and part of the users profile.

As I have experienced, even when the driver is repaired, the printers still show up in the user session when they aught not to be.

The location where these printers are defined is the following:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Printers

If this key looks familiar to you it's because it's the location in the registry where local printers live. Session printers are local printers for the user who is logged into the server and has started the published application even if the printers are network printers.