In previous versions of Exchange, you would need to access the user’s mailbox to be able to do this. Without access to the mailbox, you can’t modify data in it.
Two ways for an exchange/domain administrator to access an user mailbox:
- Grant yourself full Access mailbox permission to the user’s mailbox.
- Change the user’s password and log in as the user.
The first option grants the administrator access to all of the data in the user’s mailbox.
The second option grants the administrator access to all of the data that the user account can access within your company and locks the user out of his own user account.
Configure auto-reply options using the ECP
In Exchange 2010 SP1, you can configure auto-reply options for your users without using either of the above options.
Login to ECP through owa as Administrator or member of that group. Click options (right side top) and select “See all options”, From this screen, where “Manage Myself”, click “Another User” -> select the user you want and double click on the user. This will open his mail option ECP, and click “Tell people you’re on vacation” -> and select Automatic Replies and fillout the information and click Save.
Configure auto-reply options using the Shell Command
This command schedules internal and external auto-replies
Example, if a user is going on leave from 11/11/2011 to 12/10/2011: (MM/DD/YYYY format)
Set-MailboxAutoReplyConfiguration firstname.lastname@example.org –AutoReplyState Scheduled –StartTime “11/11/2011” –EndTime “12/110/2011” –ExternalMessage “External OOF message here” –InternalMessage “Internal OOF message here”
For detailed syntax and parameter descriptions, see Set-MailboxAutoReplyConfiguration (Applies to Exchange Server 2010 SP1).
This command retrieves auto-reply settings for a mailbox.
This command disables auto-reply configured for a mailbox:
Set-MailboxAutoReplyConfiguration email@example.com –AutoReplyState Disabled –ExternalMessage $null –InternalMessage $null
To check the status of the exchange server service, go to EMS…and type get-service *exchange*
Earlier i’ve done the Exchange server migration – 2007 to 2010 – Live cast, Its been 10 months since Exchange team release the SP1 for Microsoft Exchange server 2010….today i’m doing Microsoft Exchange server 2010 SP1 upgradation…Live page is opened.
Problem impacts Exchange management tools on servers running Exchange 2010 on
- Windows Server 2008 SP2
- Windows 2008 R2 RTM
Symptom: Event ID 1000 & 1023
- Faulting application Powershell.exe, version 6.0.6002.18111, time stamp 0x4acfacc6, faulting module mscorwks.dll, version 2.0.50727.5653, time stamp 0x4d54a59c, exception code 0xc0000005, fault offset 0x00000000001d9e19, process id 0x%9, application start time 0x%10.
- .NET Runtime version 2.0.50727.3053 – Fatal Execution Engine Error (000007FEF9216D36) (80131506)
- Exchange Management Shell does not start
- Exchange Management Console does not start
- There might be a crash in Exchange Mailbox Replication Service (it is not clear yet if this is related)
- Event Viewer might have trouble opening
Another nice feature introduced in Exchange 2010 is Administrator Audit logging. Audit logging allows an organization to examine different policies. A second important benefit is the review of configuration changes made to the Exchange organization through the Exchange Management Console, Exchange Web Services, and Exchange Management Shell. Audit Logging is useful in tracking configuration changes made within an Exchange Organization, and help identifying any errors. In Exchange 2010 Microsoft introduced AdminAuditLogConfig.
Check out the following commands
To enable if its disabled: Set-AdminAuditLogConfig -AdminAuditLogEnabled $true :http://technet.microsoft.com/en-us/library/dd298169.aspx
Search in the AdminAuditLog: Search-AdminAuditLog –Cmdlets New-Mailbox, Remove-Mailbox | FT :http://technet.microsoft.com/en-us/library/ff459250.aspx
Microsoft article about AdminAuditLog, Click here
Most of you guys must have experience the scenario when “Outlook connection lost….” even if you have Exchange server 2010 (with Edge, 2 clustered H&C and 2 DAG configured MB) and Outlook 2010 in place. The reason is that, when you are doing a maintenance on one of the H&C, and if the client is connected to that H&C, communication to the MB is lost. The reason for this is that the cluster load balancing on the H&C cluster handler is not in place, even if the cluster name is published in the DNS server.
In Exchange 2007, 5 server roles that performed distinct functions within the Exchange organization. One role in particular – the Client Access server role – introduced a variety of new Web services, including the Availability service, the Auto discover service and Calendar Concierge services.
In Exchange 2010, same 5 server roles exists. However, there are some significant architectural changes and some shift in responsibilities. The most significant change in Exchange 2010, two new services on CAS called the RPC Client Access and Address Book services establish the RPC (Repote Procedure Call) endpoint for MAPI(Messaging Application Programming Interface), NSPI(Name Service Provider Interface) and RFR (Request for Response) client access. This new functionality replaces the RPC endpoints in the Information Store. The RPC endpoint in the Information Store has not been removed in Exchange 2010, but it has been modified to only accept requests from CAS servers. The RPC endpoint for public folder database access remains on the Mailbox server, however, Outlook clients now communicate directly with the RPC Client Access service on the Mailbox Server for public folder database access, and not with the Information Store.
When CAS starts communicating with the Mailbox server, it makes sense to view it as the Client Access server communicating with the Mailbox database via the Mailbox server that hosts the database. This is especially evident in a load-balanced array of Client Access servers and/or where your environment is configured to use Database Availability Groups that are associated with a Client Access server or Client Access server array.
- In a non-load balanced environment, the mailbox database is associated with only a single Client Access server.
- In a load-balanced environment, the Mailbox database is associated with the load balanced array of multiple Client Access servers.
By default, before a Client Access array is configured,
- all databases are associated with a Client Access server in the environment
- the Outlook clients communicate directly with the Client Access server until the association with the database is updated to be the Client Access array.
In order for the clients to utilize a CAS array
- Create a Client Access array with an FQDN (Fully Qualified Domain Name).
- Load balance your CAS servers in a CAS array by whatever method you choose – Both Hardware LB or Windows Network LB are supported load balancers
- Add the Client Access servers within the AD site to a load balanced array and in DNS associate the unique FQDN to the Virtual IP of the load-balanced array.
- Configure your load balancing array to load balance the MAPI RPC ports – TCP 135, UDP/TCP 6005-65535; or set static ports
- Configure the databases to utilize the CAS array… Use the new-clientaccessarray cmdlet to create the CAS array object. Eg: New-ClientAccessArray –Name “Tromso CAS Array” –Fqdn tromso.site.com” –Site “SITEA”
How to Setup!!!..
Goto one of the CAS server where the NLB is ( to read more about New-ClientAccessArray cmdlet, click here )
 Check is there are any pre-created CAS Arrays. PS Command : Get-ClientAccessArray
 Create new Client Access Array. Run the Cmdlet in EMS New-ClientAccessArray -Fqdn server.contoso.com -Site “Redmond” -Name “server.contoso.com”
 Associate databases with this CAS Array –
Use this CMDLet to add mailbox database to CAS array. Add all mailbox databases at once – Get-MailboxDatabase | Set-MailboxDatabase -RPCClientAccessServer “CASNLB.contoso.com”
Now the best part –
Configuring Outlook 2010 using Auto Discover
If you already configured Outlook client, Close the outlook, then goto Control Panel->Mail and change the Server name to the new CAS NLB name
If you are going to use a new outlook configuration, Auto discover will return the new CAS NLB name.
Thats all folks!!! Enjoy!!!
Un-installing/De-commissioning Exchange server 2007 Mailbox from Passive cluster node for Exchange 2010
Open the command prompt of the Passive mailbox server..make sure you logged in as domain administrator.
Go to C:\Program Files\Microsoft\Exchange SErver\Bin
Type the command setup /mode:uninstall
Now you have successfully uninstall the Exchange server mailbox role from the passive node, but the cluster environment server information still exists, and we need to remove that as well.
To do that we need to…
- Open the Cluster Management Tool
- Expand the cluster resource name
- Expand the Nodes
- Right click the passive node server
- Click on More actions -> click on “Stop cluster service”
Once you “Stop Cluster Service”, then click on More actions again and click Evict and click the Evict Node….
Once you done this, restart the server.
Once the server is up…do the following too
- Open the Server manager console
- Click on Features and then click on Remove Features
- Uncheck Failover Clustering
- Click on Yes to reconfirm and click on NEXT
- Click on Remove.
- After the Server is restarted
- Remove any remaining files and folders from the Exchange Server program files folder and subfolders.
Thats the end of Exchange Server 2007 Mailbox de-commissioning on a Passive node….Now go to the Active mailbox server of Exchange server 2007
This process is not as same like passive node. Here we can’t go with uninstall command only, because this server holds the culstered mailbox server information and it is online. In order to remove this,
Go to the command prompt..change the directory to C:\Program files\Microsoft\Exchange Server\Bin
Type command setup.com /removeCMS /CMSName:<Clustername>
This will take the mailbox now offline from the cluster…
Now type setup /mode:uninstall
Once you finish this uninstallation, Exchange server 2007 last mail box has been remove from your domain..now do the evict
Goto command prompt (If the command prompt is open, close it and open it and then type
Cluster <mailbox cluster name> node <nodename> /force
That’s the end of the “EXCHANGE SERVER 2007 DE-COMMISSIONING PROCESS”
Now you are completely depended on Exchange server 2010.
Activate the product key for Exchange Server 2010 (for each role installed)..otherwise you can run it for 119 days…!!!!
To activate the same, from the Exchange Management console of 2010, right pannel, you will see “Enter Product Key”…and enter the product key which comes with it…!!
It is difficult to delete old public folder from EMC. How to do it, use the ADSIEDIT to clear the old ones.
Right click on the folder you want to delete from CN=Exchange Administrative Group, CN=Databases, and click delete. The go to Active directory Sites and Services and initiate the replication across the domain.
Go to EMC and refresh.