As we know Exchange 2010 SP 3 is prerequisite if you are planning to migrate it to Exchange 2013.
Let us go ahead with updating our Exchange 2010 to SP 3.
In larger environment, it is always preferred to update the Active Directory Schema separately\manually.
This is because you may have the schema master and Exchange Servers in different AD sites.
Another reason is the person responsible for Active Directory (Schema) may not be the same person that will upgrade Exchange Servers.
First of all extract the content of Exchange 2010 SP3 on a folder on C Drive of any Domain Controller (Schema Master) and run Setup.com /PrepareAD
To validate if the Schema update is successful or not, use ADSIEdit.msc and open the Schema partition and check the properties of Ms-EXch-Schema-Version-PT
The range upper value should 14734.
Yes as per the recent announcementÂ Edge Transport Server Role will be back on Exchange Server 2013.
This is good for On Premise customers. Â There are other things to wait for or just FYI…
- Windows Server 2012 R2 SupportÂ First answering one the most common questions since the release of Windows Server 2012 R2. Exchange 2013 SP1 will add Windows Server 2012 R2 as a supported operating system for Exchange Server 2013 with SP1. Let your planning begin.
- S/MIME support for OWAÂ Support forÂ S/MIMEÂ inÂ OWAÂ will be brought back in SP1. With SP1 customers will have S/MIME support across Outlook, Exchange ActiveSync clients, and OWA.
- Fixes and ImprovementsÂ Of course, SP1 will include fixes and improvements in areas you’ve helped us identity. SP1 is the first service pack issued in the new Exchange Server cumulative update release model – thus SP1 is essentially CU4. The installation of SP1 will follow the same process as the prior Exchange 2013Â CUreleases. SP1 will include all fixes included in previously released cumulative updates for Exchange 2013.
SP1 will require customers to update their Active Directory schema – customers should assume this requirement for all Exchange Server 2013 updates. Plan for this required update to quickly take advantage SP1 updates. Active Directory Schema updates for Exchange are additive and always backwards compatible with previous releases and versions.
This blog includes four scenarios for moving mailboxes on Exchange 2013 server with screenshots. The process flow and architecture of mailbox moves in Exchange 2013 is similar to 2010. Batch Move requests are made easy with Exchange 2013. The Alerts in EAC, Powershell cmdlets, AuditAdminLogs & Email notifications are different ways of tracking the mailbox moves. Exchange Admins are going to like the mailbox moves with Exchange 2013.
- Exchange 2013 Organization is not supported with Exchange 2003 and earlier versions. You need to remove all instances of Exchange 2003 from your organization before you can upgrade to Exchange 2013.
- Moving the Exchange 2010 System Mailbox to Exchange 2013 is a mandatory step. Failing to do so would result in issues related to mailbox search tasks.
- You cannot move mailboxes from Exchange 2007/2010 to Exchange 2013 using EMC. It has to be done through Exchnge Management Shell or Exchange 2013 EAC.
- Cross-Forest moves between Exchange servers involving Exchange 2013 is not documented here.
SCENARIO 1: Moving Mailboxes using Exchange 2013 EAC.
In this scenario, I attempted to move a mailbox from an Exchange 2010 database to an Exchange 2013 Mailbox database. Both Exchange 2010 and Exchange 2013 are under one Exchange Organization in one AD forest.
Mailbox to Move : Administrator
Source Server : AZMAN-E10
Target Server : E15
Hello Exchange Friends,
I recently worked on this issue with one of my customers. To get to the resolution, It took me months. I wanted to blog on this so that any Engineer who works on Authentication prompts with their Outlook profiles understand the right approach which could save a lot of time. The Environment can be either on Exchange 2003, Exchange 2007, Exchange 2010 or co-existing environment. The details below should be read keeping in mind that you are working on a very big environment with Exchange and AD servers located across the globe. Let’s say users’ range anywhere between 20,000 to 50,000 or more. I expect people reading this blog to be aware of how Exchange works at level 200 and above.
I worked my best to include all the possible steps to troubleshoot. In case if the you find any additional steps to add, please feel free to comment. Thanks for reading.
At no point of time, you will see this issue resolving at 100 percent. Outlook or Lync Authentication prompts are expected in any huge environment. But if there are more users calling Helpdesk daily and logging in tickets stating they keep receiving Authentication prompts intermittently or at regular intervals, then something is wrong. Troubleshooting is required.
It is important to run reports and see the graph of number of users raising incidents on weekly basis to see if there is a change as the troubleshooting progresses.
Outlook users get Authentication prompts intermittently in a large Messaging environment.
Outlook 2003, Outlook 2007 & later
Exchange 2003, Exchange 2007 and Exchange 2010 or Co-existing environment
LOGS TO COLLECT
The Service Pack 3 fails installing on Exchange 2010 Server.
Considering you have Exchange 2010 servers and Domain controllers all on Windows 2008 R2 SP1 deployed on separate machines. While upgrading the Exchange servers with Service Pack 2 or Service Pack 3 on Client Access server or All roles E2k10 server, you may see the installation failing with the following error:
“Could not find element in web.config file.
The Exchange Setup log would show the following:
With Office 365 Online or Hybrid premises, it has been a challenge to work with Dynamic Distribution Groups. Few Organizations with Hybrid environment not necessarily use DirSync tool but also use Agents to synchronize the on-premise attributes to Online services.
Extended-Customattributes and wildcard characters are used to manage multiple Distribution Groups but has limitations and can be complex to work with creating lots of Groups. One significant limitation being Extended-Customattribute that have multiple strings don’t get dirsynced over to Exchange online.
There are two workarounds that can be used in creating more Distribution Groups and manage more 20k members. I recently worked with an Engagement and came up with the two workarounds. I defer to call them solutions as they are not very robust enough to be called so.
This method requires an Exchange server to be on-premise.
You can enable Exchange Online users to send mail to a dynamic distribution list by creating one from the on-premise Exchange Server.
The procedure for the same is mentioned in the below TechNet:
Configure Dynamic Distribution Groups in a Hybrid Deployment
This second method is to add the members to an existing Distribution Group manually by exporting to a .csv file and then importing the same and perform Disrsync. This can be used if you are not having an Exchange Server on premise.
The procedure for this method is in the below Technet blog:
Directory sync cannot update distribution Group after Office 365 migration
In order to use this procedure, a request needs to be approved to increase the limit of synching Distribution Group with more than 20k members. The request can be placed with the Microsoft Online Services team with a business justification.
Time â€“ Domain Controller and some errors â€“ yeah â€“ a skewed time on DC or any of your Lync FE server can give you error as below.
Lync 2010 Server environment and Lync 2013 client, few accounts were getting below error while trying to log in to Lync.
The clientâ€™s machine time was correct because that is what our field support guys will check based on the error.
Enter the Lync Admin â€“ Smart Admin
It turned out to be easy fix. The time service on one of the Lync Front end server was not running.
Restarted the time service and the error disappearedâ€¦
Check it out –
Today Microsoft released a very interesting & useful tool/app in Windows Store for Lync 2013 named Pre Call Diagnostics for Windows 8 and Windows 8.1 clients.
Most of you from Office communications background must already be aware about PCD tool available with Office communicator 2007 R2 resource kit. More details can be read here -> http://technet.microsoft.com/en-us/library/dd572403
- About to get on an important call? Run a quick test in On Demand mode to make sure it will go smoothly.
- Run a test in On demand mode to look at your networkâ€™s performance over extended periods of time.
- Diagnose trends with a view of historical test runs
- Having trouble signing in to Lync? PCDâ€™s Signin flyout can help you figure out where the issue is
The app can be downloaded using Windows Store from here -> http://apps.microsoft.com/windows/en-us/app/lync-2013-precall-diagnostics/9607fe33-2b51-403d-9615-c23f248e7c88
The Lync PreCall Diagnostic Tool (PCD) is a client-based application that allows you to see how the current state of your network might impact the audio quality in an upcoming Enterprise Voice call.
PCD is most useful in situations where the last hop of a network is likely to be the weakest (for example, with laptops on a public WiFi network or home users). PCD creates a small packet stream that traverses this final leg of the network. The tool then analyzes the packet stream to estimate how the jitter and loss along this leg might impact call quality, and then provides a report. You can run PCD continuously on the client, even while calls are being placed. The packet stream does not have a significant effect on bandwidth
Note: Currently during our testing, noticed that it’s not working from VPN clients or workstation or non-domain joined workstations. But please test from your side and let us know if it infacts works with non-domain joined machines.
Personally I will recommend deploying this app within your environment for all clients so that when time comes for troubleshooting, it’ll be easier for users to produce reports themselves and send across to you.
If you have Lync monitoring reports deployed within your environment, you can also leverage those for complete call diagnostic report and use them along with PCD report for troubleshooting purposes if required. Lync CDR report will be generated in backend after call though un-like Pre call diagnostic report, which as name suggests can be generated before call.
Hope you find above information helpful and this tool helps troubleshooting Lync voice issues easier for you !
Thanks for reading !
From time to time in various exchange 2010/2013 DAG environment, I notice that if a database is failed over automatically due to xyz reason or has high queue length or any other problem with database copy health which will not impact end user performance, is not monitored as closely as it should be.
Monitoring database copy health in your environment is critical as if anything was to happen with active mounted database & suppose there’re high queue length (un-noticed) on passive copy, you’ll either lose some TLs or some services uptime to get database copy healthy before it can be mounted.
For same reason, I finished automating a script Get-MailboxDatabaseCopyHealthÂ for same that monitors the database copy health status for you within your environment.
- If you run the script as is, it’ll check all database copies within your environment and display results on your screen allowing you to do manual centralized monitoring.
- You can run the script against particular server or set of servers using txt/csv files and display results on your screen allowing you to check only particular copies.
- You can write the results into a HTML file and send the HTML file to administrators via email which allows you sit back and just wait for alerts
- The script will modify subject line provided while running the script to ensure it catches appropriate attention based on criticality of database copy health.
- AutoMount feature within script allows you to fail back mailbox databases to their original or designated mailbox servers if the database copy on those box are “Lossless” and “Healthy”. This reduces your manual work to fail back each database on one-off basis.
- You can automate the script using bat file or task scheduler and run it every 10 to 15 minutes within your environment based on how much time script takes to complete & size of your environment (takes about 4 minutes for 100 database copies within our environment)
Few other features that you might find helpful. To see complete details and how to use this script, please run below cmdlet on powershell window after downloading the script:
Get-Help .\Get-MailboxDatabaseCopyHealth.ps1 -Detailed
You can download the script from here as well -> http://sdrv.ms/16KTlKQ
Hope you find this script helpful and it makes administration easier for you, keeping you environment clean & healthy at all times.
Thanks for reading !
August 26, 2013 Tags: automated monitoring, DAG health, database copy health, exchange monitoring, exchange reporting, exchange shell, powershell Posted in: Exchange Server, Exchange Server 2010, Exchange Server 2013, Exchange Server General No Comments
Upon release of Exchange 2007/2010, the rate at which administrators started to deploy powershell scripts have been exponential. One such script during early start was “Exchange 2010 – Monitoring Database Usage/Statistics” which provided administrators option with importing a txt file and writing vital database statistics information into a HTML file like:
- Mailbox Database Name
- Primary mailbox server for database
- Location of EDB File
- EDB File Size in GB
- Whitespace in Database in GB
- Last Full Backup Date
- No backup since
Few weeks back I finished making this scriptÂ Get-MailboxDatabaseInfoÂ more streamlined with few new features. The attached script is on the core same with few additional outputs which includes:
- Location of Transaction logs folder – Allows all administrators to have transparent view of exchange databases without getting on server.
- Transaction Log Size in GB – Allows administrators to monitor how rapidly TLs are generated for particular database.
- Last Transaction Log TimeStamp – Works along with TL size and allow administrators to notice some issue with rapid TL growth for a given database and action accordingly.
The script also provides new features like:
- By default script will run against all databases/servers in environment. However you’ve option to choose if you want to run against single database, single server, multiple servers using txt/csv file as input etc.
- Writing to HTML is not mandatory, by default script will show results on display screen.
- Upload results to SQL for future reporting. Allows you to leverage SQL reporting services for providing business level reports of database usage & growth.
You can also modify the code to support pipeline if needed OR add some more parameters for this script to monitor on.
Please run below cmdlet from powershell window to read complete help & details regarding how to use this script:
Get-Help .\Get-MailboxDatabaseInfo.ps1 -Detailed
You can also download the script from -> http://sdrv.ms/18qVeju
Hopefully you find this script helpful and it makes you a Rock Star Administrator for your Exchange environment.
In the coming days, we’ll be uploading few other scripts like monitoring database copy health, Blackberry devices, ActiveSync devices, EnterpriseVault environment, Mailbox statistics, MailFlow statistics, Mailbox permission details etc.
Thanks for reading !
August 26, 2013 Tags: automated reporting, exchange automation, exchange reporting, exchange shell, powershell Posted in: Exchange Server, Exchange Server 2010, Exchange Server 2013, Exchange Server General No Comments