Disabling Mailbox disables another mailbox



  • When an Employee moves to a different location, we have to make a new AD account for them since all the messages and sales data in that account belong to that property. So we will have a [email protected] in a Disabled OU, and then [email protected] in the correct property OU. The disabled OU is at the root and not nested within the property ou's.

    So as you can imagine that Disabled OU is massive with old accounts. We started Disabling the account in exchange in the Disabled OU and get them put in the Soft Delete pool since it is easy to say oh crap, reconnect the mailbox. You are back online now. Sorry.... 🙂

    However that process has yeilded a disable in the Disabled OU and in their active account in the property OU. The accounts are hard deleted. Attribute Editor for msexchSoftDelete are 0 for both accounts and msexchMailboxGuid is missing on both too.

    So I have the joy of creating them a blank mailbox and hunting and pecking in Veeam since I do not know what DAG database they were on.

    The only corrolation we can come up with is an attribute we have for EmpId as that is the same for both accounts, since their payroll ID did not change.

    Does Exchange/AD look for commonalities like that and decides to nuke both?



  • @Texkonc said in Disabling Mailbox disables another mailbox:

    When an Employee moves to a different location, we have to make a new AD account for them since all the messages and sales data in that account belong to that property. So we will have a [email protected] in a Disabled OU, and then [email protected] in the correct property OU. The disabled OU is at the root and not nested within the property ou's.

    So as you can imagine that Disabled OU is massive with old accounts. We started Disabling the account in exchange in the Disabled OU and get them put in the Soft Delete pool since it is easy to say oh crap, reconnect the mailbox. You are back online now. Sorry.... 🙂

    However that process has yeilded a disable in the Disabled OU and in their active account in the property OU. The accounts are hard deleted. Attribute Editor for msexchSoftDelete are 0 for both accounts and msexchMailboxGuid is missing on both too.

    So I have the joy of creating them a blank mailbox and hunting and pecking in Veeam since I do not know what DAG database they were on.

    The only corrolation we can come up with is an attribute we have for EmpId as that is the same for both accounts, since their payroll ID did not change.

    Does Exchange/AD look for commonalities like that and decides to nuke both?

    no idea. I try to avoid exchange.



  • @JaredBusch said in Disabling Mailbox disables another mailbox:

    @Texkonc said in Disabling Mailbox disables another mailbox:

    When an Employee moves to a different location, we have to make a new AD account for them since all the messages and sales data in that account belong to that property. So we will have a [email protected] in a Disabled OU, and then [email protected] in the correct property OU. The disabled OU is at the root and not nested within the property ou's.

    So as you can imagine that Disabled OU is massive with old accounts. We started Disabling the account in exchange in the Disabled OU and get them put in the Soft Delete pool since it is easy to say oh crap, reconnect the mailbox. You are back online now. Sorry.... 🙂

    However that process has yeilded a disable in the Disabled OU and in their active account in the property OU. The accounts are hard deleted. Attribute Editor for msexchSoftDelete are 0 for both accounts and msexchMailboxGuid is missing on both too.

    So I have the joy of creating them a blank mailbox and hunting and pecking in Veeam since I do not know what DAG database they were on.

    The only corrolation we can come up with is an attribute we have for EmpId as that is the same for both accounts, since their payroll ID did not change.

    Does Exchange/AD look for commonalities like that and decides to nuke both?

    no idea. I try to avoid exchange.

    Helpful.You.Are.Not.



  • Is this on Exchange 2010, 2013, 2016 or 2019?



  • Exchange deletes the AD account once you disable the mailbox.



  • @dbeato said in Disabling Mailbox disables another mailbox:

    Is this on Exchange 2010, 2013, 2016 or 2019?

    2013



  • @dbeato said in Disabling Mailbox disables another mailbox:

    Exchange deletes the AD account once you disable the mailbox.

    We are not doing Delete in Exchange, we are just doing the "Disconnect" which drops them into the soft delete queue were you can link it up later if needed provided the time frame doesnt pass.



  • Does the UserPrincipalName stay the same?



  • @Texkonc said in Disabling Mailbox disables another mailbox:

    @dbeato said in Disabling Mailbox disables another mailbox:

    Exchange deletes the AD account once you disable the mailbox.

    We are not doing Delete in Exchange, we are just doing the "Disconnect" which drops them into the soft delete queue were you can link it up later if needed provided the time frame doesnt pass.

    That's weird,



  • @dafyre said in Disabling Mailbox disables another mailbox:

    Does the UserPrincipalName stay the same?

    No, one will be [email protected] and the other one will be [email protected]



  • Ah........
    The First, Last, and Display Name are the same.
    I just remembered that putting some on Lit Hold in the past, I wasn't able to until I changed one of them to a different display name.
    Its all due to the Display Name I bet.



  • After I finish the damage control or real accounts getting nuked, I am going to test that theory. but I have a 90% hunch.


Log in to reply