Renaming domain level shared calendars does not change the name in the users Calendars list
Problem reported by Andrew Meador - August 29, 2017 at 7:16 AM
Not A Problem
I have created a few domain level shared resource calendars and have appointments/events in them. At first, I had two but then decided to split one into two separate calendars. So, I needed to rename them for clarification purposes. Well, under Settings...Domain Settings...Shared Resources... you can select a resource (Calendar) then click the Rename button at the top of the list. This works fine. However under the postmaster account and under other users accounts, when you go into the Calendar area (clicking on the left nav bar), then clicking the Calendars drop-down - the calendars still have the original name of the Calendar. These Calendars are mapped to the users and this is all being done through the web interface. Do I actually have to tell each user to go through their Settings...Calendar Settings...Calendars...Select and Change Display name to the new correct name - to affect these name changes?
 
These are not even linked into Outlook in any way - this is all web interface.
 
Thanks!

6 Replies

Reply to Thread
1
Derek Curtis Replied
Employee Post
Hi, Andrew
 
Yeah, that should push through to those who have attached the calendar to their account. I'll add it to our bug list. Thanks for pointing it out. 
Derek Curtis
COO
SmarterTools Inc.
(877) 357-6278
0
Andrew Meador Replied
Thanks for looking at this, letting me know, and adding it to your bug list.
0
Alex Carnot Replied
Employee Post
Hi,
 
When a user attaches a shared calendar the user is able to optionally specify a new friendly name for the shared calendar. Because users have the option to name any shared, attached calendar, there is no benefit in pushing the name if the calendar owner changes their calendar name. In fact, it may lead to more confusion. Because of this, we are marking this thread as Not a Problem.
Alex Carnot
Software Developer
SmarterTools Inc.
(877) 357-6278
www.smartertools.com
0
John Marx Replied
What if the name is the SAME as the original and there be a domain option to "Rename calendar if same" (or other wording)? This way if a user chooses to rename they get to keep it but if the user doesn't the change rolls down to the user.
 
Also, what if the domain says "Name can't be changed" AND when it's changed it rolls to the user?
0
Andrew Meador Replied
So you will allow user-level naming options to override naming pushed by the postmaster on domain level resources? That doesn't make sense. If you are talking about shared calendars via the postmaster's calendars or other user's calendars, then I can see your point - but when I as the postmaster want consistent domain level resources out there for my users - and users are allowed to override my naming conventions - this will lead to confusion when I can't speak to them in terms and names that I have created and be on the same page.
0
Andrew Meador Replied
Not to mention the fact that this is allowing user-level renaming of domain resources to force extra work to the admin level which is inherently against the workflow of domain level and administrative processes.

In this scenario where a calendar needed to be split into two, the names of the calendars changed accordingly, and to get these calendars pushed to the users with the new names would require me, the administrator and postmaster, to: create 2 new calendars named appropriately, re-assign permissions, have all the events in the original calendar be re-entered across the two new calendars, delete the old calendar, and then notify the users that they have these two new calendars (with the names I specified in the end anyway). OR, I could rename the one calendar - maintaining the same permissions, only move the events that correlate to the other new calendar, assign permissions on the one new calendar, and then notify the users of the change to their existing calendar and the new calendar.

The workload in the first scenario is more time-consuming and ends with the names I wanted in the first place vs the second scenario which is more in line with administrative workflows by keeping my time to a minimum by allowing managed group resources to be properly managed vs allowing user-level naming conventions to dictate administrative processes.

Reply to Thread