Multiple Rdp Sessions Software
Imke
Is there any way to have multiple sessions running at the same time? I want one season blocking certain apps all day on the deep focus mode, but then another session for the rest of my apps on the normal mode.
We started to release [Planned] Time Limit / Budget use of distracting apps as an AB test so a small portion of you are able to test it, but we plan to release it to everyone within the month of January.
Hello, can two sessions run simultaneously as I tried to run two sessions where they overlap each other but one session finishes at a different time compared to the other but it did not work for me and only one session was running and the other started running once the first session finished
So eventually all class members for the object t are shared among all clients, and in this example for instance tags_pd is the same for all clients, although I would like them to be independent between sessions/users. Does this explain a bit better?
Yes, that explains it perfectly. As you declare the object t in the module scope, it will essentially be a global variable. Which results in shared state between clients (best case) or simply inconsistent behavior depending on the deployment setup. This is why this approach is not recommended.
If you need to share the object t between callbacks, you should save it to a Store component (or similar). And yes, that requires making the object JSON serializeable. There are other options (e.g. server side caching), but I think that you should consider revising the design of you MyApp in any case.
Hi jokin,
I am currently struggling with the same problem you once had some time ago. Did you rewrite your app as suggested by Emil? Could you share some lessons learned?
If I would create a class object within a callback, would this lead also to a stateful situation? As I understood, global scope on module level is the problem. But instantiating in callback too?
Hey there WC gurus, I've worked in different CAD/CAM packages before that would allow multiple sessions to run without tying up additional licenses. This would allow you to be working on multiple projects at a time. Especially when loading a model, updating or saving takes a while, it's nice to be able to work on a lower end project like updating some hardware or adding some finishing touches.
If there is a way to allow this in CREO 2.0, this would be great.
They took, what I call, the bad habit to open several sessions of Creo (ProE at that time) for the reasons you mentioned. At that time we were with Intralink for some and others without any connection to any database.
My question is about how to force CREO to only use 1 license for multiple sessions. As I mentioned, I know this is possible when I have a checked out license, so it should be possible to do with network licenses.
I was formerly a CATIA V5 and ENOVIA PLM instructor and CATIA would allow you to run multiple sessions on a single license and even maintain connectivity to ENOVIA. Now, ENOVIA handled PLM a little different and much better than Windchill does, but that is a different discussion.
Say you have a part in a complicated assembly that has assembly references. Let's say that some part has dramatically changed and now you have a part that has missing references all over the place and you need to babysit this 1500 feature part in as short a time as possible.
So you open a second session of pro/e...er I mean... creo, and open ONLY the part that's failing. Because it does not have the assembly or other parts in-session, the geometry references won't update. you can walk from feature 1 thru 1500 and see exactly how a reference or feature impacts the rest of the model. It's beneficial to know what the failing feature has referenced, but sometimes it's even more beneficial to be able to see what that feature does down the line when it's not failing.
It's definitely not the most fun way to repair messed up parts, but there are occasions (once or twice a year) where you're working on someone else's part and it's turned into a cluster f because of bad references, or missing parts. sure you can be a stickler and ask them to fix it, but often that's not as cost effective as just fixing it fast and dealing with it. and besides the creator might not even be in the picture any more, and I'm not about to go recreate a 1500 feature part just because it's not "elegant". If the geometry is good for tooling, then I'll get it done however I can with the least pain. SxS sessions are sometimes just that - the least painful way to repair things.
A node locked license will allow unlimited local sessions on that one computer. On the other hand, a floating license will only allow a single session. Starting additional sessions will pull additional floating licenses. Borrowing a floating licenses makes it act like a node locked license for the duration of the borrowing period.
When I have 2 sessions of same app openened ( in 2 chrome tabs of same window), I realized that when I make some selection in one app the selections reflect in the other tab of my browser.
I want the 2 instances to be independent of each other ie. I want to make selection in one tab and the other brower tab where i have same app opened, shouldn't inherit.
Try to avoid any polling in bindings in Perspective itself. Rely on the fact that bindings will refresh when a referenced tag or other property changes. Anything that needs to refresh on a schedule should happen in the gateway, not in Perspective. That way it only has to be calculated once for all clients.
My group has been having the same issues with CPU usage and latency on the loading of multiple perspective screens. We are pretty sure it has to do with the binding in our value indicator templates as well.
Recently in the past week and now this week as well. We've seen multiple users with multiple sessions (one active and other disconnected) to different session hosts in the same host pool with the breadth-first load balancing. Where it should only allow 1 session at a time to any session host in the host pool, and when trying to reconnect, it should always try to connect to the same session host it was previously connected to and not a new one.
This has caused issues with our remote app as customers have an active session to the application with their first AVD session and not able to get back into the application with the same user login (user login for application) because the new AVD session is on a different session host with a different id. If that makes sense?
Also, this started after we implemented FSLogix. Currently happens to one resource (Host pool) at a time. Started with one resource (host pool) and went on for a week, first host pool is okay now and then it started on another resource (host pool) and there for a week now.
They would open the Remote app again and it would launch the WVD session but our program would report that the user was already logged in, which is what it is meant to do if the user was logged in already.
We also saw ourselves, and random reports from users that upon relauch, the app was very degraded, which there are multiple reports of already (what appears to be 8-bit color scheme, missing buttons, icons, loss of function)
There you see the same WVD user listed twice. some case it can be 3 or 4 times. (i can make it climb to 8 and higher if i manually replicate by disconnecting my WVD session with the Remote Desktop Icon in the task tray in windows, then log back in, it just keeps stacking more sessions.)
I'll make an official feature request. I'd like to be able to execute multiple commands to ssh sessions. For instance after splitting 2 ssh's I want to have an button to engage multiple commands so all my key presses are send to all seen (splitted) terminals.
I have host 1, 2 and 3 SSH opened (ad-hoc or normally doesn't matter). Now I split the window to have 1 left and 3 right and see them both. Host 2 is on left window but left I see host 1. Then I want to have a possibility to send commands to both host 1 and 3 (but not 2 as it is not seen).
Thank you. Another feature available I didn't find. Key sequence broadcaster-panel... sounds like I can shoot rockets to moon with this panel but just wanted my keys executed to all open connections. But the idea behind absolutely makes sense: open a panel and getting keys to multiple terminals. Nice!
I'm afraid that implementing those conditions is not possible. The broadcaster is very generic and actually not aware of the session type. All it does is sending the keystrokes to the session, regardless if it's a terminal, RDP, VNC or web connection. So the panel isn't aware of any context and has no way to process any of the session's state.
Stefan, or anyone. Is it possible to change the key sequence broadcaster settings to just press ENTER to send to everything instead of CTRL + ENTER? It's very hard to get use to that and honestly kind of annoying. If it's not something that can't be changed I would like you guys to add that as a feature please.
@Robert: Although the feature is implemented differently, I think what you're looking for is "Broadcast Input to all Terminal Sessions" in the "Tab" menu of an active terminal connection. When this is enabled, all input will be broadcast to all other open terminal sessions.
I need to run multiple R sessions, and hope that they can be performed in different R sessions. In Windows, I am able to open an arbitrary number of R sessions, and run different codes in each session (both RGui and RStudio). However, in Mac OSX, neither R.app nor RStudio would allow me to open multiple independent sessions -- I have to wait until the first set of R codes are completed in order to run a second set of R codes.
It could be frustrating when I have to temporarily switch to another project to work with in RStudio Serverwhile the current session is still useful to keep. However, multi-session support is part of RStudioServer Pro but not the free version.
c80f0f1006