F5F Stay Refreshed Software Operating Systems Moving Active Directory users from Server 2008 R2 to 2016

Moving Active Directory users from Server 2008 R2 to 2016

Moving Active Directory users from Server 2008 R2 to 2016

E
Experimentl
Member
199
08-15-2016, 02:03 AM
#1
Hello, We manage several TS servers for our clients to run our applications. Previously, moving a customer between two 2008 R2 servers was seamless, keeping their settings intact. Now that Microsoft no longer supports 2008 R2, we needed to make a migration. Transferring users from a 2008 R2 to a 2016 server stopped the automatic copying of preferences from the folder I described. My ideas are: 1) The transfer isn’t compatible due to significant technological differences, 2) Activation in Active Directory (now on Windows 2016) might be required for backward support, and 3) Language differences could play a role—perhaps the user directory name varies by language. Any advice would be welcome. Thanks!
E
Experimentl
08-15-2016, 02:03 AM #1

Hello, We manage several TS servers for our clients to run our applications. Previously, moving a customer between two 2008 R2 servers was seamless, keeping their settings intact. Now that Microsoft no longer supports 2008 R2, we needed to make a migration. Transferring users from a 2008 R2 to a 2016 server stopped the automatic copying of preferences from the folder I described. My ideas are: 1) The transfer isn’t compatible due to significant technological differences, 2) Activation in Active Directory (now on Windows 2016) might be required for backward support, and 3) Language differences could play a role—perhaps the user directory name varies by language. Any advice would be welcome. Thanks!

S
shapeshifter1
Member
51
08-15-2016, 02:43 AM
#2
This app is developed by a specific team. Have you reached out to their support for assistance? It seems like a vendor-related matter.
S
shapeshifter1
08-15-2016, 02:43 AM #2

This app is developed by a specific team. Have you reached out to their support for assistance? It seems like a vendor-related matter.