The WS-Management service cannot process the request. The load quota for the system has been exceeded. Send future requests at a slower rate or raise the system quota

Issue: When I open Exchange PowerShell, I have seen that PowerShell is not able to connect properly and displaying the following error message:

New-PSSession : [EXCHANGESERVER.DOMAIN.LOCAL] Connecting to remote server EXCHANGESERVER.DOMAIN.LOCAL failed with the following error message : The WS-Management service cannot process the request. The load quota for the system has been exceeded. Send future requests at a slower rate or raise the system quota. For more information, see the
about_Remote_Troubleshooting Help topic. At line:1 char:1
+ New-PSSession -ConnectionURI “$connectionUri” -ConfigurationName Microsoft.Excha …
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
    + FullyQualifiedErrorId : -2144108120,PSSessionOpenFailed

Resolution: Go to IIS Management -> Application Pools ->MSExchangePowerShellAppPool

Click Recycle to recycle the pool

Done ! Try to open the PowerShell again and the issue should be resolved !

There is a pending reboot from a previous installation of a Windows Server role or feature. Please restart the computer and then run Setup again

I was trying to install Microsoft Exchange Server 2013 Cumulative Update 9 today. During the Rediness check, it reported the issue “There is a pending reboot from a previous installation of a Windows Server role or feature. Please restart the computer and then run Setup again“. I thought it is a normal behavior as I just extended the drive etc. and definitely want to go for a restart. But, even after the restart also, it showed the same issue. Microsoft references says to check for corresponding registry entries and to edit/delete those as explained here: But this was not really helpful as I was not able to find the exact registry entries as they mentioned.

Finally, I found the solution in the following way. This is also referred on a registry entry creation:

1. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates

2. Create a DWORD (32-Bit) Value  named as UpdateExeVolatile and set the value as 0

3. Exit Registry Editor and you are done

After performing the above steps, the Rediness Check doesn’t found the issue as it reported previously and was able to install the CU9 sucessfully

Are you fed up with the VHDX disk expansion?

Here is a free solution from Systola I used to make VHDX disk expansion life easier.

It’s a common requirement always to increase the disk size, when you want to create more Exchange Databases in a vhdx based disk or a temporary space requirement during your database defragmentation/mailbox move etc.

Traditional method in a Hyper-V environment is go to the VM properties and set the expansion size and wait for hours and hours !! (If you want to expand in TBs)


Most of the production infrastructures won’t be in a position to give such kind of downtime of the live system. In my case, it was expected to have 20Hours of downtime for a 10TB expansion !!!.

How about, anything which can do the task in seconds :) How the tool achieve this kind of miracle is as they mentioned: ‘This tool did not zero-out the new disk, thus it was lightning fast even while creating multi-gigabyte and terabyte-sized VHDs’. If you can afford this condition, go and download vhdxtool.exe:

I actually followed the method as below:

  • Shutdown the Virtual Machine with vhdx disk you wish to expand.
  • Expand the LUN at your storage. It can be EMC or a local disk
  • From the Hyper-V owner node, refresh disk management to show the added space.
  • Right-click the volume and extend to allocate the added space to the current volume.
  • Go to the folder in which you extracted the tool (Eg:C:\vhdxtool\vhdxtool.exe)
  • On the owner node, open PowerShell in Administrator mode and run “C:\vhdxtool\vhdxtool.exe extend -f <path to vhdx file> -s <new disk size>”. When you are working with huge TBs, it can expand the Block Allocation Table too. Otherwise, you can’t be able to see the additional message.
  • Power on the Virtual Machine
  • On the disk management console of the Virtual Machine , make sure that you got the disk expanded. If it’s not, you may want to expand it from there again (Some Hyper-V phenomenon when you use the disk as shared). Right-click the volume and extend to allocate the added space to the current volume.

So, let’s make our life easier with SYSTOLA’s vdhxtool. Thanks SYSTOLA :)

VSS Error 0x80042304: The volume shadow copy provider is not registered in the system

I wanted to share the resolution I found for the issue reported by VSS of a Windows Server 2008 R2. The error showed as ‘Initialization Failed. Error 0x80042304: The volume shadow copy provider is not registered in the system’ when I see the VSS tab of the drive properties as below:


I have seen various articles showing the resolution as re-registering the VSS dll files and none of the method helped in the resolution !

Finally, I checked the corresponding registry keys associated with VSS on a different server and found that there are some missing fields in the server which reported the issue. The registry keys associated are found at: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\VSS\Providers.

The Registry values should looks like as follows and on the problematic server the values under ‘Provider’ was shown as empty:


Finally, I sorted out the issue by adding the missing values: If you come across similar issue, you are advised to follow the similar way. I copied the following value in a .reg file and exported to the server reported issue and that fixed my issue

@=”Microsoft Software Shadow Copy provider 1.0″


Happy to see the result of the solution as follows :)


Source user ‘Microsoft Exchange Approval Assistant’ doesn’t have a primary mailbox

Yesterday, I fixed one of the issue I have faced while I was trying to delete the first mailbox database of an Exchange 2010 deployment. Arbitration mailboxes were presented in the database and New-MoveRequest has failed to move the Arbitration mailbox to a different database.

While trying to move, the error reported was, Source user ‘Microsoft Exchange Approval Assistant’ doesn’t have a primary mailbox’  

Then I tried a resolution in various ways, and finally the following cmdlet helped me to move the mailbox successfully to a different mailbox.

GET-Mailbox -Database “Mailbox Database 1750838926” -Arbitration | New-MoveRequest -TargetDatabase DB01

So, finally I was able to see the progress of the move request and was able to delete the first database successfully



Virtualizing & Managing Exchange with Microsoft Cloud Platform

You need to deliver a consistent and great user experience from anywhere, no matter the device. And you need to transform IT to deliver the business services that enable value. To help you meet these goals, Microsoft offers the Cloud Operating System, a unified platform built for modern business.

Take advantage of new innovations in infrastructure, data, apps, and devices. Enable modern, agile apps to extend functionality to address new app and social patterns. And make it easier for everyone to access and perform analytics on any data, any size, from anywhere.

This course focuses on how you can transform your infrastructure, going from managing server by server to data center scale and to deliver on-demand scale and real-time performance.

Instructor | ​ Matt McSpirit – Microsoft Senior Technical Product Manager

Product Review – Lepide Exchange Recovery Manager

In this product review we will have a look at the functioning and features of the Lepide Exchange Recovery Manager – an Exchange Server disaster recovery, backup restoration, and Exchange/Office 365 migration solution created by Lepide Software. Lepide is into the business of making data recovery software since 2004 and has come up with quite a few well-appreciated and awarded applications in this segment in the past years.

What it does?

Lepide Exchange Recovery Manager is being marketed as a disaster recovery, backup restoration, and Exchange Server/Office 365 to Exchange Server/Office 365 migration solution. But you can do a lot more with it. Here is a list of things you can do with this application:

  • Recover Mailboxes and Public Folders from corrupt EDB files and restore them to Live Exchange Server and PST granularly without using recovery server.
  • Exchange Server/Office 365 to Exchange Server/Office 365 data migrations.(migrates only data from mailboxes and Public Folders, their properties and permissions are not migrated)
  • Email Search across Offline EDB, Live Exchange Server, PST, and Office 365.
  • Convert EDB to PST.
  • Backup Extraction from NTBackup, Symantec, VERITAS, HP Backup (both incremental and differential backup) and CA ARCserve backup.
  • Export mailboxes from Live Exchange Server, offline EDB, OST, Office 365 and PST to a new or existing PST.
  • Archive Mailbox Migration.
  • Export emails from Live Exchange Server, Office 365, OST, and PST to EML, MSG, HTML, RTF and Text file.
  • Upload data from Offline EDB, OST and PST to Live Exchange Server and Office 365.
  • Import emails in EML, MSG, HTML, RTF and Text file into Live Exchange Server, Office 365, and PST.

These are the tasks which Exchange Server administrators have to commonly do. Apart from the above mentioned tasks, software also does a few other things which I’ve not mentioned here. As an Exchange Server administrator you are less likely to come across a requirement which it doesn’t meet.

How Lepide Exchange Recovery Manager works?

Software functioning is very simple. You need to add the source before you can search and export the Mailbox/Public Folder items. To import/upload emails from local disk you need to add destination. To migrate data from one format to another such as EDB/Live Exchange Server/OST/PST/Office 365 to Live Exchange Server/Office 365/PST you need to add both source and destination.

Adding Source

The following can be added as source.

  • Offline EDB File
  • Offline OST File
  • Outlook PST File
  • Live Exchange Server
  • Live Exchange Using Existing MS Outlook Profile
  • Office 365/OWA

Adding Source

The process of adding these to the application as a source is very simple. There are separate wizards to add each of them; all you need to do is select from the options and click Next. The wizard will guide you through the rest of steps providing you all the hints you need.

Source List Options

There are a number of tasks that you can perform in the source folder list. Right-clicking on a source item opens this context menu from where you can do a number of things like copying Folder to destination location, exporting Mailboxes to PST (You can export all or only selected Mailboxes), exporting individual messages, extracting message attachments to a folder, generating mailbox report wherein you get full details of the Mailbox content in grid format, and searching for a particular message in source.  In this screen we can see all the context menu options available.


Database Recovery

After you have added the damaged EDB file to the source you can salvage the mailbox content using “Copy Folder” or “Export Mailboxes…” option from the context menu as shown in the above diagram. So the process of data recovery, i.e. EDB to Live Exchange Server, EDB to PST, Corrupt Live Exchange Server to Production Live Exchange Server and PST can be done in only three steps: 1. Right-click and select the relevant option from the menu. 2. Select and copy what you want to recover, and 3. Paste/Export to destination.  The following screens shows export dialog box.

E-Discovery Feature

Whether it is for compliance or restoring a deleted email from the backups (and you don’t know which backup has that email), e-discovery feature can come handy as you can search for that message from the source list after specifying the search criteria.



Adding Destination

The following can be added as destination.

  • Existing PST File.
  • Create New PST File.
  • Live Exchange.
  • Live Exchange Using Existing MS Outlook Profile
  • OWA/Office 365


Same as source, process of adding destination is also very simple and wizard-driven.

Destination List Options

The following screenshot shows activities that you can do using destination list context menu options. You can paste mailboxes copied from source, import MSG and EML files directly from hard disk to Live Exchange Mailboxes, create new mailbox, and create new folders in Live Exchange Server. So if you want to do data migration from Live Exchange Server/Office 365 to Live Exchange Server/Office 365, simply add them in source and destination respectively, and copy-paste the mailboxes as you normally do in Windows.


 Backup Extraction

Using this feature you can extract EDBs from online and offline backup created by NTBackup, VERITAS, Symantec, HP Backup, and CA ARCserve backup. Once the EDB file has been extracted you can restore the full EDB or granular messages to Live Exchange Server. In this screenshot we can see an EDB file extracted from the BKF backup file.


Other options include creating and using template file to create new PST by software. You can also use this option to create PST files of other languages. All the email attachments can be extracted in a separate folder to the hard disk.  There are a lot of other things that we can do using this application. The following screenshot shows software activity log setting by which you can record all software activities.




Very useful application indeed, I would say. Software interface has been designed like Windows Explorer giving you that familiar Windows environment. All sort of activities related to data recovery and backup extraction can be done by it. While migrating mailboxes you can only copy-paste the data, mailboxes’ permissions and properties cannot be migrated, but then, as we understand it is not suppose to be full-featured migration software. Lepide Exchange Recovery Manager scores well high for what it has been made for.

I highly recommend you to download a fully functional Trial version from the Download Link and to start experiencing it today itself !

The domain join cannot be completed because the SID..

1I recently worked on fixing the following issue on my Windows 2012 R2 Data Center Edition servers in my Hyper-V lab:

The domain join cannot be completed because the SID of the domain you attempted to join was identical to the SID of this machine

Basically, I was trying to join a virtual machine to the domain, which is the clone of domain controller :)  Hyper-V helps us to take the vhdx files for re-use and you may also face this issue in your server life. Don’t worry about this. I have found the solution too as follows

You want to go through sysprep again on the machine as follows:

1. Open a command prompt

2. Change the path to  %WINDIR%\system32\sysprep

3. Run: sysprep /oobe /generalize (This will release the current SID). Shows the progress as below:


4. Server will restart automatically.

5. During starting, you have to enter the product key (depends the type of license you use), password etc.

6. The network settings shouldbe checked again and substitute the required IPs

7. Done !! See how I was able to join the domain after these steps :)


Product Review – Stellar OST Viewer

Why I need an OST Viewer?

Exchange Server keeps mailbox data as EDB files at the Exchange Server end. The same mail data for a particular user is stored at the OST file when the user access the mailbox using a MAPI client like Outlook. There are cases were OST file fails to synchronize when the MAPI gets deleted and which makes OST file Orphan. Chances are there for an OST file becomes damaged too. You might also need to scan and view the OST file in case of Exchange Server downtime to view the mailbox items and that times I would recommend you a very good tool which I have found: Stellar OST Viewer

More about Stellar OST Viewer

I had a chance to use this free utility on my corrupt OST file. Fortunately, I was able to use this tool without much ‘How to use’ documentation as it was found very simple tool to use with. Just browse the OST file and everything at mail mailbox (emails, contacts, calendars, notes, tasks) has been loaded, exactly similar to my Outlook!!! Just saved some of the emails are .msg format.  Also found some supporting formats like EML, RTF, HTML, and PDF useful in your way.

Features – Stellar OST Viewer at a Glance !

Displays Outlook File Detail : Such as emails, contacts, calendar, etc. in a list format.

Search for an OST:  ‘Select OST File’ or search for an OST file using ‘Find OST File’

Allows Deep Scan: Found that it lists entire items in the same folder hierarchy and looks like a powerful algorithm !

Mail Preview supports: Includes info like ‘subject line’, ‘From’, ‘To’, ‘CC’, ‘BCC’

Multiple Formats: From the preview window, I was able to save the email as EML, MSG, RTF, HTML and PDF formats.

Compatibility: Operating system support is found as Windows 8, 7, Vista, and XP. The tool is found as works with Outlook 2013 (32/64 Bit), 2010, 2007, and 2003 versions !

Some more Details: How it looks like

A very user friendly interface as you can see in the below screenshot


The ‘Select OST File’ option  allows to  select the OST file, if the location of the file is known and if you  don’t not know the location, choose the ‘Find OST File’ option. ‘Find OST File’  will popup a new windows as below, in which you can select Drive, Folders etc. You can also select the option to go inside sub folders by putting the check mark for this. See this as shown below:

Find OST File

I was able to view  the OST file contents as shown below:

View OST File

Once the OST file is scanned, the tool lists all the folders in its original hierarchy. The left side of the interface showed all my folders including Inbox, Drafts, Sent Items, Contacts, Calendar, and more. I further navigated to each folder to see the mail items in the middle pane of the same interface. The software also allowed me to have a preview of the selected mail items on the right side of the interface. The preview contained the ‘Subject’, ‘From’, ‘To’, and ‘Cc’ fields etc. Unfortunately, I am not able to show you the mailbox contents here :( and thus copying something from their portal to show you the look and feel:

Preview Mail Items

The Find Message’ option at the toolbar can be used to search for any particular mail items. However, I did not use that option, as I was able to find all my mail items.

Saves Mail in MSG/EML/RTF/HTML/PDF formats

Once I previewed my mail items, it was very simple to save them in any of the given formats: MSG, EML, RTF, HTML, and PDF. I just had to right click on the scanned mail items and choose any desired format. Since I wanted to save the mail items in the EML format, I choose the ‘Save as EML’ option as shown below.


Stellar OST Viewer is found as the best for my purpose. Being a free utility, it does not have any limitations or restrictions to view or save the mail items. It allowed me to view all my OST file content easily and efficiently. I was able to preview the mail items as well as saved them in a desired format. With so many features and compatibility across different versions of Windows and Outlook, the software proves to be the best in its kind.

Patching of Hyper-V Hosts

Many of you may be using Hyper-V technology as the part of your move towards server virtualization. When you want to patch the Hyper-V hosts which are not equipped with a GUI (Server Core) and not connected to internet, we may want to get the help of WSUS server.

I have employed a manual patching of  Windows Server 2008R2 Hyper-V host using a WSUS Server. As the first step, I have setup , configured the WSUS server as the part of the domain (See the link to see how to configure the Group Policy for this). I have connected my WSUS server to the internet and synced with Microsoft Repository of patches. Now everything is ready to deploy the patches to the Hyper-V Host. Cross check the WSUS console and make sure that the Hyper-V host is visible there (You may want to forcefully  apply the Group Policy)

RDP to the Hyper-V Host and I’m going to work on the PowerShell console as shown below (which comes by default when you RDP the Host):

1Note the 2 option available here, 5)Windows Update Settings 6)Download and Install Updates.

I have opted the option 5 by typing 5 and press enter.

Now the ‘Windows Script Host’ console will open and process the connection to the WSUS Server as shown below:


After a few minutes, we can see the list of available patches at the same window. Again, the program will ask to select the updates needed to install as follows:


Type  the option for you from A,N or S and press Enter.

Finally, we will get the progress as shown below. Some of the updates are not found as successful. Let me try those again, after restarting the host