Mark the replies as answers if they helped. If so, remove it and run the command above again. The version number represents Exchange 2003, so please check if there is any legacy AD object in ADSI Edit.ĬN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=,DC=com ObjectCategory : /Configuration/Schema/ms-Exch-Domain-Content-Config PreferredInternetCodePageForShiftJis : UndefinedĭistinguishedName : CN=Default,CN=Internet Message Formats,CN=Global Settings,CN=TCC,CN=MicrosoftĮxchange,CN=Services,CN=Configuration,DC=domain,DC=com MeetingForwardNotificationEnabled : False C:\Windows\system32>Get-RemoteDomain -Identity Default | FL
#Windows text encoding corrupted how to#
What's wrong with that & how to make it work? Many thx! + FullyQualifiedErrorId : 6061B09C.SetRemoteDomain + CategoryInfo : NotSpecified: (:), InvalidObjectOperationException The object's current version is 0.0 (.0). Property PreferredInternetCodePageForShiftJis can't be set on this object because it requires the object to have Get-RemoteDomain | Set-RemoteDomain -PreferredInternetCodePageForShiftJis:50220īut this didn't work with error message as below: Set-OrganizationConfig -PreferredInternetCodePageForShiftJis:50220 By observation, for those reported cases, all incoming emails somehow with charset="iso-2022-jp" in the message body.
Recently observed some incoming emails with garbage characters.
Server side MS Exchange 2013 std cu21 in DAG.
0 kommentar(er)
