Sequence for shutting down Exchange 2010 Servers

I have 3 mailbox servers, 3 CAS servers, 3 hubtransport servers, in active production, and I have 3 mailbox servers, 3 cas servers, and 3 hubtransport servers, as a DR. I have a DAG between them and a Cassarray
These Servers are virtualized using vmware.
I need to know microsoft's BPA for shutting down these servers to move to another location.

Follow these- are you completely shutting down the server or planning to do the maintenance.?
http://exchangeserverpro.com/forums/exchange-server-2010/3186-datacenter-power-shutdown-need-shutdown-all-exchange-servers.html
http://www.kreslavsky.com/2011/04/shut-down-exchange-2010-dag-member.html
The correct way to perform any maintenance is to run first StartDagServerMaintenance.ps1 script that is located under “C:Program FilesMicrosoftExchange ServerV14scripts”
This script moves all the active databases to next preferred DAG server and prevents active databases from moving to that server during the maintenance.
In addition the script ensures that all critical DAG support functionality that may be on this server has been moved to next proffered server
Once the DR site servers are in maintenance mode you can bring the serves down in DR site first, CAS and then Hub.
And then on the Primary Site shutdown the CAS and HUB, Dismount the DB and shutdown the servers.
Where Technology Meets Talent

Similar Messages

Can i create mcx for shut down properly mac when battery is less 5 %

Hi hello
Can i create mcx for shut down properly mac when battery is less 5 % ?
Thanks for your reply

You can create a mailing list by using the "Groups" feature of Address Book. Simply select "New Group" from the File menu. Name the group, and drag the contacts you need into the group.
In Mail, open up Preferences (under the Mail menu), and click on "Composing". Then make sure that "When sending to a group, show all member addresses" is unchecked.
The auto reply is a feature that is better done on your mail server, as you Mac can only send an auto reply when it is on, with the Mail application open. If you use dot Mac, you can set up a vacation responder through the web, and you can leave your computer switched off.
If you really want to leave your Mac on when you are on holiday, you can set up a mail rule (Preferences, Rules).

SCOM health check on Exchange 2010 servers

Hi,
Does SCOM have any built-in function to perform
health check on Exchange 2010 servers?

You can check health check of Exchange 2010 by install management pack of Exchange 2010.
Here's management pack of exchange 2010
http://www.microsoft.com/en-us/download/details.aspx?id=692
Before Import management Pack and how to configure it, you can check below link
http://technet.microsoft.com/en-us/library/ee758051%28v=exchg.140%29.aspx
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"

Error 1006 - Changing Ad Site for subnet where exchange 2013 servers was setup

We wanted to change Ad site for subnet where exchange 2013 servers was setup.
When we do that error id 1006 appear on 2 MBX Servers :
The Microsoft Exchange Mailbox Replication service was unable to process jobs in a mailbox database.
Database: Database02
Error: An attempt to logon cross-site for Mdb 'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx' was prevented to Server 'yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyyyy' in Site 'DomainAAA/Configuration/Sites/SiteB'. Local site is 'DomainAAA/Configuration/Sites/SiteA'.
DomainAAA - Our Domain
SiteA - AD site which temporarily cover subnet A and Subnet B
In subnet A are installed 2 DCs (Global Catalog) and other aplication servers.
In subnet B are installed all EX2013 servers (2 MBX and 2x CAS) ,1 DC (Global Catalog) and other app servers.
SiteB - new created AD site intended for subnet B
These subnets are on diferent physical location.
When we change Ad site for subnetB from the AD siteA to AD SiteB, above error appear.
There is a object ExchEdgeSyncService under the AD site : SiteA , where the installation EX2013 was done.
So do We need to create the new edgesyncservice under the siteB ?
What steps do we have to make ?
Our intention is to eventually remove all servers from the siteA and move to to SiteB.
So that siteA will no longer exist.
Thanks in advance , and sorry for bad english.
Best regards

Hi,
Why don't you just extend the VLAN so you don't have to create another site and do changes so much
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Krisna Ismayanto | My blogs: Krisna Ismayanto | Twitter:
@ikrisna

Best Practices for patching Exchange 2010 servers.

Hi Team,
Looking for best practices on patching Exchnage Server 2010.
Like precautions , steps and pre and post patching checks.
Thanks.

Are you referring to Exchange updates? If so:
http://technet.microsoft.com/en-us/library/ff637981.aspx
Install the Latest Update Rollup for Exchange 2010
http://technet.microsoft.com/en-us/library/ee861125.aspx
Installing Update Rollups on Database Availability Group Members
Key points:
Apply in role order
CAS, HUB, UM, MBX
If you have CAS roles in an array/load-balanced, they should all have the same SP/RU level. so coordinate the Exchange updates and add/remove nodes as needed so you do not run for an extended time with different Exchange levels in the same array.
All the DAG nodes should be at the same rollup/SP level as well. See the above link on how to accomplish that.
If you are referring to Windows Updates, then I typically follow the same install pattern:
CAS, HUB, UM, MBX
With windows updates however, I tend not to worry about suspending activation on the DAG members rather simply move the active mailbox copies, apply the update and reboot if necessary.

Provision for capacity alerts for Exchange 2010 servers on SCOM

Hi All,
This is one urgent requirement, please help.
We have around 25 exchange servers in our environment, we need to configure alerts to limit the threshold to 80-90% of mailbox.
My requirement is to configure SCOM alerts for mailboxes hosted on databases servers. In our environment we have set that a database should contain 208 mailboxes. So we need to have alert when mailbox limits reaches to 80% or 90% (say 180 mailboxes in number).
Please let me know hw to configure this alert and thresholds in SCOM?
Best Regards,
Harsha L P

Hi,
Have you import the Exchange management pack to your maagement group?
We may need to check the management pack guide to find if there is any monitor or rule which can do this.
Regards,
Yan Li
Regards, Yan Li

Shutting Down Exchange 2003 System after move to Office 365

We recently moved our entire exchange 2003 environment via a consultant to Office 365. The migration went fine but now i am trying to shut down my old Exchange 2003 servers. I know i cant shut down the individual 2003 servers without
removing the old mailboxes themselves from the stores. I have attempted to remove some mailboxes from some of my accounts to do this but it removes the proxyaddress field on the user objects themselves. Is there a way to delete the mailboxes
without the proxy address being deleted in ad? Without that all my users email addresses are defaulting to the onmicrosoft address, which is really annoying We are using dirsync for user updates and groups, so im losing the default email address
when it syncs up to office 365. And yes I know about adsi edit to put it back it but that's not viable for 500+ user accounts individually.
Tried asking this on office 365 forums but they shuffled me off to here.

When your mailboxes were moved to Office 365, your directory should have been updated so it pointed to the mailboxes in Office 365, not to your local Exchange 2003 mailboxes. Just thinking this through, I think your consultant didn't do a complete
job. With the Exchange 2013 PowerShell tools, you should be able to update your 500 accounts so they point to the proper system for the mailboxes.

Out of Office replies not working for external emails - Exchange 2010, Outlook 2010

Hello.
We have two Exchange 2010 mailbox servers and a third for client access. There are two mailbox databases replicated to both servers as a DAG. There is also one 2003 legacy server that is awaiting decommissioning that is basically just heating the server
room - all the mailboxes have been migrated.
We have recently noticed that out of office replies are no longer working for external recipients, but are being sent for internal users.
I have checked under "Organisation configuration" - "hub transport" - "Remote domains" and made sure that is set to "Allow external out-of-office messages and legacy out-of-office messages"
Looking at the message tracking logs it appears that the out of office reply isn't generated for external users - we do have an external mail filter that inbound and outbound messages are relayed through but that isn't blocking anything.
This was working until recently, and I can't see any errors in the logs that look related. All three servers have been rebooted just in case.
Any suggestions where to look next?

Hello,
You can capture a trace log to diagnostic
the OOF issue:
a. Start ExTRA by clicking Run on the Start menu and then entering the following command-line:
Extra.exe
b. On the “Welcome to the Exchange Troubleshooting Assistant” page click Select a task.
c. On the “Troubleshooting Task Selection Screen” page click Trace Control.
d. Click OK to the following prompt alerting you about possible performance problems running a trace:
This server does not have the module needed for interpreting traces.
Proceed only if this is being done under the direct supervision of a qualified Exchange support engineer.
e. On the “Configure Trace File” page configure the following options:
f. After configuring the options in step e, click Set manual trace tags.
g. On the “Set Trace Tags Manually” page configure the following settings:
Check the following trace tags: InfoWorker.Assistants.OOF, all.
Note: Please expand all filter options, make sure that we did not check any filter options here. And run the trace again.
h. Click Start Tracing at the bottom of the page.
i. Please reproduce this issue for 3-5 times. After reproduced this issue, stop the tracing and collect the ExchangeDebugTraces.etl
Thanks,
Simon

How to Replicate two Exchange 2010 Servers

Hello all,
This is my first post here. I fear our organization may have made a grave error. Here is our basic setup:
Location 1 - 3 2008 R2 standard servers in a domain. 1 Exchange 2010 sp3 server.
Location 2 - 3 2008 R2 standard servers in the same domain connected over CISCO VPN. 1 Exchange 2010 sp3 server
Our objective was to replicate the first site at the second site. We have setup DFS and made a BDC at the second site, no issues. However, I have been doing some reading on Exchange replication, and it looks like we are in trouble. I had read that Exchange
2010 could be fully replicated over two servers (unlike 2007). However, I now have read that this requires the Enterprise edition of Windows server 2008 R2. So, I guess I have three questions to start:
Is there ANY way we can replicate site 1 to site 2 with the current setup? Even if it means site 2 is "inactive" unless we need it for a failure at site 1?
If not, can we upgrade to the enterprise edition for the servers? Any idea on cost?
If we upgrade to Enterprise, is there a decent place to go to read on how to setup the second site?
Thanks very much.

Hello,
According to your description:
"Is there ANY way we can replicate site 1 to site 2 with the current setup? Even if it means site 2 is "inactive" unless we need it for a failure at site 1?"
For CAS and Hub Transport roles you can simply deploy an additional server in secondary site and configure namespaces, mail flow etc. For mailbox role you should configure
DAG. But it requires at least Windows 2008 R2 SP1 Enterprise or Windows 2012 Standard. In addition you cannot mix Failover Clustering and Windows Network Load Balancing so
for full redundancy you need:
1. Four Exchange servers: 2 CAS + Hub Transport with Network Load Balancing and 2 Mailbox servers with DAG.
2. Two Exchange servers with CAS, HT and Mailbox and deploy hardware Load Balancer.
"If not, can we upgrade to the enterprise edition for the servers? Any idea on cost?"
In-place upgrade is not supported when Exchange server is installed. The only option is to deploy an additional server (Windows 2008 R2 Enterprise, 2012 Standard) and move
all resources from old server.
"If we upgrade to Enterprise, is there a decent place to go to read on how to setup the second site?"
The starting point is to configure Active Sites properly. For more info:
http://technet.microsoft.com/en-us/library/dd979799%28v=exchg.141%29.aspx
http://technet.microsoft.com/en-us/library/dd979781%28v=exchg.141%29.aspx
http://exchangeserverpro.com/exchange-server-2010-database-availability-group-installation-step-by-step/
http://www.msexchange.org/articles-tutorials/exchange-server-2010/high-availability-recovery/designing-site-resilient-exchange-2010-solution-part1.html
http://technet.microsoft.com/en-us/library/dd638121%28v=exchg.141%29.aspx
Hope it helps,
Adam
CodeTwo: Software solutions for Exchange and Office 365
If this post helps resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others find the answer faster.

Sequencer machine shutting down after revert

I am running a sequencer (W7) on Hyper-V.
Suddenly when I revert this VM after packaging it shutting down. Then when start I get standard Windows was not properly shutdown. Takes long to boot. But works Ok then... I guess there is no relation to the "sequencer role" of this VM and it is
just Hyper-V related. But may somebody saw this... For me it is first time.
--- When you hit a wrong note its the next note that makes it good or bad. --- Miles Davis

The Windows was not properly shutdown error has no relation with the sequencer.
Start the VM
Ignore the Windows was not properly shutdown error
Shutdown the VM
Create a new Checkpoint

Script for unmounting/deframenting exchange 2010 database

hi all,
i need a script to unmount exchange 2010 database, defrag it and mount it again.
thanks for any comment you may add...

Tried the above commands... works like a charm, but with the following modifications:
1. Delete trash and recoverable items from all mailboxes, run repeatedly
The command using is
Search-Mailbox -Identity "mailbox.name" -SearchDumpsterOnly -DeleteContent
1A. Determining Free Space in Mailbox Database
The command using is
Get-MailboxDatabase -Status | ft name,Availablenewmailboxspace,Databasesize
2.Calculate the disk space to perform the defrag, the formula is
(Databasesize-Availablenewmailboxspace)*1.1
3.Dismount the mailbox database
In EMS, go to the folder contain the database file then use the command
Dismount-Database <DatabaseName>
3A.Copy mailbox database (edb and all related log files) to another location
In EMS, go to the folder contain the database file then use the command
4.Defrag the edb file (eseutil will recreate a temp edb and rename to the new edb after successful complete it will delete the old edb file. If anything goes wrong, it will revert back to the old edb as in the /d)
eseutil /d <file.edb>
5.Mount again
Mount-Database <DatabaseName>
You are advised to purge (step 1) all mailboxes before eseutil or move mailbox, otherwise it will just carry all the sh!t over to the new mailbox anyway. I gave up trying to tally the total mailbox space used, the whitespace avail and the edb file size already.
For example, not sure why there is such a disparity where by I have 30 2GB mailboxe est. at 60GB used, whitespace after mailbox move/eseutil at 95GB, the edb size is 106GB. This is where my older exchange 2003 edb files wins hands down. Better budget more
storage for edb files! I am considering whether it's even worth migrating all to exchange 2010 altogether! The edb files are so damn space hungry even with 3 day retention and 6 day delete with 24/7 maintenance ticked. Exchange 2010 edb beast simply cannot
be tamed.
Personally I find in EMC to online move mailbox faster and more reliable overnight. Furthermore, you can simply create a new database, sort all mailboxes by database, select all of them, follow the wizard to move them all at once, the system simply queues
them to move and complete. Overnight moving is the best, all will be done the next day.

How to Restrict Max Recipient for Inbound in Exchange 2010

Hi,
I want to restrict my inbound mails which is having more than 10 recipients (it may be TO,CC & BCC) in my Exchange 2010.
I set the limit to 10 in the following area.
1.Mailbox
2.Organization
3.Connector (for Receive connectors only)
4.Transport server
But still external users send a mail to more than 10 of our users.
Accepted domain is configured as an internal relay domain.

Hi,
Based on my knowledge, we can't restrict the inbound recipients number in Exchange server. What we can do is restrict the outbound recipients number. For an example, if you set the value of RecipientLimits to 10 for user1, then user1 can't send an message
with more than 10 recipients, but the setting can't have an effect on receiving messages. Your understanding will be appreciated.
Hope my clarification can be helpful to you.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

Outlook Web App error for new user (Exchange 2010)

Hello,
Recently, our new user can't get on OWA because their regional setting page is returning "An unexpected error occurred and your request couldn't be
handled."
with "Url: https://mail.shdm.org:443/owa/languageselection.aspx"
I've search many site and i've not been able to find a working solution.
I've check the redirection, everything seems ok
here is the complete detail message
An unexpected error occurred and your request couldn't be handled.
Request
Url: https://mail.shdm.org:443/owa/languageselection.aspx
User: [email protected]
EX Address: /o=SHDM/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=promoteurs790
SMTP Address: [email protected]
OWA version: 14.3.195.1
Exception
Exception type: System.ArgumentNullException
Exception message: Value cannot be null. Parameter name: value
Call stack
Microsoft.Exchange.Clients.Owa.Core.Utilities.RenderDirectionEnhancedValue(TextWriter output, String value, Boolean isRtl)
Microsoft.Exchange.Clients.Owa.Core.LanguageSelection.RenderTimeZoneSelection()
ASP.languageselection_aspx.__Render__control1(HtmlTextWriter __w, Control parameterContainer)
System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children)
System.Web.UI.Page.Render(HtmlTextWriter writer)
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
Hope that someone can help!
Alexandre

Hi,
I have seen this same error before. That issue resolved by Exchange 2010 SP3 RU7.
So please refer to KB 2961522
and install Update Rollup 7 for Exchange 2010 SP3 to solve this issue.
Best Regards.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Lynn-Li
TechNet Community Support

Outlook 2003 Free/Busy only shows 2 months for users on Exchange 2010

Hi,
We are moving to Exchange 2010 from Exchange 2003 and have noticed that users who have been created on or migrated to Exchange 2010 who also use Outlook 2003 can only see 2 months worth of free busy information.
After doing some testing this is only an issue if the user who is looking at the free busy is located on Exchange 2010 and they are using Outlook 2003. It doesn't matter if the mailboxes they are looking at are on Exchange 2003 or Exchange 2010.
If the user uses Outlook 2007 they see free/busy past 2 months.
We configure Outlook to publish 12 months of free/busy.
Any help would be appreciated.
Regards
Matt

Hi Matt,
According to your description, the issue only happens in Outlook 2003 but not in other Outlook versions. Please check whether there is the Auto Accept Agent installed in your Exchange server. This issue occurs when you register the Auto Accept Agent to process
meeting requests for the affected mailbox.
Here is a KB related to this issue. Please follow it to configure the period for which you want to publish Free/Busy information in a registry entry on the Microsoft Exchange Server on which you have installed the Auto Accept Agent:
The published Free/Busy information for a mailbox is displayed for the default period of two months after you have configured a longer period in Outlook
http://support.microsoft.com/kb/917687
The free/busy publish range reverts back to the default setting when you direct book a resource in Outlook 2003
http://support.microsoft.com/kb/905817
Additionally, I recommend you upgrade your Outlook 2003 clients to Outlook 2010/2013 for better working. Because Microsoft ended support for Office 2003 on April 8, 2014.
Regards,
Winnie Liang
TechNet Community Support

DFM alert for shutting down a port?

I am using LMS 3.2, and when are shutting down a port, I don't receive any alerts. Is there any alert for administratively shutting down a port of a device?

DFM criteria for a interface down is
ifOperStatus = down and ifAdminStatus = up. If you down the interface then ifAdminStatus will be down and not up, so DFM does not treat this an alarmed event.

Sequence for shutting down Exchange 2010 Servers

Similar Messages

Maybe you are looking for