MailboxImportRequest Fails

I ran into an issue with a Powershell script I wrote recently, where I received this error:

The name must be unique per mailbox. There isn’t a default name available for a new request owned by mailbox xyz

Basically, a record is kept for completed mailbox move requests, and if you do too many for one mailbox, you get the above error. Don’t worry! Just run the following command in PS to clear away the completed request records, and you’ll then be able to run the import request!


Get-MailboxImportRequest -Status Completed | Remove-MailboxImportRequest

That’s it!

VDP Upgrade Keeps Prompting To Take a Snapshot

In the course of upgrading a client’s Vmware Data Protection appliance today, I ran into an issue of it continuing to say “Create a snapshot first!”

Eventually I found that I had to re-test and re-enter the vcenter credentials into the appliance! After that, the upgrade could commence.

No Access to VDP Web Interface

I ran into an issue today that I was banging my head against until I found an obscure Vmware article.

Basically, when I tried to access my VDP appliance through the browser via port 8545, Chrome and IE would both say the connection was dropped or not accessible. “Failed to load” or “is not available” were the other errors.

This is the article I found:

When Chrome/Firefox changed some settings regarding SSL certificates, it basically broke being able to access VDP devices that hadn’t been updated in a while. The above article has a Hotfix that you can install to fix the issue. It did for me!

Converting an Office365 Recipient Mailbox to a Shared Mailbox

Quick and easy tip today. A user left the company and to free up the license used on Office365 but keep the user’s mailbox, you can easily convert the mailbox to a shared mailbox, which you don’t get charged for on Office365.

Basically, go into Exchange Admin Center > Recipients > Choose the Mailbox you want to convert  and on the right side, click “Convert to Shared Mailbox”


That’s it!

How To: Disable Clutter in Office365

To disable Clutter in Office365 via Powershell, simply do the following:

Connect to Office365 Powershell for your account

Then simply run this command to disable Clutter for all mailboxes:

Get-Mailbox | Set-Clutter –enable $false

That’s it! If you want to disable Clutter for a single mailbox, you can do the following:

Set-clutter -identity $false

To do this via the Office365 Portal, just navigate to: Mail > Automatic Processing > Clutter and turn it off!

Java Error 1603

While trying to install Java today, I encountered an error that wouldn’t go away: Error 1603. Scouring Technet forums, blogs, etc. no one had a real sense of what the cause was. Some said it was an old Windows Update. Some said it was a bad Java installer package.

Eventually I found my solution: I was connecting through LogMeIn to the device. I ended the LogMeIn task and process, RDPed in, installed Java… and voila! It worked. Re-enabled LogMeIn and I was on my way.

Improving xrdp Performance on Centos

I had some poor performance with XRDP, so I found this nugget of info that helped things a little:

Backup xrdp.ini (XRDP config)

sudo cp /etc/xrdp/xrdp.ini /etc/xrdp/xrdp.back

Open the XRDP config with nano:

sudo nano /etc/xrdp/xrdp.ini

Under [Globals] change max_bpp to 128 and add this line below:


Restart XRDP services:

systemctl restart xrdp.service

Enabling XRDP on Centos 7

I’ve been playing with Centos recently and have been working on integrated it with a Windows Domain / VM I have setup. To ease accessing it, I found that it is possible setup XRDP (an open-source version of RDP) so that you can access Centos from a Windows system using regular RDP.

Assuming you already have your desktop environment setup, open up terminal and run the following as root:

yum -y install xrdp tigervnc-server

Then, start the service:

systemctl start xrdp.service

To see if it is running, type:

netstat -antup | grep xrdp


I had to run these commands to get it to work:

chcon -t bin_t /usr/sbin/xrdp

chcon -t bin_t /usr/sbin/xrdp-sesman


Followed by restarting the service:

systemctl restart xrdp.service

Then all you have to do is enable the service:

systemctl enable xrdp.service

And put in a firewall exclusion and reload the firewall:

firewall-cmd --permanent --zone=public --add-port=3389/tcp
firewall-cmd --reload

That’s it!


For more info, this TechNet article was super helpful. 

Allow External Senders to Send to an Office 365 Distribution List

Simple one here – a VIP relies on a Gmail account when the company is on Office365. To allow the VIP to send to a distribution list, I had to do the following:

1) Open Exchange Admin Center
2) Click on Recipients and then Groups
3) Select the distribution group
4) Click the edit button edit icon


5) Click Delivery Management and select “Senders inside and outside of my organization


6) Then just click Save! save button

You can also use this area to block or allow certain senders to distribution lists by adding emails to the box below.