Exchange Environment - Lab
-
@laksh1999 - From the looks of it, you are trying to run setup.exe from C:\Windows\System32. Fix the path to wherever you installation media is located.
ex: D:\setup.exe
-
@syko24 said in Exchange Environment - Lab:
@laksh1999 - From the looks of it, you are trying to run setup.exe from C:\Windows\System32. Fix the path to wherever you installation media is located.
ex: D:\setup.exe
Tried from D drive got this error
-
@laksh1999 said in Exchange Environment - Lab:
@syko24 said in Exchange Environment - Lab:
@laksh1999 - From the looks of it, you are trying to run setup.exe from C:\Windows\System32. Fix the path to wherever you installation media is located.
ex: D:\setup.exe
Tried from D drive got this error
make sure you spelled everything correctly.
you're pictures are to small for my horrible eyesight to read.
-
@dashrender said in Exchange Environment - Lab:
@laksh1999 said in Exchange Environment - Lab:
@syko24 said in Exchange Environment - Lab:
@laksh1999 - From the looks of it, you are trying to run setup.exe from C:\Windows\System32. Fix the path to wherever you installation media is located.
ex: D:\setup.exe
Tried from D drive got this error
make sure you spelled everything correctly.
you're pictures are to small for my horrible eyesight to read.
Tried this
.\setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms -
@laksh1999 said in Exchange Environment - Lab:
@dashrender said in Exchange Environment - Lab:
@laksh1999 said in Exchange Environment - Lab:
@syko24 said in Exchange Environment - Lab:
@laksh1999 - From the looks of it, you are trying to run setup.exe from C:\Windows\System32. Fix the path to wherever you installation media is located.
ex: D:\setup.exe
Tried from D drive got this error
make sure you spelled everything correctly.
you're pictures are to small for my horrible eyesight to read.
Tried this
.\setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTermsYour posted instructions say to run Command Prompt as Administrator. It looks like you are using PowerShell. Not sure if that matters but maybe give that a try.
-
@laksh1999 said in Exchange Environment - Lab:
@syko24 said in Exchange Environment - Lab:
@laksh1999 - From the looks of it, you are trying to run setup.exe from C:\Windows\System32. Fix the path to wherever you installation media is located.
ex: D:\setup.exe
Tried from D drive got this error
That is telling you that it doesn't know about the /PrepareSchema option. Try running setup without that option.
-
Why are you trying to learn how out dated technology?
-
@travisdh1 said in Exchange Environment - Lab:
@laksh1999 said in Exchange Environment - Lab:
@syko24 said in Exchange Environment - Lab:
@laksh1999 - From the looks of it, you are trying to run setup.exe from C:\Windows\System32. Fix the path to wherever you installation media is located.
ex: D:\setup.exe
Tried from D drive got this error
That is telling you that it doesn't know about the /PrepareSchema option. Try running setup without that option.
Additionally your option of "/IAcceptExchangeLiceseTerms" is spelled incorrectly.
-
@hugh-jass said in Exchange Environment - Lab:
Why are you trying to learn how out dated technology?
Maybe he's trying to get a government job? They always use the outdated stuff.
-
@obsolesce said in Exchange Environment - Lab:
@hugh-jass said in Exchange Environment - Lab:
Why are you trying to learn how out dated technology?
Maybe he's trying to get a government job? They always use the outdated stuff.
I was going to ask this question myself… but then realized it was likely some stupid requirement to be local
-
@hugh-jass said in Exchange Environment - Lab:
Why are you trying to learn how out dated technology?
I actually agree with Studer
-
Unattended Mode is what you will be looking for:
https://docs.microsoft.com/en-us/exchange/plan-and-deploy/deploy-new-installations/unattended-installs?view=exchserver-2019 -
it was said in Exchange Environment - Lab:
Why are you trying to learn how out dated technology?
I'm curious, why is this the de-facto "go to" question when people don't feel like helping, but still want to hear themselves talk?
Maybe... this is what he has laying around his lab, AND he wants to learn?
Why is it usually a problem that one person is learning something years after someone else has?
I just don't get it.
If someone were asking how to write dos batch files, which is decades old, it is still a good basis for understanding and developing scripts; that will help with future learning.
-
@jasgot said in Exchange Environment - Lab:
If someone were asking how to write dos batch files, which is decades old, it is still a good basis for understanding and developing scripts; that will help with future learning.
No that's terrible practice and not a modern or efficient way to do anything. Powershell or Bash (neither of which is new) would actually. Ake sense. If you're using batch in 2021, you might as well use a sun dial or high noon to tell time.
-
@irj said in Exchange Environment - Lab:
@jasgot said in Exchange Environment - Lab:
If someone were asking how to write dos batch files, which is decades old, it is still a good basis for understanding and developing scripts; that will help with future learning.
No that's terrible practice and not a modern or efficient way to do anything. Powershell or Bash (neither of which is new) would actually. Ake sense. If you're using bash in 2021, you might as well use a sun dial or high noon to tell time.
Well, you'll never convince me that dismissing the basis and history of any type of knowledge is wise.
-
@jasgot said in Exchange Environment - Lab:
it was said in Exchange Environment - Lab:
Why are you trying to learn how out dated technology?
I'm curious, why is this the de-facto "go to" question when people don't feel like helping, but still want to hear themselves talk?
Maybe... this is what he has laying around his lab, AND he wants to learn?
Why is it usually a problem that one person is learning something years after someone else has?
I just don't get it.
If someone were asking how to write dos batch files, which is decades old, it is still a good basis for understanding and developing scripts; that will help with future learning.
It won't really help with future learning. Learning things like Goto statements is a waste of your time. If you (not you specifically but the editorial you) want to advance your career you will avoid old languages and systems like this.
-
@jasgot said in Exchange Environment - Lab:
@irj said in Exchange Environment - Lab:
@jasgot said in Exchange Environment - Lab:
If someone were asking how to write dos batch files, which is decades old, it is still a good basis for understanding and developing scripts; that will help with future learning.
No that's terrible practice and not a modern or efficient way to do anything. Powershell or Bash (neither of which is new) would actually. Ake sense. If you're using bash in 2021, you might as well use a sun dial or high noon to tell time.
Well, you'll never convince me that dismissing the basis and history of any type of knowledge is wise.
I get why some people like technology nostalgia, but it's not helpful for your career. You could do it as a hobby if you wanted, however for your career it's a waste of time. I agree that history is important to know and understanding old ways can be helpful. All you really need to know about batch files can be learned by a quick Google search in 5 mins of reading. Learning to write it is a complete waste of time.
-
There's rarely a day that goes by that I don't write a batch script, cmd script or powershell script. All of it is possible from having learned the basic structure of command scripting.
If I have to do anything to more than two computers that can be scripted, I script it.
I would much rather have my techs learn how to install MSExchange with a version that has been around long enough to be able to find the answer to the issue online; than have them spinning their wheels trying to solve a problem caused by a recent windows patch that no one has encountered before.
@irj said in Exchange Environment - Lab:
No that's terrible practice and not a modern or efficient way to do anything. Powershell or Bash (neither of which is new) would actually. Ake sense. If you're using batch in 2021, you might as well use a sun dial or high noon to tell time.
This is like saying you don't need to learn long division because you have a cellphone with a calculator.
You need to know long division.
-
@jasgot said in Exchange Environment - Lab:
There's rarely a day that goes by that I don't write a batch script, cmd script or powershell script. All of it is possible from having learned the basic structure of command scripting.
If I have to do anything to more than two computers that can be scripted, I script it.
I would much rather have my techs learn how to install MSExchange with a version that has been around long enough to be able to find the answer to the issue online; than have them spinning their wheels trying to solve a problem caused by a recent windows patch that no one has encountered before.
@irj said in Exchange Environment - Lab:
No that's terrible practice and not a modern or efficient way to do anything. Powershell or Bash (neither of which is new) would actually. Ake sense. If you're using batch in 2021, you might as well use a sun dial or high noon to tell time.
This is like saying you don't need to learn long division because you have a cellphone with a calculator.
You need to know long division.
I disagree, Learning batch is like learning Latin today... unless you're in a very specialized field, it's not going to be practical at all. You likely shouldn't be wasting your time in batch files at all... go directly to Powershell.
-
@jasgot said in Exchange Environment - Lab:
This is like saying you don't need to learn long division because you have a cellphone with a calculator.
No it's almost like saying you need to learn the intricacies of using one of these
Before using one of these
You can still write qbasic also, but why would you?
There's nothing wrong with understanding these languages had a purpose at one time, but don't put effort into learning them unless you have to.
