***Flashback Exchange 2003***
You have been tasked to create a mailbox that will be shared by everyone in the marketing department.
Most likely, you just created a mailbox enabled user account, and handed out the password to everyone (or you just delegated mailbox rights to a security group). Either way, there was now an enabled user account that some information security departments may take offense too.
Well, the Exchange team heard your cries of displeasure and decided to do something a little different in Exchange 2007. The change that I’m referring to is the concept of a shared mailbox recipient type. A shared mailbox in Exchange 2007 is a recipient that relates to a disabled account in Active Directory. With no need create an active user account means no need to set a password, I’m sold. There is just one catch. You cannot create these accounts using the Exchange Management Console (EMC).
As you may have guessed, to create a shared mailbox you must use the Exchange Management Shell (EMS). Like many things in Exchange 2007, this is yet another example of why you need to be proficient with PowerShell and the EMS in order to manage your organization. Anyhow, to create a shared mailbox you would use the new-mailbox cmdlet with the –Share switch parameter:
new-mailbox -alias "marketing123" -name "Ye Marketing Mailbox" -database "mvexccr01\SG3\MBDB03" -org "comp.com/Accounts" -shared -UserPrincipalName "firstname.lastname@example.org"
My next post will cover the question that is most likely now boiling over in your mind. “Now that I have created a shared mailbox, how do I grant users access to that mailbox?”
For all of today's Microsoft news, visit Microsoft Subnet
With more than ten years of experience in IT, Tyson Kopczynski has become a specialist in Active Directory, Information Assurance, Windows automation, PKI, and IT security practices. Tyson is also the founding author of the Windows PowerShell Unleashed series and has been a contributing author for such books as Microsoft Internet Security and Acceleration (ISA) Server 2006 Unleashed and Microsoft Windows Server 2008 R2 Unleashed. He has also written many detailed technical papers and guides covering various technologies. As a consultant at Convergent Computing, Tyson works with and provides feedback for next generation Microsoft technologies since their inception and has also played a key role in expanding the automation and security practices at CCO. Tyson also holds such certifications as the Certified Information Systems Security Professional (CISSP), the SANS Security Essentials Certification (GSEC) and SANS Certified Incident Handler (GCIH), and the MCTS (Application Platform, Active Directory, and Network Infrastructure).