That should eliminate the need for running the program in non-intrusive mode. Presumably it will then be possible to specify PXE and TFTP requests to go to our FOG server. However the network administrators have expressed a willingness to put the machines we want to control on their own subnet and give it a separate DHCP scope once we go into production. This would tend to be an issue since PXE boot requests are presumably set to be forwarded to the existing WDS machine. Currently the library computers are not on their own subnet. There are also wireless routers on the second floor although none of our public machines connect to the network that way. Presumably these are for the wired portion of our network.
#Deep freeze mac forum series#
However there are racks of Cisco Catalyst 3500 series network switches in various locations around the library. Second, what sort of security risks does having a FOG server present to the campus network? Although the machine we are planning on putting it on will not have an external IP address I am concerned all the same since Apache is require to run FOG. Also our public computers are set to boot from the network first and, despite not being on the domain, are on the same subnet as other public computers around campus. However networking is not my strong suit. If there library were to set up a FOG server, would it create any sort of conflicts? Given that the program uses MAC addresses my assumption would be no as long as it is set up correctly (that is the impression the user guide gives anyway). They image machines via PXE boot, although I do not think their system can do Zero Touch Installation.
#Deep freeze mac forum windows#
First, our campus IT people have their own server running Windows Deployment Services. FOG seems to be the answer to all of our prayers.Įxcept for two things. When imaging machines we use Clonezilla and have to go around to each one with a flash drive.
#Deep freeze mac forum software#
Thus there seemed to be no way to do things such as push out software to computers, image them remotely, and track usage. We also do not have a server other than a dedicated machine for our catalog and the budget is tight. The difficulty is that the library is not a part of the campus domain (but is on the network) and all of our computers are in a WorkGroup.
At the same time we have been seeking a way to centrally manage our computers. Since Microsoft discontinued SteadyState the Library has been sticking to XP, but with support ending in April we can hold out no longer and are in the process of transitioning to Windows 7. We use Windows SteadyState to lock them down and prevent unwanted changes to the machines (including everything from malware to patrons cluttering up the computers with files). We have 70 -100 public computers (Dell Optiplex 780s) currently running Windows XP. I am the Systems Librarian for a mid-sized regional University. Though convinced of its awesomeness, there are a few questions that remain. Over the past few days I have been researching FOG.
0 kommentar(er)
