VMware Cloud Community
kryichek
Enthusiast
Enthusiast

VC - Message of the Day

Today I put a message in the Message of the Day. The message keeps popping up about every 5 minutes or so. Is their a way to change that? I thought it was only suppose to appear upon login.

The message does not have any special characters. All the characters are ASCII.

Charles Mielak VCP, vExpert
0 Kudos
8 Replies
vmroyale
Immortal
Immortal

What version of VirtualCenter are you using?

Brian Atkinson | vExpert | VMTN Moderator | Author of "VCP5-DCV VMware Certified Professional-Data Center Virtualization on vSphere 5.5 Study Guide: VCP-550" | @vmroyale | http://vmroyale.com
0 Kudos
Troy_Clavell
Immortal
Immortal

If a Message of the Day (MOTD) entry is set or edited in the Sessions tab (Sessions tab is available when the Administration button in the main toolbar is selected), the message will pop up repeatedly every few minutes on all connected clients.

Workaround: This issue does not occur if you use Administration > Edit Message of the Day from the menu to set or edit MOTD.

taken from

http://www.vmware.com/support/vi3/doc/vi3_vc25u3_rel_notes.html

0 Kudos
kryichek
Enthusiast
Enthusiast

the Managemenet server is 2.5 Update 1. I am using the Update 3 client.

Charles Mielak VCP, vExpert
0 Kudos
vmroyale
Immortal
Immortal

Then what Troy said above should be correct.

Brian Atkinson | vExpert | VMTN Moderator | Author of "VCP5-DCV VMware Certified Professional-Data Center Virtualization on vSphere 5.5 Study Guide: VCP-550" | @vmroyale | http://vmroyale.com
0 Kudos
kryichek
Enthusiast
Enthusiast

I can assure you it DOES occur using the Administration / Message of the Day. That is the method I used to type up the message.

Charles Mielak VCP, vExpert
0 Kudos
Troy_Clavell
Immortal
Immortal

if that's the case, it's probably a bug and upgrading to U3 will fix it.

on a side note.... maybe using the same client build as your VCMS build will help???

0 Kudos
kryichek
Enthusiast
Enthusiast

Thank you for the ideas.

I removed the message and re-added it using a VC 2.5 Update 1 client. I still see the same behavior.

Charles Mielak VCP, vExpert
0 Kudos
Troy_Clavell
Immortal
Immortal

I wish I had a better answer for you other than upgrade to VirtualCenter 2.5.0U3. The fix is in the release notes, so I can only assume it was a known issue in previous releases.

Good Luck!

please consider awarding points for helpful/correct answers.

0 Kudos