Viral Rathod Exchange Server 2016 Blog

Microsoft Exchange Server Blog

  • Click here to Register for Experts-Exchange Account

  • My Experts Exchange Profile

  • Disclaimer

    All information is provided "AS IS" with no warranties, and confer no rights, and as such you perform at your own risk.

    NOTE: You should always make a backup of your server or export the registry before making any changes to it.

  • Advertisements

Archive for the ‘Exchange Server 2003 Posts’ Category

Best anti spam filtering software for Microsoft Exchange Server 2016

Posted by viralr on January 8, 2017

Best anti spam filtering software for Microsoft Exchange Server 2016,


I would recommend you to try, Vamsoft ORF Fusion which is a great piece of Anti-Spam software and in this software, you can set the Sender Blacklist to Blacklist ALL Addresses except the ones you specify, which will be the list of the 520 domains that you want to accept.

Once Blacklisted, the emails can be rejected (or whatever you choose to do with them) but the ones that pass the Blacklist check will be allowed through.

You can install a 42-day trial of the software to see if it does what you want it to do and then if you’re happy with it, it’s a relatively low-cost purchase and you don’t have to renew it annually, although you can to keep the software up-to-date with new releases, but it won’t stop working if you don’t renew.

Reference :-


Posted in Exchange Server 2003 Posts | Leave a Comment »

Exchange server 2016 / Exchange server 2013 error OWA / ECP :-( something went wrong

Posted by viralr on December 28, 2016

Issue :-

You have successfully installed Microsoft Exchange Server 2016 or Microsoft Exchange Server 2013. The installation process may have failed or been interrupted at some stage and then resumed and finally completed successfully. However, when you try to access Exchange Control Panel (ECP) or Outlook Web App (OWA), you receive the following error message:

“500 : – ( something went wrong”
The server operation timed out. Please try again later.


Cause :-
This issue occurs if SharedWebConfig.config is missing from either of the following locations:

C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy
C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess


Copy sharedWebConfig.config file from C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy directory.
Past sharedWebConfig.config file to C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess directory

OR Vice Versa
after copy do IISreset /noforce


Posted in Exchange Server 2003 Posts | Leave a Comment »

How to Disable IPv6 autoconfiguration in Windows servers

Posted by viralr on December 28, 2016

How to Disable IPv6 autoconfiguration in Windows server (Disabling IPv6 Stateless Autoconfiguration) :-

Stateless autoconfiguration of IPv6 allows the client device to self configure it’s IPv6 addreess and routing based on the router advertisements.

So to Disable auto configuration of IPv6 address execute following command,

First to check the network interface on which ipv6 is autoconfiguration execute following command,

netsh interface ipv6 show interface

Then finally to Disable ipv6 auto configuration execute following command
netsh interface ipv6 set interface “Local Area Connection” routerdiscovery=disabled

Please refer following article if you need more information about Disabling Stateless configuration.

Posted in Exchange Server 2003 Posts | Leave a Comment »

How to reset forgot administrator password in Hyper-V Server 2012 R2 ( bare metal)

Posted by viralr on December 5, 2016

How to reset forgot administrator password in Hyper-V Server 2012 R2 ( bare metal)

Please try steps given on following article, this trick works on all versions of Windows ,the same is tested on windows 10 / winows server 2016.

It hardly takes 5 minutes.

Posted in Exchange Server 2003 Posts | Leave a Comment »

SBS Failed to start listening (Error: 10049). Binding:

Posted by viralr on December 5, 2016

After Migration to Exchange 2013 you have some errors in eventlog.

Event ID : 1019
Failed to start listening (Error: 10049). Binding:

Solution :
SBS only supports 1 NIC at a time. Exchange was trying to communicate with both NIC’s thus it could not start listening on the 2nd one.

So basically this issue occurs if the IMAP service is not configured to listen on a local IP address or if the receive connectors for the Transport service cannot bind to an IP address.
The IMAP Service needs to bind itself to one of the local Adapters on the exchange server.

To resolve this issue, configure the IMAP service to listen on a local IP address, and configure the receive connector to listen on all IP addresses.

“netstat -a” will show you current listening ports bound to IP/interface.
This example sets the IP address and port for communicating with Exchange by using IMAP4 with no encryption or TLS encryption.

Set-ImapSettings -UnencryptedOrTLSBindings IPaddress:Port

After you’ve set the IP address and port settings for IMAP4, you must restart the IMAP4 service for the settings to take effect.

The fix available on following article

Please feel free if you have any question and I will be happy to help.

Posted in Exchange Server 2003 Posts | Leave a Comment »

How to test autodiscover connection for a user

Posted by viralr on December 2, 2016

Test-OutlookWebServices -identity: –MailboxCredential (Get-Credential)


Posted in Exchange Server 2003 Posts | Leave a Comment »

Email Server SMTP Test for Outgoing E-mails

Posted by viralr on February 24, 2015

Email Server SMTP Test for Outgoing E-mails :-

If you are facing issues where your outgoing Emails are consistently rejected by other servers or land up in Junk Email or SPAM folders of the recipient mail box, this test can help you in identifying the problems.

Testing Process

  1. Send an Email to
  2. That email will bounce with a URL in the bounce messge.
  3. Either click on the URL or Copy/paste the URL in a browser.
  4. You will see report on your Email Server.


Ref :

Posted in Exchange Server 2003 Posts, Exchange Server 2007 Posts, Exchange Server 2010 Posts | Leave a Comment »

Active Directory Interview Question and Answer

Posted by viralr on September 5, 2013

Active Directory Interview Question and Answer :-

1) Whar are the New Features in Windows Server 2008 R2:-

1. Active Directory Administrative Center—For administrators, the biggest change in Server 2008 R2 is undoubtedly the new Active Directory Administrative Center, which replaces the older Active Directory, Domains and Trusts, Sites and Services, and Users and Computers management tools. The Active Directory Administrative Center is built on top of PowerShell and its actions are scriptable. One really nice feature is the new Active Directory Recycle Bin.

2. Remote server management—Server Manager was one of the best improvements in Server 2008 because it provides a centralized and useful console for managing Windows Server. However, Server Manager is limited to working with the local system. With R2, Server Manager can be installed on network clients and can be used to manage remote Server 2008 systems.

3. PowerShell 2.0—Server 2008 R2 includes PowerShell 2.0, which features improved WMI cmdlets and support for running scripts on remote systems, creating ScriptCmdlets, and running background jobs. In addition, R2 has a new graphical PowerShell UI for developing and debugging PowerShell scripts. PowerShell 2.0 is compatible with PowerShell 1.0

4. Support for the .NET Framework in Server Core—One of the biggest disappointments in the original Server 2008 release was the lack of support for the .NET Framework in Server Core, which meant that technologies that seemed perfect for Server Core, such as Windows PowerShell and ASP.NET applications, couldn’t run on Server Core. R2 fixes this problem by adding support for a subset of the .NET Framework that supports both ASP.NET and PowerShell.

5. Live Migration—Probably one of the most anticipated features in R2, Live Migration improves VM availability by letting you move Hyper-V VMs between hosts with no downtime. Live Migration is Microsoft’s answer to VMware’s VMotion. Live Migration is built on top of R2’s new Cluster Shared Volumes technology, which lets multiple cluster nodes concurrently access the same LUN.

6. New Hyper-V—A new Hyper-V release is included in Server 2008 R2. A prerelease version of Hyper-V was shipped with the original Windows Server 2008. R2 includes the latest version of Hyper-V. In this version, VMs are able to address up to 32 cores per VM, and the use of TCP Offload and Jumbo Frames provides improved networking performance. One of the biggest improvements in Hyper-V is support for the next item, Live Migration.

7. Remote Desktop Services—Another change in Windows Server 2008 R2 is the rebranding of Terminal Services to Remote Desktop Services. However, the changes aren’t in name alone. The new Remote Desktop Services includes support for the Aero Glass interface, multiple monitors, and DirectX 11, 10 and 9.

8. Core Parking—Windows Server 2008 R2’s new Core Parking functionality enables improved power management. Core Parking lets the OS suspend cores that aren’t in use, thereby saving the power required to run those cores. Parked cores can be reactivated in milliseconds to respond to increased workloads.

9. Support for 256 cores—Improved scalability is another important feature in Server 2008 R2, which will be able to utilize up to 256 cores. This number is a huge jump from the 64-core limit in the original Windows Server 2008.

10. 64-bit only—Windows Server 2008 R2 marks the first time that the Windows Server OS will be 64-bit only, meaning that Server 2008 R2 must run on x64-compatible hardware. Almost all of today’s popular server hardware will accommodate this requirement, but the R2 release won’t run on 32-bit systems.

2) System State Backup includes which components ?

The system state Backup includes the following components on a domain controller:

  • Active Directory (NTDS)
  • The boot files
  • The COM+ class registration database
  • The registry
  • The system volume (SYSVOL)
And on a non-domain controller, the following components are included:
  • The boot file
  • The COM+ class registration database
  • The registry

When a member server or domain controller with a certificate server is installed, the following additional item is also included:

  • Certificate Server

Note: System State information is backed up and restored as a unit.


Posted in Exchange Server 2003 Posts | Leave a Comment »

What is the Exchange Server Dial-Tone server scenario?

Posted by viralr on October 5, 2011

# What is the Dial-Tone server scenario?

If you one day are faced with a relatively large corrupt Mailbox Store, restoring it can, depending on things such as backup hardware, backup application and network speed, be quite time consuming. Now the last thing you want to deal with in such a situation is frustrated users (or even worse a yelling CEO!).

So how can you get your users to calm down (and your CEO to s… up) and get back to work while you concentrate on getting the Mailbox Store back to life? There’s one simple answer and that is, you can create a dial-tone database and thereby get message flow and mailbox access recovered almost instantly. By using a dial-tone database your users can start to receive and send mail again, they can even go check out old messages that existed in their mailbox on the Exchange server (if their Outlook client has been configured to use cached mode that is), bear in mind though they have to switch between Online and Offline mode when prompted with the Outlook 2003 Exchange Recovery Mode dialog box. I’ll talk more about Outlook 2003 Recovery mode in “Demystifying The Exchange Dial-tone Restore Method (Part 2)”.

Using the dial-tone database restore method means that you, while restoring one or more corrupted Mailbox Stores from the most recent backup, have users connect to a new empty or blank Mailbox Store. The dial-tone restore method is by no means new; it’s been used with previous versions of Exchange as well, but now that we have the Exchange Server 2003 Recovery Storage Group (RSG) feature, the method becomes even more attractive when restoring Mailbox Stores within your Exchange messaging environment.

Note: With previous versions of Exchange a dedicated Exchange recovery server was required. Using a separate Exchange recovery Server meant you first had to restore the required Mailbox Store(s) or database to the recovery server, then either export the data from the restored database(s) to PST files using Exchange Server Mailbox Merge Wizard (ExMerge) or copy the whole Exchange database from the recovery server to the production server. As an Exchange database often is several gigabytes in size, this meant you typically had to copy large amounts of data over the wire which, depending on the network, could add several hours to the total recovery time.

Using the Recovery Storage Group feature makes it possible to restore Mailbox Stores without the need to build and use a separate Exchange Recovery Server; instead you can simply restore the Mailbox Store(s) directly to the Recovery Storage Group (RSG) on the respective Exchange Server or any other Exchange 2003 Server in the same Administrative Group. This makes it an easy and painless process to merge data from the restored Mailbox Store(s) to the dial-tone database, or swap the restored database from the Recovery Storage Group (RSG) to the dial-tone database in the original Storage Group, then merge data from the dial-tone database to the restored Mailbox Store. I’ll also talk more about swapping databases in “Demystifying The Exchange Dial-tone Restore Method (Part 2)”.

Note: If you’re not familiar with the Recovery Storage Group (RSG) feature, I recommend you checkout MS KB article: 824126 – How to use Recovery Storage Groups in Exchange Server 2003 which does a great job explaining how you can recover Mailbox Stores or individual mailboxes using by restoring a Mailbox Store to the RSG.

Posted in Exchange Server 2003 Posts | Leave a Comment »

Event Id 1009 The license store for the client access licenses is not valid and could not be restored from an automatic backup.

Posted by viralr on October 5, 2011

Event Id 1009 The license store for the client access licenses is not valid and could not be restored from an automatic backup:-

Observed following Event Id 1009 is occurring on the server which states that :-

Open the SBS Server Management Consol -Click on Licensing and observed there are no license key available.

Resolution :-

  1.  Open SBS Server Management Consol – Click on Licensing Tab.
  2. Click On Restore Licenses


3. Click on Next

4. Click on Browse Button

5. Select C:\WINDOWS\system32\

6.Click on Next Button

7. Click on Finish Button

8. Make sure License Code and Number of Licenses are now display on the SBS Licensing Consol


Hope this post may help you to restore the missing licenses.

Please feel free to letme know if you have any query’s.

Posted in Exchange Server 2003 Posts | Leave a Comment »