Exchange 2016 Install Issue
-
Previously had an Exchange 2013 and another Exchange 2016 Exchange Server in this environment. Was unable to install them, due to encryption attack. Was able to roll-back AD, and delete what I think was all the Exchange metadata via ADSIEdit, ADUC, and RegEdit. Running the installer prompt me with the following error.
PS G:> .\Setup /PrepareAD /IAcceptExchangeServerLicenseTerms /OrganizationName:ORG
Microsoft Exchange Server 2016 Cumulative Update 15 Unattended Setup
Copying Files...
File copy complete. Setup will now collect additional information needed for installation.Languages
Mailbox role: Transport service
Mailbox role: Client Access service
Mailbox role: Unified Messaging service
Mailbox role: Mailbox service
Mailbox role: Front End Transport service
Mailbox role: Client Access Front End servicePerforming Microsoft Exchange Server Prerequisite Check
Configuring Prerequisites COMPLETED Prerequisite Analysis 100%Setup will prepare the organization for Exchange Server 2016 by using 'Setup /PrepareAD'. No Exchange Server 2013 roles
have been detected in this topology. After this operation, you will not be able to install any Exchange Server 2013
roles.
For more information, visit: https://docs.microsoft.com/Exchange/plan-and-deploy/deployment-ref/readiness-checks?view=ex
chserver-2016Setup will prepare the organization for Exchange Server 2016 by using 'Setup /PrepareAD'. No Exchange Server 2010 roles
have been detected in this topology. After this operation, you will not be able to install any Exchange Server 2010
roles.
For more information, visit: https://docs.microsoft.com/Exchange/plan-and-deploy/deployment-ref/readiness-checks?view=ex
chserver-2016Configuring Microsoft Exchange Server
Organization Preparation COMPLETED Language Configuration COMPLETED Mailbox role: Transport service 100%The following error was generated when "$error.Clear();
Set-LocalPermissions -Feature:"Bridgehead"" was run: "System.ArgumentException: The directory "C:\Windows\Temp\ExchangeSetup\ClientAccess\PowerShell" does not exist.
at
Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
at
Microsoft.Exchange.Management.Deployment.SetLocalPermissions.InternalProcessRecord()
at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__91_1()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean
terminatePipelineIfFailed)".
As a joke (that I secretly hoped worked) I tried copying the powershell.exe from System32 folder and pasting it into this folder. That didn't work. A bit of reading tells me this may be a HubTransport role issue, but I've checked and re-installed with:
.\Setup /Role:HubTransport /IAcceptExchangeServerLicenseTerms
I've deleted watermarks via regedit, metadata from AD, re-ran .\Setup /PrepareAD /IAcceptExchangeServerLicenseTerms, but nothing is getting me past this point.
Additionally, Add/Remove Programs >Modify prompts me: "All Available Exchange Roles are installed. No Additional install action available."
Add/Remove Programs>Uninstall: "An incomplete installation was detected. Run setup to complete Exchange installation."I'm thinking of a server wipe, and reinstall, but I've done that once already and am at a loss how to move forward.
-
@G-I-Jones said in Exchange 2016 Install Issue:
I'm thinking of a server wipe, and reinstall, but I've done that once already and am at a loss how to move forward.
You've nuked this server and reloaded it from the ground up and are unable to install Exchange?
-
This post is deleted! -
@DustinB3403 said in Exchange 2016 Install Issue:
@G-I-Jones said in Exchange 2016 Install Issue:
I'm thinking of a server wipe, and reinstall, but I've done that once already and am at a loss how to move forward.
You've nuked this server and reloaded it from the ground up and are unable to install Exchange?
@DustinB3403 Correct. However, there was a lot of trying different things involved, so I may have missed something the first time. If nothing jumps out to anyone with more Exchange experience than me, then that's the obvious path.
-
@G-I-Jones I think you are misunderstanding what a nuke from space means.
Format the drives and reinstall the operating system and then required server roles.
-
Of course, if you have no backup of the emails and it resides purely on this 2016 host you're already up the creek.
-
@DustinB3403 said in Exchange 2016 Install Issue:
@G-I-Jones I think you are misunderstanding what a nuke from space means.
Format the drives and reinstall the operating system and then required server roles.
No, I understand. That's what I did. As I said though, there were previous Exchange in this environment. I may have forgot a smidge of Metadata the first time around.
-
@G-I-Jones said in Exchange 2016 Install Issue:
@DustinB3403 said in Exchange 2016 Install Issue:
@G-I-Jones I think you are misunderstanding what a nuke from space means.
Format the drives and reinstall the operating system and then required server roles.
No, I understand. That's what I did. As I said though, there were previous Exchange in this environment. I may have forgot a smidge of Metadata the first time around.
Oh from the older server. Gotcha.
-
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.
-
@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 (like some custom card that couldn't be passed to a VM) would you then consider a physical installation.
-
@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.
-
@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.
I second @DustinB3403 - virtualize 99.999% of everything except for something super special or requires direct access to hardware (USB keys, specific internal PCI cards, etc.)
Good luck with the new PERC. You shouldn't see any issues. I've been messing with my R440 all runs fantastic (SMB and NFS shares).
Also, just in case as I don't remember at the moment, make sure to use the Dell OEM ESXi 6.7 U2 or U3 iso.
-
@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?
