This post is more than 5 years old
190 Posts
0
733
October 17th, 2011 09:00
Change user name in AD
Hello,
I have a user that got married and her last name was changed. This worked fine (for over a year) until she received an new computer with Windows 7 on it. Anything she accesses on the Celerra she gets a popup for credentials. If she puts in her new user name and password, it goes through. It doesn't do this on Vista, XP, or Windows 2003 machines. Looking at the user mappings her old user name is in there. How do you update this? Edit the file directly or is there a command to refresh this? There have been a number of name changes since we imiplemented the Celerra and this is the first time we've had this problem. As far as I know, however, this is the only person with a Windows 7 machine so there may be others lurking that will hit this. DART version 6.0.40-5.
Dan
Rainer_EMC
4 Operator
•
8.6K Posts
0
October 17th, 2011 09:00
Depends on how you actually do user mapping
Did her account get a new SID when it was renamed ?
You can test with server_cifssuport (maybe on an extra VDM) to manipulate the secmap
Rainer
NickPOW1
94 Posts
0
October 17th, 2011 10:00
I believe the issue may be in the usermapper database on the Celerra and not in Windows. Please refer to: EMC Celerra Network Server Release 5.0 - Configuring Celerra User Mapping P/N 300-009-979 Rev A0. Page
17 provides conceptual information on creating a secmap mapping entry for the user. One can check the secmap entry for ther user and create one too. In any case I would recommend opening a customr support ticket to verify the procedure.
Nick
DanJost
190 Posts
0
October 17th, 2011 10:00
That put me in the right direction - ran the verify with cifssupport and then did the update on the VDMs and now everything matches (and popup is gone). Thanks!
Rainer_EMC
4 Operator
•
8.6K Posts
0
October 17th, 2011 11:00
What exactly did you do?
DanJost
190 Posts
0
October 17th, 2011 12:00
server_cifssupport ALL -secmap -verify -name thenewusername -domain SOMEDOMAIN.COM
This showed all of the DMs that had the wrong secmap.
Replace "verify" with "update" on each datamover that needed an update and the usermapper file gets updated and all of the verify's show a simple "OK"...well, for the ones in the right domain anyway but that's all I was concerned about.
Found the info I needed in the 6.0 Configuring Celerra User Mapping PDF.
Rainer_EMC
4 Operator
•
8.6K Posts
0
October 17th, 2011 14:00
Than it sound like the mapping in your user mapping source is correct now and the secmap still had the old mapping.
In that case an update on the secmap like you did is correct
Just be aware that this wont change the ownership of existing files.
If you are using multi-protocol you might also need to change these.
Or if you are using user quotas
Rainer