question about setting up a new domain controller
-
@tim_g said in question about setting up a new domain controller:
Just keep in mind Exchange 2010 support is over, and 2012 is soon over.
You may want to rethink this whole thing.
Personally, I'd migrate to O365, then upgrade DCs to 2016 with 2012 functional level (for now).
If you'd be on O365, you'd never have to worry about upgrading Exchange again.
My original plan was to deploy a new on-site, virtual Exchange 2016 server. Then afterwards, I was going to replace the old 2008 R2 DCs with 2016 DCs.
Maybe I will re-consider O365 though.
-
@dave247 said in question about setting up a new domain controller:
@tim_g said in question about setting up a new domain controller:
Just keep in mind Exchange 2010 support is over, and 2012 is soon over.
You may want to rethink this whole thing.
Personally, I'd migrate to O365, then upgrade DCs to 2016 with 2012 functional level (for now).
If you'd be on O365, you'd never have to worry about upgrading Exchange again.
My original plan was to deploy a new on-site, virtual Exchange 2016 server. Then afterwards, I was going to replace the old 2008 R2 DCs with 2016 DCs.
Maybe I will re-consider O365 though.
O365 should be the only thing considered (for Exchange) unless you have a blocking issue. Onsite is fine, if there is a reason that you can't be hosted. but if you can be hosted, you should be hosted (as as web servers, DNS, etc.) It's a commodity service that can't be done in house on par with lower cost hosted services. It's all about scale with commodity services.
If you are going to run Exchange in house, it needs to be maintained. Honestly, if I was in a company running Exchange 2010 today, I'd take that as a sign that they can't afford or manage to properly handle the needs of running Exchange and move to something else. Doesn't matter if it is a lack of money, skill, or just political problems - something is causing Exchange to not be able to be maintained and indicates that Exchange isn't a good choice for the environment.
But in any case, your plans are to either move to proper hosted, or a properly updated on premises. Whatever you are going to do, do it before making other changes because you are going to be forced to make other compromises to maintain the outdated on premises Exchange in the interim.
-
@scottalanmiller said in question about setting up a new domain controller:
@dave247 said in question about setting up a new domain controller:
@tim_g said in question about setting up a new domain controller:
Just keep in mind Exchange 2010 support is over, and 2012 is soon over.
You may want to rethink this whole thing.
Personally, I'd migrate to O365, then upgrade DCs to 2016 with 2012 functional level (for now).
If you'd be on O365, you'd never have to worry about upgrading Exchange again.
My original plan was to deploy a new on-site, virtual Exchange 2016 server. Then afterwards, I was going to replace the old 2008 R2 DCs with 2016 DCs.
Maybe I will re-consider O365 though.
O365 should be the only thing considered (for Exchange) unless you have a blocking issue. Onsite is fine, if there is a reason that you can't be hosted. but if you can be hosted, you should be hosted (as as web servers, DNS, etc.) It's a commodity service that can't be done in house on par with lower cost hosted services. It's all about scale with commodity services.
If you are going to run Exchange in house, it needs to be maintained. Honestly, if I was in a company running Exchange 2010 today, I'd take that as a sign that they can't afford or manage to properly handle the needs of running Exchange and move to something else. Doesn't matter if it is a lack of money, skill, or just political problems - something is causing Exchange to not be able to be maintained and indicates that Exchange isn't a good choice for the environment.
But in any case, your plans are to either move to proper hosted, or a properly updated on premises. Whatever you are going to do, do it before making other changes because you are going to be forced to make other compromises to maintain the outdated on premises Exchange in the interim.
Well I've gone back and forth on this a few times, not sure what to do. We have fiber internet, but we are out in the country and at least 3 times a year it goes out because something somewhere cuts a fiber line. We have a lot of users that send emails internally to other departments, like a lot. So having that channel of communication up is very important. Currently, we have a lot of services on-site which can sometimes slow internet.
I don't mind having Exchange on-site and I would kind of prefer it because it gives me a chance to learn all about it. We also have a 3rd party hosted application which is for spam filtering and email archiving, plus I have great backups. So there would be minimal risk involved, I think..
That being said, I would still do what's best for the company, which is to probably go O365 for Exchange, as well as our other Office products. We are still on 2010 Standard!! It will probably come down to cost though. Not my decision.
-
@dave247 said in question about setting up a new domain controller:
Well I've gone back and forth on this a few times, not sure what to do. We have fiber internet, but we are out in the country and at least 3 times a year it goes out because something somewhere cuts a fiber line. We have a lot of users that send emails internally to other departments, like a lot.
Keep in mind that if your fiber is cut, users can still work from home, work from phones, work from a backup ISP, work from a branch office, etc. if you use hosted; but lose all of these things if you go internal only.
-
@dave247 said in question about setting up a new domain controller:
We are still on 2010 Standard!!
It's this, more than anything, that tells me that O365 is the only option and in house should never even be considered. Nothing else matters other than one thing - the company lacks the ability to do what it takes to run email itself. Doesn't matter what the reason is whether technical, political, or financial.
It's like asking if you should buy a car or just take public transportation. If that's all we ask, we can easily say "well it depends on your situation." But once we learn that you regularly don't change your oil and your engine dies, or that you can't drive at all... then we know that the answer is "public transportation" irrespective of any other factors that might get mentioned. It's all red herrings. That Exchange can't be maintained in house alone is all that we need to know.
-
@scottalanmiller said in question about setting up a new domain controller:
@dave247 said in question about setting up a new domain controller:
We are still on 2010 Standard!!
It's this, more than anything, that tells me that O365 is the only option and in house should never even be considered. Nothing else matters other than one thing - the company lacks the ability to do what it takes to run email itself. Doesn't matter what the reason is whether technical, political, or financial.
It's like asking if you should buy a car or just take public transportation. If that's all we ask, we can easily say "well it depends on your situation." But once we learn that you regularly don't change your oil and your engine dies, or that you can't drive at all... then we know that the answer is "public transportation" irrespective of any other factors that might get mentioned. It's all red herrings. That Exchange can't be maintained in house alone is all that we need to know.
ok, thanks for the advice. It looks like O365 Business Essentials is $5 per user per month, which is pretty attractive. Is it pretty easy to migrate mailboxes from Exchange 2010 to O365? And can you still have distribution groups?
-
@dave247 said in question about setting up a new domain controller:
@scottalanmiller said in question about setting up a new domain controller:
@dave247 said in question about setting up a new domain controller:
We are still on 2010 Standard!!
It's this, more than anything, that tells me that O365 is the only option and in house should never even be considered. Nothing else matters other than one thing - the company lacks the ability to do what it takes to run email itself. Doesn't matter what the reason is whether technical, political, or financial.
It's like asking if you should buy a car or just take public transportation. If that's all we ask, we can easily say "well it depends on your situation." But once we learn that you regularly don't change your oil and your engine dies, or that you can't drive at all... then we know that the answer is "public transportation" irrespective of any other factors that might get mentioned. It's all red herrings. That Exchange can't be maintained in house alone is all that we need to know.
ok, thanks for the advice. It looks like O365 Business Essentials is $5 per user per month, which is pretty attractive. Is it pretty easy to migrate mailboxes from Exchange 2010 to O365? And can you still have distribution groups?
The migration should be easy: https://blogs.technet.microsoft.com/canitpro/2013/11/19/step-by-step-migrating-from-exchange-2007-to-office-365/
Distribution Groups are available in Office 365, yes. http://office365support.ca/creating-a-distribution-group-exchange-online/
-
@dave247 said in question about setting up a new domain controller:
@scottalanmiller said in question about setting up a new domain controller:
@dave247 said in question about setting up a new domain controller:
We are still on 2010 Standard!!
It's this, more than anything, that tells me that O365 is the only option and in house should never even be considered. Nothing else matters other than one thing - the company lacks the ability to do what it takes to run email itself. Doesn't matter what the reason is whether technical, political, or financial.
It's like asking if you should buy a car or just take public transportation. If that's all we ask, we can easily say "well it depends on your situation." But once we learn that you regularly don't change your oil and your engine dies, or that you can't drive at all... then we know that the answer is "public transportation" irrespective of any other factors that might get mentioned. It's all red herrings. That Exchange can't be maintained in house alone is all that we need to know.
ok, thanks for the advice. It looks like O365 Business Essentials is $5 per user per month, which is pretty attractive. Is it pretty easy to migrate mailboxes from Exchange 2010 to O365? And can you still have distribution groups?
Yes you can.
You can setup a 30 day trial in O365 (find a vendor to buy O365 from, but not a VAR) so you can get additional support options on your O365 account.
And reminder, that $5 account does not include locally installed Office.
-
@dave247 said in question about setting up a new domain controller:
@scottalanmiller said in question about setting up a new domain controller:
@dave247 said in question about setting up a new domain controller:
We are still on 2010 Standard!!
It's this, more than anything, that tells me that O365 is the only option and in house should never even be considered. Nothing else matters other than one thing - the company lacks the ability to do what it takes to run email itself. Doesn't matter what the reason is whether technical, political, or financial.
It's like asking if you should buy a car or just take public transportation. If that's all we ask, we can easily say "well it depends on your situation." But once we learn that you regularly don't change your oil and your engine dies, or that you can't drive at all... then we know that the answer is "public transportation" irrespective of any other factors that might get mentioned. It's all red herrings. That Exchange can't be maintained in house alone is all that we need to know.
ok, thanks for the advice. It looks like O365 Business Essentials is $5 per user per month, which is pretty attractive. Is it pretty easy to migrate mailboxes from Exchange 2010 to O365? And can you still have distribution groups?
Keep in mind, that is NOT email that you are comparing, but a services bundle. No reason that it isn't the right product for you, but you should be basing your decisions purely on email (which is $4, 25% cheaper) and then, once the decision is made and approved, consider if adding additional services onto that for an additional $1 also makes sense. Don't bundle and use that to compare to a non-bundle.
-
@dashrender said in question about setting up a new domain controller:
And reminder, that $5 account does not include locally installed Office.
But DOES include more than email.
-
@scottalanmiller said in question about setting up a new domain controller:
@dave247 said in question about setting up a new domain controller:
@scottalanmiller said in question about setting up a new domain controller:
@dave247 said in question about setting up a new domain controller:
We are still on 2010 Standard!!
It's this, more than anything, that tells me that O365 is the only option and in house should never even be considered. Nothing else matters other than one thing - the company lacks the ability to do what it takes to run email itself. Doesn't matter what the reason is whether technical, political, or financial.
It's like asking if you should buy a car or just take public transportation. If that's all we ask, we can easily say "well it depends on your situation." But once we learn that you regularly don't change your oil and your engine dies, or that you can't drive at all... then we know that the answer is "public transportation" irrespective of any other factors that might get mentioned. It's all red herrings. That Exchange can't be maintained in house alone is all that we need to know.
ok, thanks for the advice. It looks like O365 Business Essentials is $5 per user per month, which is pretty attractive. Is it pretty easy to migrate mailboxes from Exchange 2010 to O365? And can you still have distribution groups?
Keep in mind, that is NOT email that you are comparing, but a services bundle. No reason that it isn't the right product for you, but you should be basing your decisions purely on email (which is $4, 25% cheaper) and then, once the decision is made and approved, consider if adding additional services onto that for an additional $1 also makes sense. Don't bundle and use that to compare to a non-bundle.
oh I see that.. It shows that it's email, skype, SharePoint, onedrive, yammer.. etc.. how the heck do I just get email??
-
@dave247 said in question about setting up a new domain controller:
@scottalanmiller said in question about setting up a new domain controller:
@dave247 said in question about setting up a new domain controller:
@scottalanmiller said in question about setting up a new domain controller:
@dave247 said in question about setting up a new domain controller:
We are still on 2010 Standard!!
It's this, more than anything, that tells me that O365 is the only option and in house should never even be considered. Nothing else matters other than one thing - the company lacks the ability to do what it takes to run email itself. Doesn't matter what the reason is whether technical, political, or financial.
It's like asking if you should buy a car or just take public transportation. If that's all we ask, we can easily say "well it depends on your situation." But once we learn that you regularly don't change your oil and your engine dies, or that you can't drive at all... then we know that the answer is "public transportation" irrespective of any other factors that might get mentioned. It's all red herrings. That Exchange can't be maintained in house alone is all that we need to know.
ok, thanks for the advice. It looks like O365 Business Essentials is $5 per user per month, which is pretty attractive. Is it pretty easy to migrate mailboxes from Exchange 2010 to O365? And can you still have distribution groups?
Keep in mind, that is NOT email that you are comparing, but a services bundle. No reason that it isn't the right product for you, but you should be basing your decisions purely on email (which is $4, 25% cheaper) and then, once the decision is made and approved, consider if adding additional services onto that for an additional $1 also makes sense. Don't bundle and use that to compare to a non-bundle.
oh I see that.. It shows that it's email, skype, SharePoint, onedrive, yammer.. etc.. how the heck do I just get email??
Why wouldn't you want to include the current version of Office Suite rather than having running old and outdated Office 2010?
I thought I remember you mentioning allof your users have Office 2010 installed.
-
@dave247 said in question about setting up a new domain controller:
@scottalanmiller said in question about setting up a new domain controller:
@dave247 said in question about setting up a new domain controller:
@scottalanmiller said in question about setting up a new domain controller:
@dave247 said in question about setting up a new domain controller:
We are still on 2010 Standard!!
It's this, more than anything, that tells me that O365 is the only option and in house should never even be considered. Nothing else matters other than one thing - the company lacks the ability to do what it takes to run email itself. Doesn't matter what the reason is whether technical, political, or financial.
It's like asking if you should buy a car or just take public transportation. If that's all we ask, we can easily say "well it depends on your situation." But once we learn that you regularly don't change your oil and your engine dies, or that you can't drive at all... then we know that the answer is "public transportation" irrespective of any other factors that might get mentioned. It's all red herrings. That Exchange can't be maintained in house alone is all that we need to know.
ok, thanks for the advice. It looks like O365 Business Essentials is $5 per user per month, which is pretty attractive. Is it pretty easy to migrate mailboxes from Exchange 2010 to O365? And can you still have distribution groups?
Keep in mind, that is NOT email that you are comparing, but a services bundle. No reason that it isn't the right product for you, but you should be basing your decisions purely on email (which is $4, 25% cheaper) and then, once the decision is made and approved, consider if adding additional services onto that for an additional $1 also makes sense. Don't bundle and use that to compare to a non-bundle.
oh I see that.. It shows that it's email, skype, SharePoint, onedrive, yammer.. etc.. how the heck do I just get email??
It's called "Hosted Exchange."
-
-
You can also work with a partner, which is not a reseller. An Office 365 Partner provides you some additional benefits and can help you navigate the world of Office 365. NTG is an O365 partner. You can always ping @Minion-Queen for assistance.
-
@dave247 said in question about setting up a new domain controller:
@scottalanmiller said in question about setting up a new domain controller:
@dave247 said in question about setting up a new domain controller:
@scottalanmiller said in question about setting up a new domain controller:
@dave247 said in question about setting up a new domain controller:
We are still on 2010 Standard!!
It's this, more than anything, that tells me that O365 is the only option and in house should never even be considered. Nothing else matters other than one thing - the company lacks the ability to do what it takes to run email itself. Doesn't matter what the reason is whether technical, political, or financial.
It's like asking if you should buy a car or just take public transportation. If that's all we ask, we can easily say "well it depends on your situation." But once we learn that you regularly don't change your oil and your engine dies, or that you can't drive at all... then we know that the answer is "public transportation" irrespective of any other factors that might get mentioned. It's all red herrings. That Exchange can't be maintained in house alone is all that we need to know.
ok, thanks for the advice. It looks like O365 Business Essentials is $5 per user per month, which is pretty attractive. Is it pretty easy to migrate mailboxes from Exchange 2010 to O365? And can you still have distribution groups?
Keep in mind, that is NOT email that you are comparing, but a services bundle. No reason that it isn't the right product for you, but you should be basing your decisions purely on email (which is $4, 25% cheaper) and then, once the decision is made and approved, consider if adding additional services onto that for an additional $1 also makes sense. Don't bundle and use that to compare to a non-bundle.
oh I see that.. It shows that it's email, skype, SharePoint, onedrive, yammer.. etc.. how the heck do I just get email??
Those things aren't bad, however we are at a point where we use only one of all of those and are actively in the process of phasing even it out as we are unhappy with the quality of the entire line of MS products.
-
@dashrender said in question about setting up a new domain controller:
VAR
I'm currently seeking information from CDW on this..
-
@dave247 said in question about setting up a new domain controller:
@dashrender said in question about setting up a new domain controller:
VAR
I'm currently seeking information from CDW on this..
No, you CAN'T use a VAR with Exchange Online. You will be SCREWED. There is ONE thing to know about cloud services, and it is that you never involve a VAR.
-
@scottalanmiller said in question about setting up a new domain controller:
@dave247 said in question about setting up a new domain controller:
@scottalanmiller said in question about setting up a new domain controller:
@dave247 said in question about setting up a new domain controller:
@scottalanmiller said in question about setting up a new domain controller:
@dave247 said in question about setting up a new domain controller:
We are still on 2010 Standard!!
It's this, more than anything, that tells me that O365 is the only option and in house should never even be considered. Nothing else matters other than one thing - the company lacks the ability to do what it takes to run email itself. Doesn't matter what the reason is whether technical, political, or financial.
It's like asking if you should buy a car or just take public transportation. If that's all we ask, we can easily say "well it depends on your situation." But once we learn that you regularly don't change your oil and your engine dies, or that you can't drive at all... then we know that the answer is "public transportation" irrespective of any other factors that might get mentioned. It's all red herrings. That Exchange can't be maintained in house alone is all that we need to know.
ok, thanks for the advice. It looks like O365 Business Essentials is $5 per user per month, which is pretty attractive. Is it pretty easy to migrate mailboxes from Exchange 2010 to O365? And can you still have distribution groups?
Keep in mind, that is NOT email that you are comparing, but a services bundle. No reason that it isn't the right product for you, but you should be basing your decisions purely on email (which is $4, 25% cheaper) and then, once the decision is made and approved, consider if adding additional services onto that for an additional $1 also makes sense. Don't bundle and use that to compare to a non-bundle.
oh I see that.. It shows that it's email, skype, SharePoint, onedrive, yammer.. etc.. how the heck do I just get email??
Those things aren't bad, however we are at a point where we use only one of all of those and are actively in the process of phasing even it out as we are unhappy with the quality of the entire line of MS products.
We honestly don't need those additional services right now since we already have things that fill the roles they provide.
-
@scottalanmiller said in question about setting up a new domain controller:
@dave247 said in question about setting up a new domain controller:
@dashrender said in question about setting up a new domain controller:
VAR
I'm currently seeking information from CDW on this..
No, you CAN'T use a VAR with Exchange Online. You will be SCREWED. There is ONE thing to know about cloud services, and it is that you never involve a VAR.
Well where the hell do I find a partner then?
Also, please link me to the relevant article on your blog because I clearly don't know wtf I'm doing..
