Posted on 12-12-2024 03:57 PM
We have gotten some feedback from users that are working remotely about our Macs imaged through Jamf Connect. Users are seeing the message on their wifi, "Wi-Fi networks are currently unavailable." Users without hardline options are unable to login to the machines.
We are currently using Jamf Connect v. 2.37.0
Has anyone seen this issue before and if so, how did you resolve it?
Note: Potentially 16 machines affected as we halted production until we resolve this.
Solved! Go to Solution.
Posted on 12-13-2024 05:51 AM
You could be hitting the following product issue.
[PI119511] The Jamf Connect login window currently displays the following message, even while computers have an active network connection: "Wi-F networks are currently unavailable".
This product issue is resolved in Jamf Connect 2.41.0 according to the release notes.
Posted on 12-13-2024 05:48 AM
Are the users at the same location or different locations? Have the users tried known working networks like a cellphone hotspot just to see if the Mac can see the network?
I have to poke fun on this: "Macs imaged through Jamf Connect" is wrong on so many levels :). You can't "image" Macs, and "Jamf Connect" is not a management tool. Macs would be configured by Jamf Pro and have Jamf Connect installed as a part of the configuration.
Posted on 12-13-2024 05:51 AM
You could be hitting the following product issue.
[PI119511] The Jamf Connect login window currently displays the following message, even while computers have an active network connection: "Wi-F networks are currently unavailable".
This product issue is resolved in Jamf Connect 2.41.0 according to the release notes.
Posted on 12-13-2024 12:12 PM
Ended up being the issue. We are upgrading our Jamf Connect version now so we won't run into it again.
Thank you!
Posted on 12-16-2024 12:50 AM
Well, as TWF informed here, we able to upgrade to 2.42.0 the latest Jamf Connect and the Problem still persist.
"Allow network selection" is activated on the configuration Profile. it work as normal if we login one second time with the local Account.
Anyone an idea what can cause this?
20 hours ago
This issue still persist even with version 2.43.0. We researched on web and looks it's not fully solved until July 24. Yes, we have workaround but it's impacting onboarding and someone should be giving us ETA...