Exchange Environment - Lab
-
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.
-
I am not trying anything with the Government jobs.
I am in Exchange environment to learn new things.I cannot do anything with the Production exchange environment. Just to understand the alerts in the servers i am creating my own lab servers and testing it in the test environment.If any one can help do help me .If not no issues.
Close this thread or dont reply if no one is ready to help me on this topic
Corrected this as well
\Setup.exe /IAcceptExchangeServerLicenseTerms -
@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 batch in 2021, you might as well use a sun dial or high noon to tell time.
Heh - I like my Sundial... but I burned my abacus long ago. And that's all I'll say about that,...
-
@laksh1999 said in Exchange Environment - Lab:
I am not trying anything with the Government jobs.
I am in Exchange environment to learn new things.I cannot do anything with the Production exchange environment. Just to understand the alerts in the servers i am creating my own lab servers and testing it in the test environment.If any one can help do help me .If not no issues.
Close this thread or dont reply if no one is ready to help me on this topic
Corrected this as well
\Setup.exe /IAcceptExchangeServerLicenseTermsSorry about that. The majority of people on this forum are arrogant assholes who like to pick apart your posts and criticize and insult what you are doing. Then they will argue with your every reply. It really is an unprofessional IT forum. I'd suggest going to reddit and finding one of the many good technology subreddits. Sure, there's going to be a range of skill and knowledge there, but I find most the time I always get extremely helpful tidbits of info to get me going in the right direction. Plus, people are usually much more friendly there.
That said, I'd first ask you if you have an Active Directory domain controller set up first before installing Exchange?
-
@dave247 said in Exchange Environment - Lab:
The majority of people on this forum are arrogant assholes who like to pick apart your posts and criticize and insult what you are doing.
Some may see that way... while others will see it as questioning motives and pointing people in a better direction to improve their career and broaden their skillset to become more useful in the market.
But it is understandable some may not want that who are happy where they are and take offense to a better approach.
-
I can see what others are saying, onsite exchange not really no point, but a lot of MSP's still host their own copy of exchange normally in a datacenter and you could sell your own hosted exchange to customers. This only would be advantageous with lots of users. But you just cannot beat the costs of 365 with normal Businesses.
-
@obsolesce said in Exchange Environment - Lab:
@dave247 said in Exchange Environment - Lab:
The majority of people on this forum are arrogant assholes who like to pick apart your posts and criticize and insult what you are doing.
Some may see that way... while others will see it as questioning motives and pointing people in a better direction to improve their career and broaden their skillset to become more useful in the market.
But it is understandable some may not want that who are happy where they are and take offense to a better approach.
Yes, but there is a difference between constructive criticism and completely unhelpful sarcastic replies. I am referring to the latter.
-
@stuartjordan said in Exchange Environment - Lab:
I can see what others are saying, onsite exchange not really no point, but a lot of MSP's still host their own copy of exchange normally in a datacenter and you could sell your own hosted exchange to customers. This only would be advantageous with lots of users. But you just cannot beat the costs of 365 with normal Businesses.
If you want to host email, why would you use the worst platform possible to find? Why not Zimbra for example?
-
@travisdh1 said in Exchange Environment - Lab:
@stuartjordan said in Exchange Environment - Lab:
I can see what others are saying, onsite exchange not really no point, but a lot of MSP's still host their own copy of exchange normally in a datacenter and you could sell your own hosted exchange to customers. This only would be advantageous with lots of users. But you just cannot beat the costs of 365 with normal Businesses.
If you want to host email, why would you use the worst platform possible to find? Why not Zimbra for example?
Case in point.
-
@travisdh1 said in Exchange Environment - Lab:
@stuartjordan said in Exchange Environment - Lab:
I can see what others are saying, onsite exchange not really no point, but a lot of MSP's still host their own copy of exchange normally in a datacenter and you could sell your own hosted exchange to customers. This only would be advantageous with lots of users. But you just cannot beat the costs of 365 with normal Businesses.
If you want to host email, why would you use the worst platform possible to find? Why not Zimbra for example?
I'm not on about me, I personally use mailcow. But I'm stating big MSP'S and hosting companies still use hosted exchange in a datacenter enviroment.
-
@stuartjordan said in Exchange Environment - Lab:
@travisdh1 said in Exchange Environment - Lab:
@stuartjordan said in Exchange Environment - Lab:
I can see what others are saying, onsite exchange not really no point, but a lot of MSP's still host their own copy of exchange normally in a datacenter and you could sell your own hosted exchange to customers. This only would be advantageous with lots of users. But you just cannot beat the costs of 365 with normal Businesses.
If you want to host email, why would you use the worst platform possible to find? Why not Zimbra for example?
I'm not on about me, I personally use mailcow. But I'm stating big MSP'S and hosting companies still use hosted exchange in a datacenter enviroment.
I guess that requires the discussion about management not caring about the company and treating it like a hobby business yet again.
-
@travisdh1 said in Exchange Environment - Lab:
@stuartjordan said in Exchange Environment - Lab:
@travisdh1 said in Exchange Environment - Lab:
@stuartjordan said in Exchange Environment - Lab:
I can see what others are saying, onsite exchange not really no point, but a lot of MSP's still host their own copy of exchange normally in a datacenter and you could sell your own hosted exchange to customers. This only would be advantageous with lots of users. But you just cannot beat the costs of 365 with normal Businesses.
If you want to host email, why would you use the worst platform possible to find? Why not Zimbra for example?
I'm not on about me, I personally use mailcow. But I'm stating big MSP'S and hosting companies still use hosted exchange in a datacenter enviroment.
I guess that requires the discussion about management not caring about the company and treating it like a hobby business yet again.
What are you even talking about?
