Absolutely, Colin. The application must support being stored "in stasis" in
memory for the inactive user(s) as well as the active one. That is what that
documentation is all about. OP is confusing concurrent active user sessions
with concurrent occurences of an application. And actually, with the
application running entirely within the user environment, I understand that
for the program writers this requirement is much easier to implement.
--
Best of Luck,
Rick Rogers, aka "Nutcase" - Microsoft MVP
http://mvp.support.microsoft.com/
Windows help -
www.rickrogers.org
"Colin Barnhorst" <colinbarharst@msn.com> wrote in message
news:06EBA72C-D11F-43BF-82C4-BC0E1C9B7E8B@microsoft.com...
> Does fast user switching figure in here, Tom?
>
> "Tom Ziegmann" <tziegmann@nospam.msn.com> wrote in message
> news
C6C8534-9BBD-4521-84A6-744C0AD73797@microsoft.com...
>>I believe the Concurrent sessions is for RDP connections only, and I think
>> the "multiple application sessions" refers to machines where multiple
>> users
>> (i.e. family computers) may be logged on all at one time.
>> --
>> Tom Ziegmann
>> Microsoft Certified Professional
>> Windows Vista / Server Longhorn TechBeta Tester
>> Windows Server 2003 SP2 TechBeta Tester
>>
>