tupcakes

joined 1 year ago
[–] tupcakes@lemmy.world 1 points 1 year ago

docker swarm is def easier to manage, however I found it somewhat limiting. particularly around IP address assignment for services. I ended up using nomad, which is a nice inbetween. feels kinda like what swarm could have been.

[–] tupcakes@lemmy.world 2 points 1 year ago (1 children)

just curious. what do you use celery for?

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

cluster (two old laptops, and 3 PI 3s):

  • nomad
  • glusterfs
  • consul

containers on nomad:

  • gitea
  • nodered
  • traefik
  • nextdns
  • postfix
  • cloudflared
  • diun
  • uptimekuma
  • searxng
  • n8n
  • nfty
  • minecraft bedrock
  • maraiadb
  • linkding
  • ddclient

docker (on unraid):

  • audiobookshelf
  • changedetection.io
  • fileflows
  • gluetun
  • jellyfin
  • metube
  • netdata
  • qbittorrent
  • unifi controller

Stand alone hardware:

  • technitium dns server x2
  • home assistant
[–] tupcakes@lemmy.world 1 points 1 year ago

remote desktop manager by devolutions powershell - duh ansible vscode sharex or greenshot (I've been favoring sharex lately) firefox with the container plugin (so I can keep the authentication contexts separate for all the o365 consoles I have to deal with)

[–] tupcakes@lemmy.world 1 points 1 year ago

yeah thats all been checked and or cleared out. I'm going to have them do a facetime screen share with me later today. I've been all over the intune and azure ad objects, test enrolled multiple of my own devices, and no other users are having this issue.

it's gotta be something the person is doing or isn't doing. normally I don't do this kind of support, but the helpdesk couldn't figure it out so it was escalated to me. it's super frustrating.

 

So I've got a weird situation. We have one iOS (iphone 13 with 16.5) device only that is having issues completing the enrollment process.

download and sign into company portal

sign into the company portal

installed the management profile (confirmed)

device reports as not registered by company portal

the device not being registered is causing CA policies to fail for the device so the user can't setup their apps like outlook or teams.

I've also confirmed there isn't another management profile installed for another mdm.

I've walked the user through the enrollment process a few times, with and without the authenticator app installed and setup. the device doesn't show as registered in the authenticator app either. trying to register the device in authenticator just gives an generic error saying something went wrong.

I did come across something online about supervised devices in this state when the device id in azure ad is all zeros (https://learn.microsoft.com/en-us/mem/intune/apps/app-configuration-policies-use-ios#configure-the-company-portal-app-to-support-ios-and-ipados-devices-enrolled-with-automated-device-enrollment) however in this case the device id is populated.

I've re-enrolled one of my devices to walk through the setup process to make sure it's not something with the CA policies or something else. as far as I can tell this person is setup just like everyone else that is using mdm.

Hopefully someone has an idea, because i'm out of ideas on this.