Create a Shared Mailbox in Microsoft Exchange 2010

Thanks to: http://nchrissos.wordpress.com


A shared mailbox is a common mailbox that a group of users can open to read and send e-mail messages. It allows users to share a common calendar or a shared contact list. But how to create shared mailboxes in Microsoft Exchange 2010, since the Exchange Management Console (EMC) gui does not give you such an option? If you try to create a new mailbox, the only options are: User Mailbox, Room Mailbox, Equipment Mailbox and Linked Mailbox.
New Mailbox Wizard
New Mailbox Wizard
First execute the Exchange Management Shell (EMS) from the Microsoft Exchange Server 2010 menu.
Microsoft Exchange Server 2010 Menu
Microsoft Exchange Server 2010 Menu
The shell environment opens up
Exchange Management Shellvvv
Exchange Management Shell
A. Create a new Shared Mailbox
Type in the following cmdlet:
New-Mailbox -Name <Maibox Name> -Alias <Alias> -OrganizationalUnit "<OU path>" -Database "<Database>" -UserPrincipalName <E-mail Address> -Shared
And give the appropriate permissions to the user
Add-MailboxPermission <Mailbox Name> -User "<domain\username>" -AccessRights FullAccess
Add-ADPermission Research -User "<domain\username>" -ExtendedRights Send-As
For example, I will create a new mailbox called Info and setup user Secretary to have access.
New-Mailbox -Name Info -Alias info -OrganizationalUnit "mydomain.local/myCompany/myDepartment" -Database "DB1" -UserPrincipalName info@mycompany.gr -Shared
Add-MailboxPermission Info -User "mydomain\secretary" -AccessRights FullAccess
Add-ADPermission Info -User "mydomain\secretary" -ExtendedRights Send-As
Full detailed syntax and parameters are in this Microsoft link.
B. Convert a User Mailbox to a Shared one
Type in the following cmdlet:
Set-Mailbox "<Maibox Name>" -Type shared
And give the appropriate permissions to the user as well
Add-MailboxPermission <Mailbox Name> -User "<domain\username>" -AccessRights FullAccess
Add-ADPermission Research -User "<domain\username>" -ExtendedRights Send-As
For example, let’s suppose that we have created a user mailbox called Helpdesk and we need to convert it to a shared mailbox and give access right to user Operator.
Set-Mailbox "Helpdesk" -Type shared
Add-MailboxPermission Helpdesk -User "mydomain\operator" -AccessRights FullAccess
Add-ADPermission Helpdesk -User "mydomain\operator" -ExtendedRights Send-As
Full detailed syntax and parameters are in this Microsoft link.
The last two commands about access and send-as permissions can be configured from EMC gui, by selecting the mailbox and clicking on “Manage Send As Permission..” or “Manage Full Access Permission…” at the right pane of the window.
Access and Send-As Permissions
Access and Send-As Permissions

Comentarios

Publicar un comentario

Dime si la información de este blog te sirvio.

Entradas populares de este blog

Configuración de Hairpin NAT (VIP)

Imagen
 Thank to: https://fortixpert.blogspot.com/ Este artículo describe cómo configurar FortiGate para Hairpin con el uso de set match-vip y match-vip-only. En este escenario, tanto el PC como el Servidor están detrás de FortiGate y el PC quiere conectarse al Servidor apuntando a su dirección externa (92.0.2.10) en lugar de la real (10.10.10.10). Esto se llama Hairpin NAT. Solución : La solución dependerá de cómo sea el objeto IP Virtual (VIP). Solución 1 : La interfaz externa en el VIP está configurada a una interfaz particular (en este caso a wan1) #config firewall vip     edit "VIP"         set extip 92.0.2.10         set extintf 'wan1'         set mappedip 10.10.10.10     next end Nota: En este escenario, la IP externa VIP puede ser la misma que la IP de la interfaz (es decir, 92.0.2.2) Se necesitan dos políticas: 1) Una política de entrada con ...
Leer más

Deshabilitar los métodos HTTP peligrosos como PUT, DELETE y TRACE en Nginx

Imagen
  🔧 Paso 1: Editar el archivo de configuración de Nginx Objetivo: Configurar el servidor Nginx para que rechace solicitudes HTTP que usen los métodos PUT, DELETE y TRACE, devolviendo un código de estado 405 (Method Not Allowed) . ¿Por qué hacerlo? Por razones de seguridad . Algunos métodos HTTP como PUT , DELETE y TRACE pueden representar riesgos si no son utilizados correctamente. Si tu aplicación no los necesita, es recomendable deshabilitarlos. Instrucciones: Abre el archivo de configuración de Nginx. Generalmente se encuentra en: /etc/nginx/nginx.conf O también puede estar dentro del directorio: /etc/nginx/sites-available/ dependiendo de cómo esté estructurada tu instalación. Busca la sección que tenga location / { ... } o agrégala dentro del bloque server { ... } . Dentro de ese bloque, agrega las siguientes condiciones: location / { if ($request_method = PUT) { return 405; } if ($request_method = DELETE) { return 405; } ...
Leer más

Redundant or Backup ISP Links Configuration Example

Imagen
Thanks to:  http://www.cisco.com Introduction A problem with static routes is that no inherent mechanism exists to determine if the route is up or down. The route remains in the routing table even if the next hop gateway becomes unavailable. Static routes are removed from the routing table only if the associated interface on the security appliance goes down. In order to solve this problem, a static route tracking feature is used to track the availability of a static route and, if that route fails, remove it from the routing table and replace it with a backup route. This document provides an example of how to use the static route tracking feature on the PIX 500 Series Security Appliance or the ASA 5500 Series Adaptive Security Appliance in order to enable the device to use redundant or backup Internet connections. In this example, static route tracking allows the security appliance to use an inexpensive connection to a secondary Internet service provider (ISP) in the event th...
Leer más