Cant move emails to pst files
A few months ago New Outlook added support for pst files making it possible to drag emails from IMAP inboxes into pst . This worked fine for a while but this week it has stopped working, now if I try to move an email to pst it just bounces back to the inbox where it was originally stored. I can still move emails between my different IMAP accounts but no lonker to pst. Has anyone else encountered the same issue and found a solution?Get-MailboxExportRequest doesn't accept Export from date A to date B
Hi everyone, I'm faceing a strange error, when I want to export between 2 dates. We've tried infinite ways of exporting between 2 dates, but me and my colleagues can't get it. For easier reading, I reduced the following code to the minimum. We are successfully exporting with Case 1, but as soon as we want to set a end date, it will automatically fail with the wildest excuses. (See 2nd code) #Define Dates $start = (Get-Date -Day 1 -month 6 -year 2021 -Hour 00 -Minute 00) $end = (Get-Date -Day 31 -month 12 -year 2023 -Hour 23 -Minute 59) #Case 1: Export the MB works with following command WORKS. (So Export from Date X until today): New-MailboxExportRequest -Mailbox "PrimarySmtpAddress" -ContentFilter "((Received -ge '$start') -and (Sent -ge '$start'))" -FilePath "Path\file.pst" #Case 2: To keep it simple, I'll just export the received Messages (Export from Date X to Date Y (NOT NOW) doesn't work.: New-MailboxExportRequest -Mailbox "PrimarySmtpAddress" -ContentFilter "((Received -ge '$start') -and (Received -le '$end'))" -FilePath "Path\file.pst" Get-MailboxExportStatistics Error: ContentFilter is invalid. The value "31.12.2023 23:59:00" could not be converted to type System.DateTime. --> The value "31.12.2023 23:59:00" could not be converted to type System.DateTime. $end is definitely a system.datetime type; We've also used different System Cultures, f.e.: [System.Threading.Thread]::CurrentThread.CurrentCulture = "en-US" I've been working on this for a long time, please only respond, if you were able to reproduce this in your own Exchange Environment, since I want a confirmation, that this is a (currently) unhandable bug. Best regards, Florian edit: I updated the official MS docs.
Bookings Google Calendar Invite for Appt is in Wrong Time Zone
We have the correct time zone listed for our Microsoft Bookings account and the automated reminder emails show the correct time zone. But when customers use the automated Google Calendar invite, it is showing the wrong time zone for their appointment. It says UTC instead of PST. I believe it is because you have the time zone listed as "(UTC-08:00) Pacific Time (US & Canada)" if you change the wording from UTC to PST I believe it would fix this issue. Google is pulling the first time zone it is seeing which is currently UTC. Please fix this.Use network upload to import your organization PST files to Office 365 via PowerShell
We plan to upload all our .PST's using the steps provided in the below link. https://docs.microsoft.com/en-us/office365/securitycompliance/use-network-upload-to-import-pst-files How can we automate this process or use PowerShell to implement what is suggested in the article? Also, we have uploaded a lot of PST using the GUI but cannot see anything under the Blob Containers via the organizations network. It is visible from the open internet. What could be causing this? How do I identify the problem?Use network upload to import your organization PST files to Office 365 via PowerShell
Use network upload to import your organization PST files to Office 365 via PowerShell We plan to upload all our .PST's using the steps provided in the below link. https://docs.microsoft.com/en-us/office365/securitycompliance/use-network-upload-to-import-pst-files How can we automate this process or use PowerShell to implement what is suggested in the article? Also, we have uploaded a lot of PST using the GUI but cannot see anything under the Blob Containers via the organizations network. It is visible from the open internet. What could be causing this? How do I identify the problem?
