Meraki

thunt · ‎Nov 14 2022

Agreed. Sad. We have battled (and lost) the same issue.

thunt · ‎Nov 1 2022

We do use the Systems Manager agent on the device and we are getting this message. We enroll the device via Windows profile and then install the agent.

thunt · ‎Oct 31 2022

Agent version Current Version: 3.5.2

thunt · ‎Oct 31 2022

We are having the exact same issue. It works initially and then just stops working.

thunt · ‎Sep 9 2022

Meraki Windows MDM user updated their Windows 10 Enterprise machine to Windows 11 before we could block the ability to do so with a GPO. Now their Windows profile will not sync. Previously the Windows profile and agent were installed correctly per Meraki instructions and worked fine. we have tried uninstalling and re-installing the profile and agent but no luck resolving the sync error. I have seen posts about intune and this error but wanted to see if anyone here had an experience with this particular error or situation.

thunt · ‎May 6 2022

Same. Blocking our Connectwise Connect support product with NBAR ID 1889. I had to break out each individual P2P rule as a line item in the firewall. Pain in the A$$! Plus if a new category gets added I won't be protected unless I check on it periodically. Just one more thing to do. C'mon Meraki we need to allow an exception.

thunt · ‎Nov 8 2021

It would be a nice feature to have the ability to whitelist our pen tester's external IP addresses so that we do not have to turn off IPS while they can complete their scans. I hate being exposed even for a short period of time.

thunt · ‎Sep 15 2020

Why has 15.x not been pushed to at least RC status if it is so stable as so many profess? I do not share everyone elses optimism since the first line when you click the release notes for 15.x is: Important notice This is a beta version for the next major MX release. Due to this, we recommend taking additional caution before upgrading production appliances. Where applicable, MX 14 releases will provide a more stable upgrade alternative. The Meraki community has been BEGGING for IKEv2 for so long. IKEv1 shows up in every single audit and I am getting tired of justifying it. RFC 4306 updated IKE to version two in December 2005!! Why is this so hard for Meraki? I'm not being facetious. I'm not a software developer or a software engineer. It's a legitimate question. I want to understand. Why is this so hard?

thunt · ‎Nov 5 2018

I don't think anyone form Meraki monitors this

thunt · ‎Nov 5 2018

I had changed the device owner to an actual user (Bill Smith <bsmith@corp.com>) when this started happening to me and started see this same message when uninstalling and re-installing a play app on Android devices. I changed the owner back to the original "Android Enterprise User (123ab)" that appeared when I added the device to Meraki and the apps installed and the message "Your administrator has not given you access to this item" went away. The behavior of Android Enterprise devices and Apple Device Enrollment Program devices has a mighty steep learning curve IMO.

thunt · ‎Oct 23 2018

Winter is coming. Need some socks.

thunt · ‎Oct 12 2018

I am also having the same issue.

Meraki

Community

About thunt

thunt

Community Record

Badges

Re: MX NBAR blocking Statistical Peer-to-peer traffi

Re: MDM users needs to log in?

Re: MDM users needs to log in?

Re: MDM users needs to log in?

Windows 11 Profile - The sync could not be initiated (0x82ac0201)

Re: MX NBAR blocking Statistical Peer-to-peer traffi

Bypass Intrusion Detection/Prevention IP Whitelist

Re: MX v15 firmware still in beta

Re: Your administrator has not given you access to this item.

Re: Your administrator has not given you access to this item.

Re: Feedback time! We want to hear from you!

Re: IPv6 ACL Deny Any drops all IPv4 traffic

Re: MX NBAR blocking Statistical Peer-to-peer traffi

Bypass Intrusion Detection/Prevention IP Whitelist

Re: Feedback time! We want to hear from you!

Windows 11 Profile - The sync could not be initiated (0x82ac0201)