It brings nothing to the table that ZEN does not, so I can't justify spending money on it.Īnd to stop students from making changes on workstations and destroying them? Stop allowing them to boot to the BIOS to format everything first off. I also have yet to see Ghost do half the job that ZEN does from an imaging standpoint, but that's just my opinion.
#Deep freeze software name windows
It's just that the software was *made* to be managed from a workstation that boots into Windows in order to talk with the actual "Ghost server". Let's not split hairs on Ghost (which wasn't my intent either) I know it can also utilize pre-emptive boot services using the NICs as well. And yes, I know that you can go to the workstation and physically boot it with a CD or disk, but then again, you would never have to do that if you used ZEN Imaging. Plus, Ghost doesn't do you any good if the workstation won't boot into Windows.
So, to manage your network, you need the ConsoleOne management utility, DeepFreeze MU and a Ghost Enterprise MU.
Or you could add yet another management console to your arsenal to manage workstation imaging!? :no: No way. And of course, you can manage the entire workstation through ConsoleOne. ZEN already does it for you with a Linux partition. Another waste of money in my opinion again. Most network use Ghost and I just don't see the reason. So.do you push out the defs into the Thaw Space? Or create the Symantec software in there so you don't get these results? Either way, it's a headache to me. That means every time the workstation starts up, excessive traffic is on the network simply because it constantly has to push out new definitions and updates. Symantec will push out virus defs to these workstations all the time because they will get erased upon reboot. Let's take Symantec, for the sake of argument again since it's familiar.
#Deep freeze software name update
What do you do to update virus definitions on the workstations? If they are being "cleaned" from possible virus infections on reboot, what do you do when 500 XP workstations get infected with Nachia and bring your network to its knees? It's still a reality until the workstations are rebooted. I go to schools where people use this software and it becomes quite simply, more to manage. If you are using a Novell network (and I'll keep it straight with Novell because I started talking about schools here) along with ZENworks 3.2 or 4.0.1, I simply don't see the need. Let me tell you exactly why: (and forgive me if I ramble) Used in conjunction with any imaging software (like Ghost) and life suddenly became enjoyable. If anything, it will save you money in manpower, time, and network usage by NOT having to reimage all your machines. If you're administering some +1000 machines, I fail to see how having DF installed is a waste of money. Tedious process and by no means efficient. Blowing away all the software changes after we had the results we needed Making the changes on the workstation with the program recording the application install. Reinstalling the app needed to make the application "snapshot" if you will. The only way to stop this behavior was to go through the tedious task of: While checking out the changes made to the workstation, all 3 apps failed every single time in the same spot, which was the DeepFreeze folder on the local machine. They all serve pretty much the same purpose, which is looking at changes before and after an application installation is done (Wise does more than that, but we used it for that purpose) 3 prime examples were Wise for Windows Installer Ghost Autoinstall (which of course comes with Ghost Corporate Edition) and finally Novell's ZENworks snAppshot applet. We had problems with installer-based software, and gave them reproducible results which they were aware of. We had to inform them that it was problematic, which they wholeheartedly agreed to.
It doesn't interact at all with the workstation until reboot.You can do whatever you want with it and it could care less.By design it shouldn't. Deep Freeze does not interact w/ any installers whatsoever.
0 kommentar(er)
