Jump to content

Recommended Posts

Posted (edited)

Its very common for this to happen. We have 4 separate FQDN's for office 365 in our domain.

 

1 X Trust Domain

3 X One domain for each academy

plus

1 X the original .local not used by anything anymore.

 

No need to create a new domain or rename your existing domain. That would be just creating work.

 

You can use this scrip to quickly to change the UPN suffix once you have done the work on the original link.

 

https://community.spiceworks.com/scripts/show/1457-mass-change-upn-suffix

 

 

Its very unlikely that chaining suffix won't break anything either.

Edited by FN-GM
  • Thanks 1
Posted
thanks @FN-GM if memory serves me right the only thing that the upn suffix does is if you want to change the way you use your logon credentials i.e you can logon with your user name or if like you say you have multiple domains you can use the @ symbol please correct me if im wrong long time since my ms classroom days lol
Posted
That is correct. The only issue you may have is if are people are logging in with the .local upn suffix. This isn't usually the case.
Posted

We've gone done this path as well.

 

Still housing our Exchange for Staff, but have a .local domain. We added the UPN of the Office 365 FQDN and then added it for students only as they are on Office365.

 

Hasn't caused any issues.

 

Also added the students external email as mail contacts so they appear in the GAL for staff who are on our internal Exchange

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...