Even after you change the icons for your RemoteApp published programs on the RDSH servers, your icons on RDWeb may not change. This happens because RD Web server caches the icons as images. If you delete this cache, the icons are downloaded again from the RDSH servers…the next time someone launches any RemoteApp.
Here is what you need to delete on your RD Web server:
If, even after the cache delete, you do not see the icon, try this little trick:
Either remove and re–add the published application or change the published application’s alias.
Delprof is an excellent program to delete your users’ profiles:
By the way, if you want to do all this manually, here is the procedure for that:
Additionally, you may want to delete the roaming profiles on your central file server. It is usually difficult to to that because the files are in use. I use a nice little utility called unlocker for that.
I run this FOR loop on a command line on the server hosting the roaming profiles:
cd C:\Program Files\Unlocker
FOR /D %G in (“E:\Shares\Remote Desktop Services\Profile\*”) DO (unlocker “%G” /D /S & timeout /t 30 /nobreak)
Note that if you have a lot of profiles, it will take a long time!
First, why am I using 2008 R2 in year 2014? Well, because some of our applications are not supported on 2012 R2 and I cannot mix and match 2008 with 2012 in a RDS farm.
So here is the quick and dirty guide (no VDI, yet):
Here are the servers you need:
- RD gateway + RD web access (in DMZ)
This provides web access to RDS on the public internet.
- RD Connection broker (in internal network)
This routes everything. I am going to install the RD license server role on this one as well.
- RD Session Host (in internal network)
This is the actual terminal server where applications are installed
Once you have all these three servers in place, install the appropriate roles in them. I will just give a cheat sheet of things you need to do to make it all work.
Continue reading “Quick setup guide to Remote Desktop Services on Server 2008 R2”