365, Azure, Active directory User name change and how did this happen?

[Snookered]

I'm going to try and keep this as concise as possible as I tried to do something relatively straight forward but the results have been driving me bonkers.

 

A user recently married and wanted their logon and email address changed to reflect this. Looking online showed me that when 365 is integrated with a sites AD the resulting sync does not always work out 100%.

I tried a couple of test names and came across some credential errors on the Azure directory, but with some online help got it working.

Confident that I had it sussed I backed up the users Outlook data and all of their stored documents etc. and got to work.

 

Initially all looked good, the email works fine but things have changed when attempting to log on to our domain.

 

if the user signs on with original name, they can't (good)

If they sign on with new name they can (good)

But when signed on it is if they are a brand new user, no documents in their networked drive (bad)

 

In the Active directory new name is shown (good)

 

When I go to the D drive where all our users data is stored original name is still there with all the documents (bad)

New name is not there (bad).

 

I manually changed all the attributes in the original name to the new name, was that wrong?

 

...and what else did I do wrong?

[Marshall_IT]

When you change the value in AD for home drive it doesn't rename the current folder, it just creates a new one if it's not there.

 

I either rename the folder manually or just copy the files across, either way, make sure to edit the home drive path say from Smith01 to Smith02 and then back again, then click apply. This will then ask if you want to apply permissions to this folder, which you do, so that the new (renamed) user is the owner etc.

 

With Office 365, if you are using AIR sync and not ADFS (not sure what happens in that respect) when you change a users UPN in AD it doesn't update that change to O365, you will need to run the following in powershell once connected to Office 365.

 

Set-MsolUserPrincipalName -UserPrincipalName [email protected] -NewUserPrincipalName [email protected]

 

I hope this makes sense.

[Snookered]

Hi

Where would I change the values in the AD for the Home drive?

On our previous Network each user had a profile with a logon script and a connect to path with the letter of the home drive. On our new network none of this is populated.

The user doesn't see a home drive as such but a documents folder holding only their documents. Could this have been set up this way in Group policy? (not by me unfortunately)

I got the email bit that you show at the bottom correct, that was the easy bit

[themightymrp]

It will either be under the Profile tab for the properties of the user in AD (look at the bottom for 'Connect to'), OR it could be done in a group policy either with a group policy preference for drive mappings or a logon script in the User Config section.

[Marshall_IT]

So they don't get a mapped drove for their home folders?

Their files are just under libraries, documents?

 

If that's the case then it'll be in gpo somewhere. Not sure how the folders are getting created though.

[themightymrp]

Just re-read your post. If they don't have a home drive letter assigned, just the Documents, then there is a folder redirection setting somewhere in a GPO.

[Snookered]

Cheers guys, I'll take a closer look in the GPO.

[Snookered]

It was incredibly simple in the end, just renamed the old name to the new name on the D drive and everything was picked it up fine.

Thanks for the help!