mcoyne Posted September 11, 2017 Posted September 11, 2017 Hello! We are a mostly Server 2008 R2 environment but due to needing to set up a new file server fairly sharpish, I thought I may as well plan ahead and do this on server 2016. Can you think of any potential problems that I might need to know about with putting a 2016 file server in an otherwise 2008 R2 domain environment? Thanks! Mike
NB9457 Posted September 11, 2017 Posted September 11, 2017 I've used it alongside 2008R2 and 2012R2 as a file server with no issues at all.
FragglePete Posted September 11, 2017 Posted September 11, 2017 Running alongside 2008R2 and 2012 with no issues. I also have a mix of DCs running both 2012R2 and 2016 - again no problems. Looking to sort out the remainder on the DCs to 2016 in the near future so we can migrate over to the new replicated/sync/DFS thingy that 2016 has. (sorry, forgotten what its called at the mo!) Pete
caffrey Posted September 11, 2017 Posted September 11, 2017 I was going to do this last Christmas, but the server I used didn't officially support 2016 (Supermicro) so I stuck with 2012r2
mcoyne Posted September 11, 2017 Author Posted September 11, 2017 Hellooo, Thank you very much for your input - that's reassuring! Thanks! Mike
DCUK6 Posted September 12, 2017 Posted September 12, 2017 Had a 2008 R2 with 2016 FS in my last place, that was rock solid. I use de-dup for backups but never in the server. If you have roaming profiles with folder redirection, check out my thread on the 2016 server forum regarding profiles. Just moved server and had a issue as i turned the old server off.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now