Avid tech and PC enthusiast. System Administrator by day, Dad by night.

  • 7 Posts
  • 19 Comments
Joined 1 year ago
cake
Cake day: July 2nd, 2023

help-circle






  • 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.worldtoLinux@lemmy.mlSnapless Ubuntu
    link
    fedilink
    English
    arrow-up
    8
    ·
    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.









  • I kind of hear what you’re saying, but other than the GPU, and it’s waterblock, the rest of the system is not new. I originally bought the motherboard in 2019 with a 3900X when the X570 AM4 platform and the Ryzen 3000 series CPU’s came out. Then upgraded the CPU to a 5800X3D just over a year ago.

    Why the 5800X3D? 1) Because at the time I bought it, it was THE fastest gaming CPU. It’s still an incredible CPU that has a ton of performance. 2) I got the 5800X3D because I primarily play games on my PC. I don’t do any video editing, streaming, or productivity work. My rig is custom built for gaming, and only gaming. Even going as far as running a customized Windows 10 install with a bunch of background processes and analytics bloat stripped out. This is what the 5800X3D was made for. You look at benchmarks and reviews of the 5800X3D and it was beating or matching the 12900K, for less money, and most importantly, for less power draw. Performs better, runs cooler, costs less. I see that as a no brainer, not a compromise. There was nothing budget friendly about any of this platform when the parts were bought.

    If I was buying the platform now, new, yes… then I could see why you’d think that. Honestly at this point, I’d have to go to the AM5 platform, and the 7800X3D to get any better performance than I have already. Since the AM5 platform is brand new, I’ll give it a year and wait till the Ryzen 8000 series chips launch and look at the X3D variants then. I went bleeding edge with my X570 and the Ryzen 3900X and there was definitely early adopter pains. I get more than enough performance from my system, in the games I play. I judge my happiness based on how the games feel to me. If the games load fast, feel smooth, and perform well then I’m happy. I don’t look too closely at framerates, it’s just about the experience for me.

    Honestly, if Intel launched a platform and a CPU that had the better performance per $ with less power draw, and better thermals than AMD, then I’d probably buy that platform, but as it stands that hasn’t been the case, for a while now. If the 13900K beats my 5800X3D by 10% in a game, but the difference is 270FPS vs 300FPS, I honestly see that as a null win for Intel. Because those extra 30FPS will never ever be noticed or seen. Especially when I cap my FPS to my monitor’s refresh rate. Anything above that is just wasted electricity.





  • Zabbix stores all it’s data in a PostgreSQL or MySQL database. However… there are 2 ways that Zabbix Agents work. Either in passive mode, or in active mode.

    Passive Agent = “poller” process on the Zabbix server sends a request to the agent asking for values for the items it’s monitoring (based on template applied to host). Depending on the number of hosts you’re monitoring and how many poller processes are configured to start with the Zabbix server, you may run into a situation where requests are queued because the poller process is too busy. Increasing the number of poller processes will fix this, but it also adds additional load to your DB as each poller process will connect to your DB to write data, and each poller process will consume a certain amount of memory. Too many and you’ll run out of RAM, or bog down your DB.

    Active Agent = “trapper” process on the Zabbix server listens for item values from being sent to it from the agents. Agents will query the Zabbix server to see what templates are applied to it’s host, and will figure out what items it’s supposed to monitor. The agent will actively query the items without the Zabbix server requesting it, and will send the item values to the server as scheduled. This puts a lot less load on the Zabbix server.

    Item values are not read from the DB to activate the trigger. When a value is received that matches the trigger’s expression, then the trigger is activated. Live values are used to activate triggers and trigger actions (alerts).