User Profile
jimbarrgpboston
Brass Contributor
Joined 6 years ago
User Widgets
Recent Discussions
Re: Trying to add multiple users to distribution group and getting error: Cannot validate argument
Some info on exactly what you did would be helpful. I've wasted over an hour on this and I'm ready to just add the 114 people via the web interface, given there is no definitive way to validate any error message in Powershell. Test SharePoint13KViews0likes4CommentsRe: Can't empty deleted items folder - Outlook 2016 / Exchange Online Plan 1
Darren Rose and others, let me be of some assistance here. After a 10 day odyssey with Microsoft support there are specific reasons why deletion is not possible, especially as the mailbox gets to 100% full. It involves multiple steps to solve and will take some machine time to complete, but I will provide some Powershell steps to assist you. PLEASE NOTE, you will be permanently deleting items in the Deleted Items box in this process and they will NOT be recoverable! You can change things back to defaults after completion. First, create a deleted items policy for the mailbox in question by going to EAC, Compliance Management, Retention Tags. Hit the + sign and "apply automatically to a default folder." Choose Deleted Items as the default folder, then click Permanently Delete, Retention Period should be Never. Now, go to Retention Policies, and create a new policy, name it, and go to + sign for Retention Tags and add the one tag you just created and save the policy. Next, go to the mailbox in question, click on Mailbox Features, and add change the Retention Policy to the new one you just created and save. Now, open up Powershell and connect to Exchange Online (I use connect-ExchangeOnline command with modern authentication, as I've added these cmdlets to my Powershell environment, but you can still use the downloadable Exchange Powershell and connect-EXOPSession command if you like, they are both the same thing). Force update to the retention policy by typing: Start-ManagedFolderAssistant -Identity <email-address-of-affected-mailbox> You may have to wait up to 24 hours, but things should delete that can be deleted, but you're not done yet. Open EAC, and go to Permissions and add your account you log into Powershell with to the Discovery Management object under Admin Roles. You will have to wait about 10 minutes for this to take effect. Open Powershell and connect to Exchange Online again, and send this command: Get-ManagementRole -Cmdlet Search-Mailbox This will add the "search-Mailbox" command and associated cmdlets to your shell for the next command to work: search-mailbox -identity <email-address-of-affected-mailbox> -searchdumpsteronly -deletecontent The above command will take sometimes hours to complete, and mail fail with a Store connect failure, but simply re-run it until it returns a cursor. After that, you should be able to go to the Deleted Items folder on the affected mailbox using OWA and delete all mail. Don't forget to purge all deleted items after you so this so they are non-recoverable (this cannot be undone!). After all this, the "dumpster" command above can be re-run to make sure any add'l email is removed. You may then check the dumpster size with this command: Get-MailboxFolderStatistics -Identity <email-address-of-affected-mailbox> -Folderscope RecoverableItems | select name,foldersize,ItemsInFolder When done, it is advisable you REMOVE yourself as a member from the Discovery Management object in EAC/Permissions/Admin Roles so you do not accidentally delete permanent objects. Hope this helps. It was painful, but that got a mailbox from 100+% down below 10%. JB54KViews2likes1CommentRe: Can't empty deleted items folder - Outlook 2016 / Exchange Online Plan 1
Darren Rose Years later, 4 separate support tickets, multiple "I understand the frustration you are feeling" phone calls with support, and this is still an issue. Nothing works. I am, to be honest, dumbfounded by the simplicity of this request and the inability of the Great Monopoly Microsoft to comply with a simple "select," and "delete" command that would enable the removal of the trash and recoverable data.55KViews0likes1CommentRe: Dynamic Group Membership - issue with rule
VasilMichev Not really a solution. In our experience, the average time to closure on any case with Microsoft is 6 weeks or longer. The reality about support is that nobody at Microsoft really knows their products. Also, things should be wizard driven, but are not. So you are crestfallen when after 4 weeks of banging your head against the wall, someone finally tells you, "you don't have the right license".16KViews0likes0CommentsRe: Assign user automatically to group in Office 365
ChrisHoardMVP The real issues with Dynamic groups is that a user cannot see the members by expanding the distribution list. That option isn't available. We were forced to convert all groups to non-dynamic groups because of this limitation. Basically, each and every user has unique properties (might be a member of 3 main groups, then pick and choose what groups afterwards based on need). The process for replicating group membership via the GUI is very slow and extremely inefficient. More than 5 clicks to add a person to one single group. This time adds up for expanding companies. Microsoft's web GUI is very slow as well, compounding the problem. It would be great if there would be a group picker at account creation without having to script everything. Powershell is complex and haphazard.83KViews1like1Comment
Recent Blog Articles
No content to show