I'm just baffled as to why deleting a machine from network in device list does NOT do that. I would have expected that that action along with an erase and install would render the machine as a new client. If Meraki can send an email stating that DEP setting have changed for a particular serial number then surely it should be able to purge this info from SM so that re-enrollment should be as advertised. As per article ID: 1267 Removing Settings from Devices In the event a device needs to be reset and managed under different conditions, the settings applied via DEP can be removed. Navigate to Systems Manager > Manage > DEP. Click the checkbox next to the device(s) in question. Click Remove settings. and voila nothing... ... View more

AWESOME!!!! ... View more

Hi Phil~ I definitely feel your pain on this one!  The KEXT issues that have come with the added security of 10.13.4 do have a viable workaround (albeit a manual one): create .mobileconfig payloads that are delivered as profiles to the macbooks.  You could have individual ones or keep a master list.     Short Version: 1. Create a apple profile / .mobileconfig file that allows the application 2. In Meraki Go to  System Manager > MDM Settings > Add Profile  > Upload custom Apple profile   For details on step 1 and some excellent info from user sshort, go to this thread: https://community.meraki.com/t5/Endpoint-Management-Systems/whitelisting-kernel-extensions-via-team-id-s/m-p/21446#M2437  edit:  I see that you ran into that thread. I do agree that this shouldn't have to be a "thing".  It's taking a bit of time for developers to catch up to these added securities at the kernel level.  I will kudos your post for sure.   ... View more

hey Adam, Despite saying that I would not "be registering it via the below Settings > Accounts > Access work or school instructions" again, I did. I also re-installed the agent. Then removed all tags and owner from the device on Meraki Deshabord and ensured no policies were being enforced. THEN, I deleted the agent on the Win10 system, and unsync'd it from the "Access work or School" setting. LASTLY, I deleted it from the Meraki Dashboard.... Waited several hours and re-added that same machine with success (following the official Meraki steps which include the Settings > Accounts > Access work instructions...). So yes this main issue on this thread was addressed since the Win10 client now checks in properly without the red banner. BUT the looping issue continues, and I'm working on that one here https://community.meraki.com/t5/Endpoint-Management-Systems/password-policy-in-Windows-10/m-p/4159 ... View more

Thanks for the follow up. I will give this a try. ... View more

Hello Community~ I hope everyone had an awesome and safe Independence Day.   Here are the steps I took to continue the testing: On the Windows Client click start > type connect to work > click on the best match result > Clicked on Enroll only in Device Management > Entered in my work email > the server info > my network ID Windows device successfully connected. Confirmed client appeared in Dashboard. Removed any auto-tags that attached. note: No live tools appear, but that is expected.  Logged out and back in. Password remained intact. Downloaded the agent onto the Windows Client and installed it. Waited 15 mins. Checked client in the dashboard and the Live Tools appear. Tested notifications, screenshot and remote desktop successfully. Sent a reboot command to the Windows Client using Power Control successfully. Logged in without password change prompt on both accounts on that client. Waited 1 hour and tested the passwords again via logoff/logon and also a reboot and they remained intact.   Now I have a baseline. The client is checking in, reporting activity, and not prompting for password changes. We know  per Tech Support that adding a profile with a password payload will trigger the issue. I will refrain from adding any profile payload at all. Next Phase of Testing: Add tags to the Windows Client, Create a Windows Custom App and attach those tags, and prior to pushing that app, ensure that this does not cause the password loop issue.  I will report again.   out-of-scope research: Confirm why this system fails the policy audit due to "FW not installed, FW not enabled, AV not running" even though Windows Defender and Windows Firewall are both enabled / running / updated.    ... View more

JAMF is fantasic and super powerful for *just* Mac OS and iOS devices. My end users want more. They want Windows OS, BYOD, Chrome OS..etc... JAMF just won't do that. So, we either buy a SECOND tool to do that, or migrate to one tool to use them all. Plus, cost wise, 1 year of JAMF = 3 years of Meraki.... My accounting guy really loved that math. ... View more

Thanks jared_f. This gets us partway there 🙂 ... View more