u/uLmi84

EXO Archive Issue

I do a lot of Exchange Hybrid stuff and normally on a hybrid Identity with a remotemailbox in EXO, I would simply go to EXO an enable an Archive there, without any issues.

In this situation: I have multiple MSP each managing a portion of the setup and I dont have full insights into the config. But in general its also just a hybrid Identity with a remotemailbox.

When I enable archive in EXO, I receive the following error in the M365 Admin Center:

Exchange: Failed to disable the archive of mailbox GUID due to a conflict in directory settings. To disable this archive, first run Enable-RemoteMailbox -Archive on-premises. After the next Dirsync sync cycle, run Disable-RemoteMailbox -Archive on-premises to disable this archive in the datacenter..;

I done the fix in this message yesterday and the error disappeared. Then I enabled the Archive in EXO again. Today the Error is back... I checked the AD-Attributes:

  • msExchArchiveGUID
  • msExchArchiveStatus
  • msExchArchiveName

and they are all empty.

any one know why this error exists?

reddit.com
u/uLmi84 — 9 days ago
▲ 1 r/Intune

MDM migration

Source MDM is broadcoms omnissa one.
Target MDM is intune

Im looking for a smooth transition and need to make sure that only company devices can access m365 data via conditional access:
Preferably via „isCompliant“ from intune.
Im also thinking about creating a Compliance partnership between both MDM to help for a phased transition.

But mostly im interested about the feature where I can add the devices EMEI to intune. My understanding is that this defines a device as corporate owned. Then i could block personal device enrollment and also block access to M365 via conditional access based on is a devices is not flagged as Corporate Owned.

The end goal is to move DEP and android enterprise zero touch completely to and use „isCompliant“ in conditional access to restrict access, but we also want to use m365 quick and I feel waiting for the entire MDM migration to be finished, only that we can block access for devices that are not compliant feels a bit overkill.

I was hoping that the devices can be in the old mdm but also enroll into intune (if there EMEI are on the whitelist) then conditional access can see them properly and devices can transition easier over time from the old mdm.

To be clear i have multiple requirements:
1)Limit access to m365 only to company devices (the emei whiteliste approach)

  1. transfer the actual MDM functionality to intune incl. DEP, policies, app config and deployment.

Anyone know if the EMEI approach is working?
Anyone know if a device can be in the old MDM but also enroll into intune?
Can DEP exist in old MDM and new MDM? I assume not.. how does one to a transition or cutover when the old mdm is still active? Seems very complicated

Im only talking about android / ios devices

reddit.com
u/uLmi84 — 13 days ago

I have a very stable and satisfying version of the os (plasma) running a few minor software installed and mostly some UI changes. Nothing deeply crazy or complicated or weird. I like to stay as simple and vanilla as possible. I noticed in desktop mode my 4090 is doing the work (seen in NVTOP) and the igpu of my 9800x3d is at 0%.

In windows this was different and I believe that the power consumption is better that way. Is it possible to make bring the IGPU to render desktop (e.g lightweight stuff) and have the 4090 kick in when needed like when a game starts?

I was hoping for a simple setting in an existing menu or existing tool. Im very cautious about installing crazy tools and doing deep mods.

If its not natively and with minimal configuration possible I willing to leave it as it is. As i dont wont to ruin the system.

Sorry for my noob terminology and weirdness

reddit.com
u/uLmi84 — 14 days ago

Is it possible to have local exch mbxs while having the mx record of the domain pointed to exo, with in that having a hybrid connector down to onprem?

I hope I just missed policies..

reddit.com
u/uLmi84 — 27 days ago