If you have a mixed environment of Windows XP and Windows 7, DO NOT, I Repeat DO NOT Upgrade to SP3.
It will break many of your XP deployments, because the new Driver Management is automated and relies on the integrity of the *inf files within your driver repository, you cannot guarantee that the drivers you had manually assigned and tested for in SP2 will be chosen by the new HII Client process.
In SP2 after many months of tesing and re-jigging of LANDesks way of doing things, I finally had a resonably stable OS deployment platform. Then along came SP3 and decided to throw a mighty spanner in the works.
I now cannot deploy any XP images, it constantly picks windows 7 drivers that do not work on the various models we have in use. it is a graphics driver that is causing the issue and even if you have the correct XP drivers in your repository, The HIIClient will still pick the windows 7 driver as being more appropriate!!!!
"Remove the offending Windows 7 driver" i hear you say, but that just breaks the images for machines that need that windows 7 driver. Amend the .inf file was the other fix....so what happens the next time we upload a driver that landesk cannot tell what OS the driver is for?
Unfortunately i am finding out the hard way of the need for a full DEV environment to test these upgrade on. Foolishly we accepted Landesk's version of events of over 20,000 tests were done on this Service Pack. If 20,000 thousand test were done, why did it take just one afternoon for us to find a bug and our support company recreated the issue in their labs. Even the support engineers gave a workaround to bypass the new HII process ( They were that confident in it, they didn't even try to fix it)
Back to the drawing board on HII LANDesk. Instead of designing things in a lab, design things in conjunction with a customer so that you can actually see what happens in the real world. If it wasn't for the fact that so much money was invested on this platform, i would have shut it down by now.
Sooooooooo not impressed