Upgrading to Exchange 2013 SP1

I'm running windows server 2012 and exchange 2013 with CU3 I believe.

I was going to upgrade to Exchange SP1, but I read that it does a complete uninstall  and reinstall, so it seems a bit more complicated.

Does anyone know of any good websites that describe the process in detail, step by step.

I also noticed that CU7 has been released, If I upgrade to CU7 instead of SP1, I'm assuming that includes all previous CU's, so maybe that might be wiser?

Any thoughts or ideas?

Thanks.
DanNetwork EngineerAsked:
Who is Participating?
 
Simon Butler (Sembee)ConsultantCommented:
No prep is required, the setup tool will do that for you.
In most cases the installer will find the errors before it actually runs the installation and will stop - telling you to fix the problems. However if you have third party tools integrated with Exchange (AV, Anti Spam, Backup etc) you should stop and disable their services.

The installer will roll back up to a certain point, and it isn't unknown for the installation to fail afterwards. Unfortunately there is no way to know if that will happen. If it does happen, then the logs will tell you what the problem was. Once corrected, then running setup.exe should mean it resumes from where it stopped.

The most common cause of problems is actually a bad download of the file, corrected with a fresh download. However no way of knowing really, until you get an error.

Simon.
0
 
Satya PathakLead Technical ConsultantCommented:
0
 
DanNetwork EngineerAuthor Commented:
Thanks, actually, I only have win 2012, not R2.   Also, it looks like CU7 fixed a lot of bugs, so instead of upgradingto SP1, I think I should upgrade directly to CU7 instead.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
Simon Butler (Sembee)ConsultantCommented:
Skip SP1, go straight to CU7.
Service Pack 1 is basically CU4 with a new name.

While it does remove and reinstall the product, you don't have to do anything. The configuration is retained.
If you are in a single server/domain environment, just download CU7, double click to extract, then run setup.exe and let it get on with it. The installer will stop if an error is encountered.

Simon.
0
 
DanNetwork EngineerAuthor Commented:
Yes, I have only 1 Exchange serer and 1 domain.  So you're saying it's fairly straight forward?

So I don't need to do any AD or Schema preparation or anything?

What happens if there is an error, besides informing me there is an error, will it roll back automatically, because if it has to uninstall and reinstall from scratch, how will it reinstall my previous installation after it has already removed it?
0
 
DanNetwork EngineerAuthor Commented:
The install was successful, but a problem I have now is, when I try to log into the EAC, it doesn't work, I entered my credentials and it just spins and spins, I gave it like 20 minutes.  Any ideas?  I'll look through the logs now to see if I find anything.
0
 
DanNetwork EngineerAuthor Commented:
I have these Schannel errors:

An TLS 1.2 connection request was received from a remote client application, but none of the cipher suites supported by the client application are supported by the server. The SSL connection request has failed.

A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 40. The Windows SChannel error state is 1205.


Any ideas how to resolve?
0
 
DanNetwork EngineerAuthor Commented:
looks like this error was there prior to the upgrade as well, so It has nothing to do with the upgrade.
0
 
Simon Butler (Sembee)ConsultantCommented:
How far in to the login process for ECP do you get? Do you see any prompts at all?
The error you have posted and nothing on the screen would suggest the SSL certificate is corrupt.

Simon.
0
 
DanNetwork EngineerAuthor Commented:
what's strange is when logged into the server, the EAC works fine, it's only when I try to access the site from my PC that it doesn't work. I can ping the server, so the IP has not changed. If the site works on the physical server, could that still be a certificate issue?
On the physical server, it does say "certificate error", but it allows me to log in.
Shouldn't it do the same from my PC as well?
0
 
Simon Butler (Sembee)ConsultantCommented:
Can you get to IIS from a remote system?

So just https://host.example.com/ 

Simon.
0
 
DanNetwork EngineerAuthor Commented:
I can get to the EAC on the physical exchange serer.  Here's the website: https://localhost/ecp/
Then when I select "continue to this website",  the website changes to:
https://localhost/owa/auth/logon.aspx?replaceCurrent=1&url=https%3a%2f%2flocalhost%2fecp%2f

Then I enter my domain user and password and I can log in on the exchange server.

But from my PC, when I do the same thing, it doesn't work, it used to work before the upgrade.
0
 
Simon Butler (Sembee)ConsultantCommented:
That wasn't exactly what I meant.
On the server, that is fine, so don't worry about that.
However you need to establish whether it is a problem with IIS, accessing the web site, or Exchange.

By just browsing to the root of the server - you could try the iisstart.html page - so https://host.example.com/iistart.html you should get something back.
If you don't, then that suggests the issue is with IIS.
If you do, then it points at the problem being with Exchange.

Simon.
0
 
DanNetwork EngineerAuthor Commented:
So when I'm physically on the server, I go to:  https://elijah/iistart.html
and I'm prompted with the OWA login screen.
I enter my credentials and I get this:

404
can't find page :-(

The page you're looking for couldn't be found on the server.

More details...

 refresh the page
0
 
DanNetwork EngineerAuthor Commented:
when I click on more details, it shows me this:
X-ClientId: BLBZ - ZIXL - E0MY - KXCTXRLOA
X-FEServer: ELIJAH
Date: 3/10/2015 6:32:17 PM
0
 
DanNetwork EngineerAuthor Commented:
Then I hit "refresh the page" and it log me into OWA
0
 
DanNetwork EngineerAuthor Commented:
But I closed the browser and tried again and it's just spinning and spinning thinking
0
 
Simon Butler (Sembee)ConsultantCommented:
You haven't put any kind of redirect on the server that could be getting in the way?
The page I have indicated should physically exist on C:\InetPut\wwwroot\iisstart.html (or it might be htm).

Don't do the test on the server, as that isn't valid. You need to do it from a workstation.

Simon.
0
 
DanNetwork EngineerAuthor Commented:
so from my own workstation, when I browse to:  https://elijah/inetpub/wwwroot/iistart.html

I get this:

404 - File or directory not found.
The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable
0
 
Simon Butler (Sembee)ConsultantCommented:
Again, that wasn't exactly what I wanted you to do, but it proves that IIS is working correctly.

The physical path is at c:\intepub\wwwroot\iisstart.htm

However when you browse to the server it is at https://host/iisstart.htm

The next thing you need to do is check the bindings in IIS manager are correct. You should have a binding on the default web site for both 127.0.0.1 and a wildcard for HTTPS, with a certificate connected.

Simon.
0
 
DanNetwork EngineerAuthor Commented:
here's a picture of my bindings, not exactly sure what should be there or not.
bindings
I think though the problem is with SSL settings, of require SSL, or those kind of settings.

For example, I went to IIS, default website, SSL settings and removed the "require SSL" option.
Then in IIS, under HHTP redirect, I removed the option "redirect all requests to exact destination"

And now, OWA works from my computer, but ECP does not work.  I get to the login page, but when I get an error
"the webpage cannot be found"

Both ECP and OWA still work on the physical server though.
0
 
DanNetwork EngineerAuthor Commented:
figured out the problem, needed to stop the redirect for ecp and owa in IIS.  then iisreset and it's working now.

Thanks for your help.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.