Hi everybody,   I figured out the problem and am now able to email support@meraki.com just fine. It was specifically caused by how Google Drive and Google Workspace handle interactions with external users. It's likely not something Meraki could fix unless they can see my account as some sort of guest in their own Workspace. I don't know much about how that works since we don't use Google for our email provider.   I imagine this is a very niche problem, but I'll add what I found out and my best assumptions below.   Q1: Why did the bounce-back say my Gmail account was disabled? A: Early last year, I received a Google Drive document from a vendor using a Google environment. I never created an account to access the document but I did receive a One-Time-Passcode to open the file inside of Google Drive. Near as I can tell, me accessing that document auto-created a Google account using my work email even though I didn't go through any setup process. I have not accessed that file since the day I received it, thus I have not even opened Google Drive for probably over a year. I imagine Google auto-suspends accounts like these after a period of no usage.   Q2: Why did the bounce-back happen when sending to Meraki support's email address but not others? A: Google processes emails to Workspace Group accounts and individual accounts differently. If a Gmail account is disabled (my auto-created account), it cannot send to group accounts. My assumption is support@meraki.com is one of those Workspace Group accounts. My organization deals with individuals so this is probably the first time anyone here has sent an email to a Google Group account.   Q3: How did it get fixed? A: I had to log in to the Google account tied to my organization email. That's it. Before I even logged in, it said my account was disabled. I was then emailed a One-Time-Passcode to sign in and it forced me to create a password and setup a Google account. The account I created doesn't appear to be set up like a typical account. It does not have Gmail capabilities by default, certain settings are turned off, etc.   Overall, this was an easy fix once I realized what happened. I now know more about Google Workspace environments than I ever wished. Google auto-creating an account like that then suspending it is a bit frustrating though. Especially when the person doesn't realize their Microsoft work email even has a Google account!   Thanks to everybody who gave suggestions! ... View more

Though I don't have experience specifically with this happening after license expiration, I have had to deal with orphaned MDM devices which I would assume would occur once the Systems Manager license expires. Assuming that's what would occur:   1. Will the settings remain on the smartphones that he has already setup? Answer: Yes. To remove the settings, you will need to either unenroll them first via Systems Manager, unenroll them on each device (if you allowed to be removed from the device), or erase each device AFTER the license has expired. 2. will the installed apps remain on smartphones? Answer: Yes, unless it is an app set to remove with MDM and you or the client were able to remove the MDM profile from the device. 3. Is there anything that he has to take care of that may happen if licenses are not renewed? Answer: No, if you unenroll the devices BEFORE the expiration period. Otherwise, they will need to remove the MDM profile on each device or erase it.   If I were you, I would start unenrolling them a couple of weeks before the expiration to give enough time to take care of any devices that may be turned off/lost network. If they are tied to something like Apple Business Manager, remove those as well. And if I were your client, I would erase the devices anyways. ... View more

A quick test you can do is to install the msi via PowerShell using the same installation arguments you have in SM. You'll get more information this way if it does fail and can troubleshoot from there. If it doesn't fail, then you can add a log switch in the installation arguments using /l*v "C:\Log\File\Path.log". If you can see download logs on the computer, I would think you would be able to create a log file too.   Hope this helps. ... View more

If you have the settings @ekramer configured then you should be able to do it from the device list. If you click the checkbox for the devices you want, there's a drop-down list called "Command" and you can choose "Send notification" from there. ... View more

You can view SM agent log files on Windows client machines at C:\Windows\temp\m_agent_service.log, m_agent_service.log.1, etc. You may also find logs specific to the software you tried to install in the same directory. There are also potential event errors that might occur. If you open Event Viewer > Applications and Services Logs > Microsoft > Windows > DeviceManagement-Enterprise-Diagnostics-Provider > Admin. Meraki has some documentation for these here near the bottom of the page.   Frankly, when this happened to me neither of those provided enough information to narrow down the cause. Redeploying or reinstalling at the client device did end up fixing it for me and I am still digging into why. ... View more