Frosty's questions

So we have 3 Exchange 2019 servers in our environment. Two of them are DAG servers storing mailboxes, third is archive mailboxes only.

For most users everything works fine, however there are few, where all items marked with archive retention tags are moved to inplace archive mailboxes, but straight to "Recoverable Items" folder (found this by exporting user archive to pst).

What's interesting, if I move archive mailbox to the same database, as mailbox connected to it, everything works fine.

Of course I checked all the retention tags set by user.

Here is how it looks if i use Get-MailboxFolderStatistics

[email protected]\Folder nadrzędny magazynu informacji - 290.1 MB (304,214,249 bytes) (root folder)

[email protected]\Recoverable Items - 1.467 GB (1,575,517,001 bytes)

Tried creating new inplace archive mailbox, repairing, moving to different DB - nothing.

Any ideas, Guys?

Edit: I have found that this problem occurs only when mailbox is on different SERVER than archive

I'm struggling with update deployment from WSUS server (2012 R2) to our client computers and can't find solution on Google so I'm here. For the first time.

The problem occurs only on some hosts and not always. Currently I'm trying to fix this while using a laptop with fresh installation of Windows 10 1703 as a test client.

What happens: When I click search for updates button on Windows client, it finds 31 items (MS Office, Silverlight - selected on wsus) but doesn't progress with download - it's stuck at 0 percent.

Here is what i get from "ReportingEvents.log" file on client machine:

DllHost.exe Success Software Synchronization    Windows Update Client successfully detected 31 updates.
DllHost.exe Success Pre-Deployment Check    Reporting client status.
TrustedInstaller FOD    Success Software Synchronization    Windows Update Client successfully detected 0 updates.

So first it finds updates but then "naaah, there are no updates, brah"

Any clues?

Thank you in advance.

EDIT: So i uninstalled all the updates from client machine and searched for them once again. Windows found uninstalled packages, downloaded them but got stuck at 27% when these Office updates started to download.