From time to time we come across scenarios where a meeting room or resource has been removed, relocated or we simply would like it to show another name than the original one in our system.
So, is there an easy way to rename the resource in Exchange and have it reflected in the users calendar for previous bookings?
The answer is Yes, and No.
Renaming of the resource is fairly simple using PowerShell. You have to change the attributes Name, Alias, DisplayName, SamAccountName, and UserPrincipalName.
Set-Mailbox “TestRoom” -Name “NewTestRoom” -Alias “new_testroom” -DisplayName “New Test Room” -SamAccountName newtestroom -UserPrincipalName firstname.lastname@example.org
You also have to change the FirstName attribute using the Set-User command:
Set-User “NewTestRoom” -FirstName “NewTestRoom”
So, does this do the trick?
The answer is yes, in regards to new bookings. The problem is that the name change does not reflect in the previous bookings of the resource. The old name will still show in the booking, but if you click on the name of the room, the new name will show in the properties of the resource.
There is no way to change the name of the room without deleting the booking and make a new reservation with the new name. The room is reserved in the system with the old name, and there is no way for Exchange to display the new name in available resources(if you choose Change Room in the booking) without deleting the reservation and making a new one.
As you all probably know, Microsoft has enabled the possibility of having Dial-in PSTN Conferencing in Skype for Business Online. In order to do this, you either have to have an E5 license plan in O365, or you can purchase the add-on for PSTN Conferencing in your excisting E1 or E3 plan.
PSTN Conferencing is a very valuable add-on to the O365 Skype for Business as it will enhance the possibilities of joining meetings without having to use a client.
To read more about PSTN Conferencing, visit this site on Microsoft.com:
To se which countries have PSTN Conferencing available, check out the list here.
I was doing a migration between Exchange 2013 and Office 365 in a Hybrid configuration when I recieved the above error message. Couldn’t quite figure out why until I stumbled accross a forum thread that pointed me in the right direction.
This is what you have to check out and remediate if you have this error:
The ExchangeGuids of on-premise users are different to the ExchangeGuids of the corresponding users in Office 365.
Update the online user’s ExchangeGuid to match the on-premise ExchangeGuid and start migration.
1. On the on-premise Exchange server:
Get-MailBox -Identity userID | Select ExchangeGuid
2. In an Office 365 PowerShell session:
Get-MailUser -Identity UserID | Select ExchangeGuid
If the results don’t match, copy the guid result from command 1 and then run the following command in the Office 365 PowerShell session:
Set-MailUser -Identity userID -ExchangeGuid “copied guid”
$Cred = Get-Credential
$s = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell -Credential $cred -Authentication Basic -AllowRedirection
$OnPremAdmin = Get-Credentials
New-MoveRequest -identity “UPN” -Remote -RemoteHostName “remote host ex OWA URL mail.domain.com” -RemoteCredential $OnPremAdmin -TargetDeliveryDomain domain.mail.onmicrosoft.com
This is a great post done by Skype4B enthusiast Mark Vale on Cloud PBX and Office 365 E5 which is to be launched in the US on December 1st 2015. I recommend everyone to read his thoughts and keep them in mind.
Source: Skype for Business Cloud PBX with PSTN Calling – 5 Steps to Success