Here is my experience Installing Exchange 2013 preview on Windows 2012 Server.
The first install was a flop. I’m not sure what went wrong, but I’ll post back if I figure it out.
This is an Exchange server with both CAS and MBX role installed.
Here is the article I followed.
In Windows 2012 server virtual server, make sure the server window is in focus. Hit the windows key.
Windows-Q will search apps.
You’ll also probably want the enable Desktop Experience is under Features\User Interface and Infrastructure for the snipping tool.
And here are some help key strokes
Windows key = Ctrl+Esc
In powershell, run the following
Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, 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
For Exchange 2013 Preview, you must also uninstall Microsoft Visual C++ 11 Beta Redistributable (x64). This must be done after you’ve installed UCMA, but before you run Exchange 2013 Preview Setup. To uninstall Microsoft Visual C++ 11 Beta Redistributable (x64), do the following:
Open Control Panel > Programs and Features.
Select Visual C++ 11 Beta Redistributable (x64) – 11.0.50531 and then click Uninstall.
In Microsoft Visual C++ 11 Beta setup, click Uninstall.
When Microsoft Visual C++ 11 Beta is uninstalled, click Close.
After you’ve installed the operating system roles and features, install the following software in the order shown:
From a Command Prompt run
setup /PrepareSchema or setup /ps
From a Command Prompt window, run the following command.
setup /PrepareAD [/OrganizationName:<organization name>] or setup /p [/on:<organization name>]
Run setup /PrepareDomain or setup /pd to prepare the local domain
run setup /PrepareAllDomains
I only had one at this time so setup /pd worked just fine
So now let’s run setup
Now go to https:/localhost/ecp
But for some reason I can’t yet explain, this wouldn’t work. I’d get HTTP 500 errors every time I tried to open ECP.
The fix seemed to be going to the domain controller and making a user, and adding that user to the domain admins group.
Then I ran the enable-mailbox for that user. The it worked.
Then, as if I didn’t know better to start with, I added the user to the Exchange organizational management group. Then the Exchange tools popped up.
The reason: I had trouble with the first mailbox server so I just shut it off. That’s where the mailbox for the administrator was.