We have several Room Resources setup in Exchange 2013. When people are looking at the room calendar they would see the name of the organizer rather than subject of the…
Category: <span>Exchange</span>
We started getting reports that some people were not getting their email on their mobile devices. I did some checking and this appeared only effect mailboxes that were in databases…
We require our users to change their password periodically like most organizations. I’m also sure like other organizations, our users typically ignore the warnings when logging in until they are…
So I did some updates on our Exchange 2013 servers last week, and then started getting some complaints that people couldn’t see there calendar when the logged into OWA. Once…
We have an Exchange admin that when he attempted to login to ECP he would get a 500 error. The simple solution was to add a mailbox to his domain…
Earlier this week I started getting alerts that our Exchange 2013 server was running low on disk space for our transaction logs. When I started looking at the drive, I…
We have several room resources in our Exchange 2013 environment. Occasionally, we need to make changes so new people can actually see what appointments are scheduled and not just see “busy” in the time slot. I used to be able to make these changes via Exchange Management Console in previous versions of Exchange; however, it looks like I have to go to Exchange Management Shell now.
Today we had someone make a request for a few users to be able to see what appointments were scheduled for some room resources. They didn’t want these people to add any appointments, but just needed to be able to see what was scheduled rather than seeing “Busy”. I came across this site which has the PowerShell commands to set the Reviewer permission. The article talks about changing the Default user permission which is not what I wanted to do. So I used add–mailboxfolderpermission cmdlet instead of the set-mailboxfolderpermission cmdlet.
At work we are getting ready to create new user accounts for everyone and move their mailbox from the current AD account to the new account. The reason for this is a bit lengthy, but a big reason is people have been granted permissions based on their AD account rather than by group membership. So by switching AD accounts we can clean things up a bit. Currently the format of our usernames is first initial last name (example: John Doe is JDoe), and we will be changing to a first name dot last name format (example: John.Doe).
Today I’ve been looking into how I can create and Exchange Mailbox using PowerShell.
A little background. We have been using PowerShell to create new Active Directory accounts for awhile, but hadn’t looked into being able to create the mailbox on Exchange at the same time. The biggest problem (more a concern) is that I thought we needed to install the Exchange Management Tools (EMC and EMS) on our domain controllers or admin desktops. I was concerned these servers and computers wouldn’t get updated at the same time as our Exchange Servers and I didn’t want services packs and other updates to get out of sync.