Let me preface this post with saying: running Office Communicator or Lync on Citrix is not ideal. Why? It's a presence application. Unless you're working directly in OCS or the Lync client, your session on the XenApp server is idle, there fore your 'available' or 'idle/away' indicators may be inaccurate.
That being said, it can be handy to have your IM client readily available on Citrix.
I had been running Office Communicator 2007 R2 successfully, but Lync 2010 was giving me error messages:
"Either there is no default mail client or the current mail client cannot fulfill the messaging request. Please run Microsoft Office Outlook and set it as the default mail client."
I had installed Outlook 2010 and launched it, checked the default mail client, all to no avail.
The problem? I had actually published the wrong exe.
This Citrix forum post tipped me off to the mistake. The correct application? "C:\Program Files (x86)\Microsoft Lync\communicator.exe"
http://forums.citrix.com/thread.jspa?messageID=1715879
Tuesday, February 19, 2013
Thursday, February 7, 2013
Dell Servers, clearing the amber light
I run an environment consisting of Dell servers. I'm quite happy with them. They have some good management and monitoring utilities, and they've greatly improved applying things like firmware updates over the years.
This one was easy, but Googling didn't get me the answer, so I figured it warranted a post.
I had dealt with a nasty disk issue previously. In the end, I recovered the server to health, but my original RAID1 running in drives 0 and 1 had to reconfigured to run from drive 1 and drive 7 as a global hot spare. It seemed that there was a hardware problem in slot 0, and as the server is nearing retirement, it was easier just to leave drive 0 empty.
Some weeks later, someone else pointed out the "amber light." I monitor my systems through OMSE (Open Manage Server Essentials) which relies on OMSA (Open Manage Server Administrator), and the server showed healthy.
Physical examination yielded "PowerEdge 2950 E1812 HDD 0 Removed." Well, that was true, but I didn't need to see an amber light for it.
Going online netted me results like "Clear SEL" without telling me how to do that.
The quick and easy solution: clearing the hardware log.
From the OMSA web interface, from System, select Logs, and then Hardware. Then Clear Log.
Voila. Healthy blue display screen, no amber light.
This one was easy, but Googling didn't get me the answer, so I figured it warranted a post.
I had dealt with a nasty disk issue previously. In the end, I recovered the server to health, but my original RAID1 running in drives 0 and 1 had to reconfigured to run from drive 1 and drive 7 as a global hot spare. It seemed that there was a hardware problem in slot 0, and as the server is nearing retirement, it was easier just to leave drive 0 empty.
Some weeks later, someone else pointed out the "amber light." I monitor my systems through OMSE (Open Manage Server Essentials) which relies on OMSA (Open Manage Server Administrator), and the server showed healthy.
Physical examination yielded "PowerEdge 2950 E1812 HDD 0 Removed." Well, that was true, but I didn't need to see an amber light for it.
Going online netted me results like "Clear SEL" without telling me how to do that.
The quick and easy solution: clearing the hardware log.
From the OMSA web interface, from System, select Logs, and then Hardware. Then Clear Log.
Voila. Healthy blue display screen, no amber light.
Subscribe to:
Posts (Atom)