Installing a new Cumulative Update (CU) on the Exchange Server is always somehow stressful. If something goes wrong, you may be left with a corrupted/not working Exchange Server what means a financial loss to your company. To prevent this scenario from happening, make sure you always create an up-to-date backup copy before starting the CU installation process. If there are no obstacles, it is also worth trying to test the update of Exchange in a lab environment. This way you can measure and eliminate potential risk while performing the update in a production environment.
In this article, I will describe how changing Exchange 2013 components state may be helpful while implementing a new CU and how to set Inactive components Active when the installation of the Cumulative Update fails.
Continue reading ‘Exchange 2013 components inactive’
When preparing a Hyper-V virtual machine, it is a good idea to create it and configure it on your own computer, and then implement it in the production environment. The usual scenario would be to export the virtual machine from the local host and move it to the server host. This scenario, however, may not work in all situations. Unluckily, along with the release of Windows 10, the export/import functionality has been restricted – in other words, it is no longer possible to perform export/import move of the virtual machine from Windows 10 to Windows Server 2012 R2. To see what happens when you try to import such virtual machines, go to the Import Virtual Machine wizard and locate the folder with your virtual machine:
Continue reading ‘How to export a Hyper-V VM from Windows 10 to Windows Server 2012 R2?’
In 2017 Exchange Server 2007 will reach the end of its life-cycle. This will inevitably prompt many companies to contemplate an upgrade to Exchange 2016 – by now a mature enough product to meet the highest security standards.
With these companies in mind, the CodeTwo Team has prepared a free guide detailing how to prepare and perform a smooth migration from Exchange 2007 or 2003 directly (no double-hop!) to Exchange 2016.
Continue reading ‘Free ebook: Exchange Server 2016 migration guide’
Everything you need to know about migrations to Office 365 provided in a fun and easy to read fashion…
Sounds too good to be true? Probably because you haven’t read Conversational Office 365 Migrations by J. Peter Bruzzese (Microsoft MVP) yet!
Don’t panic – you can now download the updated PDF version for free from our website.
Continue reading ‘Conversational Office 365 Migrations by JP Bruzzese (2nd edition) – get it for free!’
Since mainstream support for Exchange 2007 ended in 2012, the product’s users have been relying on ‘extended support’, i.e. a guarantee that Microsoft will provide fixes to security bugs and offer paid technical support in case of issues. Soon, however, even this will be gone. Extended support for Exchange 2007 will expire on April 10, 2017.
Read The Exchange Team’s reminder about the fact
Continue reading ‘Time to start saying goodbye to Exchange 2007?’
In this article, I am going to show you how to export Office 365 mailboxes to PST files using a workaround which utilizes Office 365’s native in-place eDiscovery mechanism.
The reason why you may need to use it, is that Microsoft doesn’t provide any tools dedicated specifically for this purpose (like the New-MailboxExportRequest cmdlet in on-premises Exchange). In fact, if you want to export mailboxes to PST files to e.g. add a layer of extra protection to your Office 365 data or migrate away from Office 365, the eDiscovery mechanism is your only option, other than opening the mailboxes in Outlook and using its Import/Export functionality.
IMPORTANT: eDiscovery is supported in all Exchange Online plans and in selected Office 365 plans. For more see this TechNet article.
Note that this solution can also be used in Exchange 2016 and 2013.
Continue reading ‘How to export Office 365 mailboxes to PST using eDiscovery’
ESEUTIL is an Exchange tool that is well known among administrators as it accompanies them since the era of Exchange 4.0. It was proofed to be tremendously useful for a variety of purposes, e.g. for fixing corrupted databases, defragmenting them, reducing their size or checking their integrity.
Sometimes it is a matter of time, when the administrators are faced with the problem of a server failure with the Exchange installed on. The failure may be just the temporary power cut-off but it also may turn to be something serious. No matter what the reason is, when you manage to get the server up again it may come out that the .edb file has troubles to mount and shows the status called Dirty Shutdown. The same may happen when you attempt to recover a backup file. In those scenarios, ESEUTIL will prove to be very helpful.
In order to use this tool extensively and effectively, it is good to take a brief look at the way the Exchange database works.
Continue reading ‘How to use Exchange Extensible Storage Engine Utilities (ESEUTIL) tool?’
In the hour of the Microsoft’s Exchange 2016 release, some of you fellow admins are probably starting the day with heads burdened with different data migration scenarios, and your brain synapses are struggling to work out the fastest and easiest solution to achieve the aim of moving your mailbox databases to the newest Exchange or Office 365 servers. It is easier said than done, especially when it comes to migrate huge organizations with scores of users whose work must remain uninterrupted in the process. Most often new mailboxes and mail flow are required to function immediately after the operation is accomplished. A good way to reach your goal is to perform migration in batches, migrating first the most needed data for users from the last relevant period of time, and then in the succeeding batch older data.
Continue reading ‘Exchange Server mailbox migration based on item age’
The release of Exchange 2013 brought us another gem to the precious set of Exchange functionalities, Managed Availability is also known as Active Monitoring or Local Active Monitoring (LAM). Briefly speaking, it is an in-built Exchange monitoring system, which automatically analyses mail server components, and in case of any detected errors or corruptions attempts to fix them (e.g. switches a mailbox database to another server, etc.)
Continue reading ‘Managed availability in Exchange 2013’
Issues concerning a single user’s mailbox malfunctions are nothing peculiar in web administrator’s everyday work. The scope of such issues is pretty wide, starting from the wrongly displayed number of public folders in mailbox view, to problems with search items or with access to folders. These issues particularly concern shared mailboxes with a high number of active users. To overcome these problems admins usually used three most popular solutions:
- Mailbox data export to PST files. An Exchange administrator deletes the current mailbox and creates a new one, where he/she imports the previously exported PST files.
- An administrator completely dismounts the whole database from the server, and then using the Isinteg tool repairs the dismounted database. Basically, this solution has two major flaws. It is time-consuming (it depends on the size of the database), and it suspends Exchange services availability not only for the malfunctioning mailbox, but for all mailboxes within the database.
- An administrator recovers a backed up version of the current database what results in the partial loss of the newest data.
All above mentioned solutions appeared insufficient for Exchange administrators in meeting demands of nowadays IT environments. It all has changed with the emergence of Exchange 2010 SP1, and the cmdlet called New-MailboxRepairRequest.
Continue reading ‘New-MailboxRepairRequest – the successor of the Isinteg tool’