Yes; this is what I do: update the x500 record on the mailbox; update the legacyExchangeDN to the same thing update the address book restart the Microsoft file distribution service on all the CAS Servers Update the Outlook offline address book test... (pick the name from the GAL, delete the one from the cache)
You can block user access to it - just change the password. I don't think there's a way to prevent admins from moving it... that would kind of defeat the purpose. They want to prevent it getting email as well? Set the send / receive to 0 MB.... On Wed, Jan 21, 2015 at 1:48 PM, Ben Scott <[email protected]> wrote: > On Wed, Jan 21, 2015 at 9:45 AM, Candee <[email protected]> wrote: > > How many users, Ben? > > Around 80 mailboxes on the server, 3 targeted by the lockdown. > > > You can put them on legal hold; that should satisfy the powers that be. > > Hmmm, that's a new feature to me. Looking at the docs, it seems > like this prevents items from being permanently deleted (purged from > "Deleted Item Recovery"). We needed more than that, we needed to > prevent changes to the mailbox (including moves), and prevent the user > from reading their own mailbox, too. > > Still, good to know that's there. It is likely to come in handy in > the future. Thanks. > > > Anyway, if it's only a few users (yes, you're right, I didn't read the > whole > > thread); you need to edit it in ADSIEdit as well. > > Edit what, the legacyExchangeDN, or something else? > > I had considered setting the legacyExchangeDN on the old account to > something different, and then setting the legacyExchangeDN on the new > account to be what used to be on the old account. But it seems like > monkeying with the legacyExchangeDN field invites bad karma, and that > wasn't worth it in this case. > > -- Ben > > >
