Blog

First things first.....


Tags :


        Libby prompted me that I slacked the past couple days. One was I had some family emergencies to deal with, all is well there.  Secondly, I was hoping for some more input on the previous post, but ahh well.

        Well here we are, the Friday before Admin2003 and I just don't feel like everything was completed.  I am on patch #3 from Lotus for Sametime 3.0 for numerous customers.  We have now patched, patched and newly patched Stconf.nsf trying to remove error after error.  Currently we fixed the little pop-up window that didn't used to go away.  Some of you say Ah Ha!  Either yours always goes away or for some of you it doesn't.  Well I can definitively say the answer to fix it is, well unknown to them also, LOL.  It is different each time for each customer we have.
        The current environment has a hostname that differs from the actual WWW name because it is a hosted server.  Then they use an alias name.  The WWW is a C Name entry in DNS, the alias name we entered as an A record in DNS.  So guess what, different results.
        Secondly, multiple NIC cards.  Sametime has the uncanny ability to bind to the first card in the operating system order.  Well we build with the backup NIC first because well, we like to make sure backup works before it goes live.  So the production NIC goes second.  Disable NIC, install, re-enable NIC? Yeah right, lets just fix this issue.  Editing the sametime.ini file for every server does not bode well inputting hostnames and addresses under [config].

        On a side note, if you wish to read a true/fantasy/we don't really know blog, then the link at the right for FlightRisk is for you..hmmmm.  Start at the bottom of it and read up to follow the story.  DO NOT start at the top, you get stuck in the middle.