Tuesday, August 10, 2010

Repeat after me: "Read the NOTES in the documentation"

We've recently migrated our iPrint from NetWare to Linux and put in PaperCut to replace PCounter (they weren't even developing for Linux when we started the project).  Bear in mind, I'm not even included in this project team, but I hear things and get asked to open up tickets when things don't work as planned.

So, I had to laugh at myself a bit when stumbling across this new issue.  You see, I have the habit of reading anything starting with "NOTE".  Even more so when it's in a nicely outlined text box in the documentation.  The particular note I'm referring to is a smidge vague in the wording, but from Novell's site, here's the "note" for the ShortInstallName feature that got overlooked:

NOTE:When changing the value use only lower ASCII characters and do not use slash, quote, space, or comma.

What they're telling you is IF you use the ShortInstallName (as we do), make sure the name is all in lower case and don't use the noted characters - including spaces.  We didn't do that.

What happens if you don't follow that rule?  The HP Universal Driver causes issues in iManager where it thinks the broker is down when it's up, ditto for the print manager and the printer.  And this causes iManager to not be able to do anything with the affected printer/broker/manager.

This note is also included in the .ini file on the server, and that's where it was first noticed.  I had to giggle a bit.  It's always that little tidbit that's right under your nose that gets missed in the middle of a production implementation.  Which is why I always pay attention to those special boxes.  Still, from time to time, they get overlooked, so this is your friendly reminder to please read the NOTE section.  It's there for a reason.

I have asked the PM to look into putting a TID out on this subject as it's come up in the forums with no answers.

As a side note, I also gave Microsoft some feedback on their training/certification pages - basically I told them to go take a look at Novell's certification/training pages and "grab a clue".  All I ended up with from trying to traverse that site in search of what classes are needed for which exams was a huge Excedrin headache.