Using RDS as a user desktop
in [Terminal Services]
|
Prev: TS Session Broker / License Server into a cluster
Next: Unable to login Windows 2003 server stuck at applying computer settings
From: Zaur Bahramov on 30 Nov 2009 16:44 Hi! I have a general question about usage of RDS. Currently we run Windows 2003 terminal services in application mode. We have several applications published which users connect to from their desktops. However, while we decide migration to Windows 2008 R2 I wonder whether it's OK to allow users to use RDS server as their desktops, instead of just publishing applications through RDS. I mean from practical, security and setup and configuration point of view. So far I've set up a session host and web access. Also I've set up a user experience to let the remote desktop be more nice for end users. So, I actually want to know at this stage whether this solution is good, or whether it's better just to publish applications and let users work directly on their desktops instead of using the RDS server desktop? Thank you in advance!
From: Soo Kuan Teo [MSFT] on 1 Dec 2009 12:06 Yes, it is quite a common deployment. If your users need to access full desktop to do their task, you can also let them remote desktop to the terminal server. -- This posting is provided "AS IS" with no warranties, and confers no rights. "Zaur Bahramov" <zbakhramov(a)msn.com> wrote in message news:O1ItcZgcKHA.2188(a)TK2MSFTNGP04.phx.gbl... > Hi! > > I have a general question about usage of RDS. > > Currently we run Windows 2003 terminal services in application mode. We > have several applications published which users connect to from their > desktops. > > However, while we decide migration to Windows 2008 R2 I wonder whether > it's OK to allow users to use RDS server as their desktops, instead of > just publishing applications through RDS. I mean from practical, security > and setup and configuration point of view. > > So far I've set up a session host and web access. Also I've set up a user > experience to let the remote desktop be more nice for end users. > > So, I actually want to know at this stage whether this solution is good, > or whether it's better just to publish applications and let users work > directly on their desktops instead of using the RDS server desktop? > > Thank you in advance!
From: Zaur Bahramov on 1 Dec 2009 16:30 Soo Kuan Teo [MSFT] wrote: > Yes, it is quite a common deployment. If your users need to access full > desktop to do their task, you can also let them remote desktop to the > terminal server. > Thank you very much for your input! So far I believe that the full desktop option is more convenient in my case. My aim is to make desktop management easier and more centralized. Also, computers where purchased in different periods, some are old some are new, different vendors, etc. So, going for RDS could resolve many hardware/software compatibility issues, I hope. What do you think about services provided with RDS in Windows 2008 R2? There're various options, session host and TS licensing are principal ones, while others are optional. We also think about providing users a Web Access which will enable them to connect to the RDS without having to establish a VPN first, which means I have to set up TS Gateway and TS Web Access. Did you experience any complexity issues with this services? Also, how about a TS Session Broker? I know it's required for load-balancing, but if I don't implement it do I still need it installed? Also, "session draining" that comes with TS Session Broker, is this the only "transparent" way to "switch" users to another RDS server while I need to make a maintenance on another? We have CITRIX MetaframeXP server on two of our Win2003 Terminal Servers. There's a possibility to easily switch users from one server to another, while they still have to logoff and logon once. How about RDS? IP Virtualization... Is it better to implement it or not (Our line of business application is MBS Dynamics Nav)? Sorry for so many questions from here and there, but I have to accomplish this project soon, and I don't want to miss something and have troubles after users will start using RDS. Thank you very much in advance!
From: Soo Kuan Teo [MSFT] on 1 Dec 2009 21:23 Have you got a chance to check out Windows 2008 R2 new role Remote Desktop Virtualization Host? It provides many of the benefits you are looking for such as desktop consolidation/centralization, software compatibility. For more info: http://technet.microsoft.com/en-us/library/dd759170.aspx http://blogs.msdn.com/rds/archive/2009/11/16/personal-virtual-desktops.aspx Thanks Soo Kuan -- This posting is provided "AS IS" with no warranties, and confers no rights. "Zaur Bahramov" <zbakhramov(a)msn.com> wrote in message news:u5zrz1scKHA.5796(a)TK2MSFTNGP06.phx.gbl... > Soo Kuan Teo [MSFT] wrote: >> Yes, it is quite a common deployment. If your users need to access full >> desktop to do their task, you can also let them remote desktop to the >> terminal server. >> > Thank you very much for your input! So far I believe that the full desktop > option is more convenient in my case. My aim is to make desktop management > easier and more centralized. Also, computers where purchased in different > periods, some are old some are new, different vendors, etc. So, going for > RDS could resolve many hardware/software compatibility issues, I hope. > > What do you think about services provided with RDS in Windows 2008 R2? > There're various options, session host and TS licensing are principal > ones, while others are optional. We also think about providing users a Web > Access which will enable them to connect to the RDS without having to > establish a VPN first, which means I have to set up TS Gateway and TS Web > Access. Did you experience any complexity issues with this services? Also, > how about a TS Session Broker? I know it's required for load-balancing, > but if I don't implement it do I still need it installed? Also, "session > draining" that comes with TS Session Broker, is this the only > "transparent" way to "switch" users to another RDS server while I need to > make a maintenance on another? We have CITRIX MetaframeXP server on two of > our Win2003 Terminal Servers. There's a possibility to easily switch users > from one server to another, while they still have to logoff and logon > once. How about RDS? > > IP Virtualization... Is it better to implement it or not (Our line of > business application is MBS Dynamics Nav)? > > Sorry for so many questions from here and there, but I have to accomplish > this project soon, and I don't want to miss something and have troubles > after users will start using RDS. > > Thank you very much in advance!
From: Zaur Bahramov on 2 Dec 2009 02:53
Soo Kuan Teo [MSFT] wrote: > Have you got a chance to check out Windows 2008 R2 new role Remote > Desktop Virtualization Host? It provides many of the benefits you are > looking for such as desktop consolidation/centralization, software > compatibility. > For more info: > http://technet.microsoft.com/en-us/library/dd759170.aspx > http://blogs.msdn.com/rds/archive/2009/11/16/personal-virtual-desktops.aspx > > Thanks > Soo Kuan > > Yes, I have read earlier about this role. However, this is not I need to implement at this time. VDI will be used only for particular users, as for the rest of users, they will use RDS. |