This is an archive of the Maximo Yahoo Community. The content of this pages may be a sometimes obsolete so please check post dates.
Thanks to the community owner Christopher Wanko for providing the content.
have an active user in the system that was married recently hence her last name changed.
This change will be made in ADirectory. I'm looking for options and suggestions on how to handle this in the maximo environment.
She has a user record and person record but i dont believe she is part of any groups receiving email notifications generated by escalations.
thanks for the help
This is a real pain in an AD connected environment and something we have
struggled with for some time now. There is no good answer. You
basically have two bad options to choose from.
1. Allow the change in AD to create a brand new user. The downside to
this is all history will not follow along to the new user. If the
history following is not that important to your organization then this
is the cleaner option.
2. Update the MAXUSER, PERSON and all record references BEFORE the
change is made in AD. This must be done by a script through the
back-end (bad practice) and the script must find and update all
references to PERSONID so the history follows along. This is a pain and
very easy to really mess up if you're not careful. Once this is changed
in the MAXIMO objects, the AD change may be made and the VMMSYNC job
will find the existing rather than create a new and all should be well.
-Chris H
-----Original Message-----
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf
Of oscjake
Sent: Wednesday, August 14, 2013 11:22 AM
To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] User Name Change Process
have an active user in the system that was married recently hence her
last name changed.
This change will be made in ADirectory. I'm looking for options and
suggestions on how to handle this in the maximo environment.
She has a user record and person record but i dont believe she is part
of any groups receiving email notifications generated by escalations.
thanks for the help
Hi,
We don't use personal names for users in any system - we have a sequential code allocated by HR as part of the set-up process, which is valid on all authorised systems. That way when personal names change there is only a textual update, not a code one.
--- In MAXIMO@yahoogroups.com, "Hanna, Christopher A CTR" <christopher.a.hanna@...> wrote:
>
> This is a real pain in an AD connected environment and something we have
> struggled with for some time now. There is no good answer. You
> basically have two bad options to choose from.
>
> 1. Allow the change in AD to create a brand new user. The downside to
> this is all history will not follow along to the new user. If the
> history following is not that important to your organization then this
> is the cleaner option.
>
> 2. Update the MAXUSER, PERSON and all record references BEFORE the
> change is made in AD. This must be done by a script through the
> back-end (bad practice) and the script must find and update all
> references to PERSONID so the history follows along. This is a pain and
> very easy to really mess up if you're not careful. Once this is changed
> in the MAXIMO objects, the AD change may be made and the VMMSYNC job
> will find the existing rather than create a new and all should be well.
>
> -Chris H
>
> -----Original Message-----
> From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf
> Of oscjake
> Sent: Wednesday, August 14, 2013 11:22 AM
> To: MAXIMO@yahoogroups.com
> Subject: [MAXIMO List] User Name Change Process
>
>
>
> have an active user in the system that was married recently hence her
> last name changed.
>
> This change will be made in ADirectory. I'm looking for options and
> suggestions on how to handle this in the maximo environment.
>
> She has a user record and person record but i dont believe she is part
> of any groups receiving email notifications generated by escalations.
>
> thanks for the help
>
Yep, if you have that option, that is a great solution. From a data
modeling perspective, had the designers used PERSONUID instead of
PERSONID for all external references this would not be such an issue.
Never quite understood why almost all Maximo objects have a surrogate
key but it is seldom used for anything.
-----Original Message-----
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf
Of peter.males
Sent: Monday, August 19, 2013 9:54 AM
To: MAXIMO@yahoogroups.com
Subject: Re: [MAXIMO List] User Name Change Process
Hi,
We don't use personal names for users in any system - we have a
sequential code allocated by HR as part of the set-up process, which is
valid on all authorised systems. That way when personal names change
there is only a textual update, not a code one.
--- In MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com> ,
"Hanna, Christopher A CTR" <christopher.a.hanna@...> wrote:
>
> This is a real pain in an AD connected environment and something we
> have struggled with for some time now. There is no good answer. You
> basically have two bad options to choose from.
>
> 1. Allow the change in AD to create a brand new user. The downside to
> this is all history will not follow along to the new user. If the
> history following is not that important to your organization then this
> is the cleaner option.
>
> 2. Update the MAXUSER, PERSON and all record references BEFORE the
> change is made in AD. This must be done by a script through the
> back-end (bad practice) and the script must find and update all
> references to PERSONID so the history follows along. This is a pain
> and very easy to really mess up if you're not careful. Once this is
> changed in the MAXIMO objects, the AD change may be made and the
> VMMSYNC job will find the existing rather than create a new and all
should be well.
>
> -Chris H
>
> -----Original Message-----
> From: MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com>
> [mailto:MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com> ] On
> Behalf Of oscjake
> Sent: Wednesday, August 14, 2013 11:22 AM
> To: MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com>
> Subject: [MAXIMO List] User Name Change Process
>
>
>
> have an active user in the system that was married recently hence her
> last name changed.
>
> This change will be made in ADirectory. I'm looking for options and
> suggestions on how to handle this in the maximo environment.
>
> She has a user record and person record but i dont believe she is part
> of any groups receiving email notifications generated by escalations.
>
> thanks for the help
>
We tied our A/D authentication to user name field not the user id so when a name change is required you just change the User Name and the user has a new access id.
Roy Cline
Phone: (203) 492-8189
Cell: (203) 640-9743
FAX: (203) 492-8462
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of oscjake
Sent: Wednesday, August 14, 2013 11:22 AM
To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] User Name Change Process
have an active user in the system that was married recently hence her last name changed.
This change will be made in ADirectory. I'm looking for options and suggestions on how to handle this in the maximo environment.
She has a user record and person record but i dont believe she is part of any groups receiving email notifications generated by escalations.
thanks for the help