Troy Knabe wrote:
On Oct 13, 2008, at 8:40 PM, P.S.M.Swamiji wrote:
Troy Knabe wrote:
We currently have the Sun Windows connector as the default
application but we are finding that every two minutes when the
Windows login times out the screen flashes. We have written a python
application that has buttons for windows login, and other
applications. When I go to "Advanced" and "Kiosk Mode" in the web
gui, I don't see a "New" button per the documentation.
It will be available only if the currently selected Kiosk session
supports the addition of applications as
mentioned in the documentation. SRWC kiosk session doesn't support
additional of other applications.
It would be supported JDS3/CDE kiosk sessions on Solaris.
Ok so if I select either a JDS3/CDE kiosk session then I can add my
application.
Yes.
By default to these two sessions still have no applications associated
with them?
Yes.
I don't want to give users a terminal window or other way of accessing
the server.
Also when I make this change it is essentially going to be like a cold
restart in that all of the clients will hit my servers at once right?
Not required. All the new sessions will get the new config.
If you want the existing sessions to get the new config kill them
individually or cold restart.
Thanks
P.S.M.Swamiji
Note:These are my personal opinions, nothing to do with my employer
Thanks for the help.
-Troy
Thanks
P.S.M.Swamiji
Note:These are my personal opinions, nothing to do with my employer
It has been a while (SRSS 3.1) since I set up CAM any help here
would be greatly appreciated, as this is now SRSS 4.x and in
production with 250 Thin Clients.
Thanks
-Troy
Here is from Sun's Docs.
procedure icon To Add an Application
1. Select the Advanced tab.
2. Select the Kiosk Mode tab.
If the currently selected Kiosk session supports the addition of
applications, there is an Applications setting at the bottom of the
page.
3. Click the New button.
a. To use one of the predefined Kiosk application descriptors:
i. Select Predefined Descriptor.
ii. Choose the relevant descriptor from the drop-down menu.
b. To define a custom Kiosk application descriptor:
i. Select Custom Path to use your own custom Kiosk application
descriptor or a system application.
ii. Enter the path to your custom Kiosk application descriptor or
executable.
If you choose Custom Path, indicate whether the path refers to a
custom Kiosk application descriptor or an executable by choosing
either Descriptor or Executable.
4. Select your preferred Start Mode for the application.
a. Choose USER to allow users to start the application themselves,
for instance from a menu or launcher item.
b. Choose AUTO to make the application start automatically when the
Kiosk session starts.
c. Choose CRITICAL to make the application start automatically when
the Kiosk session starts, to allow users to start the application
themselves, and to force the Kiosk session to restart if the
application terminates.
5. Enter any application specific arguments.
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
