Tuesday, January 30, 2007

Well that's... Annoying

You would think that Citrix could automatically adjust the processor metrics on a server if it detects multiple processors during install. I guess that's asking too much.

Context switches/sec appear to be scaled as a total across all processors, but the default threshold isn't adjusted to reflect multiple procs.

Lesson: At the least, multiply the threshold by the number of processors in the server.

More info...

Ugh... Symantec buys Altiris?

Just when I was starting to get over the licensing pain of Veritas being bought by Symantec, they go and buy Altiris.

I so look forward to yet another licensing scheme change. Yay.

Which port goes to which blade?

I do a lot of work with HP p-Class blades. For the most part, they are great to work with, but one of the most annoying things about them is that when you use the half-height blades, figuring out which network port goes to which server is SUPREMELY annoying.

So, I went out and grabbed the 17 page document on which port goes where and managed to distill it down to this picture.

Simply put, the top blade is on the left port and the bottom blade is on the right port. And PXE is serviced by the ports on the right (A side) interconnect.

Easy enough.

Monday, January 29, 2007

PXE-E55: ProxyDHCP service did not reply to request on port 4011

I was working on a client’s server today and trying to get HP’s Rapid Deployment Pack (RDP) to connect to a blade for imaging.

The PXE boot environment kept recycling and I couldn’t figure out why until I managed to snag a screen capture of the error.



I did a little bit of digging and found this article on Microsoft’s site.

While it didn’t help me exactly, since the PXE server was on the same server as the DHCP service, it did lead me to the right answer.


The Altiris PXE Server was set to manual and wasn’t started. I should have checked that first, but live and learn.

Sunday, January 28, 2007

I've seen this before...

Don't you hate that?

You're working on a problem and you know you've seen it before, but now you can't find the knowledgebase article!

What's that registry key? Which version of the driver do I need again?

It happens to me all the time. I overcome a lot of little annoying problems and gotchas each day, and unless I journal them someplace, it's a 50/50 chance that I'm going to have to start all over again finding the answer the next time I run into the same problem.

In order to help solve this annoying problem of memory, I have resolved to chronicle my daily experiences here, in the hopes that if I've seen it before, I can fix it again without jumping through the same hoops.

Wish me luck!