Microsoft started the year with a serious Y2K22 error

Microsoft has welcomed the new year around the world with the failure of Exchange servers, and the fix has not been too bright.

For many, New Year was a time of being with family and friends and making New Year’s resolutions. However, the situation was quite different for administrators responsible for Exchange servers, as Microsoft Exchange servers could not process the new date properly and therefore could not process the mail.

The first community report in this regard was received at 1 a.m. (US Eastern Time) from the Reddit user / u / FST-LANE who assumed it was that Microsoft has released a bad update that is aptly named “220101001”. This was presumably a planned fix to allow the new date to be processed, but nothing happened as planned. “I see a lot of bugs from the FIPFS service that say: Cannot convert” 220101001 “to long” – by /u/FST-LANE.

It agrees Marius Sandbu , with reports from the manager of the Norwegian company Sopra Steria, who issued a detailed summary of the reasons. It is reported that Microsoft Exchange servers have stopped processing mail completely because they were not prepared to handle the January 1 date. It states, “This is because Microsoft uses a signed int32 for the date and the new value of 2.201.010.001 exceeds the maximum value of” long “int, which is 2,147,483,647.”

The most worrying part of this is the bridging solution. In order to continue processing mail , administrators disable malware scanning on their exchange servers , allowing users and possibly themselves to servers also become vulnerable to attacks.

The vulnerability affects Exchange Server 2013 as well as 2016 and 2019.

Microsoft has released the official fix for the Y2K22 Exchange Server bug, but the situation has gotten worse

Microsoft has indicated that it is aware of this problem and is working on it.

We are aware of and working on an issue that causes message jams on Exchange Server 2016 and Exchange Server 2019.

We’re actively working to resolve this issue, and we’re expected to post the details of how to resolve this issue today.

The company kept its promise and issued a solution to the problem. It provided both an automated scripting solution and a manual solution.

First of all, here is the automated scripting solution

Available at https://aka.ms/ResetScanEngineVersion https: //aka.ms/ResetScanEngineVersion page. It can run on multiple servers in parallel. Successful completion of the script should yield the following output:

[PS] C: Program Files Microsoft Exchange Server V15 Scripts>. Reset-ScanEngineVersion.ps1
EXCH1 Stopping services … EXCH1 Removing Microsoft engine folder …

EXCH1 Emptying metadata folder … EXCH1 Starting services … WARNING: Waiting for ‘Microsoft Filtering Management Service (FMS)’ to start …
WARNING: Waiting for the ‘Microsoft Filtering Management Service (FMS)’ to start …

WARNING: Waiting for the ‘Microsoft Filtering Management Service (FMS)’ to start …

WARNING: Waiting for the ‘Microsoft Filtering Management Service (FMS)’ to start .. .

WARNING: Waiting for ‘Microsoft Exchange Transport (MSExchangeTransport)’ to start. ..
EXCH1 Starting engine update …

Running as EXCH1-DOM Administrator.

——–

Connecting to EXCH1.CONTOSO.com.

Dispatched remote command. Start-EngineUpdate -UpdatePath http://amupdatedl.microsoft.com/server/amupdate ——- –
[PS] C: Program Files Microsoft Exchange Server V15 Scripts & Converters Get-EngineUpdateInformation
Engine: Microsoft
LastChecked : 01/01/2022 08:58:22 PM -08: 00

LastUpdated: 01/01/2022 08:58:31 PM -08: 00
EngineVersion: 1.1.18800.4
SignatureVersion: 1.355.1227.0
SignatureDateTime: 01/01/2022 03:29:06 AM -08: 00
UpdateVersion: 2112330001
UpdateStatus: UpdateAttemptSuccessful

This is followed by the manual repair steps

For those who prefer manual restore

Removal of existing engine and metadata

  1. Stop the
  2. Microsoft Filtering Management service. When you are prompted to stop
  3. Microsoft Exchange Transport, click Yes. button.
  4. Delete the following folder:% ProgramFiles% Microsoft Exchange Server V15 FIP-FS Data Engines amd64 Microsoft
  5. Remove All Files from the metadata of% ProgramFiles% Microsoft Exchange Server V15 FIP-FS Data Engines

Update to the latest engine

  • Start
  • Microsoft Filtering Management Service and Microsoft Exchange Transport Service
  • Open the Exchange Management Shell, navig go to the Scripts folder (% ProgramFiles% Microsoft Exchange Server V15 Scripts) and run the Update-MalwareFilteringServer.ps1 file
  • Check engine update information

      In the Exchange Management Shell, run the Add-PSSnapin Microsoft.Forefront.Filtering.Management.Powershell.

    1. Run Get-EngineUpdateInformation and verify that the UpdateVersion information is 2112330001.

    More details linked here official Microsoft blog post here

    Hardware, software, tests, curiosities and colorful news from the world of IT by clicking here!

    Note : This article has been indexed to our site. We do not claim legitimacy, ownership or copyright of any of the content above. To see the article at original source
    Click Here

    ) (adsbygoogle=window.adsbygoogle || []) push ();

    Related Posts
    In 15 seconds, Apple created a whole world of intrigue thumbnail

    In 15 seconds, Apple created a whole world of intrigue

    Do you see a slight, human wobble? Screenshot by ZDNet What's all the fuss about?What did I miss?When did I miss it?What could it be? I simply have to know.These, and other short, blunt utterances surely echoed around the firmament as soon as Apple announced it was holding, gasp, another event on March 8.Yes, there…
    Read More

    Apple Watch Series 7 rumored to hit stores in mid-October

    Apple Watch Series 7 was announced at Apple’s September special event along with the iPhone 13 lineup and the new iPad models. However, unlike its siblings, Apple Watch Series 7 is not available to customers – and there’s no word from Apple on when it will be. According to Jon Prosser, the next-generation Apple Watch…
    Read More
    一男子因利用假冒iPhone诈保牟利超百万美元而被判两年监禁 thumbnail

    一男子因利用假冒iPhone诈保牟利超百万美元而被判两年监禁

    0 cnBeta.COM   2022-02-02 17:45:16 摘要:美国司法部周二公告称:一名男子因参与利用假冒 iPhone 申请售后、对苹果公司造成超百万美元的损失,而被判处 26 个月的监禁。32 岁的 Haiteng Wu 于 2013 年前往美国攻读工科,并于 2015 年获得硕士学位。尽管两年后合法就业,但与此同时,他也开始了一项为期三年半的诈保计划。 公告指出,当事人谋划了从香港接收 IMEI 和序列号与正品苹果设备相对应的仿冒品,然后与其他同谋者将这些声称还在质保期内的假冒 iPhone 退还给苹果。在成功骗取了替换用的真机后,赃物又被其发回在香港的同谋者那里转手牟利。更让人无语的是,Wu 还将包括妻子在内许多人拉下了水。为了“壮大”iPhone 诈保的生意,他还涉及伪造身份证件、开设多个商业收件箱、以及安排其他参与者穿越美国。但在美国土安全部 / 国土安全调查局 / 邮政监察局的联合督导下,Wu 最终承认其从苹果公司诈取仅百万美元的财物。但若团伙没有在 2019 年落网,他们还打算继续开展下去。2020 年 5 月,Wu 承认犯下一项串谋邮件欺诈罪。周二的时候,法官 Emmet G. Sullivan 终于对已服刑 26 个月的 Wu 下达了裁定。除了罚没非法所得,他还必须支付 98.7 万美元的赔偿金。至于 Wu 的妻子 Cai 女士,也于 2020 年 5 月承认在某县犯下了一项串谋邮件欺诈罪。
    Read More
    Index Of News
    Total
    0
    Share