Exchange Environment - Lab
-
@stuartjordan said in Exchange Environment - Lab:
At the end of the day, if the op want's to learn exchange that's up to him. This is a forum where we can give constructive criticism but, there is also no need to go on about it and give a little help instead. Just a thought??
At this point I was just trying to let dave know of the typical MO around here.
-
As for the OP's error? No clue - but the person who asked if he actually had AD setup or not - that's a great starting place.
Has the OP looked at all of the prerequisites and ensured they are all in place before trying to install Exchange?
-
@dashrender said in Exchange Environment - Lab:
@stuartjordan said in Exchange Environment - Lab:
At the end of the day, if the op want's to learn exchange that's up to him. This is a forum where we can give constructive criticism but, there is also no need to go on about it and give a little help instead. Just a thought??
At this point I was just trying to let dave know of the typical MO around here.
Yes, I understand that, in summary, it is the unified intent of the original initiative of SAM (and others) over at Spiceworks, before the banning and exodus. Given what that place was/still is, I guess I don't blame you all for the general tone and approach - but gottdamn, most the new posters here might be confused but they are friendly and want to learn. No need to push them away with rudeness.
-
@dashrender said in Exchange Environment - Lab:
As for the OP's error? No clue - but the person who asked if he actually had AD setup or not - that's a great starting place.
Has the OP looked at all of the prerequisites and ensured they are all in place before trying to install Exchange?
We're beyond that now. I answered his issue with why it happened, what happened, and how to fix it here.
-
@obsolesce said in Exchange Environment - Lab:
@dashrender said in Exchange Environment - Lab:
As for the OP's error? No clue - but the person who asked if he actually had AD setup or not - that's a great starting place.
Has the OP looked at all of the prerequisites and ensured they are all in place before trying to install Exchange?
We're beyond that now. I answered his issue with why it happened, what happened, and how to fix it here.
Yeah but if he doesn't have AD set up, then he's gonna have a hard time despite running the setup.exe properly
-
@obsolesce said in Exchange Environment - Lab:
@laksh1999 said in Exchange Environment - Lab:
Hi Team,
I am trying to create a Exchange 2016 in Microsoft 2016 server DataCenter Evaluation version.I am trying to do this from my virtualbox application.Any one have followed this lab setup before ?
Followed Link : https://www.prajwaldesai.com/step-by-step-guide-to-install-exchange-server-2016/
Your whole issue here is that you didn't follow the instructions.
You first need to mount the Exchange Server 2016 installation Media.
Then from the location of where your media is mounted, you run that command.
What you are doing, is blindly running commands from where ever. You aren't running the command from the proper directory, which only you can know where you have mounted or extracted the Exchange Server 2016 media.
This is actually pretty hilarious though.
-
@dave247 said in Exchange Environment - Lab:
@obsolesce said in Exchange Environment - Lab:
@dashrender said in Exchange Environment - Lab:
As for the OP's error? No clue - but the person who asked if he actually had AD setup or not - that's a great starting place.
Has the OP looked at all of the prerequisites and ensured they are all in place before trying to install Exchange?
We're beyond that now. I answered his issue with why it happened, what happened, and how to fix it here.
Yeah but if he doesn't have AD set up, then he's gonna have a hard time despite running the setup.exe properly
I was addressing his error in his very first post. How far back do you go regarding prerequisites that has nothing to do with the error posted? I mean, should we verify he has an active network connection as well? The direct cause of the error is obvious, let's get past that first, and see what happens next. I mean, the whole point of the command is to extend the AD schema... if he doesn't have AD, then no guide will help him at this point, as it's also insanely clear in the guide he's following.
-
Have you made sure you have downloaded the latest CU for that version of exchange as well otherwise it will all go to shit. Any reason why you don't want to trial 2019 when it's up to CU10?
-
@obsolesce said in Exchange Environment - Lab:
@dave247 said in Exchange Environment - Lab:
@obsolesce said in Exchange Environment - Lab:
@dashrender said in Exchange Environment - Lab:
As for the OP's error? No clue - but the person who asked if he actually had AD setup or not - that's a great starting place.
Has the OP looked at all of the prerequisites and ensured they are all in place before trying to install Exchange?
We're beyond that now. I answered his issue with why it happened, what happened, and how to fix it here.
Yeah but if he doesn't have AD set up, then he's gonna have a hard time despite running the setup.exe properly
I was addressing his error in his very first post. How far back do you go regarding prerequisites that has nothing to do with the error posted? I mean, should we verify he has an active network connection as well? The direct cause of the error is obvious, let's get past that first, and see what happens next. I mean, the whole point of the command is to extend the AD schema... if he doesn't have AD, then no guide will help him at this point, as it's also insanely clear in the guide he's following.
Ah yes, I see waht you're saying. I should have first asked him if his home has electricity. Then move on to Powershell. Yes.
