Enable Syncing of Ublock Whitelist and Settings

I’ve been a big fan and user of Ublock (and now uBlock Origin) for a while now, but hated having seperate whitelists on all my devices. I recently found out you can indeed sync those lists if you sync settings within your Chrome or Firefox browser!

Simply right-click on the uBlock icon and click on Options

And on the first page that pops up, you’ll see this option which you should check off:

On your various settings, rules, and whitelist pages you should now see these arrows:

Click the up arrow to upload your current list and then on your other devices, you can enable the setting and hit the down arrow to download that list. And you’re all set!

More info can be found on the github wiki

 

Sharepoint Error – User Not in Directory

Had an odd one today. An internal user with permissions to a Sharepoint site was getting the error “user not in directory”. Searching Google comes up with many different options and reasons for this error, but no concise cause / solution.

The user was able to login to Office365 webmail normally without any errors and was had a Sharepoint license for several weeks and hadn’t reset their password recently.

Eventually, I had the user un-invited and then re-invited and it worked!

Trouble With Running Microsoft eDiscovery Export Tool

I ran into this one yesterday. I was attempting to export a PST file with the findings of a compliance search within Office365. I couldn’t run it on my computer, nor the server where I was offloading the PST to. The error I got was simply “Make sure the export content hasn’t expired”.

Helpful. It obviously hadn’t expired.

Eventually I did the following: First, I started using Internet Explorer to do the export. Next, I found this Microsoft help doc that stated to add the following websites to the trusted or intranet zone in IE.

*.outlook.com, *.office365.com, *.sharepoint.com and *.onmicrosoft.com are added to the Local intranet zone trusted sites.

Voila! That did the job and my PST downloaded nicely.

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!

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:

https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2111900

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!

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.

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

distribution-groups-list

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

delivery-management

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.

 

ERROR: The Windows Filtering Platform has blocked a packet

One of my servers has been getting numerous events logged saying “The Windows Filtering Platform has blocked a packet” with internal IP addresses usually listed.

 

I found that running these two commands quieted the logging:

auditpol /set /subcategory:”Filtering Platform Packet Drop” /success:disable /failure:disable

auditpol /set /subcategory:”Filtering Platform Connection” /success:disable /failure:disable

If you need any other commands, you can check out the full Microsoft article here: https://msdn.microsoft.com/en-us/library/windows/desktop/bb736284(v=vs.85).aspx

Error Backing Up 0x807800C5

After a round of Windows Updates, I encountered the same error on two different servers at different clients. Both used BackupAssist that relied on Windows Server Backup. They both backed up to NAS’s but one NAS was connected as an iSCSI device and the other was mapped as a network share. The versions of BackupAssist were different, as well. One server was bare-metal, one was an ESXI VM. One was 2012 R1, one was 2012R2.

Among the things I tried were:

  • Changing the time of the backup
  • Resetting shadow copies
  • Changing maximum size for shadow copies
  • Changing the VSS mode
  • Checking the status of VSS writers
  • Restarting the servers
  • Restarting backup devices

Eventually I found the backup code, 0x807800C5, on both servers. Googling yielded nothing but a number of other people with the same error running everything from Windows 7 to Windows 2012. After a lot of troubleshooting, I ended up renaming the backup destination that Windows Server Backup used, which gave the backup a clean slate of sorts. Both backups have succeeded since then.

 

The full error I received was:

(There was a failure in preparing the backup image of one of the volumes in the backup set.). Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.