Vista: The Death of HII(or at least a dramatic shift)
paul.e.dearment.jr| May 15, 2007 10:13 pmI’ve been hit by the coding bug recently. I don’t know, but summer seems to be the time when me and programming re-ignite our love affair with each other. While coding, I get a lot of time to think. To think about fun items. To think about projects, life, etc… And while coding my project today, I started to think back to a webcast that an Altiris Consulting company put on a week or two ago. They were touting a third party product for doing Hardware Independent Imaging. During the course of their presentation, they mentioned that they would soon have support for Vista. That got me to thinking. Once Vista hit the main stream, how much would HII really benefit enterprise clients? Currently, this is a huge item for enterprise customers to do, as it allows them to have one image to deploy across multiple hardware platforms. Thats good for XP which has a HAL which is specific to the hardware. But Vista is a different beast! At the core of it all, Vista is Hardware Independent when rolling out the image. Wait. What? Vista(when deployed with their method–have to try with Altiris sometime soon…hmmm…I’ll get back to you all on that one….) is by nature hardware independent. No longer do you have to worry about if you have a uniprocessor hal, a multiprocessor hal, a hal for a hyperthreading desktop, a hal for a non-hyperthreading desktop. Its all the same.
So with this little “advent” that Microsoft has brought to the imaging world, where does that leave HII? It leaves it at driver deployment. If you do HII as suggested by Altiris in their white paper, you will get a fully functional computer. You won’t get(however) all the little specifics and customizations that you would want to do for all the images. For example. When installing Nvidia drivers, the drivers install perfectly with no problem. The situation arises when the client wants to use the Nvidia control panel. Well, depending on if the drivers were signed or not, you may or may not have the panel. Also, the panel would not be added to the right click context menu for clients. I know not many people use it, but those one or two that do…… You also wouldn’t get any of the registry keys entered under startup for any helper processes the drivers rely on when the computer starts…so you’ll have to manually(read: WITH A SCRIPT) install those registry keys for the client.(otherwise the drivers won’t work properly)
Another problem with the white paper is the lack of customization as far as applications go. Sure, you can run the installer after the HII is done with an Altiris job, but it fails to mention a small bug in Altiris where either
- Altiris looses track of what process is running on what computer, and unable to detect when that process is done and to move on to the next one.
- Altiris sometimes forgets to wait for data to fully finish downloading before it tries to run executables, which results in “corrupt” installs of the software
Those are kinda annoying, and can bring the whole process to a grinding stop. (as an FYI, I’m doing a thing on HII at http://www.armentpau.comon how to make HII super customized and more than just a driver delivery method, and how to deliver drivers in such a way that you don’t miss any of the extras that the driver installs) So with HII being a driver delivery method(in the near future), I can forsee a lot of companies getting mad that they have started to invest a lot of money into HII images. For a company(corporation) they can afford to have one image across all computers(read: same software load) wheres where I am currently employeed, we have different software loads based on the location of the computer as well as the role(student versus administration images) that the computer will be used for. Current white paper specfications leave little to nothing for the customization of these situations. They provide for the drivers and let you do the software afterward(or have all the software already installed for EVERYONE).
Because of this, I predict that we will start to see a major shift in what HII means. The focus will move more towards application deployment with the deployment of (initially) on the network driver, with the rest of the drivers being installed along with the applications. This process might be rough at first, but I predict it moving along and eventually being done seamlessly while using one base image across all computers in such a manor that it is streamlined as well as efficient(again, Vista being HII at heart makes that part easy(again—I will check whether it holds true when Ghosted or Altirised). Ok. Enough ranting from the old man who loves HII. I should get going. I got some things in TIMS to figure out how/what to do with.
Categories: Technology
No Comments »
