Raising Domain/Forest from 2008 to 2016: What do I need to know?
-
@scottalanmiller said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@dashrender said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
Curious - why do you want/care about upgrading the domain/forest?
One reason to not do it is the ability to integrate Linux boxes with Samba. Unless Samba released a version I'm unaware of, it only compatible with forest/domain level of 2012 R2.
https://wiki.samba.org/index.php/Raising_the_Functional_Levels
If you plan to never do this, then don't worry about it
See you mention compatibility. It's compatible with 2016. The limit you are mentioning is not related to compatibility.
Again - so true - I specifically was referring to the ability to be a DC, as like you, I assumed that general ability to access 2016 shares for example was likely possible, regardless of forest/domain level.
-
I usually go and enable the AD recycle bin right after that. It's one of those things you don't think about until the day you need it ...
-
@mike-davis said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
I usually go and enable the AD recycle bin right after that. It's one of those things you don't think about until the day you need it ...
Yes!
-
@nerdydad said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
I am currently in the process of retiring my 2008 AD servers in order to raise our forest and domain levels to 2016. We already have 3 WS 2016 AD servers in our environment (1 at each location). I have about 4 2008 AD servers to retire before I can do that, so I have some time. There is only 1 forest/1 domain to be concerned about here. We're not tied to any other domains or forests. We are tied to O365 through AAD Sync. We currently use SYSVOL batch scripts to map drives.
What do I need to consider changing before raising the domain/forest level?
It only ever adds functionality, never removes any.
In every case you can go ahead and raise it. It's a myth that you need to be concerned about it -
@mike-davis said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
I usually go and enable the AD recycle bin right after that. It's one of those things you don't think about until the day you need it ...
Done
-
@tim_g said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@nerdydad said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
I am currently in the process of retiring my 2008 AD servers in order to raise our forest and domain levels to 2016. We already have 3 WS 2016 AD servers in our environment (1 at each location). I have about 4 2008 AD servers to retire before I can do that, so I have some time. There is only 1 forest/1 domain to be concerned about here. We're not tied to any other domains or forests. We are tied to O365 through AAD Sync. We currently use SYSVOL batch scripts to map drives.
What do I need to consider changing before raising the domain/forest level?
It only ever adds functionality, never removes any.
In every case you can go ahead and raise it. It's a myth that you need to be concerned about itOther than raising it to a level where you block your choice to move off of Windows. That's the only thing.
-
@scottalanmiller said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@tim_g said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@nerdydad said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
I am currently in the process of retiring my 2008 AD servers in order to raise our forest and domain levels to 2016. We already have 3 WS 2016 AD servers in our environment (1 at each location). I have about 4 2008 AD servers to retire before I can do that, so I have some time. There is only 1 forest/1 domain to be concerned about here. We're not tied to any other domains or forests. We are tied to O365 through AAD Sync. We currently use SYSVOL batch scripts to map drives.
What do I need to consider changing before raising the domain/forest level?
It only ever adds functionality, never removes any.
In every case you can go ahead and raise it. It's a myth that you need to be concerned about itOther than raising it to a level where you block your choice to move off of Windows. That's the only thing.
That's not going to be a decision management will support unless we can come up with an entirely new environment that will support all of our functions.
- ERP System
- Email (easy)
- Integration with FedEx
- Integration with other parties/customers for order management
I am sure there is more here that I am missing. Just can't think of what it was.
-
@nerdydad said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@scottalanmiller said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@tim_g said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@nerdydad said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
I am currently in the process of retiring my 2008 AD servers in order to raise our forest and domain levels to 2016. We already have 3 WS 2016 AD servers in our environment (1 at each location). I have about 4 2008 AD servers to retire before I can do that, so I have some time. There is only 1 forest/1 domain to be concerned about here. We're not tied to any other domains or forests. We are tied to O365 through AAD Sync. We currently use SYSVOL batch scripts to map drives.
What do I need to consider changing before raising the domain/forest level?
It only ever adds functionality, never removes any.
In every case you can go ahead and raise it. It's a myth that you need to be concerned about itOther than raising it to a level where you block your choice to move off of Windows. That's the only thing.
That's not going to be a decision management will support unless we can come up with an entirely new environment that will support all of our functions.
- ERP System
- Email (easy)
- Integration with FedEx
- Integration with other parties/customers for order management
I am sure there is more here that I am missing. Just can't think of what it was.
What do any of those things have to do with your AD level?
-
@scottalanmiller said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@nerdydad said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@scottalanmiller said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@tim_g said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@nerdydad said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
I am currently in the process of retiring my 2008 AD servers in order to raise our forest and domain levels to 2016. We already have 3 WS 2016 AD servers in our environment (1 at each location). I have about 4 2008 AD servers to retire before I can do that, so I have some time. There is only 1 forest/1 domain to be concerned about here. We're not tied to any other domains or forests. We are tied to O365 through AAD Sync. We currently use SYSVOL batch scripts to map drives.
What do I need to consider changing before raising the domain/forest level?
It only ever adds functionality, never removes any.
In every case you can go ahead and raise it. It's a myth that you need to be concerned about itOther than raising it to a level where you block your choice to move off of Windows. That's the only thing.
That's not going to be a decision management will support unless we can come up with an entirely new environment that will support all of our functions.
- ERP System
- Email (easy)
- Integration with FedEx
- Integration with other parties/customers for order management
I am sure there is more here that I am missing. Just can't think of what it was.
What do any of those things have to do with your AD level?
Nothing about AD level. About going from a Windows environment to a Linux environment. I am sure this will save us a ton of money by freeing up licenses, but I am also looking at support of the business.
-
@scottalanmiller said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@nerdydad said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@scottalanmiller said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@tim_g said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@nerdydad said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
I am currently in the process of retiring my 2008 AD servers in order to raise our forest and domain levels to 2016. We already have 3 WS 2016 AD servers in our environment (1 at each location). I have about 4 2008 AD servers to retire before I can do that, so I have some time. There is only 1 forest/1 domain to be concerned about here. We're not tied to any other domains or forests. We are tied to O365 through AAD Sync. We currently use SYSVOL batch scripts to map drives.
What do I need to consider changing before raising the domain/forest level?
It only ever adds functionality, never removes any.
In every case you can go ahead and raise it. It's a myth that you need to be concerned about itOther than raising it to a level where you block your choice to move off of Windows. That's the only thing.
That's not going to be a decision management will support unless we can come up with an entirely new environment that will support all of our functions.
- ERP System
- Email (easy)
- Integration with FedEx
- Integration with other parties/customers for order management
I am sure there is more here that I am missing. Just can't think of what it was.
What do any of those things have to do with your AD level?
It has more to do with Linux implementation.
-
@nerdydad said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@scottalanmiller said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@nerdydad said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@scottalanmiller said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@tim_g said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@nerdydad said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
I am currently in the process of retiring my 2008 AD servers in order to raise our forest and domain levels to 2016. We already have 3 WS 2016 AD servers in our environment (1 at each location). I have about 4 2008 AD servers to retire before I can do that, so I have some time. There is only 1 forest/1 domain to be concerned about here. We're not tied to any other domains or forests. We are tied to O365 through AAD Sync. We currently use SYSVOL batch scripts to map drives.
What do I need to consider changing before raising the domain/forest level?
It only ever adds functionality, never removes any.
In every case you can go ahead and raise it. It's a myth that you need to be concerned about itOther than raising it to a level where you block your choice to move off of Windows. That's the only thing.
That's not going to be a decision management will support unless we can come up with an entirely new environment that will support all of our functions.
- ERP System
- Email (easy)
- Integration with FedEx
- Integration with other parties/customers for order management
I am sure there is more here that I am missing. Just can't think of what it was.
What do any of those things have to do with your AD level?
Nothing about AD level. About going from a Windows environment to a Linux environment. I am sure this will save us a ton of money by freeing up licenses, but I am also looking at support of the business.
Oh, but what does THAT have to do with it, either? Just as disconnected as the AD level.
-
@dbeato said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@scottalanmiller said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@nerdydad said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@scottalanmiller said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@tim_g said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@nerdydad said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
I am currently in the process of retiring my 2008 AD servers in order to raise our forest and domain levels to 2016. We already have 3 WS 2016 AD servers in our environment (1 at each location). I have about 4 2008 AD servers to retire before I can do that, so I have some time. There is only 1 forest/1 domain to be concerned about here. We're not tied to any other domains or forests. We are tied to O365 through AAD Sync. We currently use SYSVOL batch scripts to map drives.
What do I need to consider changing before raising the domain/forest level?
It only ever adds functionality, never removes any.
In every case you can go ahead and raise it. It's a myth that you need to be concerned about itOther than raising it to a level where you block your choice to move off of Windows. That's the only thing.
That's not going to be a decision management will support unless we can come up with an entirely new environment that will support all of our functions.
- ERP System
- Email (easy)
- Integration with FedEx
- Integration with other parties/customers for order management
I am sure there is more here that I am missing. Just can't think of what it was.
What do any of those things have to do with your AD level?
It has more to do with Linux implementation.
But how? What's the association?
-
@nerdydad said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@scottalanmiller said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@tim_g said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@nerdydad said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
I am currently in the process of retiring my 2008 AD servers in order to raise our forest and domain levels to 2016. We already have 3 WS 2016 AD servers in our environment (1 at each location). I have about 4 2008 AD servers to retire before I can do that, so I have some time. There is only 1 forest/1 domain to be concerned about here. We're not tied to any other domains or forests. We are tied to O365 through AAD Sync. We currently use SYSVOL batch scripts to map drives.
What do I need to consider changing before raising the domain/forest level?
It only ever adds functionality, never removes any.
In every case you can go ahead and raise it. It's a myth that you need to be concerned about itOther than raising it to a level where you block your choice to move off of Windows. That's the only thing.
That's not going to be a decision management will support unless we can come up with an entirely new environment that will support all of our functions.
This doesn't make any sense . Linux is a drop in replacement here. So all of this is already supported. Windows and Linux aren't relevant to the discussion. The discussion is AD.
-
@scottalanmiller said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@tim_g said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@nerdydad said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
I am currently in the process of retiring my 2008 AD servers in order to raise our forest and domain levels to 2016. We already have 3 WS 2016 AD servers in our environment (1 at each location). I have about 4 2008 AD servers to retire before I can do that, so I have some time. There is only 1 forest/1 domain to be concerned about here. We're not tied to any other domains or forests. We are tied to O365 through AAD Sync. We currently use SYSVOL batch scripts to map drives.
What do I need to consider changing before raising the domain/forest level?
It only ever adds functionality, never removes any.
In every case you can go ahead and raise it. It's a myth that you need to be concerned about itOther than raising it to a level where you block your choice to move off of Windows. That's the only thing.
Let me back up and ask for clarification on the statement above.
-
@nerdydad said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@scottalanmiller said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@tim_g said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@nerdydad said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
I am currently in the process of retiring my 2008 AD servers in order to raise our forest and domain levels to 2016. We already have 3 WS 2016 AD servers in our environment (1 at each location). I have about 4 2008 AD servers to retire before I can do that, so I have some time. There is only 1 forest/1 domain to be concerned about here. We're not tied to any other domains or forests. We are tied to O365 through AAD Sync. We currently use SYSVOL batch scripts to map drives.
What do I need to consider changing before raising the domain/forest level?
It only ever adds functionality, never removes any.
In every case you can go ahead and raise it. It's a myth that you need to be concerned about itOther than raising it to a level where you block your choice to move off of Windows. That's the only thing.
Let me back up and ask for clarification on the statement above.
What does AD have to do with the listed applications? They run on Windows correct? Then moving to a Linux based SAMBA server probably wouldn't be an issue.
-
@scottalanmiller said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@nerdydad said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@scottalanmiller said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@tim_g said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@nerdydad said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
I am currently in the process of retiring my 2008 AD servers in order to raise our forest and domain levels to 2016. We already have 3 WS 2016 AD servers in our environment (1 at each location). I have about 4 2008 AD servers to retire before I can do that, so I have some time. There is only 1 forest/1 domain to be concerned about here. We're not tied to any other domains or forests. We are tied to O365 through AAD Sync. We currently use SYSVOL batch scripts to map drives.
What do I need to consider changing before raising the domain/forest level?
It only ever adds functionality, never removes any.
In every case you can go ahead and raise it. It's a myth that you need to be concerned about itOther than raising it to a level where you block your choice to move off of Windows. That's the only thing.
That's not going to be a decision management will support unless we can come up with an entirely new environment that will support all of our functions.
This doesn't make any sense . Linux is a drop in replacement here. So all of this is already supported. Windows and Linux aren't relevant to the discussion. The discussion is AD.
Totally understand that this discussion was about AD. I thought you were trying to turn the subject somewhere else.
-
@nerdydad said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@scottalanmiller said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@tim_g said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@nerdydad said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
I am currently in the process of retiring my 2008 AD servers in order to raise our forest and domain levels to 2016. We already have 3 WS 2016 AD servers in our environment (1 at each location). I have about 4 2008 AD servers to retire before I can do that, so I have some time. There is only 1 forest/1 domain to be concerned about here. We're not tied to any other domains or forests. We are tied to O365 through AAD Sync. We currently use SYSVOL batch scripts to map drives.
What do I need to consider changing before raising the domain/forest level?
It only ever adds functionality, never removes any.
In every case you can go ahead and raise it. It's a myth that you need to be concerned about itOther than raising it to a level where you block your choice to move off of Windows. That's the only thing.
Let me back up and ask for clarification on the statement above.
If you raise the AD level to 2012 R2, you can still optionally use Windows or Linux for your AD servers. If you go to 2016, Linux is no longer an option until Samba brings out an update to allow it to be a 2016 level server. As long as you don't go all of the way to 2016, you have no Windows based AD dependency here.
-
@nerdydad said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@scottalanmiller said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@nerdydad said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@scottalanmiller said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@tim_g said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@nerdydad said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
I am currently in the process of retiring my 2008 AD servers in order to raise our forest and domain levels to 2016. We already have 3 WS 2016 AD servers in our environment (1 at each location). I have about 4 2008 AD servers to retire before I can do that, so I have some time. There is only 1 forest/1 domain to be concerned about here. We're not tied to any other domains or forests. We are tied to O365 through AAD Sync. We currently use SYSVOL batch scripts to map drives.
What do I need to consider changing before raising the domain/forest level?
It only ever adds functionality, never removes any.
In every case you can go ahead and raise it. It's a myth that you need to be concerned about itOther than raising it to a level where you block your choice to move off of Windows. That's the only thing.
That's not going to be a decision management will support unless we can come up with an entirely new environment that will support all of our functions.
This doesn't make any sense . Linux is a drop in replacement here. So all of this is already supported. Windows and Linux aren't relevant to the discussion. The discussion is AD.
Totally understand that this discussion was about AD. I thought you were trying to turn the subject somewhere else.
People always like to claim that I do that, and the constant claiming that I do that has led more people to see things that aren't that as being that. It's something people repeat to try to make it look like I'm just spewing topics, because I often point out gaps in business decisino making making it relatively easy for people to overlook that I stayed more on topic than the people complaining about it.
I was 100% responding in the context of the question asked.
-
@scottalanmiller said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@nerdydad said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@scottalanmiller said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@nerdydad said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@scottalanmiller said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@tim_g said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@nerdydad said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
I am currently in the process of retiring my 2008 AD servers in order to raise our forest and domain levels to 2016. We already have 3 WS 2016 AD servers in our environment (1 at each location). I have about 4 2008 AD servers to retire before I can do that, so I have some time. There is only 1 forest/1 domain to be concerned about here. We're not tied to any other domains or forests. We are tied to O365 through AAD Sync. We currently use SYSVOL batch scripts to map drives.
What do I need to consider changing before raising the domain/forest level?
It only ever adds functionality, never removes any.
In every case you can go ahead and raise it. It's a myth that you need to be concerned about itOther than raising it to a level where you block your choice to move off of Windows. That's the only thing.
That's not going to be a decision management will support unless we can come up with an entirely new environment that will support all of our functions.
This doesn't make any sense . Linux is a drop in replacement here. So all of this is already supported. Windows and Linux aren't relevant to the discussion. The discussion is AD.
Totally understand that this discussion was about AD. I thought you were trying to turn the subject somewhere else.
People always like to claim that I do that, and the constant claiming that I do that has led more people to see things that aren't that as being that. It's something people repeat to try to make it look like I'm just spewing topics, because I often point out gaps in business decisino making making it relatively easy for people to overlook that I stayed more on topic than the people complaining about it.
I was 100% responding in the context of the question asked.
You answered your question as you should based on your statement, while @Tim_G stated a different qfact
@scottalanmiller said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@nerdydad said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@scottalanmiller said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@nerdydad said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@scottalanmiller said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@tim_g said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@nerdydad said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
I am currently in the process of retiring my 2008 AD servers in order to raise our forest and domain levels to 2016. We already have 3 WS 2016 AD servers in our environment (1 at each location). I have about 4 2008 AD servers to retire before I can do that, so I have some time. There is only 1 forest/1 domain to be concerned about here. We're not tied to any other domains or forests. We are tied to O365 through AAD Sync. We currently use SYSVOL batch scripts to map drives.
What do I need to consider changing before raising the domain/forest level?
It only ever adds functionality, never removes any.
In every case you can go ahead and raise it. It's a myth that you need to be concerned about itOther than raising it to a level where you block your choice to move off of Windows. That's the only thing.
That's not going to be a decision management will support unless we can come up with an entirely new environment that will support all of our functions.
This doesn't make any sense . Linux is a drop in replacement here. So all of this is already supported. Windows and Linux aren't relevant to the discussion. The discussion is AD.
Totally understand that this discussion was about AD. I thought you were trying to turn the subject somewhere else.
People always like to claim that I do that, and the constant claiming that I do that has led more people to see things that aren't that as being that. It's something people repeat to try to make it look like I'm just spewing topics, because I often point out gaps in business decisino making making it relatively easy for people to overlook that I stayed more on topic than the people complaining about it.
I was 100% responding in the context of the question asked.
@scottalanmiller said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@nerdydad said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@scottalanmiller said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@nerdydad said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@scottalanmiller said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@tim_g said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@nerdydad said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
I am currently in the process of retiring my 2008 AD servers in order to raise our forest and domain levels to 2016. We already have 3 WS 2016 AD servers in our environment (1 at each location). I have about 4 2008 AD servers to retire before I can do that, so I have some time. There is only 1 forest/1 domain to be concerned about here. We're not tied to any other domains or forests. We are tied to O365 through AAD Sync. We currently use SYSVOL batch scripts to map drives.
What do I need to consider changing before raising the domain/forest level?
It only ever adds functionality, never removes any.
In every case you can go ahead and raise it. It's a myth that you need to be concerned about itOther than raising it to a level where you block your choice to move off of Windows. That's the only thing.
That's not going to be a decision management will support unless we can come up with an entirely new environment that will support all of our functions.
This doesn't make any sense . Linux is a drop in replacement here. So all of this is already supported. Windows and Linux aren't relevant to the discussion. The discussion is AD.
Totally understand that this discussion was about AD. I thought you were trying to turn the subject somewhere else.
People always like to claim that I do that, and the constant claiming that I do that has led more people to see things that aren't that as being that. It's something people repeat to try to make it look like I'm just spewing topics, because I often point out gaps in business decisino making making it relatively easy for people to overlook that I stayed more on topic than the people complaining about it.
I was 100% responding in the context of the question asked.
I see you answered your question, but the other statements stemmed from @Tim_G fact.
-
@scottalanmiller said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@nerdydad said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@scottalanmiller said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@nerdydad said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@scottalanmiller said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@tim_g said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
@nerdydad said in Raising Domain/Forest from 2008 to 2016: What do I need to know?:
I am currently in the process of retiring my 2008 AD servers in order to raise our forest and domain levels to 2016. We already have 3 WS 2016 AD servers in our environment (1 at each location). I have about 4 2008 AD servers to retire before I can do that, so I have some time. There is only 1 forest/1 domain to be concerned about here. We're not tied to any other domains or forests. We are tied to O365 through AAD Sync. We currently use SYSVOL batch scripts to map drives.
What do I need to consider changing before raising the domain/forest level?
It only ever adds functionality, never removes any.
In every case you can go ahead and raise it. It's a myth that you need to be concerned about itOther than raising it to a level where you block your choice to move off of Windows. That's the only thing.
That's not going to be a decision management will support unless we can come up with an entirely new environment that will support all of our functions.
This doesn't make any sense . Linux is a drop in replacement here. So all of this is already supported. Windows and Linux aren't relevant to the discussion. The discussion is AD.
Totally understand that this discussion was about AD. I thought you were trying to turn the subject somewhere else.
People always like to claim that I do that, and the constant claiming that I do that has led more people to see things that aren't that as being that. It's something people repeat to try to make it look like I'm just spewing topics, because I often point out gaps in business decisino making making it relatively easy for people to overlook that I stayed more on topic than the people complaining about it.
I was 100% responding in the context of the question asked.
Okay. Calm down. I simply inferred that when you mean of a total migration from Windows to Linux, AD to Samba, mail, desktops/servers, everything. That is where I got confused at.
