Amazing to me that the odds are that small we should survive. Considering all of the 100 year periods the human race has already survived, you'd think that, statistically, we'd already have eaten a bullet many times over!
I never used any cloning features, so actually can't speak to that function.
We use a manual method with spare PC's to swap in as needed. Our techs use an image to dump to the HD using PowerQuests DriveImage.
I did all of the application deployments and a wide variety of system change deployments, quick fixes to combat worms and other issues, etc. I'd even created a process that would package an in-house Java app that gets monthly updates to create the NDS application object without needing to do a snapshot of an install. It was actually fun for a while, but did get boring.
Price, I can't actually speak to. I would like an omlet every morning, though. Maybe when we renew our LANDesk contract. Sales weasels will promise anything for a comission.
What's nice is this: I was getting about 98-99% success rates on app deployments using the snapshot tool and careful planning. It's easy to create a bad deployment. Consider the complexity of delivering to PC's that are running various DLL versions, modified registries, different software installs, etc. Software install snapshots are an imperfect solution since they assume virgin cloned PC's. It appears simple when it works, it gets ugly quickly if not tested well and watched over.
Novell has done some things very right (marketing and user interfaces not being among them) I used ZenWorks for a few years to manage and deploy applications to about 500 NT clients. It's very polished and powerful. Being very empowering, it makes it very easy to do lot's of stupid things quickly to lot's of clients.
Would port fowarding not get around your broadcast address requirement?
A pointless point to make anyway, I think, since CAIDA also claimed SCO's FTP servers were attacked. It wouldn't matter how you reached it, you did reach it. As I understand it, some folks were getting very snappy FTP connections. Hmmmm.
Slashdot Mirror
..more than 1000 billion degrees.
Aw, damn. I always thought it was a hundred gazillion bazillion degrees. Isn't that just 1 trillion to us laymen?
...but the point still stands well. This is cheap and works. At this price point, paying for a second setup would still be effective.
Amazing to me that the odds are that small we should survive. Considering all of the 100 year periods the human race has already survived, you'd think that, statistically, we'd already have eaten a bullet many times over!
:) Entertaining, they are!
Whacky doomsayers.
I never used any cloning features, so actually can't speak to that function.
We use a manual method with spare PC's to swap in as needed. Our techs use an image to dump to the HD using PowerQuests DriveImage.
I did all of the application deployments and a wide variety of system change deployments, quick fixes to combat worms and other issues, etc. I'd even created a process that would package an in-house Java app that gets monthly updates to create the NDS application object without needing to do a snapshot of an install. It was actually fun for a while, but did get boring.
Price, I can't actually speak to. I would like an omlet every morning, though. Maybe when we renew our LANDesk contract. Sales weasels will promise anything for a comission.
What's nice is this: I was getting about 98-99% success rates on app deployments using the snapshot tool and careful planning. It's easy to create a bad deployment. Consider the complexity of delivering to PC's that are running various DLL versions, modified registries, different software installs, etc. Software install snapshots are an imperfect solution since they assume virgin cloned PC's. It appears simple when it works, it gets ugly quickly if not tested well and watched over.
Just plain silly.
Novell has done some things very right (marketing and user interfaces not being among them) I used ZenWorks for a few years to manage and deploy applications to about 500 NT clients. It's very polished and powerful. Being very empowering, it makes it very easy to do lot's of stupid things quickly to lot's of clients.
Blame the one who wielded the tool, not the tool.
Have we found one of the lost landers still looking for a place to park, close to the entrance?
Would port fowarding not get around your broadcast address requirement?
A pointless point to make anyway, I think, since CAIDA also claimed SCO's FTP servers were attacked. It wouldn't matter how you reached it, you did reach it. As I understand it, some folks were getting very snappy FTP connections. Hmmmm.