> Management of these limitations has proven almost impossible for IT
> desktop support teams to sustain. Windows continues to crash and
> become corrupted. Desktops are almost never backed up, office
> desktops are unattended 18-20 hours a day, notebooks are lost, very
> few companies update Windows automatically or apply system and
> application patches to every computer religiously. And what happens
> when your desktop is slashdotted?
> Do you see any of these issues being completely resolved?
> If not, there is a clear role for K-Log servers and server farms to
> deliver reliability, availability, performance, and security. While
> these are not free, corporate and government IT rarely invest
> time or budget unless these are addressed. Designing the
> 4th Generation K-Log without addressing these baseline IT
> needs may interfere with acceptance.
*Excellent* points. There's nothing that says harnessing the power
of local desktops isn't a good idea. But, in practice, it often
turns out to be a tremendous headache. The single largest hassle is
*backup*. People turn the things off and all the tricks with Wake-on-
LAN and the like just don't work reliably. Taking this to the next
step would have the desktops *tightly* integrate themselves with
network resources that act as repositories or standby systems. This
runs afoul of a hurdle often insurmountable by technology:
That's going to take some doing to overcome.