[THIN] Re: Altiris with HP Blades
- From: "Malcolm Bruton" <malcolm.bruton@xxxxxxxxxxxxxxxxxx>
- To: <thin@xxxxxxxxxxxxx>
- Date: Thu, 9 Aug 2007 10:24:32 -0400
Hi Greg
Not seen the name changing happen with any other servers except the blade.
I have seen when you want to change the name later it is easier to delete the
server and re-add.
I have heard of the usepmtimer switch and it is particularly useful for AMD
servers. Not seen any issues but I have heard horror stories about not using
it. We are sitting on the fence with this. Would have thought they would have
patched the OS by now to correct the behaviour rather than a manual switch.
Any thoughts on what would happen to an Intel box if it was added?
Again with the Win2k3 password we have one build that we have used for 12
months. Added the blade and it starts prompting for password. Rebuild a
360g3, G4 etc and it doesn't prompt.....
Feel like I'm missing something basic...We are running Altiris 6.5 SP1 not HP
RDP.
Malcolm
________________________________
From: thin-bounce@xxxxxxxxxxxxx on behalf of Greg Reese
Sent: Thu 8/9/2007 2:39 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Altiris with HP Blades
I have this same setup. BL465C and altiris. they're nice boxes. fast, fast,
fast.
The name changing is normal during the first build and during the pxe process.
After that and on rebuilds rebuilds it will show the true name. Once you
change it, it is hard to get it to go away. It almost becomes a problem
sometimes when you want it to change.
also, on those BL465C's, add /usepmtimer to the boot.ini file. We had problems
with domain communication because this was missing.
You shoudl be able to set the Win2k3 password in the build so it doesn't ask
for it. Did you ake your own automated build or let the HP RDP software make it
for you?
Greg
On 8/9/07, Malcolm Bruton <malcolm.bruton@xxxxxxxxxxxxxxxxxx> wrote:
Hi All
I know there a few people who use Altiris so hoping someone can help.
We have an automated scripted build which we use to build DL 380G3,
DL360 G3 and G4, DL 385 G1 and G2.
It is a single build with all drivers etc loaded.
We are now trying to build a BL465c blade. We have added all drivers
etc to our build and all other model types continue to work fine. However with
the blade the automated build keeps stopping on the PXE boot screen and the
name of the host within Altiris keeps changing. It changes too
"UnnamedRack-GB11111111-14" If we change the name with altiris back and hit
enter on the PXE screen it continues to work.
Anyone else seen this. Got PXE set as the primary boot option on the
blade and going to try an updated NIC firmware but everything else seems up to
date.
Also whilst doing our automated 2003 build it stops and asks for the
admin password. None of the other server models to this. Again ideas?
I don't have to do anything special with a blade with Altiris do I? I
am not trying to mange the blade enclosure or anything like this and can't see
that within altiris.
Malcolm
Other related posts:
