Автор Тема: Глобальные обновления Exchange  (Прочитано 2301 раз)

0 Пользователей и 1 Гость просматривают эту тему.

Оффлайн sirarthur

  • Постоялец
  • ***
  • Сообщений: 351
  • Рейтинг: 4
  • Пол: Мужской
    • Просмотр профиля
  • Откуда: sub-MSK
Глобальные обновления Exchange
« : 18 Декабря 2015, 17:24:25 »
СU обновление 11 вышло:
Exchange Server 2013 Cumulative Update 11 Released
Цитата
Microsoft has released Cumulative Update 11 for Exchange Server 2013.

From the Microsoft Exchange Team blog:

The release includes fixes for customer reported issues, minor product enhancements and previously released security bulletins. A complete list of customer reported issues resolved can be found in Knowledge Base Article KB3099522. Customers running any previous release of Exchange Server 2013 can move directly to Cumulative Update 11. Customers deploying Exchange Server 2013 for the first time may skip previous releases and start their deployment with Cumulative Update 11 directly.

Cumulative Update 11 does not include updates to Active Directory Schema, but may add additional RBAC definitions to your existing configuration. PrepareAD should be executed prior to upgrading any servers to CU11. PrepareAD will run automatically during the first server upgrade if Setup detects this is required and the logged on user has sufficient permission.

Cumulative Update 11 also includes a change in behavior when deploying/administering Exchange Server 2013 in a co-existent manner with Exchange Server 2010 or 2016. These changes are outlined in the following blog article: Exchange Management Shell and Mailbox Anchoring.

The changed behavior for PowerShell management is important if you have a co-existence deployment, and in particular a geographically distributed deployment. You may need to do some internal education with your IT team, and review any scripts or other tools that rely on PowerShell access to Exchange. If you have a single Exchange server or any other relatively simple deployment the change will not be of any significant impact.

Also note that CU11 fixes the bug that allowed an Exchange 2016 mailbox server to be added to an Exchange 2013 DAG.


качать тут (1.6 Гб) https://www.microsoft.com/en-us/download/details.aspx?id=50366


Updated: 18 December 2015, 17:26:41

Установка апдейта - внимательно читать тем у кого DAG группы
http://exchangeserverpro.com/exchange-2013-installing-cumulative-updates/


Updated: 18 December 2015, 17:39:02

и да
Цитата
Exchange MVP Michael Van Horenbeeck has published a script for automating the process of starting and stopping maintenance mode.

там 404 - всем бобра  :trollface:
« Последнее редактирование: 09 Декабря 2016, 11:43:27 от Retif »

Оффлайн sirarthur

  • Постоялец
  • ***
  • Сообщений: 351
  • Рейтинг: 4
  • Пол: Мужской
    • Просмотр профиля
  • Откуда: sub-MSK
Глобальные обновления Exchange 2013
« Ответ #1 : 28 Января 2016, 10:29:37 »
Exchange Analyzer v0.1.0-Beta.1 Released
Цитата
Exchange Analyzer is a PowerShell tool that scans an Exchange Server 2013/2016 organization and reports on compliance with best practices.

Exchange Analyzer Sample Report

Exchange Analyzer is an open-source community project started by a group of Microsoft MVPs, and is currently a beta release seeking feedback and results from real world environments. This beta release includes five tests:

Checks that at least one Exchange 2013 or 2016 server exists (Exchange Analyzer will not check Exchange 2010 or earlier servers)
Checks that the Exchange 2013/2016 servers are running the latest build
Checks whether multiple namespaces exist for a Client Access protocol within an Active Directory site
Checks whether namespaces contain server FQDNs
Checks whether a database backup has occurred within the last 24 hours

Анализатор здесь
http://exchangeserverpro.com/exchangeanalyzer/
Как работает
Цитата
Installation Instructions

1. Download the latest Zip file

2. Extract or copy the following files and folders to a computer that has the Exchange 2013 or 2016 management shell installed. For example, place all of the files and folders in a C:\Scripts\ExchangeAnalyzer folder.

Run-ExchangeAnalyzer.ps1
\Data
\Modules
\Tests
3. Copy the folders in the \Modules folder to C:\Windows\System32\WindowsPowerShell\v1.0\Modules\

4. Open a new Exchange Management Shell

Important Note: if you are updating your copy of Exchange Analyzer please make sure you copy the updated module in step 3.

Running Exchange Analyzer

To run the Exchange Analyzer open an Exchange management shell, navigate to the folder with the script files (e.g. C:\Scripts\ExchangeAnalyzer) and run:

PowerShell
.\Run-ExchangeAnalyzer.ps1
To see verbose output run:
PowerShell
.\Run-ExchangeAnalyzer.ps1 -Verbose



Updated: 28 January 2016, 17:54:50

свежак
Цитата
Exchange Analyzer v0.1.1-Beta.2 Released
This release contains the following fixes and improvements:

Added new test AD001: Active Directory domain functional level
Added new test AD002: Active Directory forest functional level
Fixed error being thrown by Get-DatabaseAvailabilityGroup when an Exchange 2010 DAG was present
Fixed errors when script was run from a path with spaces in it
Added an intro and summary to report
Added a summary of Client Access URLs to assist with identifying causes of CAS test failures
Changed database backup timestamp comparisons to UTC for accuracy
Various minor fixes for typos and clarity
Changed “More Info” links to standardised Wiki-based documentation
Several of those improvements are thanks to Exchange admins in the community who took the time to run the tool in their environments, and sent us bug reports and other feedback. This has helped us to improve the framework that Exchange Analyzer is built upon, which will assist us with the further development of new tests and features for the next releases.

http://exchangeserverpro.com/exchange-analyzer-v0-1-1-beta-2-released/?awt_l=1hIXj6&awt_m=3intFV2WeDG0vZC
« Последнее редактирование: 28 Января 2016, 17:54:51 от sirarthur »

Оффлайн sirarthur

  • Постоялец
  • ***
  • Сообщений: 351
  • Рейтинг: 4
  • Пол: Мужской
    • Просмотр профиля
  • Откуда: sub-MSK
Глобальные обновления Exchange 2013
« Ответ #2 : 04 Мая 2016, 10:36:41 »
Не совсем обновления, но тоже  нужно представлять как работает.
Exchange Server Database Corruption and Dirty Shutdown Scenarios
Цитата
During normal Exchange database operations, it’s certainly not unusual for a database process to terminate unexpectedly. A termination might be due to losing access to backend storage, file system corruption, or server-wide power loss. Many Exchange support problems involve corrupt databases which will not mount, and therefore prevent users from accessing their mailbox data. The following issues can prevent an Exchange database from mounting:

The Microsoft Exchange Information Store Service is unable to start
Missing Exchange database files
Database is in “Dirty Shutdown” state
Not enough free disk space on database or log file volume
Loss of access to underlying storage
While database is in Clean Shutdown state, significant logical corruption exists causing the database to dismount when an attempt is made to read the data
In situations where the Information Store service will not start, the most common issues involve communications between Exchange and Active Directory or some interaction involving a file used by Exchange and anti-virus software. I recommend using event viewer to verify Active Directory communications as well as verifying there are no service dependencies not met (such as the Microsoft Exchange Active Directory Topology Service not being started). With anti-virus software, verify all exclusions have been properly configured. It is common to discover that an anti-virus product either locks the database files or blocks necessary RPC communications. Anti-virus is also a common reason why database files become corrupt as a result of multiple processes attempting to access the files simultaneously. It is also common to see that an anti-virus product quarantines database files or logs, a step that might break the sequence of the log stream, making recovery from backup challenging, and possibly breaking DAG replication.

DIRTY SHUTDOWN

The words “Dirty Shutdown” are fairly self-explanatory; a database is down and not in a healthy state. The words can still cause anxiety for Exchange Administrators who recall spending many hours while frantically attempting to get a database to mount and restore functionality. Over ten years of support, I have probably worked on well over a hundred Dirty Shutdown support cases. But to be honest, a decade worth of experience is not required to troubleshoot a Dirty Shutdown event accurately, especially since the proper course of actions can easily fit into a decision tree. The diagram below provides a high-level flow chart for navigating common scenarios where a database will not mount.


http://exchangeserverpro.com/exchange-server-database-corruption-and-dirty-shutdown-scenarios/?awt_l=1hIXj6&awt_m=3gKR8W.VzPG0vZC

Оффлайн sirarthur

  • Постоялец
  • ***
  • Сообщений: 351
  • Рейтинг: 4
  • Пол: Мужской
    • Просмотр профиля
  • Откуда: sub-MSK
Глобальные обновления Exchange 2013
« Ответ #3 : 07 Ноября 2016, 09:50:15 »
Проблема с обновлениями CU14 (2013) / CU3 (2016)
http://exchangeserverpro.com/issues-reported-exchange-server-2013-cu14-exchange-server-2016-cu3/
Цитата
Issues Reported with Exchange Server 2013 CU14 and Exchange Server 2016 CU3

OCTOBER 27, 2016 BY PAUL CUNNINGHAM 22 COMMENTS

Fellow Exchange MVP Jaap Wesselius has written about reports of content index failures for Exchange servers that have been installed or updated with Exchange Server 2013 CU14 or Exchange Server 2016 CU3. Those cumulative updates were released by Microsoft in September of this year.

Although I have not personally observed the issue in the field, a number of customers are reporting the same issue in a Microsoft TechNet forums thread.

One customer who opened a support ticket with Microsoft has reported back to the forum thread to say that a bug has been acknowledged, and that the solution is to deploy a new Exchange server (either Exchange Server 2013 CU13 or Exchange Server 2016 CU2) and migrate mailboxes to the new server.

If you are experiencing the issue in your own production environment then I recommend you raise a support case with Microsoft to determine whether you are impacted by the same bug (don’t rely on blog posts or forum threads to confirm a production impacting issue).

If you are considering deploying a new server as the resolution to the issue then you can refer to my like for like Exchange migration article for some high level guidance.


Иными словами - официальное решение от MS:
у вас был 2013 CU13/2016 CU2 - вы обновились CU14/CU3?
Легла база индексов Exchange?
Не беда - поднимайте рядом новый экземпляр 2013 CU13/2016CГ2 -мигрируйте ващи ящики туда - и будет вам нирвана и счастье...

Оффлайн Retif

  • Администраторы
  • Олдфаг
  • *****
  • Сообщений: 7718
  • Рейтинг: 77
  • Пол: Мужской
  • Афтар
    • Просмотр профиля
    • Мой блог
  • Откуда: Орёл-Москва

Оффлайн sirarthur

  • Постоялец
  • ***
  • Сообщений: 351
  • Рейтинг: 4
  • Пол: Мужской
    • Просмотр профиля
  • Откуда: sub-MSK
Глобальные обновления Exchange
« Ответ #5 : 25 Декабря 2016, 23:54:55 »
Лучше позже чем ни разу :)
Цитата
Microsoft has released new updates for all supported versions of Exchange Server, announcing:

Cumulative Update 4 for Exchange Server 2016 (download | UM language packs)
Cumulative Update 15 for Exchange Server 2013 (download | UM language packs)
Update Rollup 16 for Exchange Server 2010 SP3 (download)
Update Rollup 22 for Exchange Server 2007 SP3 (download)
The Exchange 2010 and 2007 updates contain daylight saving time fixes, as both of those versions of Exchange are in extended support now.

A public folder indexing issue experienced by some customers who upgraded to Exchange 2013 CU14 or Exchange 2016 CU3 last quarter are now fixed in these latest releases for those two versions of Exchange. Microsoft’s advice is:

To ensure all public folders are indexed appropriately, all public folder mailboxes should be moved to a new database after applying the appropriate cumulative update released today.

When Exchange 2016 CU3 was released, it became the first version of Exchange to support installation on Windows Server 2016. Shortly after that release it was discovered that there was a bug with Exchange 2016 DAG members running on Windows Server 2016 that would result in repeated crashes of IIS on the server. The Windows Server team has released an update that fixes the underlying issue, and all Exchange 2016 deployments on Windows Server 2016 require that update to be installed.

Both Exchange 2013 and 2016 now also support .NET 4.6.2, and Microsoft encourages you to deploy .NET 4.6.2 as soon as possible, because it will be the required version for Exchange 2013/2016 releases from March 2017 onwards.



Updated: 25 December 2016, 23:55:14

http://exchangeserverpro.com/december-2016-updates-released-versions-exchange-server/?awt_l=1hIXj6&awt_m=3f5.AdQaeDG0vZC

Оффлайн sirarthur

  • Постоялец
  • ***
  • Сообщений: 351
  • Рейтинг: 4
  • Пол: Мужской
    • Просмотр профиля
  • Откуда: sub-MSK
Глобальные обновления Exchange
« Ответ #6 : 06 Марта 2017, 23:10:53 »
Не совсем обновление.
11/04/2017 - Exchange 2007 - EoL
http://practical365.com/blog/exchange-server-2007-end-of-life/
Цитата
On April 11th this year, Exchange Server 2007 will reach the end of its support lifecycle, otherwise known as end-of-life. For customers still running Exchange Server 2007, you should start making plans now to migrate to a newer version of Exchange, or to Office 365. In fact, I’d love it if you would take a moment to answer my poll question to share what your plans are. Click here to take the poll (only one question, won’t take long at all).

Exchange Server 2007 Service Pack 3 (the last service pack that was released in June of 2010) reached the end of mainstream support in April 2012. When mainstream support ends, products go into an extended support phase for another few years. Products in extended support usually receive no further feature updates, but continue to receive security updates and some bug fixes. The extended support period for Exchange 2007 ends on April 11th, 2017. After extended support expires, the product received no further updates at all.

Оффлайн Retif

  • Администраторы
  • Олдфаг
  • *****
  • Сообщений: 7718
  • Рейтинг: 77
  • Пол: Мужской
  • Афтар
    • Просмотр профиля
    • Мой блог
  • Откуда: Орёл-Москва
Глобальные обновления Exchange
« Ответ #7 : 03 Апреля 2017, 16:56:48 »
Тоже не совсем обновление, а даже наоборот.
Microsoft прекращает поддержку Exchange Server Edge Role:

Цитата

Exchange Server Edge Support on Windows Server 2016 Update

The Exchange TeamMarch 23, 20177   

Today we are announcing an update to our support policy for Windows Server 2016 and Exchange Server 2016. At this time we do not recommend customers install the Exchange Edge role on Windows Server 2016. We also do not recommend customers enable antispam agents on the Exchange Mailbox role on Windows Server 2016 as outlined in Enable antispam functionality on Mailbox servers.
Why are we making this change?

In our post Deprecating support for SmartScreen in Outlook and Exchange, Microsoft announced we will no longer publish content filter updates for Exchange Server. We believe that Exchange customers will receive a better experience using Exchange Online Protection (EOP) for content filtering. We are also making this recommendation due to a conflict with the SmartScreen Filters shipped for Windows, Microsoft Edge and Internet Explorer browsers. Customers running Exchange Server 2016 on Windows Server 2016 without KB4013429 installed will encounter an Exchange uninstall failure when decommissioning a server. The failure is caused by a collision between the content filters shipped by Exchange and Windows which have conflicting configuration information in the Windows registry. This collision also impacts customers who install KB4013429 on a functional Exchange Server. After the KB is applied, the Exchange Transport Service will crash on startup if the content filter agent is enabled on the Exchange Server. The Edge role enables the filter by default and does not have a supported method to permanently remove the content filter agent. The new behavior introduced by KB4013429, combined with our product direction to discontinue filter updates, is causing us to deprecate this functionality in Exchange Server 2016 more quickly if Windows Server 2016 is in use.
What about other operating systems supported by Exchange Server 2016?

Due to the discontinuance of SmartScreen Filter updates for Exchange server, we encourage all customers to stop relying upon this capability on all supported operating systems. Installing the Exchange Edge role on supported operating systems other than Windows Server 2016 is not changed by today’s announcement. The Edge role will continue to be supported on non-Windows Server 2016 operating systems subject to the operating system lifecycle outlined at https://support.microsoft.com/lifecycle.
Help! My services are already crashing or I want to proactively avoid this

If you used the Install-AntiSpamAgents.ps1 to install content filtering on the Mailbox role:

    Find a suitable replacement for your email hygiene needs such as EOP or other 3rd party solution
    Run the Uninstall-AntiSpamAgents.ps1 from the \Scripts folder created by Setup during Exchange installation

If you are running the Edge role on Windows Server 2016:

    Delay deploying KB4013429 to your Edge role or uninstall the update if required to restore service
    Deploy the Edge role on Windows Server 2012 or Windows Servers 2012R2 (Preferred)

Support services is available for customers who may need further assistance.

https://blogs.technet.microsoft.com/exchange/2017/03/23/exchange-server-edge-support-on-windows-server-2016-update/