How to connect to exchange in domain from non-domain network
Hi I'm trying to connect from my home PC to Exchange (via VPN) like this $username = "mylogin" $password = "p@$$w0rd" $securePassword = ConvertTo-SecureString $password -AsPlainText -Force $cred = New-Object System.Management.Automation.PSCredential($username, $securePassword) $session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://mail.mydomain.com/powershell/ -Credential $cred -Authentication Basic -AllowRedirection I get an error The WinRM client received HTTP status code "440" from the remote WS-Management service. I also tried to connect like this and execute commands Enter-PSSession -ComputerName 10.10.0.42 -Credential $cred [10.10.0.42]: PS C:\Users\mylogin\Documents> Add-PSSnapin Microsoft.Exchange.Management.PowerShell.SnapIn [10.10.0.42]: PS C:\Users\mylogin\Documents> GET-mailbox I also get an error Active Directory operation failed in . Invalid credentials provided for 'domain\mylogin'. How to properly connect to Exchange and execute commands from a non-domain PC?
Exchange 2019 Event ID 9042 - File Extraction Time Based Assistant skipps mailbox
Hello everyone! We only have 3 mailboxes left in our Exchange Server 2019 on-premises, the rest was already migrated to Exchange Online (we have a hybrid environment). We cannot move the other mailboxes at the moment. Since a couple of days however we receive the following warning message in the event log of our Exchange Server: Event-ID: 9042 (MSExchange Assistants) "Service MSExchangeMailboxAssistants. File Extraction Time Based Assistant for database <dbname> (<db id>) is exiting a work cycle. No mailboxes were successfully processed. 1 mailboxes were skipped due to errors. 0 mailboxes were skipped due to failure to open a store session. 0 mailboxes were retried. There are 0 mailboxes in this database remaining to be processed." Unfortunately, that's all the error messages we receive and I have no clue how to find out which mailbox is skipped. Or why... How can we find out which mailbox is causing the problem? How can we then solve it? Many thanks! Best regards, Markus
Correct path in SharedWebConfig.config for ClientAccess
Hello, community. After installing the next update, I received a non-working OWA.As you may know, Microsoft recommends that you create the file SharedWebConfig.config in ClientAccess folder again using the utility DependentAssemblyGenerator.exe. But, when command DependentAssemblyGenerator.exe -exchangePath "%ExchangeInstallPath%\bin" -exchangePath "%ExchangeInstallPath%\ClientAccess" -configFile "%ExchangeInstallPath%\ClientAccess\SharedWebConfig.config" done, I got the nextI am getting the following content in the file <codeBase version="4.2.0.0" href="file:///C:\Program Files\Microsoft\Exchange Server\V15\\bin\AntiXssLibrary.dll" /> or <codeBase version="1.1.5274.28150" href="file:///C:\Program Files\Microsoft\Exchange Server\V15\\bin\AsyncDnsManaged.dll" /> So I have a question. Why does there appear another \ character in the path before \bin? And when I check the server status with script from PSGallery, one of the items is that the file SharedWEbConfig.config is missing. Could this be related?
EOL - DDG - EQ operator wildcard bug fix
EOL > MSFT recently announced (i/t Health - Message center -MC912176) a bug fix related to the -eq operator and use of wildcards ('*') to compile the member list for Dynamic Distribution Groups. When the update takes effect, the * character will be treated as a literal value and not a wildcard. Therefore, expressions using the -eq operator will only evaluate to true if the right-hand side value matches the property values exactly. For example, the expression(WindowsLiveID -eq '*@microsoft.com')will only return true if the recipient’s WindowsLiveID property is exactly"*@microsoft.com". The current behavior will no longer function after the fix, and this may impact any processes that rely on this behavior. To distinguish the DLs (for corporate communication) membership of internal employees only and external consultants/contractors, we've created several DDGs using PowerShell to define the Recipient filter options based on our internal naming conventions (FTEs getFN.LN@emaildomainwhereas consultants/contractors get FN.LN.ext@emaildomain). The formula was based on -eq operator combined with '*' wildcard > formula extract > -RecipientFilter {(( RecipientType -eq 'UserMailbox') -and ((WindowsLiveID -eq '*.*.ext@emaildomain') ... When the bug fix is corrected the formulas will no longer return the expected members. We've tried already several alternatives w/t -like operator but were not able to retrieve the same list. Other operators as -contains and -match are not supported i/t context of EOL. Are there other operators or other parameters to compile a filtered list using wildcards?
Exchange server transport logs reading tool
Hi Exchange Brain Trust, I need to get rid of any inactive IP addresses out of my SMTP receive connectors in Exchange 2019 server (Hybrid environment). Is there a free tool to monitor/study transport logs which provides a good UI as opposed to notepad readings? Appreciate any suggestions. Thank you!Validate the working of default policy tag in MRM policy
Hi All, We have applied a retention policy to all mailboxes in our environment which also includes a default policy tag that moves all mails older than a year to Archive. Now, i know that the policy is applied and the default tag is doing its job, but, is there a way where i can see whether the mails are moved after the policy was applied ?
Outlook Desktop - Searching Large, Shared Mailboxes Either Not or Poorly Functional
Not a new topic, but looking for any new insights! We have a significant number of large, shared mailboxes in EXO - and Outlook desktop users who need to do frequent searches of these mailboxes. With Outlook desktop's caching behavior [regardless of whether or not 'download shared folders' is checked/unchecked], search functionality is either not working at all, or not providing complete/accurate results if it [sort of] works. Of course, Outlook desktop users mutiny over trying to use the Outlook Web App for shared mailbox functions. Does anyone have a solid solution or recommendation for the searching of large, shared mailboxes?
