garethEds Posted October 14, 2008 Posted October 14, 2008 Hi, We are currently running RIS to build our machines and it works a treat. When the machines boot up we press F12 and it looks to the network to boot and build. All nice - no issues there. We now want to implement a thin client solution for older machines. We have the server, we have the machines and we have a few licences to play with. However we cannot find a way of getting the machines to boot into thin client - it wants to load into the RIS build. It seems we cannot boot a thin client solution over the network if we have something else to boot into (RIS) - is this making sense? Therefore we are considering running something called ThinStation to boot into the XP image. Is this the right way to go or can we set it so that it boots straight into the XP image and not affect the other machines that will need to boot into RIS. It makes sense in my head what I am asking LOL. Cheers GJE
GrumbleDook Posted October 14, 2008 Posted October 14, 2008 Have a search on the main forums and the wiki for Thin Station. Should answer your needs.
garethEds Posted October 14, 2008 Author Posted October 14, 2008 Have a search on the main forums and the wiki for Thin Station. Should answer your needs. yeah - should have searched first. Cheers GD GJE
ssiruuk2 Posted October 14, 2008 Posted October 14, 2008 incase you dont find your answer.. I got around this by having my pxe booting thin clients in a different vlan \ subnet and just put the relevant boot file info in the dhcp scope for the scope giving out the ip addresses to the thin clients. Thats way ris \ wds can stay on and the thin clients boot with no problem.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now