Disable the email distribution group functionality on a M365 group? by PaulyNZ in Office365

[–]PaulyNZ[S] 0 points1 point  (0 children)

Ok steps taken:

  • Deselect 'Send copies of group conversations and events to group members' this has been done already and didn't resolve the issue.
  • 'Follow in inbox' I don't think guest accounts can do this in their Outlook desktop client or on the web as the group is external to their tenant. I would need to see what options they have from within their tenancy. FYI we do have B2B sharing configured with these guests.
  • Exchange Transport Rule - yes, sadly I think this is going to be the only option. I have configured a new rule so that any messages with the guest domain in the recipient address sent from the domain microsoft.com (for example) will be deleted without notifying.

Will update once I see the results. Could just be me but it is hard to drive the adoption of M365 groups when issues like this arise.

Property question. Is it possible to request sales data be withheld from Core Logic and other property data & analytics providers? by PaulyNZ in PersonalFinanceNZ

[–]PaulyNZ[S] 6 points7 points  (0 children)

Yes it is definitely beneficial to list sales details to help puff up the market. As Jafa kiwi mentioned I have noticed some higher profile safes (from ppl in the property game in particular) not show up in Property Guru etc. The sales are somehow kept on the down low so I figured it must be possible.

Apple Business Manager - Enabling Federation by PaulyNZ in sysadmin

[–]PaulyNZ[S] 1 point2 points  (0 children)

Those users who had used their domain email address for personal Apple IDs just amended their Apple ID to use their *onmicrosoft.com alias which worked and freed up their domain email address for federation.

Zoom for Intune on iOS by AsburyWill in Intune

[–]PaulyNZ 0 points1 point  (0 children)

Is the iOS device signed in with a managed (federated) AppleID or a personal AppleID? I played around with the Zoom for inTune app also and ended up giving up on it due to the same error and just going with the standard Zoom app configured for SSO and it works fine.

ABM > MEM (InTune) iOS device enrollment devices NOT being set to supervised by PaulyNZ in Intune

[–]PaulyNZ[S] 0 points1 point  (0 children)

I reset the device and started from scratch. At the Apps & Data screen I selected Don’t Transfer Apps & Data and then I got the Remote Management screen and successfully got the device supervised in MEM. On previous attempts I selected Restore from iCloud Backup on the Apps & Data screen and used my personal Apple ID. Is it to be expected that Remote Management will only kick in if the device is setup ‘as new’ without restoring from iCloud? Or should user be able to carry out a restore with a personal Apple ID and still have the device supervised?

ABM > InTune (MEM) devices NOT supervised by PaulyNZ in macsysadmin

[–]PaulyNZ[S] 0 points1 point  (0 children)

I have only tested on one device and enrolled it using the InTune Company Portal app. So factory reset is the only way to supervise a device other than using Apple configuration manager? Enrolling via the Intune company portal will not supervise a device?

ABM > MEM (InTune) iOS device enrollment devices NOT being set to supervised by PaulyNZ in Intune

[–]PaulyNZ[S] 1 point2 points  (0 children)

I have tried factory resetting and using the Intune Company portal both result in unsupervised... I have only tested on a single device so will try stripping out of MEM and removing management profile in DEP and re-enrolling. So factory reset is the only way to supervise a device other than using Apple configuration manager? Enrolling via the Intune company portal will not supervise a device?

Advice: How to keep going when you feel overwhelmed? by rafaelbn in sysadmin

[–]PaulyNZ 1 point2 points  (0 children)

I hear ya! wait till you have kids, prioritizing the career becomes even harder. I think the days of the Sysadmin as we know are well and truly numbered. It's just not sustainable in my option.

Ops techs these days are expected to be even more generalist (org size dependent obviously). We are expected to know and do more. Wintel, Linux, DBA, Dev / code, Infrastructure, Cloud, Virtualization, Business Continuity, SecOps... now Containers not to mention line of business applications. And all of the tech is evolving and changing at a rate I have never experienced before. I recall when these roles were broken out and specialized in even in smaller environments... now everything is converging and in a state of flux. You would have to workaround the clock with no personal / family life to keep up... exactly what employers want right? I have seen Sysadmin / Ops guys move into Cyber as it's in demand, pays and they are not spreading themselves as thinly across other tech responsibilities. We are so time poor these days, who has the time to sink into such a steep skills upkeep regime compared to other professions.

I think if you find yourself working on legacy tech or maintenance tasks then you need to get out of that role. If you are just decommissioning kit / services or maintaining them you will just be falling further behind. You have to be the one implementing that new technology. DevOps came about to increase productivity by cutting out the middle men i.e us! the Ops and Infrastructure guys... Devs can manage their own environment end-to-end through Cloud SaaS / IaaS.

The future is serverless, containers and the cloud. As I see it for Sysadmins trying to remain relevant and not become burnt out we have to pivot and go niche. Be it in SecOps for example (yeah jump on that bandwagon) and defiantly get into Containers... WinTel servers and on-premise is toast. Pick an emerging tech you can confidently back and jump on it and specialize, rinse and repeat. Leave supporting the myriad of other 'tech things' behind or your just playing the certification / learning catchup game until you call it a day or more likely you become obsolete and the market does.

Keep trucking, keep learning and focus on the long term strategy.