I did setup an interconnect. I ran the command utfwadm -Aa -N all -G force to enable the GUI firmware to be pushed out. I can now open the Gui on the 2FS.
I also learned you can push out the Sunray server ip in DHCP specifically with Option 49 in the DHCP scope. None the less putting it on a private interconnect and pushing out a GUI firmware with utfwadm worked 100% thanks everyone for the suggestions. On Wed, May 23, 2012 at 12:28 PM, Craig Bender <[email protected]>wrote: > Could you please answer the question about the current version of > firmware? If you setup a private interconnect, then it should be handing > out firmware. By default it will be the non-gui version. But if the unit > has firmware that is newer than what you have, you'll have to follow the > steps in the admin guide to downgrade the firmware. The commands are also > in the admin guide to tell the client to use the GUI version of the > firmware. > > > On 5/23/12 7:17 AM, Jeremy Loukinas wrote: > >> I set them on a priv interconnect and via DHCP was able to point them to >> a test Sunray server. How would I go about pushing a GUI firmware out so >> that I can enable the menu on the thin client itself? >> >> The reason for going through this is I will not be able to have a >> private interconnect for these I will need to manually configure each >> unit to point at a different subnet for their server. >> >> On Tue, May 22, 2012 at 3:22 PM, Jim Klimov <[email protected] >> <mailto:[email protected]>> wrote: >> >> 2012-05-22 22:18, Craig Bender wrote: >> >> If you have Sun Keyboard, what does stop+v report? How do you >> know you >> have the GUI menu? Stop+C would clear any configuration. >> >> If you setup a private interconnect and use a small hub or >> crossover >> cable, you can put any firmware on there since the Sun Ray >> Server will >> control the DHCP and use vendor class tags. >> >> >> @Jeremy: It is possible that the DTU not only connected to a specific >> SRSS server, but also had static IP configuration, in its previous >> life. In this case it might be useful to try and determine that >> addressing (i.e. by sniffing on the private interconnect - which >> itself is the way I'd go too), and also set the target server's >> IP address 66.22.xx.xx on your server's interconnect interface. >> >> Craig, is it possible that a GUI firmware was installed, set up via >> menu, and then a non-GUI firmware was installed - but the settings >> saved into Flash remain in force? I guess in this case there would >> be no way to override that setting except by reflashing the firmware >> using the interconnect, as you suggested first :) >> >> HTH, >> //Jim >> >> ______________________________ _________________ >> SunRay-Users mailing list >> [email protected] >> <mailto:SunRay-Users@filibeto.**org<[email protected]> >> > >> http://www.filibeto.org/ mailman/listinfo/sunray-users >> >> <http://www.filibeto.org/**mailman/listinfo/sunray-users<http://www.filibeto.org/mailman/listinfo/sunray-users> >> > >> >> >> >> >> ______________________________**_________________ >> SunRay-Users mailing list >> [email protected] >> http://www.filibeto.org/**mailman/listinfo/sunray-users<http://www.filibeto.org/mailman/listinfo/sunray-users> >> > ______________________________**_________________ > SunRay-Users mailing list > [email protected] > http://www.filibeto.org/**mailman/listinfo/sunray-users<http://www.filibeto.org/mailman/listinfo/sunray-users> >
_______________________________________________ SunRay-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sunray-users
