Rick,
I may have been a bit harsh...sorry bout
that.
We did encounter a similar issue with running SS 6.x on
older hardware (like the 3xxx series, 5500, 8000's, G1 series etc), and
yes, I blame HP squarely for this. What we basically did is pull the new
driver kits out of the new SS and retrofit them into a modified version of the
previous SS (using things like the SST - Smartstart scripting toolkit). All of
our SS 6.x series boxes get recycled into CD-cases *grin*.
The only real major
components that require support during the basic Win2k / Win2k3 build is the
RAID Controller, basic hardware and network interfaces, most of which is covered
in the base Windows installation kit anyway. Additional support for
the multitude of hardware components (ilo boards etc) is enabled by installing
the appropiate Support Pack (NTSSP or whatever its currently called) AFTER
windows is installed, and thats pretty much what our build does (and is
essentially what SmartStart does under the covers anyway). Use the
absolute minimum mods to get the system up and running appropiately, then
install the Support Pack to get the rest of the
functionality.
Not 100% foolproof - HP introduced a driver
mismatch between some versions of the RAID controller software / hardware
combinations (the models escape me atm), which necessitated a forked build until
we got the problem resolved.
There will of course end up being an issue where HP
depreciate support for older hardware types under the new operating systems,
however we are hoping that the hardware has well and truly reached its
use-by-date by then. The "canned" SmartStart however masks this to a large
extent, and "forces" you down the path you described - buying newer
hardware.
My suggestion would be to
look into the SSST (SmartStart Scripting Toolkit), and forego the "canned"
SmartStart installation completely. The toolset basically allows the
creation of a scripted build using essentially the same tools the canned install
does. Adding additional hardware support is trivial, AND you arent
subjected to the whims of HP marketing who may decide that your hardware is "too
old" to support anymore - even though it still may be quite capable (and
technically still supported from a driver prespective).
Glenn
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rick Kingslan Sent: Thursday, 10 June 2004 11:20 AM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] OT: Compaq Servers Huh. Well, clearly I'm doing something wrong, or
don't have the build that you do, Glenn. There is no option to choose
Win2k3, so the right drivers can't get installed. Is there something
specific that you're doing, like installing as a Win2k and then upgrading the
drivers after the fact?
I guess I'm a bit confused now.....
-rtk From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Glenn Corbett Sent: Wednesday, June 09, 2004 3:54 AM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] OT: Compaq Servers Rick, I’m not quite sure what
you mean by this. Sure, SmartStart version 6.x is only *really* useful for G3 based computers, but
there isn’t anything stopping you from using SmartStart 5.5x on older and newer
hardware. We have a unified build
(based on the 5.5x SmartStart) that will quite happily do builds on G1, G2, G3
(even the older PL1600, 5500’s, 8000 based hardware) that supports Win 2k / Win
2k3. It’s really not too difficult. Just don’t use v6.0 (I know we
don’t). Glenn From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rick Kingslan Sadly, HP/Compaq flat
pissed me off with orphaning all of my '2nd gen' systems to Windows 2000, unless
I don't want to use SmartStart for anything other than coasters. So, I
really have no need for the 6.0 stuff that they keep sending me that DOES
support Windows Server 2003, but not my still quite useful but somewhat
dinosaur-ish (according to HP/Compaq, I
suppose....) To me - dumb
move. But, I'm sure that they had a great reason for it. Like, not
having any interest in customers who weren't buying brand new machines for
Windows Server 2003.... Rick Kingslan
MCSE, MCSA, MCT, CISSP From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Kitchens Arthur E I believe
RDP is free. The smartstart cd *is* free and you could build a master image with
that then distribute/implement with any of the methods/tools previously
mentioned in this thread. You can also get a 30 day eval license for the altiris
deployment server (what utilizes the RDP tool set) so I don't see any money
invovled with exploration of that either. It may also be the case the one
of the Insight Manager flavors would be useful for you. At least one
(4.something) was free by download a few weeks ago. Just my 2 cents.
-----Original Message----- I've spied
the RDP tool before and it does look like a quality system, but can't really
warrant the £££. If I remember it was expensive. **drifts
off to dreamland** Oh how I
wish HP would provide me with a simple and free tool... Or a good old gui based
front end to produce a script. **wakes to
reality** Thud! -----Original Message----- You can use
also our tool RemoteDeploymentPackage (http://h18013.www1.hp.com/products/servers/management/rdp.html).
> I used
Ghost to distribute Sysprep'd images either by Multicast or IP
List
info : http://www.activedir.org/mail_list.htm This e-mail
and the information it contains are confidential and may be privileged. If you
have received this e-mail in error please notify the sender immediately and
delete the material from any computer. Unless you are the intended recipient,
you should not copy this e-mail for any purpose, or disclose its contents to any
other person. The
MCPS-PRS Alliance is not responsible for the completeness or accuracy of this
communication as it has been transmitted over a public network. Whilst the
MCPS-PRS Alliance monitors all communications for potential viruses, we accept
no responsibility for any loss or damage caused by this e-mail and the
information it contains. It is the
recipient's responsibility to scan this e-mail and any attachments for viruses.
Any The
MCPS-PRS Alliance Limited is a limited company registered in List
info : http://www.activedir.org/mail_list.htm |
Title: RE: [ActiveDir] OT: Compaq Servers
- RE: [ActiveDir] OT: Compaq Servers Roger Seielstad
- RE: [ActiveDir] OT: Compaq Servers Rutherford, Robert
- RE: [ActiveDir] OT: Compaq Servers simon.geary
- RE: [ActiveDir] OT: Compaq Servers Frost . David
- RE: [ActiveDir] OT: Compaq Servers volker . seyboldt
- RE: [ActiveDir] OT: Compaq Servers Rutherford, Robert
- RE: [ActiveDir] OT: Compaq Servers Kitchens Arthur E
- RE: [ActiveDir] OT: Compaq Servers Rick Kingslan
- RE: [ActiveDir] OT: Compaq Servers Glenn Corbett
- RE: [ActiveDir] OT: Compaq Servers Rick Kingslan
- RE: [ActiveDir] OT: Compaq Servers Glenn Corbett
- RE: [ActiveDir] OT: Compaq Servers Ken Cornetet
- RE: [ActiveDir] OT: Compaq Servers Rutherford, Robert
- RE: [ActiveDir] OT: Compaq Servers simon.geary
- Re: [ActiveDir] OT: Compaq Servers Steve Schofield
- RE: [ActiveDir] OT: Compaq Servers Glenn Corbett
- RE: [ActiveDir] OT: Compaq Servers Ken Cornetet
- RE: [ActiveDir] OT: Compaq Servers Glenn Corbett