admin
647 TopicsHow to clear the Discovery Holds folder
To find whether this discovery holds folder is completely full, use the below-mentioned command. Step 1: Connect-ExchangeOnline and then, Step 2: Get-MailboxFolderStatistics -Identity user | select name,foldersize Note: This DiscoveryHolds folder is having a limit of 100 GB. If it is full, we will get issues like "Unable to clear deleted items folder", "deleted items are getting auto-restored" etc., One of the reasons for this folder is full: If Organization Hold is turned on(All Exchange mailboxes are selected in Compliance Retention Policy) or the Individual ID is selected on Compliance Retention Policy. Solution: Please try the below-mentioned steps to overcome this issue. Step 1: Exclude the DiscoveryHolds full ID in the Compliance Retention policy or run the below-mentioned commands in PowerShell. Connect-IPPSSession and then, Set-RetentionCompliancePolicy -Identity "Compliance Retention Policy Name" -AddExchangeLocationException user for multiple users, Set-RetentionCompliancePolicy -Identity "Compliance Retention Policy Name" -AddExchangeLocationException user1, user2, user3 Now on PowerShell, Connect-ExchangeOnline and then, Set-Mailbox -Identity user -RetainDeletedItemsFor 0 and then run the below-mentioned command two times. Start-Managedfolderassistant -Identity user Start-Managedfolderassistant -Identity user After 2-3 minutes, run the below-mentioned commands. Get-Mailbox "user" | FL DelayHoldApplied,DelayReleaseHoldApplied If the output is received as true for any above-mentioned holds, then run the below-mentioned commands. Set-Mailbox user -RemoveDelayHoldApplied Set-Mailbox user -RemoveDelayReleaseHoldApplied and then run the below-mentioned command two times. Start-Managedfolderassistant -Identity user Start-Managedfolderassistant -Identity user After 2-3 minutes, this DiscoveryHolds folder will become zero as per the below-mentioned screenshot. This process helped me a lot. If you have any doubts/concerns/suggestions about this post, please comment below. Best Regards, Venkat Kiran Kona.Solved39KViews6likes9CommentsMigrate traditional Distribution Groups to Office 365 Groups
Over the past few months, customers are increasing both the number of Office 365 Groups created and average monthly usage. It’s great to see customers getting value out of the service. If you are using Office 365 and haven’t yet moved traditional Distribution Groups (also known as Distribution Lists or DLs) over to Office 365 Groups, here are a few of the advantages of making the move. Read more on the Exchange TechNet Blog.671Views4likes0CommentsExchange Hybrid Configuration Wizard error - root element is missing when connecting to 365
Hi Exchange Brain trust, I have an Exchange 2016 environment where I recently joined a Exchange 2019 server to move everything and eventually decommission 2016 server. Everything is configured manually to match what we currently have in 2016 server - configuration wise, they both are identical now. We don't have any mailbox on-prem. Its just being used for administration and SMTP relay. The question is, do we still have to run Hybrid Config Wizard ? The reason I'm asking is, I'm stuck on the following stage with an error I pulled my hair off for hours trying to figure the root cause. Connectivity is all working well. Any idea would be really appreciated !2.4KViews4likes18CommentsExchange SMTP Auth Fails with: 451 4.7.0 Temporary server error. Please try again later. PRX5
Office 365 refuses SMTP authentication with error: 451 4.7.0 Temporary server error. Please try again later. PRX5 This is when accessing External Send SMTP AUTH through OAUTH2 authentication. Initial authentication is successful (and is logged as so in Entra ID) but when trying to send send messages through authenticated SMTP, you get the above error. Working with multiple support reps, we looked through login logs and could not find any trace of the error in Entra ID. Support reps all blame the third party application. The issue is connected to a special use case, where a user has both the GLOBAL ADMIN role, as well as certain other admin roles. When you have a certain combination of those roles, for a selected user, OAUTH2 will fail, even though OAUTH2 for (apparently) ALL OTHER SERVICES - work without error! - ONLY SMTP Auth is affected. RESOLUTION: Keeping Global Admin while simply removing excess roles will almost immediately resolve the issue. This bug has been publicly noted as far back as August 2022, perhaps earlier. This needs to be fixed.1.7KViews3likes10CommentsExchange Server 2010 End of Support is (Still) Coming!
In April 2018 we blogged about the coming End of Support date for Exchange Server 2010. It’s time for another reminder, but today’s post is extra special. Why? One year from today Exchange Server 2010 will no longer be supported. What does ‘end of support’ mean? Exchange Server, like almost all Microsoft products, has a support lifecycle during which we provide new features, bug fixes, security fixes, and so on. This lifecycle typically lasts for 10 years from the date of the product's initial release, and the end of this lifecycle is known as the product's end of support. Learn more about what this means and what your options are on the Exchange blog.1KViews3likes1CommentShared Mailbox can have a password and login enabled without license
I'm very much aware of the license requirements for Shared Mailboxes in Exchange Online and for all Shared Mailboxes we always give licensed users access to them. If we need to login to the actual shared mailbox, we assigned them a license. This could be necessary if you also have some 3rd party application that actually need to login to the mailbox and fetch e-mail for some reason. I have recently realized that you CAN actually set a password to a Shared Mailbox. Just go to admin.microsoft.com > Users > Active Users > select the Shared Mailbox > Reset password. After this, you can login with the username/password. Of course, if you access it via portal.office.com you won't see Outlook but if you go directly to outlook.office365.com you will get access to the mailbox. Anyone know anything more about this feature? Limitations? I'm not looking to break the licensing terms, all our physical users for all our customers have their own personal accounts but there are scenarios where you have a 3rd party application accessing the mailbox for some reason.Solved708KViews3likes24CommentsTip: a few useful PowerShell scripts for Exchange and Office 365 Admins
Recently there has been some helpful activity over on the Microsoft Script Center for Exchange and Office 365 administrators. Here are 3 scripts that we wanted to call out, as well as a bit of an overview of what they do: Install Exchange 2016 Pre-requisites.ps1 – makes it easier to install Exchange 2016 prerequisites O365_Installs_Connections.ps1 – makes it easier to prepare machines from which you administer Office 365 O365_Logon Module – an easier way to log into Office 365 services using PowerShell Read more on the Exchange Blog!654Views3likes0CommentsInviting a group calendar without sending invites to the distribution group
Hi, I'm struggling with finding a good way to have a shared calendar with our Microsoft Teams team of 100+ members. We'd like to have a shared calendar where things like all the teams standups, demos, testing with users etc are added. This is meant to be for general information so that everyone can decide themselves what they should be part of, or just know that it is happening, rather than the meeting host needs to invite "the right" people. Thus, we don't want everyone in the team to get e-mail invites to each of these events. We have the Office 365 Group shared calendar automatically showing up (after a lot of work), but find it cumbersome to add events to it without distrubing everyone. The suggested approach seems to be to go into the calendar and create the event there. However, there are a few user experience issues with that: Adding an event behaves differently on Outlook desktop app vs Outlook 365 - on desktop the distribution group is added automatically as a recipient and on the web version it is not. This makes it difficult for us to write clear instructions for users. If anyone opens an event on the desktop app, it seems as if the distribution group is added as a reciptient automatically, meaning everyone will have to remember to take away the distribution group as a reciptient. Point 1 and 2 means that very often there will be e-mail invites sent to everyone unintentionally. It is annoying to have to go into another calendar to add events. I really need there to be an easy way of having a shared calendar with events that everyone can see and join in to, but not get an e-mail invite to. I've thought of two possible solutions based on the current functionality of Outlook: Solution A Preferably, I'd like this to be achieved through adding that group as an "attendee" (just as I do with room bookings). The way I thought of to solve this was to create another shared calendar that everyone can edit, but whose team no one is a member of. Unfortunately, it seems like I'm not allowed to set permissions of the shared group calendar in the same way I can do with my own calendars. Thus, I can't give edit access to people that aren't a member of the team. Solution B Another way I thought of would be to disable the calendar invites being sent to the team members. If I understand the documentation of Set-UnifiedGroup correctly, that would be possible through setting -AlwaysSubscribeMembersToCalendarEvents:$false. It says that means "ReplyOnly". However, I don't know for sure what that value means, because it's not really explained. Also, I'm not sure how to set this for exsiting members, as this setting is only for new members. Any help on how to achieve either of my two solutions are greatly appreciated. And of course, if you can think of any other solution to achieve my goal of an easily adminstered shared calendar that doesn't disturb everyone, I'm all ears. Oh, and of course...being a former G Suite user, I'd really like there to be a way for the user to set if they wish the event to be modifiable by others or not. But I guess that's just not possible with Microsoft's solution? Thanks, Jonatan39KViews3likes18CommentsConnect to Exchange Online PowerShell using multi-factor authentication
https://technet.microsoft.com/en-us/library/mt775114(v=exchg.160).aspx Yesterday I found that now we can connect to Exchange Online through Powershell even with MFA enabled account. This is a preview feature. IMO, this is one of the long awaited feature.867Views2likes1Comment