LAZARUS and the Active Directory Recycle Bin скачать в хорошем качестве

LAZARUS and the Active Directory Recycle Bin

What do you do when you need to "remove" a user account? Do you delete it? What happens if you make a mistake, or if your efficiency department has to re-hire most of the people they fired? Is there any sort of remedy for this? Well, let's find out! Today we're talking about the value of disabling accounts rather than deleting them outright. We're also going to look into the details of the Active Directory Recycle Bin to see how enabling this optional feature can give us an additional safety net when things go wrong! EXTRA CREDIT: Because Office 365 is based on Active Directory (Entra ID used to be called Azure Active Directory!), you might expect to see signs of various AD features there. And we do! Accounts that are "soft-deleted" and available to be recovered within a certain amount of time are making use of the AD Recycle Bin! True story: One time, I accidentally deleted every user account (except Administrator) in an entire company. On a Tuesday morning, around 10:30am, no less. Worse, AD Recycle Bin hadn't been enabled, so I had to first reanimate all those tombstones, then reset everybody's passwords, then try to figure out the group memberships that had been lost. I was a very, very unhappy admin that morning. (And learned a permanent lesson about never using the "Remove-Mailbox" cmdlet--always use "Disable-Mailbox" instead!) I also had to go and restore 150-ish user accounts that were incorrectly deleted (not by me!) at a different customer just in the last week. Fortunately, I had already enabled the AD Recycle Bin there, so recovery was much easier! It's important for us to know what we should and should not do, but having that extra safety net in place can really save the day sometimes!