Outlook Keeps Prompting Connecting to Office365 Email

Outlook Keeps Asking for Password Credentials, Office 365. 

Outlook 2010 not fully completing the setup process when connecting to Office 365 can occur more often with Outlook installed on Windows XP. One of the signs to this problem is that under the security tab when using the manual configuration method does not display Anonymous Authentication as an option. Anonymous authentication works well but is the default for Outlook 2013, not Outlook 2010 and Outlook 2007. Outlook 2010 and Outlook 2007 do not have this option by default. In this specific case for which I generated this article, the desktop Windows XP and started out with Outlook 2007 which as one of the attempts at resolving this issue was upgraded to Outlook 2010 with SP1. The first two check-marks appeared during automatic Outlook setup but the third would repeatedly prompt for a password. The setup would not fully complete. The password was correct and was tested using Outlook Web Access.

Please Share others can find this solution faster
 

Outlook Office 365 Configuration Does not Complete

Outlook Keeps Prompting for Password  

Outlook 2010 with SP1 installed on Windows XP with SP3 and other updates would not connect to Office 365 for email. It would not fully setup. Outlook constantly prompted the user for a password. The password was well known and being entered correctly. As previously mentioned this desktop originally had Outlook 2007 which was upgraded to Outlook 2010 and this upgrade process may not have been required at all. One of the best ways to assist users with this problem and to provide support for this and other issues is by using software that enables access over the web. In particular, to connect to a remote computer system and fix the technical  problems remotely with online software for remote desktop control. The software enables remote connectivity and access. This Outlook email and other technical general desktop issues in general can be resolved with screen-sharing. 

Resolving Outlook Setup Not Completing with Office 365

A little more back ground first to help set the stage as to why the focus was completely placed on the local desktop and environment. The user's account setup with no problem in Outlook on an off-site computer desktop. The off-site computer was not connected to the domain and there was no VPN connecting it to the domain.

The steps taken to resolve this issue consisted of : 

Registry Changes: 

Run Regedit and go to  HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\AutoDiscover
for Outlook 2010

Add or modify the following

"ExcludeScpLookup"=dword:00000001
"ExcludeHttpsAutodiscoverDomain"=dword:00000001
"ExcludeHttpsRootDomain"=dword:00000001
"ExcludeSrvLookup"=dword:00000001
"ExcludeHttpRedirect"=dword:00000000
"ExcludeSrvRecord"=dword:00000001

These keys could also be added to help prevent Outlook frm using the local CAS server if one exists on your network. In this case there was indeed a local Exchange 2007 server. The customer had migrated to Office 365 but the local Exchange server was still present on the network and int he domain.

[HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\AutoDiscover\RedirectServers]
"autodiscover-s.outlook.com"=hex(0):
"autodiscover.outlook.com"=hex(0):

The only look-up type that will be used now is HTTP Redirect to the XML file. If this fails, there'll be no Autodiscover. This removes local domain interference.

Microsoft Hotfix to Connect Outlook to Office 365 

The most generally accepted suggestion from many forums, but seems not to always work for people having this problem with Outlook connecting to Office 365,  is to run Windows updates and update your operating system and Microsoft Office installation (at least Outlook 2010). As mentioned previously this particular desktop had Outlook 2007 with Office 2007, I upgraded only Outlook.  Perhaps I did not need to upgrade Outlook at all. The operating system already had Service Pack 3 for Windows XP. I did not run Windows updates because I did not want to have other applications break.

Add the anonymous option to Outlook Logon Security Option list. 

Instead of running every single Windows update available which did not work for many people having the similar issue with Outlook and Office 365, I ran the following a hot-fix. The hot-fix both added the Anonymous option to Outlook's configuration options and enabled Outlook to connect and fully configure to Office 365.

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)

 

Remove System Reserved 100MB Partition or Volume

Windows Server 2008 cycle boots or stuck in Startup Repair Loop

Windows 7 cycle boots or stuck in Startup Repair Loop

The 100 MB system reserved partition that normally contains the boot-manager for windows 2008, Vista, and Windows 7/8, Windows 2008 and 2012 server operating system platforms sometimes need to be removed. Regardless of the reason, there are situations that will call on its removal which are beyond the scope of this post.

Windows Server 2008 Doesn't Boot

Windows 7 Doesn't Boot

This volume/partitions reason for existence is to be the home of the boot files and boot loader. However, if you are finding that this partition is causing boot-up problems, there are ways to successfully.

This will be done with windows 2008 server in mind as juts recenlty there was a need to try to recover from boot-failing server.  On every reboot, the system repair always runs. There are other posts about his problem early (per season) .
Firstly, have the server install media and add it to the dvd drive of the computer. The computer that is attempted to be repaired must have the CD ready.
Insert into drive and satr tthe installation. Select Repair installation. At this point you will have booted from the DVD and selected Repair. Open a command window.
From the command window. run DISKPART. The prompt will change to :
    diskpart >
         type list volume and hit enter. This will list all the volumes.

You will get a list of all volumes with and without drive letters.
                  Similar to the following :

   

Please Share so others could find this solution faster

Windows Server 2008 stuck in Startup Repair Loop

As seen. the system reserve partition has been assigned the C drive so of coruse this server does not boot and every time the drive letter is set appropriately using diskpart, the drive letter reverts back to C.

So the solution is to copy all the files and folders that are on the reserved partition to the actual Windows drive. In this case that's the E drive. Copy using > xcopy /h as all files are hidden. To view the hidden files when listing the directory contents, use >dir /a:h   .

The boot folder and other files located at the root of the system reserved partition need to be copied to the real C drive. Once they are copied, mark the real C drive as active. remove the letter assignment from the system partition thus freeing up C . Assign C to the real windows drive that now also includes the boot manager files. Use diskpart remove the system reserved partition. Make the Reserve Partition the selected partion to work with. Be sure you have chosen the right partition. active

       diskpart> select volume # {volume # of 100MB reserved partition)
       diskpart> list volume         (be sure you see the asterisc next to the reserved partition)
       diskpart> remove

Make sure the right partition has been marked active:
     select the c volume as the active volume to work with
       diskpart>  select volume # {volume # of the the C volume)
       diskpart> active

Exit Diskpart by typing exit.

Then run fro mthe command prompt:

bootrec.exe /fixmbr

bootrec.exe /fixboot

bootrec.exe /rebuildbcd

       
Now restart the system .
   


Thank you Ed Hammond http://edhammond.blogspot.com/2010/07/removing-100mb-system-reserved.html
Another good source http://www.tweakhound.com/2012/11/13/how-to-fix-the-windows-bootloader/

Basic Cisco QoS for IP Phone System to IP Phone VoIP System Voice Garbled

Sample Cisco QoS for IP Phone System to IP Phone System to Solve Distorted Voice Quality

In this situation, the remote office's router is a Cisco 1841. The VoIP (voice) over a  legacy T1 Point-to-Point was garbled. The conversations sounded like the callers were underwater. There was need to clear up the voice quality and the best method to do so was to use QoS.  The unclear voice occurred on nearly all phone conversations both internal and external. The phone sets at the remote office were digital but the phone system is IP (VoIP) based. The remote office phone system and the phone system at the main office communicated via IP.  The simple solution, using the existing hardware already installed, for this problem was to implement QoS on the router. The goal was to prioritize the voice packets that were sent in and out of the router from one system to another. At the same time, the goal was to also keep the solution as simple as possible.

Cisco Remote Office Router - QoS class-map, policy-map, and access-list on router for Voice Quality

This simple basic QoS example firstly required a simple access list that contained both of the phone systems' ip addresses. After the simple access-list, a class-map and policy-map were also configured on the router. In the end, the policy map is applied to an interface.
 First, in configuration mode of the router,  the access-list. is created.  The access list basically will contain a lists of our phone system ip addresses for the main office and the remote.

Replace the ip addresses shown below with the ip addresses of your phone system. Also, if the access-list number is already taken on your router for another access-list, use another number. This example uses 101 for an extended access list.

   access-list 101 permit ip any host 192.168.1.10
   access-list 101 permit ip any host 192.168.2.10

 Next, create a class-map on the branch router. The class-map is basically a map or list of the match criteria. If you haven't guessed it already, the match criteria will be the ip addresses of the phone systems. In the class-map, we add "match access-group 101. 101 is the access list that contains our phone systems' ip addresses.
    class-map match-any IPPhoneSys-to-IPPhoneSys
   match access-group 101

 After the access-list and class-map is configured, the class-map is applied to the policy map. The policy map can contain more than one class-map.  So the policy-map is like a list of class-maps. The policy-map is applied to an interface. In this example it will be the serial interface corresponding to the T1 (point-to-point T1).: The bandwidth statement is key to what we are trying to accomplish. This is a simple example of QoS so I have just merely taken 20 percent of the bandwidth and pretty much assigned it to voice (VoIP)

    policy-map QoS_Policy_Priority
    class IPPhoneSys-to-IPPhoneSys
    bandwidth percent 20
    class class-default fair-queue

In this example it is a legacy point-to-point T1 that connects the two offices. The interface you use may differ. To apply the policy-map that contains the class-map with 20 percent bandwidth defined for voice change to the interface level commands by entering the interface on which you plan to apply the QoS policy map. In this example it is a serial interface for the t1 (S0/0/0)

    config# interface serial0/0/0

 Then apply the policy on the interface by running the command

    service-policy output QoS_Policy_Priority

 The above is a simple basic QoS policy using one of the many Cisco Modular QoS solutions. Once applied, it cleared the voice issues immediately. In the example above the bandwidth reserved for voice over ip (VoIP) was 20 percent. You can change that percentage to fit your environment.

QoS can be applied to all types of data streams including RDP (remote desktop protocol).  Applicable for access to server and desktop or for managing RDP.  The protocol by port number or IP address can be managed so that it's given higher priority, or lower priority if that's what the situation requires. RDP port setting can be set to a custom value on RDS servers for standard access or for managing RDP (Terminal Server). 

 

small-portable-fast-malware-anti-virus-scanner

For a fast small portable malware removal scanner try superantispyware portable edition scanner. It is free and can run from the infected computer's hard-drive or from a USB drive. Often malware and other bad-ware will disable internet access or sites that contain tools that can clean the computer.

Superantispyware portable does not need to be installed and can run from a USB or other drive.
I have used this program often over the years and even before they had the portable edition. Works very well.

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. 

God Mode in Windows 7

Windows 7 interface (and desktop) is rather clean and minimalist. Control panel as XP, 2000, and other previous OS version before offers a place to access and change settings. There's a lot of clicking into the different applets in control panel to get to the setting you may need at the time. It won’t allow you to see and easily use all those nested settings included in the main options.

Did you know that you can become a God? Well, at least on Windows 7!
One of the less known options on Windows 7 is the God Mode feature. Basically, it lets you have every setting and option right in front of you, ready to be used without having to browse among different settings before getting what you are looking for.

Here is how to enable it:

Right click on any bank space on your desktop.
Click New from the menu and create a New Folder.
Rename the folder as follow: GodMode.{ED7BA470-8E54-465E-825C-99712043E01C}
DO NOT use this trick on Vista and Windows 7 64X. It will cause your Windows to crash! (read comments below)

This simple command will create a special shortcut to the God Mode option letting you access all Windows 7 functions via a handy GUI!
EDIT: GodMode also works on Windows Vista!
[credit: stadt-bremerhaven.de]

List Users With Forwarding Enabled Exchange 2003

List Users With Forwarding Enabled Exchange 2003

To find all users in AD that have forwarding turned and enabled for their account and mailbox create a new saved query in AD Users and Computers and use the following LDAP query.

(&(mailNickname=*)(altRecipient=*))





This is very useful obviously if there a many accounts and you need to find all users that have had forwarding turned on for their account. The alternative to this is to select the properties of each user account one at a time and look at the delivery options configuration.

A Browser Active Sync Test URL

Technical issues with IIS, OWA, other web based email services and even email clients such as Outlook can be resolved remotely. Software for Online Computer support can help resolve problems remotely. More often than not, user experience is increased by enabling your support team to have on-demand remote access to desktop computers and server. The more methods there are to test, the more likely the problem you're working on can be resolved with certainty and assuredness.  

https://owa.{yourdomain.gr}/Microsoft-Server-ActiveSync/

The URL could even be http if SSL is not configured on the server to be required.

Testing active sync using a browser returns as an error in the browser window of Error 501/505 - Not implemented or not supported.

For Exchange 2007 and Outlook Web Access 2007, the error 501 and 505 seen on the page displayed is actually normal and should be the response the browser receives from the web server. After all, it's not a mobile phone it's a browser.

Although the error massage has changes slightly in windows server 2008 and windows server 2008 R2, it is very similar. The URL for testing ActiveSync is still in new versions of Exchange. Microsoft Exchange 2007 and Microsoft Exchange 2010 still use the same service point with the IIS web server structure and virtual directories.

To the remote user and to the smartphone it's still the same. underneath, server side, there have been many changes to Internet Information Services. In Windows server 2008 and 2008 R2, IIS has undergone many functional and interface changes for server administrators. When trying to setup a smartphone or mobile device, iPad or iPhone for ActiveSync to get email from an Exchange server, the URL is still the same. The URL that can be used to test active sync access and connectivity is the same and can be tested bot internally and externally. The difference being of course what name is entered into the browser and support for internal and external access is the same as well.

Since the writing of the above article Exchange and email hosting has changed dramatically. There are fewer installations of Exchange servers on-premises, and the use of hosted email or online exchange has increased tremendously.  I'm personally not a huge proponent of hosted everything. Once hosted, the hosting company essentially has a key control of your destiny and future. I do understand the need, convenient use, and the economics of hosting. The use of hosting services is invaluable. The are still those who have their own servers in their server rooms and data closets. In addition, there are companies that have their servers hosted in a cloud whereby the server is still theirs essentially, it's not just a service but a windows server that's accessible as if it was present in their own server room. A convenient method for accessing those servers has still remained to be RDP (remote desktop protocol).

Managing RDP Connections

RDP access is used extensively by network and server administrators all across the world. Small and large IT departments benefit from using RDP. Initially part of Microsoft's NT Terminal server which was a separate independent edition of Microsoft Windows server. RDP was then implemented as an add-on service feature of windows server. The RDP was added to desktops such as the pro editions of Windows, RDP is widely used to access servers in their own closest or hosted in a cloud. RDP provides benefits that on the surface assist in accessing and managing servers remotely. RDP protocol helps with troubleshooting issues with file servers, email servers, or other enterprise servers such as domain controller servers for Active Directory and more.  RDP clients have been developed for macOS and Linux systems. There are even RDP protocol clients for android and tablets. Managing RDP connections can be achieved by using installable desktop software or a better method for accessing RDP connections is online using a browser.  Managing RDP connection is beneficial to all administrators and also could be useful for standard general users of desktop. Since the RDP protocol has been implemented into the pro editions of the windows desktop operating system, RDP connectivity has bee made available for general purpose productivity and application use by users. Managing RDP connection can be centralized with the proper software tool. An RDP manager can provide access in a centralized manor to RDP connection made available to administrator and user. https://4RemoteSupport.com software for managing RDP connections centrally is 100% online and compatible with macOS, Linux and MS Windows and virtually any device can manager RDP connections. 

RDP Connection Manager

Microsoft has since initial inception of RDP and terminal server RDS gateway. remote desktop Gateway is a method for network and server administrators to provide a centralized location for users to access to connect to RDS (Remote desktop Service) servers or their own desktops. Independant of RDS gateway are RDP connection manager software tools that enable administrators and server admins to give access for themselves and for users An RDP connection manager software centralizes connections.  RDP connection manager software that's completely online further simplifies access to RDP connections for administrators and general users by offering a single point of connectivity and predefined connections 4RemoteSupport has a RDP Connection manager software tool that enable A centralized RDP manager, that also simplifies managing and connecting to desktops and services through a simple UI. Administrators can add new connections in seconds and are available to other administrators or users immediately. RDP connection manager software tool by 4RemoteSupport creates RDP files "on the fly". When a connection attempt is made using one of the saved RDP connections, a file is created and downloaded through the browser's standard file download interface. There's no need to save RDP files on servers, or on web sites. there's no way for a hacker to get all connections because they are automatically crated and downloaded each time the RDP connections are accessed by an administrator or user. RDP connection manager software that saves files requires exporting. managing RDP connections using an RDP connection manager that's online instead of installed on a desktop provides faster easier access to RDP connections with a centralized easy t use interface that benefits administrators and general users of RDP. https://4RemoteSupport.com RDP Connection manager is a software tool that doesn't require installation for centralized RDP connection management with a simple browser UI securely.