In this article, I go over how to get rid of Orphaned Shadow Copies that do not get cleared out by issuing: vssadmin shadows delete /all Steps to clear out all orphaned shadow copies vssadmin shadows delete /all vssadmin shadows list verify orphaned shadow copies still exist Use the following command to resize shadow storage, consequently, clears out any shadow copies on that drive vssadmin Resize ShadowStorage /For=C: /On=C: /MaxSize=300MB Note: Repeat this for each drive with orphaned shadow copies Afterward, do a shadows list to verify the shadow copies have been cleared out This process can take a very long time for large drives with a lot of shadow copies.
Use the following from an Elevated Powershell Prompt to force active directory sync to your O365 admin portal. You will be performing this on the server where Azure AD Sync is installed, however, when running this command you will need to wait 5 minutes before checking your portal to verify it is working. In larger environments, this can take a longer time. Import-Module “C:\Program Files\Microsoft Azure AD Sync\Bin\ADSync\ADSync.psd1”<br /> Start-ADSyncSyncCycle -PolicyType Delta
Run the following commands if you are running low on C: drive space. Generally, this is caused by windows updates and you need to clear WinSxS free space. Do this in your PowerShell prompt and you will free up a substantial amount of space. Please Note: You have to run updates on Windows Server 2008 if you are far behind and these commands don’t exist! MASTER CLEANUP: (Run this First)
This article explains how to fix the “Target account name is incorrect” error you are getting on your domain controllers. This usually stems from a system administrator doing a snapshot revert on the Domain Controller which messes up the KDC service and domain replication. It also can happen if you had a DC offline for a long time 30+ days. Commands Stop and disable the Key Distribution Center (KDC) service on the troubled domain controller
I was recently installing and configuring a new server with 32 processors and installing server 2008 Standard and Exchange 2007 SP1 Standard. During installation I received the following error: HRESULT E_FAIL has been returned from a call to a COM component. After finding a Knowledge-base article from Microsoft, I discovered Exchange 2007 SP1 doesn’t support installation on a server with more than 24 processors but is perfectly fine updating and running on a server with more than 24 processors.
When installing a program I kept getting the prompt below that an update is pending. Even after a restart, this would display, therefore I changed these registry keys to clear up the issue. Microsoft Server setup cannot continue because a restart from a previous installation or update is pending. The Fix for an update is pending The following Registry keys control this error message. If you have rebooted and are still experiencing this issue, clear out these keys and relaunch your installer.
This is a workaround for EBS Administration Console that can no longer launch or has errors on launch. Consequently, Microsoft put the Licensing in this Console only, and no other GUI exists for it. However, that is why Powershell exists, and here are the commands to manage all your CALs in your network. Step-by-Step Guide Open Powershell on Management Server. (Start ->All Programs -> Windows Powershell 1.0) Type this at command prompt: Add-PsSnapin Microsoft.
If you had the misfortune of installing Exchange on Primary Domain Controller you will experience some pain when doing a reboot. Typically it will take 10-15 minutes before it restarts and up to 30 minutes to start the Microsoft Exchange Information Store. Consequently, what is really happening in the background is the IS service is being terminated incorrectly on shutdown and the store is left in a “DIRTY” shutdown state. This is very bad on several levels and can cause the Store to corrupt and not start at all, which can be catastrophic.
By default the standard outlk12.adm templates do not come with a configuration of Outlook Anywhere. You can configure the “Configure Outlook Anywhere user interface options” options to disable or grey out the settings. However, this DOES NOT disable Outlook anywhere, just user interaction with it. You will need to download a new administrative template that Microsoft released in this hotfix. If you don’t like reading Microsoft’s wonderful support site instructions or Microsoft changes their support site after this blog post, here is the file and instructions paraphrased.
Using Group Policy Objects can be a huge time saver, but if used improperly can be a big headache. Once you’ve messed around with GPO settings enough, you quickly figure out that you need to create new GPOs for specific programs, events, etc… that are not all in one GPO. This gives you a lot more flexibility and makes it very easy to track down troublesome GPO related issues when done properly.