Hi Matt,
The Operating system is Windows 10.
The actions are executed from device in the portal.
There are no specific applications, it can be any.
What I see is that since the team was registered from another profile, the MaaS360 application does not appear in the user profile (The application that shows the messages, applications and configuration of the MaaS360, it only appears in the profile from where it was registered start, but the team does continue to report to the portal.
Regards,
------------------------------
Marlon Barrios
------------------------------
Original Message:
Sent: Thu March 05, 2020 09:57 PM
From: Matt Shaver
Subject: Name changes - marriage, divorce, etc
Hi Marlon -
I need a little more information - what type of operating system are you managing here? Where are the actions being executed from (group view or device view)? What kinds of apps are you trying to distribute?
------------------------------
Matt Shaver
System Architect
IBM
mshaver@us.ibm.com
Original Message:
Sent: Thu March 05, 2020 07:40 PM
From: Marlon Barrios
Subject: Name changes - marriage, divorce, etc
Hello good afternoon. I have a problem in relation to profiles and I see that it is related to what they have commented, in the infrastructure the end users who use the equipment do not have administrator permissions, due to security issues. Then the invitations were sent to the users and the credentials were copied in a notebook, the teams were registered to MaaS360 in the profile of a local administrator user with all the permissions and the teams were registered and appear in the portal and also report Now we are reviewing and not all the features of MaaS360 work, for example if from the portal you send a blocking request to the device, this works, but if you send a message or distribute an application or document, this does not work! Is there any way to make all the features of MaaS360 work, taking into account that the registration was made from the profile of a local administrator, but whoever uses the equipment is an end user and that it is not an option to unravel the agent and Install it on the end user.
I look forward to your comments, and thank you for your support.
Regards,
------------------------------
Marlon Barrios
Original Message:
Sent: Thu January 16, 2020 09:08 PM
From: Matt Shaver
Subject: Name changes - marriage, divorce, etc
Yes - the reason I stress "manual" enrollment is because there are automated enrollment programs available that require a full device wipe in order to start over, but those are not required to get user data to change. You can avoid the lengthier process of a full device wipe (and the potential data loss) by simply removing control of MaaS360 via portal actions (this can be done on an individual device basis or in bulk) and then having the users visit a web URL or download our agent (depending OS type) and entering the updated AD information to re-enroll.
This could still cause potential data loss as apps and docs could be removed by having the user unenroll, but it's not as cumbersome a process as a full device wipe. There is also the option of simply changing some variables in the portal policy, though this might be less than ideal if record keeping is a top priority, as we'd use custom attributes to map the new data for device services such as email login, but the device would remain enrolled under the old username, domain, and email address.
------------------------------
Matt Shaver
System Architect
IBM
mshaver@us.ibm.com
Original Message:
Sent: Thu January 16, 2020 05:57 PM
From: Ann Grif
Subject: Name changes - marriage, divorce, etc
Matt, many thanks for your quick reply. I'm desktop support so don't have much experience with the server side of MaaS.
In opposite order -
I looked at the link, that seems very do-able. I guess which name appears as primary in the portal a business decision.
When you say removing control of MaaS360 and then going through a manual enrollment. Are you saying that something is done on the portal, and then the user uninstalls just the MaaS360 app on the phone and re-installs from the MaaS app catalog?
Again, thank you
------------------------------
Ann Grif
Original Message:
Sent: Thu January 16, 2020 04:45 PM
From: Matt Shaver
Subject: Name changes - marriage, divorce, etc
Hi Ann,
The users information that is passed down at the time of enrollment remains the same for the length of that enrollment, even if it changes in the portal. There are really two ways that you can approach this - the first is to un-enroll and then re-enroll the device. This doesn't generally require a full factory reset - just removing control of MaaS360 and then going through a manual enrollment.
The other option - if the concern is more about configurations than the name attached in the portal - is to simply use variables to map the new user info to the device. Custom attributes can work as well. More information on this can be found in our Knowledge Center: https://www.ibm.com/support/knowledgecenter/en/SS8H2S/com.ibm.mc.doc/pag_source/concepts/pag_users_attributes.htm
If you have any questions around specifics, feel free to reply here.
------------------------------
Matt Shaver
System Architect
IBM
mshaver@us.ibm.com
Original Message:
Sent: Thu January 16, 2020 02:27 PM
From: Ann Grif
Subject: Name changes - marriage, divorce, etc
When someone changes their name, and their AD account and email are updated, I've been told by the MaaS server techs in my company, that iphone users need to completely reset their phones and re-enroll in MaaS with the new name/email.
Can someone point me to a link that explains this, or a link that I can send the server techs that explains how it should be done.
thank you
------------------------------
Ann Grif
------------------------------