A bit of a disconnect here. Multicast is for the host group
communication. DHCP/DNS is for DTU to contact a server. The vendor
class tags are a legacy item that I don't think many people involved
with the product favor their use.
A DNS for sunray-config-servers.FQDN when combined with parms files on
the Sun Ray Servers is IMO the best way to go. FW managemnet, server
select feature (for initial contact, Load balancer takes over after
that), and a bunch of other options from keyboard layout to compression
can all be handled without ever touching a DTU. Just need to keep the
FW files up to date.
http://blogs.sun.com/ThinkThin/entry/sun_ray_provisioning
[email protected] wrote:
On Thu, Jul 9, 2009 at 8:51 AM, Diego
Naufel<[email protected]> wrote:
Use an external dhcp server and add extended dhcp info on
that dhcp servers,
for sunrays, so no need to multicast searching servers.
Impractical here. We (the people who run the Sun Ray
deployment) don't operate the network's DHCP, and we've been
told that vendor extensions for DHCP clients can't or won't be
supported.
Or use vpn firmware, and configure manually each DTU with
servers info.
Also impractical; our Sun Ray plant is just too big relative
to staff for us to be able to hand-adjust each DTU. That's
part of what brought us to Sun Ray in the first place.
No, we're stuck using DNS for server discovery and feeling
lucky we were able to get that that much.
_______________________________________________
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
