What am I missing here (Exchange 2010 on server 2012r2)
-
Hey guys.
I feel like I'm missing something really stupid.
Just installed Exchange 2010 on a Server 2012r2 box (more for messing around than anything)
I've installed before, so I feel like I just missed a stupid step but cant seem to find my mistake.
After fresh install I essentially cant expand to see any of my options, anyone know which direction to point me in minus re-doing it from step 1
Thanks
-
I thought Exchange had to be at a specific SP before it would work on 2012(r2). Are you on such SP?
-
@Dashrender
Definitely not up to date, I'll start updating right now thanks. -
Any reason you're using a three version old copy of Exchange?
-
@Dashrender
Haha not really no, best answer I can honestly give you.... I had the ISO downloaded already.Guess this is the kick in the butt I needed to download a new ISO
-
Test environment?
yeah I would never start with something so old.. maybe go with Exchange 2013, but even that.. nah.. 2016 has been our for 6 or so months..
-
I think you need upgrade Exchange 2010 to SP3 RU5 to execute it in W2012R2
-
@iroal
Ya I ended up upgrading which just honestly screwed everything up.
Had to manually go in and remove the database, so that I could uninstall, so that I could start installing 2013....gah -
@Dashrender
2016 eh...hmm dont know if I'm ready to take that jump =/
But ya, gonna jump on the 2013 board atleast, I'll think about 2016Thanks
-
What's to be worried about with 2016?
-
Personally find 2013 a pain vs 2010 so I can only assume (having looked into it less than 3 minutes) that its less GUI and more powershell, which honestly I'm not the hugest fan of.
-
That may be true, but it's also the future.
I'm currently still on 2010 and need to move. I plan to push to O365 this summer, so I'll have to get used to that one way or the other.
-
@Sparkum 2013 uses a web based gui now. Of course you can do everything with powershell as well.
-
Haha ya good point.
We actually went the opposite route at work and pulled out of O365 after about a year.
-
@brianlittlejohn
Ya for sure there is still a gui, you can just do less in the gui in 2013 vs 2010 -
@Dashrender said:
That may be true, but it's also the future.
I'm currently still on 2010 and need to move. I plan to push to O365 this summer, so I'll have to get used to that one way or the other.
I'm in the same position. Doing research on cloud based services, software based VPN w/ Azure, O365, ODFB and maybe bitium for SSO or something. I still don't know a lot just in general so I'm trying to study about it but I'm going through a masters program right now in addition to working full time.
-
@Sparkum said:
Haha ya good point.
We actually went the opposite route at work and pulled out of O365 after about a year.
How come?
-
Honestly it just 100% came down to price,
We only had a small portion of users on O365 (20-30 if I remember) and IMO we probably chose the wrong plan for how we operate.
But the simpe math of $12.50 * 30 = $375/month (Not sure if that was the exact pricing just googled in quickly) * 12 =$4500/year
Just didnt seem worth it to us.
If we had done the $5 plan maybe, but for what we are doing in house works just fine.
-
@Sparkum said:
Honestly it just 100% came down to price,
We only had a small portion of users on O365 (20-30 if I remember) and IMO we probably chose the wrong plan for how we operate.
But the simpe math of $12.50 * 30 = $375/month (Not sure if that was the exact pricing just googled in quickly) * 12 =$4500/year
Just didnt seem worth it to us.
If we had done the $5 plan maybe, but for what we are doing in house works just fine.
Even if you calculate the cost the server and the man hours you dedicate to maintain it?
-
Server already existed so its a blind cost (sort of speaking) we just added another virtual, and honestly we haven't touched it since it went into production.
Other than adding a user here or there, but we would be doing the same process with O365 as we would in house for thatSo I would say as of today we are definitely ahead.