vCenter 6.7 Resizing Disk Fails Invalid Operation for Device 0

 This one has been around for some time but now due to the data drive on my Exchange server getting closer and closer to full, I had to find a fix and here it is.  So simple and yet so hard to find on the web.

Checking the D: drive on the Exchange server showed the disk had a size of 150.254450347GB.  This disk had been restored from Datto at some point in the past and since that date this was the size showing.

Whenever attempting to expand the drive vCenter thew this error:  Invalid operation for device '0'.

I tried different sizes from adding just a few gigs to going all the way up to 200GB but getting the same error.

Ready for the fix?  You won't believe how easy it was.

1. Log into vCenter using the flex (Flash) client instead of the HTML 5 client.

2. Resize your disk successfully.

THAT'S IT!!  Can you believe it?  After all of these articles I read about changing the parameters on the VMX file, cloning the server, etc. etc. it turned out to be the behavior of the HTML 5 client.  Let's hope VMware fixes this in the next versions of vCenter before they fully remove the Flash functionality.

Good luck!

[SOLVED] Blank Screen after ECP Login Exchange 2013/2016

Issue:

After logging into the Exchange ECP with the correct credentials you get just a blank screen with no errors messages.  This will almost always happen if you remove a certificate using the certificates MMC or even sometimes if you remove one using the ECP.

Below is what you need to check to fix this problem:

Since this change is not reflected in the backend website you have to make sure that the Exchange ECP site is looking at the same certificate in both locations.

IIS Default Site SSL Certificate

IIS Back End SSL Certificate

The certificate choice in both of these locations have to match exactly then the issue is resolved.

Good luck!

Exchange 2013 Blank ECP/OWA Screen, Showing Event ID 15021 HttpEvent System Log

I hit this one today after switching out an expired UCC certificate on two Exchange 2013 servers in a DAG.  Both the ECP/OWA screens after login just went to a white page and never load.  The servers were both showing hundreds of ID 15021 in the system event log that says "An error occurred while using SSL configuration for endpoint 0.0.0.0:444.  The error status code is contained within the returned data."

Here's the steps to fix it:

1. Open a command prompt.

2. Enter netsh http show sslcert  This will show the certs on the server.  Copy and paste this information into notepad.  Copy this info "IP: port: 127.0.0.1:443".  Note that this information contains the certificate hash and the application ID.  This is the information needed.

3.  Run this command:  netsh http delete sslcert ipport=0.0.0.0:444

4.  Next run this command:  netsh http add sslcert ipport=0.0.0.0:444 certhash=123443211234321123 appid="{ab34k32abkr3252jsnekgljw}"  Make sure to include the quotes around the appid.

5. Finally restart the server.

This is all it takes to correct the issue.  Apparently this glitch is specific to Exchange 2013 as a web based ECP doesn't exist in the earlier versions.

Simple fix to a real inconvenience.

Good luck!

Certificate Not Showing After Importing Into Exchange 2013

I ran into this one today with two servers in a DAG.  This is caused by the certificate you're using not having the private key.  Here's how I fixed it:

Go to the 1st server -> Start -> Run -> MMC -> File -> Add/Remove Snap Ins -> Certificates -> Computer Certificates -> Local Computer

Browse to the personal certificate store, right click on the correct certificate, select All Tasks, and then Export.  Make sure here you choose "Export Private Key" and assign a password.  Click Next and then name the file and where you want to save it.  The file will have a .pfx extension.

From there on the 1st server inside ECP you can go to Servers -> Certificates -> Choose the server you want and then import the certificate.

Once this process is done just assign the services to the certificate (SMTP, POP, etc) and then restart the server if possible.  If not some say you can do an IISRESET from the command prompt and then you'll be good.

Good luck!

Adjust Exchange 2013 Send-Receive Message Size Limits

After setting up and Exchange 2013 SP1 server on Server 2012 R2 I ran into this small issue with a customer.  Even though I had all of the send/receive connectors in the ECP set at 100M, I was still hitting the default 10M attachment size limits.

Here's how to fix that by changing the Global Transport Settings: (short answer)

Check to see what the size limits currently are -
Get-TransportConfig | ft MaxSendSize, MaxReceiveSize

Once you know those sizes then here's the command to change them to what you need -
Set-TransportConfig –MaxSendSize 100MB –MaxReceiveSize 100MB

I know these sizes are a little large but just using them as an example.  Go ahead and bounce the Transport service just to be sure the settings take effect and you'll be good to go.

All of the other size limits can be set using the ECP under Mailflow and then Send Connectors and Receive Connectors.

Update:  I've just completed reading almost all of Mastering Microsoft Exchange Server 2013 .  This is an excellent read that will give you tons of insight into installing, maintaining, and mastering all there is to Exchange 2013.  I highly recommend you give the book a read.

Exchange 2013 Installation Step-by-Step Cheat Sheet

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.

- Remote Tools Admin Pack ( Install-WindowsFeature RSAT-ADDS )

- Windows Components ( Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, RSAT-Clustering-Mgmt, RSAT-Clustering-PowerShell, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation )

- Install Microsoft Unified Communications Managed API 4.0, Core Runtime 64-Bit

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 )

6.  Install Office 2010 Filter Packs - Version 2.0  http://go.microsoft.com/fwlink/?LinkID=191548 

7.  Install Office 2010 Filter Packs - Version 2.0 SP1  http://go.microsoft.com/fwlink/?LinkID=262358 

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.

Enjoy the read and good luck!

PST Capture Tool Setup and Use

Exchange PST Capture Use

There's a few things to do to get this to work properly.  Here's how mine is setup and I have no problems pulling PST files into Exchange 2010.

1. Windows 7 Professional on the domain.

2. Install .NET 4.5 framework.

3. Install Powershell 3.0.  It's part of the Windows Management Framework.  Download HERE.

4. Install Outlook 2010.  Make sure you use the 64-bit version.  Even if the PST file comes from a 32-bit machine.  This is because Exchange 2010 is 64-bit.

5. Run this command using Exchange Powershell  "New-ManagementRoleAssignment -Role "Mailbox Import Export" -User "PSTImportUser"

**If you do not run the Powershell command you will get ERROR OPENING MAILBOX**

6. Install PST Capture.

Once these things are done you are ready to pull the PST files into Exchange using PST Capture.

I highly recommend you go into Settings and remove the check box  beside "Create a subfolder for each PST file".  This will put all mail into the proper folder structure as what is inside the PST.

Also make one more edit under Non-mail items. Check both boxes so it will get their calendar, contacts, etc.

That's pretty much it.  The rest inside PST Import is pretty easy to understand and you're on your way to importing files as needed into a new or existing Exchange server.

Good luck!