All Posts

Hi Gideeuup, To my knowledge, those Device Events are not publicly documented. Nethertheless, "Device Attribute Device MCC Modified"  as far as I remember is triggered when: - SIM card is changed or removed from device - Any network changes like roaming device If think "Device Attribute Phone Number Modified" is also linked to SIM card change and "Device Operating System Changed" means the OS is updated but this could also be triggered when applying some compliance policy with OS version.

There is no call-in line any more for support. That was done away with earlier this year. There is Chat capability on that webpage -- have you tried that because that can also be used to create a ticket. To get the access issues resolved, you'll want to open a non-technical support ticket to get it addressed.  If you have no way to talk to support via the Support page in Customer Connect, you'll need to reach out to your Account Exec within VMware to have them open a non-technical support ticket for you so you can get the access issue resolved. 

Thanks Joel. Yeah....that's the issue. I've tried the support page, but our SuperUser never set up a VMWare account in order to allow me to create support tickets and is no longer here. I've tried calling in to have that changed and have had no success.

The easiest way to open VMW support tickets now is to go to Customer Connect (https://customerconnect.vmware.com/), login, then click on the "Support" tab at the top of the screen. If your Customer Connect account is setup to create support tickets, then Get Support will provide you with several ways to create the ticket. If you don't currently have the ability to create support tickets, work with your company's SuperUser or Primary Contact to get that ability. They can assign you that ability via their Customer Connect account.

Just to be clear, I did not say your devices would not be impacted by an expired cert. The impact will fully depend on which cert or certs are expired. Your best bet is to contact VMW Support to get a better idea of what will and will not be impacted.

Thanks very much Joel! Just want to make sure the devices themselves won't be affected. No loss of personal data or operability? I guess we are moving away from iOS MDM so just want to confirm our end users won't be affected. 

This depends on which cert is expired. For example, if you have iOS devices and your Apple APNs cert has expired, those devices will be unable to communicate with WSO UEM to get profiles and other updates via UEM.

Symptoms When attempting an MDM enrollment on iOS 16 beta or iPadOS 16 beta, the enrollment will fail while installing the MDM profile with an error message that states "Profile Installation Failed" A Connection to the server could not be established.   Resolution The iOS 16 and iPadOS 16 beta versions need to be seeded into the UEM environment in order for enrollment to succeed. For SaaS customers: new versions of iOS and iPadOS will be seeded automatically.  For On Premise customers: please use the latest seed script to update your environment.  

For Workspace ONE training, I would first turn to Tech Zone. Go there and login using your Customer Connect (formerly known as My VMware) credentials. Next, in Tech Zone, click Start in the upper left corner and then Activity Paths and choose the Workspace ONE Activity Path. Most of the cards in the path are short lessons that are easily consumable. Because you already logged in, it will let you pick back up where you left off the next time you log in. You can skip the cards you already know. Some of the cards are also links into Hands On Labs where you can play with all the solutions in that HOL, not just the ones that are setup for that lab which is pretty cool.  If you find that you need more a more formalized setting, like an online instructor-led course or classroom training, those are also available via VMware Learning. Here is information on earning Certifications as well. For WSO, I'd recommend going for the VCP-DW 2022.

Ok, here's how you can get this pretty easily. You are going to have to be careful which groups you are choosing filter parameters from. This has burned me recently because I apparently wasn't paying attention to which group the filter was being pulled from. Here's how to create the report:  Add a new report and select Custom Report.  In Category, select Workspace ONE UEM then Devices Give your report a name so you can save it In the rules, type in "platform" in the Select Attribute area MAKE SURE you choose "Platform (Normalized)" from the Device group. If you select it from the default Apps group, you will not get the results you want.  Add "Windows Desktop" as the platform after the "includes" parameter. Refresh the Report Preview to see how many Windows Desktop records you have. Next, add a new rule and choose Devices > OS Version (Normalized) and make the rule reads like this: OS Version does not include (10.0.19044) Refresh the Report Preview and that will be the number of Windows Desktop devices that do not have the most current GA release of Win10.  Hope that helps,  Joel