I ran into this issue today when trying to extend out the drive size on a data drive on our primary file server. After expanding the virtual disk in VMware, I brought up computer management (compmgmt.exe if you want to go command line quicker).
I expanded out the disk and immediately noticed that explorer didn't reflect that change after a refresh. Also, disk management could no longer access the disk to make any edits. I restarted the virtual disk service with no success. A restart also proved futile.
MAKE A BACKUP BEFORE RUNNING THESE COMMANDS!
After some quick research, here is the fix. Use DISKPART from an elevated command prompt. Just follow the commands below and choose the proper disk on your VM. After running the command, a quick refresh of explorer now shows the correct size.
I ran into this issue today while trying to run the Microsoft BPA (Best Practices Analyzer) 2.3 on a Windows Server 2012 R2 box with IIS 8.5 installed. Below is the full text of the error:
"Unable to scan IIS status - The IIS Common Files are not installed on the local computer. Refer to the system requirements list under the Microsoft Business Security Analyzer Help."
Here's the short fix:
Go back into Roles and under Web Server (IIS) and install IIS 6 Management Compatibility-->IIS 6 Metabase Compatibility.
Apparently from what I find this is a Windows Server 2003 item that hasn't been updated in the current server platform documentation on the MBSA to reflect the need for this additional set of files.
The longer explanation is that in order for the MBSA to be able to scan IIS properly it needs to have IIS 6 Management Compatibility turned on and more specifically the IIS 6 Metabase Compatibility.
I hope this one helps as it took me quite a bit of research to run this issue down.
Powershell was released some time ago but it feels to me like it was just yesterday. Part of that is because as time moves on Microsoft is adding more and more features. With Windows Server 2012 R2 now in full effect and quite stable, it's clear PowerShell is taking over as the primary Windows scripting language of choice.
I am a firm believer that everything in Windows Server 2012 R2 that can be done in the GUI can also be done in PowerShell. Case in point, I just upgraded one of our network Domain Controllers from Windows Server 2012 to Windows Server 2012 R2.
Since this server was a DC the first thing I needed to do before the upgrade was to ensure the server was not running any of the five FSMO roles on our network. To do this I ran the following command in PS on the server.
netdom query FSMO
This will return which DC or DCs on your network contain the FSMO roles. Since the server I was upgrading had none then I had none to move before the upgrade. Once the upgrade had completed I now wanted to make sure the newest DC on the network had the roles while others were being upgraded.
To transfer all five roles you can simply run this command in PS:
For reference the command line syntax replaces the role number for the full name of the FSMO role.
PDC Emulator = 0
RID Master = 1
Infrastructure Master = 2
Schema Master = 3
Domain Naming Master = 4
If you find yourself in a situation where the DC you want to transfer roles from is offline and cannot be brought back then you'll need to seize the roles. Here's the command for that:
Move-ADDirectoryServerOperationMasterRole -Identity “Target_DC_name” –OperationMasterRole 0,1,2,3,4 - Force
Finally to transfer or seize just one role you would run the exact same command and just use the number of the role you need to move. These commands work on Server 2008 R2 and up or Windows 7 with the RSAT (Remote Server Administration Tools) installed.
I don't find myself moving FSMO roles often but when I need to this is much easier than using the GUI. A great reference on PowerShell is Learn Windows PowerShell 3 in a Month of Lunches. It's a great read and has tons of great PowerShell information.
Ok so I've setup a new Exchange 2013 server for a customer and got it installed with no errors. These instructions pertain to installation on Windows Server 2012/2012R2. I have condensed it down to make sense. We all know TechNet instructions look like they were written by a lawyer. I hope this helps with your install. Good luck.
1. Install all OS updates
2. Install all the following prereqs
- .NET Framework (already on Server 2012R2). Just use the server manager to install this as a Feature.
3. Extend the AD schema. Use Command Prompt to drive letter with Exchange ( setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms ). When setup completes allow some time for AD replication to complete across all DCs.
4. Prepare AD for Exchange. Use Command Prompt to drive letter with Exchange ( Setup.exe /PrepareAD /OrganizationName:"" /IAcceptExchangeServerLicenseTerms )
5. Prepare all domains for Exchange 2013. Use Command Prompt to drive letter with Exchange ( Setup.exe /PrepareAllDomains /IAcceptExchangeServerLicenseTerms )
8. Run setup.exe. Follow prompts and allow wizard to complete install.
That's pretty much all there is to it to get it installed.
If you want more information on detailed installation, configuration after install, and maintaining then I highly recommend you read Mastering Microsoft Exchange Server 2013. I did and it has been a tremendous reference point for me now that Exchange 2013 deployments are becoming more common for me.
. I did and it has been a tremendous reference point for me now that Exchange 2013 deployments are becoming more common for me.