/build/static/layout/Breadcrumb_cap_w.png

SMS 2003 & OSD imaging

Hi,
We are using SMS 2003 and the OSD feature pack for imaging and deploying desktop and server images through the org. I've built and prepped a DL380 G5 server ready for imaging and created the SMS Image Capture CD with network and what seems to be the latest storage drivers. The CD runs and the server reboots ready to have it's image captured. It fails though just before the file copying starts stating the it can't see the hard disks and to load the correct storage drivers. The latest drivers have been downloaded from HP but no luck there. Any suggestions welcome ?

Cheers

0 Comments   [ + ] Show comments

Answers (2)

Posted by: dunnpy 16 years ago
Red Belt
0
sibot,

It sounds like a driver issue.

If you install your server OS manually from CD on this box - do you have to hit F6 and supply the drivers for controller, or does Windows just do it?

If you don't have to F6 it, then the OSD disk doesn't require additional drivers for storage, so don't specifiy any when creating your capture ISO.

If you do have to F6 - do the drivers you've given to the OSD capture work on a manual (F6) install?
This would be a way to test your storage drivers are correct before going through the process of creating an OSD restore disk, only to find the drivers are incorrect - you'll end up with a stack of coasters [:D]

Incidentally - there is a tool out there called PE2USB, which will blow a mounted ISO onto a USB pen drive to allow you to boot from this, instead of CD (hardware permitting) - which again saves on the amount of wasted CDs.

Hope this helps,

Dunnpy
Posted by: sibot 16 years ago
Yellow Belt
0
Cheers for the info....yeh defo some form of driver issue.

Haven't tried the W2K3 CD yet as the server was built initially from the SmartStart CD, but will give it a go. From experience on the Dell servers, I'd expect to it to ask for the drivers.

I have mailed HP regarding the issues and they mailed back links to the latest storage drivers for the DL380. These have been tried using the F6 and a floppy disk approach...so far it still errors! The 2 message received are either "disks not found" or the <drivername>.sys cannot be found...yet is there larger than life!
Will try a few of these options further.

PE2USB - good idea, i should have used that before but there again, didn't think i'd be using so many CD's

Thanks.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ