@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.

@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.

@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

@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:

@dave247 said in Exchange Environment - Lab:

@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?

you must be new around here - This is a general theme in many, I'd go so far as to say most, discussions around here.

Don't treat your company like a hobby. Do business correct, i.e. don't use local Exchange unless you have a regulation forcing you too.
Run the company like a real company - care about costs, do the 'right' thing, not just the simple get it done thing, etc.

No, I'm not that new around here but I don't view that many threads to be honest.

Arguing about someone treating their business like a hobby is stupid because at a certain point it's going to come down to matter of opinion, knowledge and experience - all things that are subject to change as people and businesses grow. Just because someone is using Product X vs Product Z doesn't mean they don't give a shit about making the business money.

@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?

@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.

@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.

@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 /IAcceptExchangeServerLicenseTerms

Sorry 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?

@pete-s said in best way to map various combinations of mapped drives to AD users?:

@dave247 said in best way to map various combinations of mapped drives to AD users?:

Problem: we have about 10 different shared folders as mapped drives and a handful of simple bat scripts used as AD logon scripts for users...

I think it would make more sense to just have one mapped drive and use sub directories for each department. That's probably how the files are organized anyway - at least judging from the looks of it.

The users that have permissions to a particular directory can use it and the other can't. That way you don't have to mess with the different drive mappings because everyone get the same one drive.

This also also how I have seen organizations with many departments do it. They basically use one drive mapping per entire file server. Everyone has gets the same shared drive(s) but permissions determine what directories they can access. It's more flexible to do it like that.

Yes actually that's one plan I've had for a long time, just haven't gotten around to doing it mainly since it will disrupt everyone's workflow for a bit.

@travisdh1 said in best way to map various combinations of mapped drives to AD users?:

@dave247 said in best way to map various combinations of mapped drives to AD users?:

@travisdh1 said in best way to map various combinations of mapped drives to AD users?:

@dave247 said in best way to map various combinations of mapped drives to AD users?:

I could probably use group policy to make a mapping for each drive, then assign each GPO to the necessary user.. but I feel like that would still be a little numerous or something.

Also, I know usually this sort of things is group based access, but we have a small company and many people wear multiple hats and essentially we end up with multiple combinations of access for every employee which makes group based permissions and things challenging.

I think you're halfway there. Yes, use GPO, but instead of assigning users to each GPO, create a group and assign the group to the GPO. Once everything is created, all you have to do for who gets what is add/remove users from the group for the drive mapping.

You mean make a group and apply each GPO for each drive to it, then add users? That makes sense.

Yep

I'll give that a try, thanks for the idea

@travisdh1 said in best way to map various combinations of mapped drives to AD users?:

@dave247 said in best way to map various combinations of mapped drives to AD users?:

I could probably use group policy to make a mapping for each drive, then assign each GPO to the necessary user.. but I feel like that would still be a little numerous or something.

Also, I know usually this sort of things is group based access, but we have a small company and many people wear multiple hats and essentially we end up with multiple combinations of access for every employee which makes group based permissions and things challenging.

I think you're halfway there. Yes, use GPO, but instead of assigning users to each GPO, create a group and assign the group to the GPO. Once everything is created, all you have to do for who gets what is add/remove users from the group for the drive mapping.

You mean make a group and apply each GPO for each drive to it, then add users? That makes sense.

@dustinb3403 said in best way to map various combinations of mapped drives to AD users?:

While this is a very legacy approach it still works. If everyone is on premise (or VPN) based this should work fine.

We have remote users (using VDI) too and mapped drives work just fine regardless.

I could probably use group policy to make a mapping for each drive, then assign each GPO to the necessary user.. but I feel like that would still be a little numerous or something.

Also, I know usually this sort of things is group based access, but we have a small company and many people wear multiple hats and essentially we end up with multiple combinations of access for every employee which makes group based permissions and things challenging.

Problem: we have about 10 different shared folders as mapped drives and a handful of simple bat scripts used as AD logon scripts for users. Most users have the same exact list of drives so they all have the same login script referenced in their AD account settings. However, I have a number of users that maybe need just one more or one less of those drives mapped. So my question is is there a more common or simple method to easily map any combination of folders as mapped drives to any combination of users without having to use a separate logon bat script for each? Like I don't want to have a specific bat script for each user's individual combination of mapped drives because then I'd eventually end up with 20+ of them. I also don't want to have some users that get a drive map error because of permissions.

Example of what my logon bat scripts look like:

@ECHO OFF

net use g: /delete /y
net use k: /delete /y
net use l: /delete /y
net use o: /delete /y
net use t: /delete /y

net use g: \\fs1\GeneralShare
net use k: \\fs1\Accounting
net use l: \\fs1\Finance
net use o: \\fs1\Marketing
net use t: \\fs1\IT

Also I understand that its been said not to use mapped drives anymore and instead use UNC share, but I'm not doing that right now. Maybe down the road though.

@hobbit666 said in Changing subnet mask?:

@siringo said in Changing subnet mask?:

If I get the Cisco gear changed, prior to me changing the servers, PCs, printers etc to /24 will everything remain working??

For example, If I get the Cisco gear changed to /24 on weekend 1, will everything still communicate & work fine until I can change the other gear on weekend 2??

I know the subnets are different, but with all devices having 10.0.0.x addresses I'm thinking they still may be seen by the /24 devices????

Does that make sense?

From what i remember
no they won't talk to each other once they are on a /24
e.g. 10.0.1.X/24 wont talk to 10.0.2.X/24

Have you checked the devices are using different IPs? 10.X.X.X? if your lucky they might all be on 10.0.X.X/24

They would talk to each other if you use a router. If it were me, I would just create the new network(s), VLAN(s) and router/firewall rules, then gradually move things over until everything was off the /8. That's what I did at my present company where we once had everything on a single /23