Exchange 2016 Install Issue
-
@G-I-Jones said in Exchange 2016 Install Issue:
@DustinB3403 said in Exchange 2016 Install Issue:
@G-I-Jones said in Exchange 2016 Install Issue:
Since I've got you all here. What are your thoughts on Exchange server built in Esxi? I was told be someone with more experience than me recently that this is a bad idea, but wasn't given much insight into why or how.
The rule of thumb is to virtualize everything, and unless you have a really very good reason
I thought that to be the case. Thanks for that. Just got that PERC H730P installed. I'm going to try again with a VM I think.
you mean you were not making this a VM? crazy man, crazy!
-
you mean you were not making this a VM? crazy man, crazy!
Nah man, remember I was waiting on the H730P? I was hoping to get up a bare metal in the meantime, but that didn't work out.
-
Just so I understand the environment.
You had/have
AD server - still have
Exchange 2013 - now gone
Exchange 2016 - now goneIs that right?
Assuming it is, now you're trying to add a new Exchange server back into this environment, on a new server, so you'll end up with
AD server
Exchange serverQuestion - do you still have the old data from Exchange 2013/2016? that you need to put into this new Exchange server?
-
@G-I-Jones said in Exchange 2016 Install Issue:
you mean you were not making this a VM? crazy man, crazy!
Nah man, remember I was waiting on the H730P? I was hoping to get up a bare metal in the meantime, but that didn't work out.
Sure, but even a temp box should still be a VM. No reason to really ever make it bare metal.
If I was building a temp Exchange box, I'd slap whatever hypervisor on that box first - make a VM, install windows Server and then Exchange... no different than the ultimate location where I want to host Exchange. Do it this way makes it cake to move to the new hardware - just shut down the VM, transfer it over, import if needed, start it up and go! no worrying about doing a P2V...
-
@Dashrender said in Exchange 2016 Install Issue:
@G-I-Jones said in Exchange 2016 Install Issue:
you mean you were not making this a VM? crazy man, crazy!
Nah man, remember I was waiting on the H730P? I was hoping to get up a bare metal in the meantime, but that didn't work out.
Sure, but even a temp box should still be a VM. No reason to really ever make it bare metal.
If I was building a temp Exchange box, I'd slap whatever hypervisor on that box first - make a VM, install windows Server and then Exchange... no different than the ultimate location where I want to host Exchange. Do it this way makes it cake to move to the new hardware - just shut down the VM, transfer it over, import if needed, start it up and go! no worrying about doing a P2V...
They have identical PERC Adapters, lol.
-
@G-I-Jones said in Exchange 2016 Install Issue:
@Dashrender said in Exchange 2016 Install Issue:
@G-I-Jones said in Exchange 2016 Install Issue:
you mean you were not making this a VM? crazy man, crazy!
Nah man, remember I was waiting on the H730P? I was hoping to get up a bare metal in the meantime, but that didn't work out.
Sure, but even a temp box should still be a VM. No reason to really ever make it bare metal.
If I was building a temp Exchange box, I'd slap whatever hypervisor on that box first - make a VM, install windows Server and then Exchange... no different than the ultimate location where I want to host Exchange. Do it this way makes it cake to move to the new hardware - just shut down the VM, transfer it over, import if needed, start it up and go! no worrying about doing a P2V...
They have identical PERC Adapters, lol.
that doesn't really matter - it could have been a desktop for the temp machine - assuming it had enough storage for your needs
this is because you're migrating the VM, which is mostly if not entirely, hardware agnostic... -
@Dashrender said in Exchange 2016 Install Issue:
Just so I understand the environment.
You had/have
AD server - still have
Exchange 2013 - now gone
Exchange 2016 - now goneIs that right?
Assuming it is, now you're trying to add a new Exchange server back into this environment, on a new server, so you'll end up with
AD server
Exchange serverQuestion - do you still have the old data from Exchange 2013/2016? that you need to put into this new Exchange server?
I don't. We're considering it a complete loss. Silver lining is we'll get the funding to protect ourselves now, and the opportunity to build everything into VM's.
-
@G-I-Jones said in Exchange 2016 Install Issue:
@Dashrender said in Exchange 2016 Install Issue:
Just so I understand the environment.
You had/have
AD server - still have
Exchange 2013 - now gone
Exchange 2016 - now goneIs that right?
Assuming it is, now you're trying to add a new Exchange server back into this environment, on a new server, so you'll end up with
AD server
Exchange serverQuestion - do you still have the old data from Exchange 2013/2016? that you need to put into this new Exchange server?
I don't. We're considering it a complete loss. Silver lining is we'll get the funding to protect ourselves now, and the opportunity to build everything into VM's.
Is there a reason you are returning to onsite Exchange instead of moving to O365 or some other hosted solution?
-
Is there a reason you are returning to onsite Exchange instead of moving to O365 or some other hosted solution?
Money.
-
@G-I-Jones said in Exchange 2016 Install Issue:
Is there a reason you are returning to onsite Exchange instead of moving to O365 or some other hosted solution?
Money.
As in you already have the Exchange licenses, so it's mostly a non cash setup situation?
-
How many users do you have? how many workstations? How many file shares - are permissions used a lot in those file shares?
perhaps, it would be worthwhile to start your AD all over again?
-
As in you already have the Exchange licenses, so it's mostly a non cash setup situation?
Nail on the head.
-
@Dashrender said in Exchange 2016 Install Issue:
How many users do you have? how many workstations? How many file shares - are permissions used a lot in those file shares?
perhaps, it would be worthwhile to start your AD all over again?
I'm gonna power through this build first and see how it goes.
-
@G-I-Jones said in Exchange 2016 Install Issue:
@Dashrender said in Exchange 2016 Install Issue:
Just so I understand the environment.
You had/have
AD server - still have
Exchange 2013 - now gone
Exchange 2016 - now goneIs that right?
Assuming it is, now you're trying to add a new Exchange server back into this environment, on a new server, so you'll end up with
AD server
Exchange serverQuestion - do you still have the old data from Exchange 2013/2016? that you need to put into this new Exchange server?
I don't. We're considering it a complete loss. Silver lining is we'll get the funding to protect ourselves now, and the opportunity to build everything into VM's.
So why not setup a fully new AD domain and reinstall Exchange there then? It would be the best course of action as it will be clean.
-
@dbeato We may have to, but like I said I'm going to power through this build first, and we'll see how it goes.
-
@G-I-Jones said in Exchange 2016 Install Issue:
@dbeato We may have to, but like I said I'm going to power through this build first, and we'll see how it goes.
Do it side by side. Setup another AD in another Server and work through it. I bet the new one will go much faster.
-
@dbeato My plan is to just roll back the snapshot of the AD we have now to when we first built it pre-Exchange. Giving me a blank canvas if it comes to that.
-
@G-I-Jones said in Exchange 2016 Install Issue:
@dbeato My plan is to just roll back the snapshot of the AD we have now to when we first built it pre-Exchange. Giving me a fresh canvas if it comes to that.
This is a horrible idea. Rolling back AD is almost never a good idea.
-
@JaredBusch please elaborate.
-
@JaredBusch said in Exchange 2016 Install Issue:
@G-I-Jones said in Exchange 2016 Install Issue:
@dbeato My plan is to just roll back the snapshot of the AD we have now to when we first built it pre-Exchange. Giving me a fresh canvas if it comes to that.
This is a horrible idea. Rolling back AD is almost never a good idea.
OMG - THIS, one million times this!
