Good day all,
I am in the proces of installing a brand new Windows Server 2012 R2 RDS farm. So far I have the Sessions host, broker, licensing, gateway etc all in working order. So I am moving on to the more complicated migration issues, about which I have a few questions. I hope someone can shed some light on these questions:
1. I have 150-200 users, most of them working currently on Windows Server 2003 terminal servers. The first thing I want to test, is to migrate the content of the TS profiles to UPD disks in Windows Server 2012 R2. I am going to copy all profiles to Windows XP, use a combination of Windows Easy Transfer, to transform the profile structure on a Windows 7 desktop and then copy the content of the new profile structure into the specified user mounted UPD. Is it possible to copy data into a mounted UPD file?
2. The two "main" applications, that we use are: Office 2013 and MS Dynamics NAV. Would it be best practise to install those applications locally on all the RDSH servers and then publish them using RemoteApp? Or would it be wiser to build an App-V Application server, to stream Office 2013 / MS Dynamics NAV to the RDS servers? The way I understand it, is that with RemoteApp I need to install all application on the Sessions Hosts, in order to publish something. With App-V I can stream from a different server (application servers). My preference would be to install all user applications on seperate application server, instead of having to install Office / NAV on 6 or 7 different RDSH servers. The idea is, that when I need to change something to these applications, then I need to do that on all 6 or 7 RDSH Servers. I prefer doing it on a single server, that will stream the changes to the RDS servers. What would be best for me to do?
Another reason why I want to avoid installing Office 2013 on multiple servers, is because of licensed plugins. We are using two Excel plugins, which have system based licenses. So the license works only on the local host. I need to redirect Excel users, using these plugins to a specific Terminal Server atm, which has the license installed. If I can stream Office from a single Application server, then I don't have to worry anymore about that license constriction.
Ingmar