sorted by: new top controversial old
[-] packetloss@lemmy.world 1 points 11 months ago

Looking to perform daily backups of all users OneDrive files, SharePoint data, Teams (teams, channels, files, tabs), Exchange Online mailboxes.

This would be for long-term retention. 5+ years. Thinking of using object storage like Wasabi as a destination.

[-] packetloss@lemmy.world 6 points 1 year ago

All the time!

I've woken up smacking myself thinking a spider is crawling on me, and then spend the next 20 minutes trying to convince myself that there's no spider and its safe to fall asleep again.

[-] packetloss@lemmy.world 23 points 1 year ago

Haha!

Totally had me. Excellent shitpost.

[-] packetloss@lemmy.world 2 points 1 year ago* (last edited 1 year ago)

Edit: September 25, 2023 - Added more details to the solution for my issue.

Just wanted to update this so if anyone else is having the same issue hopefully it helps them.

During initial tenant setup I created a couple of retention policies. I thought these would only affect Teams data, but it turns out it also applied to Exchange Online mailboxes. When I tried to remove the Exchange Online license from the user it would give an Exchange error message in admin console and the mailbox would not get removed.

The issue turned out to be caused by holds that were applied to the user mailbox. Specifically these two:

DelayHoldApplied

ReleaseDelayHoldApplied

Both were set to $true.

  1. I removed the retention policies, they probably weren't configured correct in the first place.

  2. Used the following Powershell command to identify the holds applied to mailboxes:

Get-Mailbox | FL Identity,*HoldApplied*

  1. Used the "Set-Mailbox" command to remove those holds:

Set-Mailbox -Identity @mydomain.com -RemoveDelayHoldApplied

Set-Mailbox -Identity @mydomain.com -RemoveDelayReleaseHoldApplied

  1. Delete the user's mailbox by removing the Exchange Online license from the user and waited for the mailbox to disappear from the Exchange Online admin center.

  2. Run the following command to wipe out the pre-existing mailbox data. Without doing this, even after the on-prem user is synced Exchange Online will not care that the user has an on-prem mailbox, and will restore the previously deleted cloud mailbox from step 4.

Set-User @mydomain.com -PermanentlyClearPreviousMailboxInfo

  1. Force a sync of users using Azure AD Connect

  2. Re-enable the Exchange Online license for the user. After this is done in the users Mail settings you should see a message "This user's on-premises mailbox hasn't been migrated to ‎Exchange Online‎. The ‎Exchange Online‎ mailbox will be available after migration is completed"

Thanks to everyone who replied and offered help.

[-] packetloss@lemmy.world 1 points 1 year ago

No, we don't have any licenses other than Business Basic or Business Standard.

[-] packetloss@lemmy.world 32 points 1 year ago

Update the OS and all installed applications using a single command.

[-] packetloss@lemmy.world 6 points 1 year ago

Perfect depiction of downtown Vancouver.

[-] packetloss@lemmy.world 8 points 1 year ago

This.

I just went from Arch to Debian 12 Bookworm. Running the stable branch, but so far most of the packages are rather recent. Kernel is 6.1 instead of 6.4, but I could switch to the Testing or Unstable branch to get the "bleeding edge" packages/kernels if I need to. But honestly so far it's been a real pleasure to use. Everything is just working and is stable.

[-] packetloss@lemmy.world 4 points 1 year ago* (last edited 1 year ago)

The only time I've experienced a AAA game not working at launch or shortly after launch is when the developer explicitly goes out of the way to block usage on Linux.

Looking at you Bungie.

[-] packetloss@lemmy.world 13 points 1 year ago

I don't have a Steam Deck, but I just made the transition to fully running Arch on my gaming rig. So far everything just works.

[-] packetloss@lemmy.world 2 points 1 year ago

Not saying you have to or anything, and I can understand and respect using something like MX Linux to save time on the customization. Just know that because it's based on Debian, any core OS updates will be delayed while the MX team rebases them into their fork.

[-] packetloss@lemmy.world 6 points 1 year ago

Honest question, but why not just install Debian with the Xfce DE? Why rely on a fork for updates?

From what I can tell both by testing MX Linux and by reading about it, it's nothing more than Debian with a few pre-installed packages and some customization. All of which could be done on Debian directly without much trouble.

view more: ‹ prev next ›

packetloss

joined 1 year ago