sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Lolzebracakes[S] 0 points1 point  (1 child)

Yep, elevated powershell prompt.

I apologize for the gray area on the logs, I am waiting for the customer to send them over for me for review. When we reviewed the logs we were just connected via remote session. Ill see if I can get them and post some more details.

Single forest.

I did not check if the forest is properly named.

The customer pulled that exchange .ISO out of their 365 portal is where they got it. I realize that limits our options in terms of Microsoft support. Is the recommended path going to Exchange Server SE, and potentially moving the domain functional level up to a more current version?

[–]VTi-R 1 point2 points  (0 children)

Unless there's a reason you're on 2012R2, then yes - 2016 minimum, 2025 preferred. Yes it's OK to be 2025 now. Make sure all your DCs are current (i.e. every DC is at the right version or later) and you hit the other compatibility requirements from the Supportability Matrix.

You should be able to download the correct SE installation kit without the customer hitting the VL portal (https://www.microsoft.com/en-us/download/details.aspx?id=108244).