Hello Maciej! Maciej Zawado schrieb: > Hello Everyone! > > The landscape is: > - mostly PC-based Active Directory network > - few thin clients connected via RDP to Microsoft Windows Terminal Server > - DHCP for client configuration > - no PXE machines yet
Perfect. > My thin clients does not always want to connect to Terminal Server, so I > want to try to boot them with OpenThinClient and then connect to > Terminal Server. I am not an expert with network services like AD, DNS Fine. To use network boot with OpenThinClient you will have to activate the network boot ROM of the NIC. The necessary steps for that depend on your thin clients (what brand and model are you using?). Often it works like that, here as example a TC with AWARD BIOS: - enter BIOS by pressing DEL, F1 or F2 - go to integrated peripherals and activate the boot rom - it might help to make the boot screens visible - F10 to save and exit - now during the BIOS phase press Shift-F10, Shift-Tab or whatever combination your manufacturer has chosen to enter the NIC BIOS - change "BIOS disabled" to "INT 19 - Network boot first" or something like that. - often it is F4 to save and reboot. Voila, now you have a TC booting via PXE. Now, you have to install the OpenThinClient package on one of your servers in that network (ok, for testing you could also use your PC). > and DHCP, so my question is - can I run OpenThinClient server in my > existing enviornment without affecting non-PXE clients and existing AD > and DHCP servers? I can not make any changes to that enviornment and I Yes, certainly. All you need is that the DHCP server issues an IP address to the thin client. You don't have to (and must not) add special options like 66 or 67 (on windows DHCP). > don't want to cause disaster by installation of OpenThinClientServer. That is most unprobable. OTC does not modify anything in your existing environment except adding network services that can be shut down at once should you ever experience problems that you attribute to your change (but this, too, is not likely). > I'm not sure how OpenThinClient will interact with my Acive Directory > and DHCP servers - would standard PCs still connect to AD and DHCP I repeat: it will not change anything there. > servers after OpenThinClient server installation? Some how-to about Sure. > integration OpenThinClient server with Active Directory would also be nice. At the moment we can use AD to lookup and authenticate users. But for your setup that should suffice. > Thanks for help. > Maciej Zawado -- Bye, Tobias Abt levigo systems gmbh ----------- ein unternehmen der levigo gruppe Max-Eyth-Strasse 30 Telefon: 07031 / 4161-10 D-71088 Holzgerlingen Telefax: 07031 / 4161-11 Geschäftsführer: Oliver Bausch http://systems.levigo.de/ Registergericht: Stuttgart HRB 245 180 USt-ID: DE813226078 ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ The Open Source Thin Client Solution http://openthinclient.org [email protected] https://lists.sourceforge.net/lists/listinfo/openthinclient-user
