Page 1 of 1
Set up school network
Posted: Sat May 30, 2009 6:36 pm
by Crozz
I'm going to talk to my schools IT employees and see if he accept to run F@H at all 100-200 computers. Well, my question is then, how will I manage this?
I know, there is a lot of threads but I never got the answer. Shall I install F@H console on every computer or can we manage this via one computer? How?
Thanks!
Re: Set up school network
Posted: Sat May 30, 2009 7:47 pm
by John Naylor
It depends on whether your school uses disk imaging or not. If it does, then you just need to install the client on the disk image, and then delete the UserID from the registry. On each client's first start, it will download its own UserID and run in the background.
If your school does not use disk imaging, then you would need to install the client individually to each machine.
Re: Set up school network
Posted: Sat May 30, 2009 8:11 pm
by Crozz
Thank you for the answer.
But what do you mean by disk imaging? Never heard of it in my entire life :/
Re: Set up school network
Posted: Sat May 30, 2009 8:30 pm
by John Naylor
Disk imaging is where a computer has a standard setup installed, which comes with the OS and all programs already installed... Basically everything is already installed and that file is merely copied onto the machine and unpacked (usually over the network). That file is a disk image.
Re: Set up school network
Posted: Sat May 30, 2009 9:22 pm
by Crozz
Well yeah, I think its disk imaged then
Re: Set up school network
Posted: Sat May 30, 2009 10:26 pm
by compywiz
Considering most schools don't have the funds to buy high end computers, isn't loading an application that uses 100% CPU going to considerably murder those computers?
Re: Set up school network
Posted: Sun May 31, 2009 1:35 am
by jrweiss
No.
F@H only uses 100% of the CPU when so configured AND nothing else is using the CPU. When higher-priority (i.e., virtually ALL other) apps are using the CPU, F@H yields the cycles.
For lower-end computers where 100% F@H usage may cause a perceptible delay when yielding to a newly-opened app, reducing the CPU usage to 95% eliminates that delay in almost all cases (I had to go down to 85% on a P3/733)...