[Users] Is it safe to remove the `default` COS?

[Naisiew Yeak]

If not mistaken the "default" CoS can't be removed (there is error when
you hit delete from Admin Console). During installation or upgrade, the
installation script will do modification to the default CoS but not others
(when it is needed to apply certain defaults). Also I notice all default
CoS has the same ZimbraId: e00428a1-0c00-11d9-836a-000d93afea2a.

It should be able to make "default_restored_zimbra1.example.com cos" as
default:
1. In Global Settings, set default domain to example.com.
2. Modify example.com domain, set the default cos to "
default_restored_zimbra1.example.com".



On Wed, Jun 19, 2019 at 5:49 PM Info Zeta Alliance <info at zetalliance.org>
wrote:

> Yeah I did put that description, but it appears there are some bugs in the
> Admin UI, in thta
> it still creates users in the `default` COS, even if I set a different COS
> as domain default.
>
> So when one creates an account, and let COS set to AUTO (which is default)
> it put the
> new user in the `default` cos, which is not the one set as default cos for
> the domain.
>
> As a result, people get a wrong feature set, if the admin is not aware of
> the weird behavior
> of `auto` cos.
>
>
> Kind regards,
>
> Barry de Graaff
> Zeta Alliance
> Co-founder & Developer
> zetalliance.org | github.com/Zimbra-Community
>
> Signal: +31 617 220 227
> Fingerprint: 97f4694a1d9aedad012533db725ddd156d36a2d0
>
> ------------------------------
> *From: *"Guy CARRÉ" <guycarre at free.fr>
> *To: *"info" <info at zetalliance.org>
> *Cc: *users at lists.zetalliance.org
> *Sent: *Wednesday, 19 June, 2019 11:30:06
> *Subject: *Re: [Users] Is it safe to remove the `default` COS?
>
>   Hello Barry,
>
>  yes you can delete it safely. But from my point of view I'd prefer to
> preserve it and not changing
> anything in it. By this way I can use it to do some tests when something
> goes wrong with some account.
>
>   Maybe you can add in the description of it "Do Not Use In Production" ?
>
>    Regards,
>
> ------------------------------
>
> *De: *"Info Zeta Alliance" <info at zetalliance.org>
> *À: *users at lists.zetalliance.org
> *Envoyé: *Mercredi 19 Juin 2019 11:21:26
> *Objet: *[Users] Is it safe to remove the `default` COS?
>
> Hello All,
>
> After doing a side-by-side migration using Zextras, I ended up with these
> 2 COS'es:
>
> default_restored_zimbra1.example.com
> and
> default
>
> Where as `default` is a newly created COS by the installer, and the `
> default_restored_zimbra1.example.com`
> is the one where are the migrated users ended up in.
>
> I know I can set the default cos for a domain using;
>  zmprov md example.com zimbraDomainDefaultCOSId <uuid of
> default_restored_zimbra1.example.com here >
>
> I have verified that there are no more users in `default` but I want to
> prevent admins to accidentally add
> users into it.
>
> Can I hit the delete button on the `default` and then rename
> default_restored_zimbra1.example.com to default?
>
> Or would that break something?
>
> Kind regards,
>
> Barry de Graaff
> Zeta Alliance
> Co-founder & Developer
> zetalliance.org | github.com/Zimbra-Community
>
> Signal: +31 617 220 227
> Fingerprint: 97f4694a1d9aedad012533db725ddd156d36a2d0
>
>
>
>
> --
>   ___________________________________
>  /                                   \
> /-------------------------------------\
> |  Guy CARRÉ                          |
> |  *************                      |
> |  PostMaster - WikiMaster - SysAdmin |
> |                                     |
> | "Free Your Mind. Think Open Source" |
> |  april.org                          |
> |                                     |
> |_____________________________________|
>
>

-- 
Naisiew Yeak
+60 12 5067818


*Zimbra • Linux • Security*

My Directory Sdn Bhd
E-2-22, IOI Boulevard, Jalan Kenari 5, Bandar Puchong Jaya
47170 Puchong, Selangor, Malaysia.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.zetalliance.org/pipermail/users_lists.zetalliance.org/attachments/20190619/4528963a/attachment.html>