We have created a host that is running a version of windows 10 prior to the baked in end of flash date. Meaning this host can run flash so you can use it to connect to WFC. Since this OS version is not supported (nor is any flash version anymore) the host is heavily firewalled and access controlled. So only an allowed list of users can connect to it and once you have connected that host can only connect to whitelisted internal hosts and one external source, WFC. Since this needed to be win10 + flash this had to be a desktop OS version, meaning one user can connect to this host at a time. If another users tries to connect while it already has a session in progress it will warn you of who is connected and ask if you want to request the session. The already connected session will be prompted with an allow or disallow message.

• If allowed the current users session is terminated, the new users logon will be connected and they will become the current user
• If disallowed the current user’s session continues, the requesting user will need to reconnect later.

Because this can cause these conflicts it would be best to practice good shared resource management. Connect to the host to accomplish your tasks and logoff once you have completed them. This leaves the system in a ready state for the next user that needs to use the host. There are some limits to help keep this accessible:

• Active Sessions have a 2 hour time limit. After that time you will be disconnected and will need to reconnect to restart this timer.
• Idle sessions are logged off after 15 minutes.
• Disconnected sessions are logged off after 15 minutes.

To connect

1. Use the WFC shortcut on your desktop. You may need to perform a logoff/logon action if this has not already appeared for you.
   
2. Authenticate with your m# and password
3. Kronos WFC shortcut should be available on the desktop of the remote computer.
   
   
4. Disconnect your session when completed.