On 6/27/12 3:23 AM, Lin Yuan wrote: > Currently in AOO, only part of the data in user profile is locked and can > not access by mutiple instances. So as tested on Windows Server 2008, AOO > will crash in such situation. The patch is not to really support one user > to launch multiple instances on mutiple sessions case. According to the > suggestion in Windows 8 Certification below: > *Note*: If an app does not support multiple user sessions or remote access, > it must clearly state this when launched from this kind of session. > With the patch, AOO will popup a warning dialog and exit in this case. So > it will still not support mutiple user sessions for one user but the UX is > more frendly than the current crash issue.
we have to define fast if we want include it for 3.4.1 or not. It will require some translation effort that we have to organize in time (e.g. updating Pootle etc.) Juergen > > Thanks, > Lin Yuan > > 2012/6/27 Joost Andrae <joost.and...@gmx.de> > >> Hi Rob, >> >> >> >>>> but in a Windows Terminal Server session you have user profiles for each >>>> user. >>>> >>>> >>> This patch is for if you connect with Terminal Services twice using >>> the same user account. >>> >>> >> I just wanted to make sure that there is no real problem to get OpenOffice >> configured so it can be used within a multi user environment (MS TS, >> Citrix, Sun SGD, or UNIX profiles). If the same user connects a second time >> then there might be a locking problem with his profile data. If you want to >> fix this then it's OK but in my opinion it's not really needed because >> usually it should be prevented that one user accesses the same user profile >> from another terminal (RDP, X11) session. >> >> Just my two € Cents, Joost >> >> >
