Hey so i am a bit new to jamf, so perhaps i am doing somethign wrong here.
Problem: Wifi network which is pushed with configuration profile, does not stick / stay for some reason.
So i have a configuration profile of a WPA2 key that i am trying to push to these new macbooks we just got. They are macbook pro with the new m1 chip in them (probably not relevant, just providing all info i can).
So i configure the configuration profile, apply it to the machines and then give them to the users. This was at the beginning of jan. The users which are a lab (24 devices) say that every day some subset of the macbooks will not be on wireless that day. How they resolve this is that they connect up a wired adaptor, login, and then they will work on wireless again.
I have an example on my desk right now. There is no wifi connections at all under "preferred networks". From the logs, i can see it was connected fine on friday in the evening after school was closed (10pm). So probably just sitting in its cart at that time passively connecting.
I thought the students were disconnecting it, so i put a policy so that changing wireless networks require admin approval, but the macbooks are still doing this.
I am new to jamf, so perhaps i am doing something wrong? why would it occur like this and is there any other way to set the wireless key that works better? I mean i can manually set it if i cant figure it out and remove the configuration profile entirely, but i kind of want this functionality to work.
Is the log time on jamf cloud (like the policy log local time or UTC time? Because on the machine i see it doing something weird in the wireless at around 9:30am on friday but it was still connecting to jamf untill 5:47pm that night.
