27 June 2008
And so it begins...
25 April 2008
Quickr... Tip #2 and #3 from The Notes Apprentice
Tip #2 from The Notes Apprentice...
It's Quickr NOT QuickR. Now seriously, I'm not sure it matters but I was corrected so I feel the need to spread the word. It matters to someone so I decided they must have put some blood, sweat and tears (or at least some spare time) into making Quickr what it is today. Thus, it matters now to me since Quickr is a pretty cool tool. Your welcome!
Tip #3 from The Notes Apprentice...
Never add the Sametime Community Server info to Quickr unless you're sure that your Sametime server also has LDAP authentication turned on like the Quickr server (this was under the Other Options in Quickr v8.0). This is important, especially if it's right after the initial company training and you think "surely this won't effect anything and I can make the change without testing". Bad things happen... All of the sudden no one could log in to Quickr at all... including me! Luckily, I had a genuis from Workflow Studios there wrapping up his Quickr training who offered to help. He quickly started having me check various settings, patiently asking what I'd been doing before it happened. I knew I'd re-registered some places but he assured me that wouldn't cause any problems. It took at least 5 minutes of Jr. Admin panic before I remembered that I'd added that Sametime server info. However, it felt like an hour and it was very hard to think while I mentally updated my resume at the same time! However, Lance (very nicely) taught me about the differences of authenticating between LDAP and the Domain Directory while I backed out the Sametime server info, restarted http and magically everything worked again. So feel free to learn from my mistake... Your welcome!
23 April 2008
To blog or not to blog...
13 March 2008
I may be a little behind the times, but Quickr is cool
I never imagined when I stumbled into Rob at Lotusphere that it would lead to so much information that would help me in my job later. I'm glad I paid attention!!! And more importantly that I remembered it all the next day!
12 March 2008
My little work buddy Hal :)

By the way.... I helped reset her internet password just fine if anyone was worried about the end user. Nah, didn't think so :)
05 March 2008
Ah, the joys of being a junior admin...
26 February 2008
Cloud 9
25 February 2008
You always remember your first...
A funny sidenote, my Sr. Admin made sure to remind me in intial setup of the server to move Outlook Express over to the "Entertainment" group on the taskbar. I know it's a small victory but one he clearly enjoys with every server build.
18 February 2008
RSS Feeders
Ahh Rules... Tip #1 from The Notes Apprentice
Situation: User calls and is getting duplicate emails from "random" users. Luckily, I was one of the "random" users that she claimed was sending her two of everything so it made it easier to test.
Troubleshooting: Ok, so where to start... I had no idea for a good solid minute before my old help desk troubleshooting skills fired up! I remoted into her box to confirm the duplicate messages, yep two. I watched mail.box to see if two emails actually were coming through the router (pronounced 'rou-ter'), only the one message. I admit I spent hours trying to figure out what was causing the duplicate messages, but alas I gave up and called IBM Support. I felt a little better when everything she had me try was where I had already started.
Resolution: After a good 30 minute call with the ever helpful Lotus Support they suggested I look at the rules on the users mailfile. Sure enough they had a test rule to send a copy of full messages to inbox if "me" was in the sender field. Viola! Sure enough there is a "me" in my name and in the name of all the other "random" duplicates the user was getting. Sure, I felt a little dumb for not looking for the obvious, but that's why I'm here posting for you! Your Welcome :)
15 February 2008
Admins vs Developers...
I read this on Jamie's blog the other day...
"Developers want: new processes, changes to existing processes, integration between systems, access to systems from any device anywhere, systems emailing/feeding/serving other organizations' systems. In short, they want ACTION.
Administrators want: no changes to business, no incidents or system events, and no-one talking about or remembering anything that happened that day. In short, they want NOTHING TO HAPPEN. If they could achieve this by unplugging the servers without anyone noticing, they would."
I would just like to say as an Admin... Is that so wrong?!? I am some what teasing but it truly is a great day in my world when there are no changes and everything runs smoothly all day. I can handle the users, I just need to figure out how to get the developer or desktop support to stop making changes and life would be smooth! Just kidding D!!
14 February 2008
Updates....
Lotusphere 2008
On to the rest of Lotusphere, sessions sped by in a whirl of trying to figure out how things applied to my job back home and realizing the true task I've taken on with becoming a Notes Admin.
The true highlight of the experience, Jellyrolls! Sure there was mass amounts of alcohol consumed but I met a great group of people that truly made me feel welcome. For that, Lotusphere ranks up there as one of the most exciting things I've done in my life. Thanks everyone!!