Cloud migrations can be painful. Part of the pain with migrating to Office 365 is getting ALL of the company email into the cloud. Active users are typically easy as there are endless methods for migrating active users. But what about companies that have archived and\or offline email? Trying to manage them locally on PCs is cumbersome and risky. Opening them over the local networks is slow and unstable. We need a method to upload PSTs into shared mailboxes where we can easily attach them to other mailboxes using Office 365 memberships. This blog post is how you should upload PST files into Office 365 mailboxes.
PC performance issues can be difficult to diagnose sometimes. In my experience the hard drive is the most common culprit. Now, I am only talking about a hard drive. Not a solid state drive. Solid state drives have a different set of diagnostic tools because of the nature of their inner workings. This blog post is only for those needing to troubleshoot hard disk drive based PC performance issues.
Office 365 suite installs are updated regularly these days and sometimes things go wrong. Sometimes when it goes wrong, it is stuck with a cryptic bad image error involving the ApiClient.dll file. You can’t launch any Office apps. You can’t repair the install. You can’t even uninstall it without getting this error and it crashing. Sit back, relax. Here is how you fix it.
Exchange 2013 is a whole new beast when it comes to a stand alone Exchange server. A failed Exchange 2013 CU (Cumulative Update) can leave your Exchange server unresponsive to outside requests even though all Services are up and Powershell diagnostics are reporting everything working correctly. It leaves many Exchange Admins new to 2013 scratching their heads and attempting to restore from backup only to learn that a restore from backup does not work! What is this sorcery?! Stay calm. This is an easy fix and a lesson for new 2013/2016 Exchange admins that are used to the previous versions.
Migrating DHCP roles between Windows servers can be painful. I wanted to share my favorite method for doing this. I think it is the least difficult and the most effective way of getting your DHCP services moved to a newer Windows server with ZERO downtime. It isn’t perfect and it can fail. However, it works most of the time and when it does, you will feel like it was too easy!
This sounds really easy but it can be challenging if you have never done it before. Out of the box Windows does not want to run Powershell scripts in an automated fashion. There are some security hurdles put in place for this reason. This blog post will show you what you need to know to make Powershell task scheduling a breeze.
This will get much more intense through the remainder of the year as Microsoft ramps up the upgrades of Windows 7/8 computers joined to Active Directory domains. This post is all about what you need to know to block this upgrade from happening without having to manage Windows Update Services.
This is something that is super easy to accomplish and can have a big impact on your Group Policies management scope.
Microsoft updates are not to be trusted. A lot of you might hear that and say “Duh”, however, it hasn’t always been this bad. Recently, Microsoft has really hit a wall with security updates reeking havoc on systems and applications. The new Microsoft CEO has been actively pushing faster software development cycles. This has been a boon for them as it keeps developers and enterprises moving to refresh their software and hardware. This has also been a huge pain for the IT staff in charge of managing upgrades and updates.
Over the years I have seen so many approaches to migrating Windows file server shares to new servers. Most methods are valid and some are down right brilliant uses of native tools. I have an affinity for migrating shares in a specific way that does not utilize the native tools. It has worked really well for me over the years and I want to share it with all those out there that might need help with shares that are problematic.