>________________________________ > From: Craig Bender <craig.ben...@oracle.com> >To: sunray-users@filibeto.org >Sent: Wednesday, April 17, 2013 5:13 PM >Subject: Re: [SunRay-Users] Oracle VDI + Sun Ray and Microsoft DHCP > > >Did this previous company implement vendor class options (aka Vendor >Tags) That's "the old" way, and requires a lot of work to maintain >(where as if doing the same on the Sun Ray Server itself, utfwadm does >this for you). Note that these options are not the standard DHCP >options, and the option numbers don't line up what most are familiar >with. These vendor class options are fully documented here: >http://docs.oracle.com/cd/E35310_01/E35309/html/Alternate-Client-Initialization-Reqs-Using-DHCP.html#Alternate-Vendor-Specific-DHCP-Options > >However, I can't stress enough, that this is *not* the way to do things. > You have to fully understand DHCP, again, these are not standard >options, they are client options for a vendor class of SUNW.NeWT.SUNW. > >The best bet (and far easier than dealing with the above) is using >either standard DHCP option 66 or the DNS name of >sunray-config-server.fqdn, both of which eventually points to a tftp >sever that houses the parms files. In the parms file, you can control >where the Sun Ray gets pointed to for sessions, along with many other >configuration options such as firmware versions. > >Option 49 is OK, but you don't get firmware management with that, itjust >points the Sun Ray at a server. > > > Thank you Craig, I'll check that link. One question about the parms file, is there a standard configuration or is this file created when I activate the DHCP on a SRSS Server?, I ask you this because there isn't any parms file inside the folder /tftpboot. Thank you again for your time, Christian Montero H.
_______________________________________________ SunRay-Users mailing list SunRay-Users@filibeto.org http://www.filibeto.org/mailman/listinfo/sunray-users
