Jump to content

i-away

Members
 View Profile  See their activity

  • Posts

    462

  • Joined

  • Last visited

 Content Type 

Blog Entries posted by i-away

  1. i-away
    We are happy to report that the fix for the Exchange Management
    Console issues when IE9 is installed is now available. To be specific,
    we have talked about this in a previous blog post:
    Exchange
    2007 or 2010 EMC might fail to close with "You must close all dialog
    boxes before you can close Exchange Management Console"
    How does this fix need to be applied?
    In order to install the fix, a released version of IE9 needs to be installed on the machine first. Then:
    MS11-081: Cumulative Security Update for Internet Explorer: October 11, 2011
    needs to be installed. This can be obtained from Windows Update or - if
    you need to download it for local network installation, the packages
    can be obtained here.
    Please note that the packages for client and server OSes might be
    different, depending on what you need. The installation of this package
    is REQUIRED for proper operation of the EMC hotfix. In
    order to obtain the actual hotfix that resolves the interoperability
    problem with EMC, you will need to call Microsoft support and request a
    hotfix. The hotfix package is currently not available for public
    download, but can be obtained from support engineers, who can get it
    from internal hotfix servers. When you talk to support, the hotfix that
    you need to request is for the KB 2624899. Please note that this article is not publicly available at this time either. How do I call support? Will I need to pay for this?
    In order to reach Microsoft support, you can find the correct support contact for your location here.
    Also - Microsoft does not charge for hotfixes or support cases related
    to product bugs. Both IE and Exchange support teams should be able to
    get this patch for you.
    Why is this fix not available for public download?
    It
    is planned that this fix will be rolled into a version of Internet
    Explorer or a fix that will be released at the later time. Due to the
    amount of feedback that we have received about this problem though, we
    wanted to give you a way to resolve this problem right now, if you are
    impacted by it. Individual hotfix packages such as this one do not go
    through as extensive testing as our roll-up fixes and therefore - we
    want to have a way to reaching out to our customers who use it in case
    there is a problem that is identified with it at the later time.
    Finally,
    I would like to thank the Internet Explorer team for working with us on
    this interoperability issue and producing this hotfix.
    Source





  2. i-away
    Πολλές φορές λαμβάνουμε στο mailbox μας μηνύματα που έχουν αποστολέα όχι συγκεκριμένο άτομο αλλά μια πιο γενική διεύθυνση του τύπου [email protected]. Η διεύθυνση αυτή αποτελεί συνήθως μια γενική διεύθυνση ενός τμήματος ( μάρκετινγκ συνήθως ). Παρόλα αυτά όλοι αυτοί που βρίσκονται στα συγκεκριμένα τμήματα έχουν την δική τους διεύθυνση και στέλνουν - λαμβάνουν από αυτήν.
    Το παραπάνω “τρυκ” ονομάζεται Address rewriting και δημιουργήθηκε απο την Microsoft για αυτόν ακριβώς τον λόγο. Η τακτική αυτή βρίσκει πολλές εφαρμογές τόσο σε εξερχόμενα email ( πχ. μαρκετινγκ) όσο και σε εσωτερικά email ( σε περιπτώσεις merge εταιρειών ). Εδώ να σημειώσουμε ότι για να δουλέψει το address rewriting πρέπει να ενεργοποιηθεί και στα εισερχόμενα αλλά και στα εξερχόμενα email έτσι ώστε να υπάρχει σωστή αντιστοίχηση τους.

    Βέβαια χρειάζεται προσοχή γιατί το Address rewriting δεν αλλάζει μηνύματα που είναι attached στο προς rewrite μήνυμα, όπως και τα SMTP Return-Path, Received, Message-ID, X-MSTNEF-
    Correlator, Content-Type Boundary=string headers και τους headers εντός των MIME body parts. Τα Message-ID, X-MS-TNEF-Correlator, Content-Type Boundary=string
    headers, και οι headers εντός των MIME body parts χρησιμοποιούνται για την ασφάλεια και την κρυπτογράφηση των email με τεχνολογίες όπως η Microsoft Rights Management γιαυτό και δεν μπορούν να μεταβληθούν καθώς η μεταβολή τους αλλάζει το authenticity του email.
    Για την διασφάλιση της σωστής αντιστοίχησης και δρομολόγησης πρέπει να έχουμε υπόψην μας κάποια πράγματα:
    Καταρχήν το αποτέλεσμα της αντιστοίχησης θα πρέπει να είναι μοναδικό για να μην δημιουργηθεί όπως είναι λογικό conflict.
    Συνέπεια του παραπάνω είναι ότι πρέπει να ενεργοποιηθει το address rewriting και στους 2 connectors όπως έχουμε αναφέρει παραπάνω.

    Κάτι άλλο εξίσου σημαντικό είναι ότι δεν μπορούμε να χρησιμοποιήσουμε εκτεταμένα wildcards παρά μόνο σε εσωτερικά domains, για παράδειγμα τα kladakis*@finance.autoexec.gr ή blackman@sales*.autoexec.gr δεν υποστηρίζονται ενώ το spanougakis@*.autoexec.gr υποστηρίζεται. Χρήσιμο για παράδειγμα θα ήταν το rewriting των *@development.autoexec.gr και *@software.autoexec.gr σε *@support.autoexec.gr.

    Δυστυχώς το Address rewriting configur-άρεται μόνο μέσω Exchange Management Shell. Ακόμα δεν υπάρχουν επιλογές στην Exchange Management Console ( stay tuned… ).Υπάρχουν 4 ειδών εντολές :
    Get-AddressRewriteEntry
    New-AddressRewriteEntry
    Set-AddressRewriteEntry
    Remove-AddressRewriteEntry.
    Από τα προθέματα τους είναι προφανής η χρήση τους. Για παράδειγμα:
    New-AddressRewriteEntry -Name “Two-way Rewrite entry for autoexec.gr”
    -InternalAddress autoexecint.gr -ExternalAddress autoexecext.gr

    Η εκτεταμένη χρήση του Address Rewriting ενδείκνυται σε μεγάλα περιβάλλοντα με πολλά υπο-τμήματα και όχι μόνο . Θεωρείται πιο “επαγγελματικό” το [email protected] παρά το [email protected]
    Σημείωση: Μετά απο διαδηλώσεις-διαμαρτυρίες-πολιορκίες εξαγριωμένων administrator στα Headquarters του Exchange Product Group εδόθη η υπόσχεση ότι το θέμα με την EMC θα διορθωθεί σύντομα .. Εν αναμονή λοιπόν..
  3. i-away
    he Exchange Sustained Engineering team recently made the decision to recall
    the June 22, 2011 release of Exchange 2010 SP1 Rollup 4. This was not
    an action we took lightly and we understand how disruptive this was to
    customers. We would like to provide you with some details that will
    give you a deeper understanding of what actually happened and, more
    importantly, what improvements we are making to prevent this in the
    future.
    Q: What actually triggered the recall?
     
    A:
    While fixing a bug that prevented deleted public folders from being
    recovered, we exposed an untested set of conditions with the Outlook
    client. When moving or copying a folder, Outlook passes a flag on a
    remote procedure call that instructs the Information Store to open
    deleted items which haven’t been purged. Our fix inadvertently caused
    the RPC to skip all content that wasn’t marked for deletion because we
    were not expecting this flag on the call from Outlook on the copy and
    move operations.
    Q: Why didn’t you test this scenario?
     
    A:
    The short answer is we thought we did. We didn’t realize we missed a
    key interaction between Exchange and Outlook. The Exchange team has
    well over 100,000 automated tests that we use to validate our product
    before we ship it. With the richness and number of scenarios and
    behaviors that Exchange supports, automated testing is the only scalable
    solution. We execute these tests in varying scenarios and conditions
    repeatedly before we release the software to our customers. We also
    supplement these tests with manual validation where necessary. The
    downside of our tests is that they primarily exercise the interfaces we
    expose and are designed around our specifications. They do test
    positive and negative conditions to catch unexpected behavior and we did
    execute numerous folder copy and move tests against the modified code
    which all passed. What we did not realize is that our tests were not
    emulating the procedure call as executed by Outlook.
    Q: Exchange has been around a while, why did this happen now?
     
    A: In Exchange 2010 we introduced a feature called RPC Client Access. This functionality is responsible for serving as the MAPI
    endpoint for Outlook clients. It allowed us to abstract client
    connections away from the Information Store (on Mailbox servers) and
    cause all Outlook clients to connect to the RPC Client Access service.
    As
    part of our investigation, we discovered that there was some specific
    code added to the Exchange 2003 Information Store to handle the
    procedure call from Outlook using the extra flag. This code was also
    carried forward into Exchange 2007. But when the Exchange team added
    the RPC Client Access service to Exchange 2010, that code was not
    incorporated into the RPC Client Access service because it was
    mistakenly believed to be legacy Outlook behavior that was no longer
    required. That, unfortunately, turned out not to be the case. The fact
    that we were not allowing a deleted public folder to be recovered was
    masking this new bug completely.
    Q: Are there other similar issues lurking in RPC Client Access?
     
    A:
    We do not believe so. The RPC Client Access functionality has been
    well-tested at scale and proven to be reliable for the millions of
    mailboxes hosted in on-premises deployment and in our own Office 365 and
    Live@EDU services.
    Q: What are you doing to prevent similar things from happening in the future?
     
    A:
    We have conducted a top-to-bottom review of the process we use to
    triage, develop and validate changes for Rollups and Service Packs and
    are making several improvements. We have changed the way we evaluate a
    customer requested fix to ensure that we more accurately identify the
    risk and usage scenarios that must be validated for a given fix.
    Recognizing the diversity of clients used to connect to Exchange, we are
    increasing our client driven test coverage to broaden the usage
    patterns validated prior to release. Most notably, we are working even
    closer with our counterparts in Outlook to use their automated test
    coverage against each of our releases as well. We are also looking to
    increase coverage for other clients as well.
  4. i-away
    You’ve told us that one of your top concerns is the increasing diversity of mobile devices that employees use to access your company resources. While many of these devices use Exchange ActiveSync (EAS) for mobile email, we all know that not all EAS clients are created equal. Exchange ActiveSync policies and features aren’t consistently implemented by licensees, so it can be challenging to find out what’s supported on each device.
    Today, we launched the Exchange ActiveSync Logo Program to establish baseline for EAS functionality in mobile email devices . The program is designed for device manufacturers that license the EAS protocol from Microsoft for use in mobile email clients that connect to Exchange. Wireless carriers may also join the program to include the Exchange brand to identify compliant devices for end-users. See Exchange ActiveSync Protocol for a list of current EAS licensees.
    This qualification program includes a test plan defined by Microsoft and a third-party lab to qualify implementations by handset makers. Qualifying clients must use EAS v14 or later, and implement the following features and management policies. Information on these and other EAS features can be found in Exchange documentation on TechNet:
    Direct Push email, contacts & calendar Accept, Decline & Tentatively Accept meetings Rich formatted email (HTML) Reply/Forward state on email GAL Lookup Autodiscover ABQ strings (device type and device model) provided Remote Wipe Password Required Minimum Password Length Timeout without User Input Number of Failed Attempts All Windows Phone 7 and Windows Phone 6.5 devices are compliant, as are Nokia devices running Mail for Exchange 3.0.50, including the Nokia E7, and Apple devices running iOS 4, including the iPhone 4, iPhone 3GS, iPad and iPad 2. We have a healthy pipeline of mobile device manufacturers ready to join the program and plan to announce additional participants in the coming months.
    Over time, the program will evolve to require additional features and management policies. We hope this program is a first step in helping you manage mobile email devices in your enterprise.
    For more info on managing your organization’s EAS devices, check out the previous post: Controlling Exchange ActiveSync device access using the Allow/Block/Quarantine list.
    Greg Smiley
    Senior Product Manager
    Exchange Product Management
  5. i-away
    Earlier today the Exchange CXP team released an updated version of Update Rollup 4 for Exchange Server 2010 SP1
    to the Download Center. This updated release is being made available
    after a complete review and revalidation of the list of fixes included
    in the previously released version of Rollup 4 dated June 22, 2011.

    The review completed by the Exchange CXP team determined that the issue identified in 'KB 2581545:
    The copy or move operation on a folder that contains subfolders does
    not work as expected after you install Update Rollup 4 for Exchange
    Server 2010 SP1 dated June 22, 2011’ introduced a serious regression in
    the original release of Rollup 4. As a result, a new version of Rollup 4 dated July 23, 2011 has been tested and released with the change that caused the regression removed. The re-release of Rollup 4 is tracked by 'KB 2579150: Description of Update Rollup 4 for Exchange Server 2010 Service Pack 1'.

    The updated Rollup 4 is being released to allow customers to install
    the list of fixes previously committed to on the normal rollup schedule
    using normal rollup installation routines without the need for further
    action. The re-released version of Rollup 4 is functionally equivalent
    to the combination of the original Rollup 4 release and (the interim updatein) KB 2581545. Here are answers to some install questions:

    Customers who have installed KB 2509910 (Rollup 4, dated June 22, 2011) and
    KB2581545 (fix for Rollup 4 regression) do not need to install KB
    2579150 (re-released Rollup 4) but may do so if they choose to. Customers who have already installed KB 2581545 and want to update
    their systems to the updated Rollup 4 should first uninstall KB 2581545
    (or any interim updates) prior to installing the new rollup. You do not need to uninstall original RU4 (KB 2509910) to install the re-released RU4 package (KB2579150). The re-release of Rollup 4 does not change the release plans for
    Update Rollup 5 for Exchange Server 2010 Service Pack 1. Rollup 5 is
    currently scheduled to release in August 2011.
    Some of the above KnowledgeBase articles are not
    replicated/live at the time of writing this post. Please check back
    later in the day if you can't reach them.

    General Notes

    Note for Exchange 2010 Customers using the Arabic and Hebrew language version:
    We introduced two new languages with the release of Service Pack 1,
    Arabic and Hebrew. At present we are working through the process of
    modifying our installers to incorporate these two languages. Customers
    running either of the two language versions affected are advised to
    download and install the English language version of the rollup which
    contains all of the same fixes.

    Note for Forefront users: For those of you
    running Forefront Security for Exchange, be sure you perform these
    important steps from the command line in the Forefront directory before
    and after this rollup's installation process. Without these steps,
    Exchange services for Information Store and Transport will not start
    after you apply this update. Before installing the update, disable
    ForeFront by using this command: fscutility /disable. After installing the update, re-enable ForeFront by running fscutility /enable.
  6. i-away
    Μετά απο πολύ καιρό και το αίσιο τέλος μιας μεγάλης αλλαγής σε πέλατη (
    migration στο migration ) αποφάσισα να γράψω τις εμπειρίες μου για ένα
    πρωτόγνωρο πράγμα για εμένα. Την συνύπαρξη του Exchange με τα Μαύρα Μούρα. Είχα
    ακούσει απο συναδέρφους εμπειρίες και απόψεις , είχα δει video αλλά επί της
    πράξης ανακάλυψα πολλά μυστικά και κολπάκια.

    Πολλές εταιρείες καταφεύγουν στα λεγόμενα “consumer BlackBerrys “ καθώς είναι
    εύκολο να συνδεθούν στην  cloud-based BlackBerry Internet
    Service και σε έναν  IMAP4 ή POP3-capable mail server. Με την ύπαρξη
    ενός Exchange server μπορούν  να συνδεθολυν  ακόμα και σε μία
    Outlook Web Access σελίδα.Τα  “consumer BlackBerrys “ είναι
    τέλεια για απλούς χρήστες ή για μικρού μεγέθους mailboxes, αλλά ζορίζονται όταν
    υπάρχουν πολύπλοκα mailboxes με πολλούς φακέλους.Επίσης  οι
    χρήστες πρέπει να συγχρονίζουν τα  calendar και τα contacts τους χειροκίνητα
    μέσου του  BlackBerry Desktop Software. Επίσης η υπηρεσία έχει 
    SLAs απλού χρήστη και όχι επαγγελματία, με τα όποια μειονεκτήματα αναδεικνύει
    αυτό.

    Για τις πιο επαγγελματικές περιπτώσεις χρησιμοποιείται ο BlackBerry
    Enterprise Server.Η δουλειά του είναι να συνδέει το δικτύο μας με το
    δίκτυο της RIM περνώντας mail απευθείας απο τον Exchange ή
    Notes ή GroupWise server απευθείας στο BlackBerry.
    Για την ιστορία η RIM ήταν απο τις πρώτες εταιρείες που χρησιμοποίησαν το
    λεγόμενο  push email.

    Όλα αυτά θα ήταν τέλεια αν και η εγκατάσταση του BES ήταν εύκολη …. Δυστυχώς
    όμως απαιτείται η αλληλεπίδραση του με το Windows network σε βαθύ επίπεδο. Δεν
    μιλάμε για μια απλή εγκατάσταση software αλλά για δημιουργία users που έχουν
    administrator-level access στον email server μας. Απο αυτό καταλαβαίνετε την
    σοβαρότητα και την προσοχή που απαιτείται κατά την εγκατάσταση και την
    παραμετροποίηση του.

    Στις απαιτήσεις της εγκατάστασης προτείνεται dedicated server . Το ευτύχημα
    είναι ότι ένας low-end Xeon ή ένας AMD Athlon server με  2 GB  RAM είναι αρκετός.
    Προσοχή χρειάζεται  διότι δεν γίνεται εγκάτάσταση σε  Windows Server
    2008, οπότε η λύση του Windows Server 2003 R2 είναι
    μονόδρομος. Παρόλα αυτά υπάρχει υποστήριξη  64-bit οπότε στο μέλλον θα δούμε εγκαταστάσεις και σε Windows server 2008 R2.

    Το παρακάτω γρήγορο tutorial αφορά Exchange Server 2007 SP1
    σε  64-bit εγκατάσταση Windows Server 2003 R2, σε δίκτυο με
    Windows Server 2008 domain controller. Η διαδικασία είναι
    παρόμοια και για τον Exchange Server 2003 με μόνη διαφορά την
    δημιουργία του  BESAdmin λόγω της διαφορετικής αλληλεπίδρασης του Exchange
    Server 2007 με το Active Directory.


    Τον  BES μπορούμε να το κατεβάσουμε είτε απευθείας απο την RIM είτε να τον προμηθετούμε σε
    CD. Επίσης χρειαόμαστε εκτός απο  CALs για τους χρήστες και product keys.



     


    Ξεκινώντας απο τον Exchange server το πρώτο βήμα είναι να δημιουργήσουμε ένα
    mailbox account για τον BESAdmin account. Αυτό μπορεί να γίνει απο την Exchange
    Management Console. Προσοχή στο password, γιατί θα μας χρειαστεί αργότερα.

    Τώρα αυτό το account πρέπει να γίνει Exchange administrator με  view only
    rights.

    Στο αγαπητό μας Exchange Management Shell λοιπόν:

     
    add-exchangeadministrator “BESAdmin” –role ViewOnlyAdmin


     


    Και για επιβεβαίωση:

     
    get-exchangeadministrator | Format-List



      


    “Real man do it CLI “ Blackman σου θυμίζει τίποτα? ( χεχεχ )

     
    get-mailboxserver <mailserver> | add-adpermission –user
    “BESAdmin” –accessrights ExtendedRight –extendedrights Send-As, Receive-As,
    ms-Exch-Store-Admin


    Έλέγχουμε με :
    get-mailboxserver <mailserver> |
    get-ADpermission -user BESAdmin | Format-List


    Πάμε τώρα στον server που θα φιλοξενήσει τον BES.
    Μπαίνουμε ως domain administrator και δίνουμε στον BESAdmin account local
    administration rights.Ο  BES πρέπει να εγκατασταθεί με την
    χρήση του service account που θα χρησιμοποιεί για να εξασφαλιστεί η σωστή και
    απρόσκοπτη λειτουργία των  components και των databases που εγκαθιστά .Μπαίνουμε λοιπόν με τον
    BESAdmin account και συνεχίζουμε.

      
     


    Μετά την επιλογή της τοποθεσίας εγκατάστασης, επιλεγούμε τους servers που θα
    συνδέετεαι ο BES . Με την επιλογή της άδειας επιλέγουμε και τον
    τύπο εγκατάστασης. Ο κάθε BES μπορεί να υποστηρίξει μέχρι 2,000
    users γιαυτό υπάρχει η επιλογή για multi-server scalable enterprise-grade
    system σε περιβάλλοντα άνω τοων 2000 χρηστών.

    Ο  BES μπορεί να εγκατασταθεί είτε ώς απλός  mail server είτε  για να συνεργάζεται με
    άλλα applications με την χρήση του MDS (BlackBerry Mobile Data System).
    Εάν χρησιμοποιούμε εργαλεία όπως ο  Microsoft’s Office
    Communications Server διατίθενται εργαλεία για την σύνδεση των
    BlackBerrys στην internal instant messaging and presence service.
    Μετά την
    αποδοχή αρκετών άδειων για τα components που χρησιμοποιεί ο BES ( συμπεριλαμβανομένου και του Apache
    Web server ) ξεκινάει η εγκατάσταση μετά τον έλεγχο και την
    εγκατάσταση των όποιων pre-requisites λείπουν.

    Τώρα ήρθε η σειρά των Microsoft’s Exchange Server MAPI
    Client και των Collaboration Data Objects. Αυτά διατίθενται ώς
    ξεχωριστό download που μπορούμε να κατεβάσουμε απο την Microsoft.

      
     


    Η υπόλοιπη διαδικάσία κυλά σχετικά ανώδυνα.


     


    Μετά τον απαραίτητο έλεγχο του  install summary για τυχόν λάθη και το
    απαραίτητο reboot , έρχεται η ώρα της εισαγωγής των keys του BES. Αυτά
    καθορίζουν πόσες  BlackBerry συσκευές θα συνδέονται στο δίκτυο της
    RIM.


     


    Με την εισαγωγή της πρώτης άδειας μπορούμε να κάνουμε και τον έλεγχο για το
    αν συνδεόμαστε σωστά στο δίκτυο της BlackBerry.Αν όλα πάνε καλά ήρθε η ώρα να
    προστεθούν οι  BES’s identifiers: Το SRP ID και το SRP
    authentication key. Αυτά τα προμηθευόμαστε είτε απο την ίδια την RIM είτε απο
    εκεί που πήραμε το Blackberry.Επίσης μπορούν να γίνουν download σε μορφή .SRP
    file. Αυτά πρέπει να γίνουν  πρώτα validate πρίν μπορέσουμε να προχωρήσουμε στο
    επόμενο βήμα.

    Ο BES με την ολοκλήρωση των παραπάνω βημάτων είναι έτοιμος να συνδεθεί στον
    Exchange server. Εάν έχουμε εγκαταστήσει τα Microsoft’s connection tools, θα
    δούμε ότι η διαδικασία είναι παρόμοια με την ρύθμιση ενός  Outlook account.

    Υπάρχουν εδώ και κάποιες έξτρα επιλογές όπως η χρήση των δεδομένων των
    BlackBerry πάνω από WLAN. Επίσης μπορεί να γίνει και
    ενεργοποίηση μέσω WLAN το λεγόμενο WLAN OTA activation. Μία
    πολύ χρήσιμη επιλογή εδώ είναι η δυνατότητα ρύθμισης password για την σύνδεση
    του BES και των built-in communication components όπως τον 
    MDS.


     


    Με κλίκ στο Finish έχουμε ολοκληρώσει την διαδικασία εγκατάστασης. Τώρα
    μπορούμε να βγούμε απο τον BESAdmin account και να κάνουμε log on με τον
    standard administrative account για να τρέξουμε τον BlackBerry
    Manager. Αυτόν θα τον χρησιμοποιήσουμε για να ενεργοποιήσουμε τις
    συσκευές και να προσθέσουμε χρήστες απο το Active Directory. Μπορούμε να κάνουμε
    provision τις συσκευές μας απευθείας μέσω USB connection στον BES server ή
    μπορούμε να τουσ στείλουμε απλά ένα email με το activation password. Οι χρήστες
    το μόνο που πρέπει να επιλέξουν είναι το built-in Enterprise Activation εργαλείο
    που υπάρχει στα  BlackBerrys τους , να εισάγουν το password και την email
    address τους για να ενεργοποιήσουν την συσκευή τους.


     


    Ο BES Manager παρέχει τα εργαλεία που μας επιτρέπουν να στείλουμε πολιτικές
    και ρυθμίσεις στις συσκευές . Αυτό γίνεται αν πάμε στο in the BlackBerry Domain
    view, ανοίξουμε το  Global Tab, επιλέξουμε  Edit Properties και μετά ανοίξουμε
    το IT Policy settings.

    Σύντομα θα ακολουθήσει ένα “ Deeper Dive “ post στον τρόπο λειτουργίας και
    διασύνδεσης.
  7. i-away

    BPOS Guidelines

    By i-away,

    Παίρνοντας αφορμή απο πρόσφατο post συναδέρφου θα δώσω κι εγώ με την σειρά μου την δικιά μου οπτική και άποψη για το σύννεφο.
    Με την εξάπλωση του Cloud Computing ολοένα και περισσότερες εταιρείες μετακινούν τις υποδομές τους στο σύννεφο επωφελούμενες από τα οφέλη που τους παρέχει.
    Microsoft Business Productivity Online Suite
    Το μοντέλο που προσφέρει η Microsoft είναι το εξής απλό: Για κάποιο αντίτιμο η Microsoft προσφέρει σε κάθε χρήστη της εταιρείας e-mail, instant messaging, presence, Web conferencing και πρόσβαση σε intranet portal για collaboration. Απο την πλευρά της εταιρείας δεν υπάρχει ανάγκη για server software, hardware, storage ή maintenance costs. Η σουίτα του BPOS περιλαμβάνει Exchange Online (e-mail), SharePoint Online (intranet/Web portal), LiveMeeting (Web conferencing) και Office Communications Online (instant messaging/presence).
    Υπάρχουν δύο εκδόσεις BPOS: Standard και Dedicated. Η κύρια διαφορά τους είναι ότι στην Standard έκδοση πολλές εταιρείες μοιράζονται τα resources του ίδιου server στην Dedicated έκδοση κάθε εταιρεία έχει τον δικό της server. Να σημειώσουμε εδώ ότι η Exchange Online Dedicated υπηρεσία προσφέρεται μόνο σε εταιρείες μεγαλύτερες των 5,000 users.
    Εκτός του προαναφερομένουν υπάρχουν και άλλες διαφορές μεταξύ των δύο εκδόσεων όπως για παράδειγμα η αδυναμία deploy custom Web parts στην BPOS Standard SharePoint Online σουίτα ή η δυνατότητα search μεταξύ πολλών site collections στο Sharepoint,κλπ.
    Migrating στον Exchange Online
    Η μετάβαση ενός παραδοσιακού Microsoft Exchange απο τοπική υλοποίηση στον σύννεφο είναι κάτι που αν και με αρκετά προβλήματα και παγίδες ακόμα είναι μια διαδικασία που ολοκληρώνεται εύκολα και γρήγορα.
    Για την μετάβαση αυτή προσφέρονται 2 τρόποι: Η χρήση του native BPOS toolset ή η χρήση του migration tool για απευθείας σύνδεση του Exchange Online απο μία πλατφόρμα messaging τύπου Lotus Notes/Domino ή Novell GroupWise.
    On-premises to Exchange Online (Σε 2 βήματα) – Μέχρι πρόσφατα ο μόνος δρόμος για να ανεβάσουμε ένα μη-Microsoft σύστημα στο σύννεφο ( Lotus Notes/Domino,Novell GroupWise ) ήταν το on-site migration σε ένα νέο Exchange περιβάλλον και μετέπειτα στο Online περιβάλλον.
    Direct to Exchange Online (1 βήμα) – 3rd-party migration προιόντα έχουν κάνει δυνατή την απευθείας μετακίνηση απο μη-Microsoft σύστηματα σε Exchange Online με μία κίνηση κάνοντας όλα τα βήματα μαζεμένα.
    Σημεία προσοχής στα Exchange Migrations
    Directory Synchronization – Με το Microsoft Online Services Directory Synchronization Tool οι χρήστες ενός on-premises Active Directory (AD) μπορούν να συγχρονιστούν με το hosted Active Directory σε οποιοδήποτε στάδιο του migration.
    Content Migration – Στα on-premises migrations χρειάζεται προσοχή στο είδος των δεδομένων που θα μεταφερθεί μεταξύ των mail servers καθώς αυτά θα μεταφερθούν στην online πλατφόρμα μέσω του Internet.
    Mailboxes – Επειδή η μεταφορά γίνεται μέσω του Internet είναι σκόπιμο να μεταφέρονται μόνο τα απαραίτητα mail data. Εδώ προτείνεται η χρήση του archive για λόγους ταχύτητας και μείωση του όγκου δεδομένων.
    Resources – Σε περίπτωση που υπάρχουν “generic mailboxes” αυτά θα πρέπει να δημιουργηθούν στο onlime Active Directory πριν κάνουμε την διαδικασία του συγχρονισμού.
    SharePoint Online
    Η υπηρεσία του SharePoint Online προσφέρει τα ίδια ακριβώς πράγματα με τον Microsoft Office SharePoint 2007 (MOSS), χωρίς το επιπλέον “μπελά” της διαχείρησης – παραμετροποίησης της SharePoint farm. Είναι πλήρως λειτουργικό σε λίγα λεπτά εν αντιθέσει με της ακόμη και εβδομάδες που πολλές φορές χρειάζεται για να έχουμε ένα πλήρως λειτουργικό SharePoint και φυσικά μειώνει κατακόρυφα το κόστος της επένδυσης αυξάνωντας κατά πολύ το ROI.
    Το SharePoint Online διατίθεται σε 2 εκδόσεις και αυτό: Standard και Dedicated.Η standard έκδοση ( προτείνεται μέχρι 5,000 χρήστες ) παρέχει πλήρη πρόσβαση στο εκάστοτε SharePoint site collection αλλά όχι στο central administration ούτε και στο shared service provider. Η πλήρης πρόβαση – λειτουργικότητα προσφέρεται στο SharePoint Online Dedicated επίπεδο το οποίο δίνει πλήρη πρόσβαση σε όλα τα στοιχεία και τις λειτουργίες του Sharepoint ( personalization services, advanced search, Excel Web Services,Business Data Catalog).
    Challenges of Migrating to SharePoint Online
    Σε αντίθεση με το Exchange Online Migration η μετάβαση στο SharePoint Online, εστιάζεται σε 3 τομείς:security, user interface και functionality.
    Security: Ιδιαίτερη προσοχή χρειάζεται κατά την μεταφορά sharepoint contect από την on-premises στην off-premises κατάσταση εξαιτίας διαφορών στην δομή που μπορεί να υπάρξουν με αποτέλεσμα να δημιουργηθεί πρόβλημα με τα user permissions. Προτείνεται η ακριβής μεταφορά της δομής από την μία κατάσταση στην άλλη . Το πρόβλημα είναι εντονότερο σε περίπτωση που δεν έχουμε Sharepoint τοπικά αλλά κάποια 3rd party λύση.
    User interface: Εδώ δεν υπάρχει ιδιαίτερο πρόβλημα και το μόνο θέμα είναι σε μετάβαση από διαφορετική πλατφόρμα λόγω αλλαγής του "look and feel".
    Functionality: Επειδή το Sharepoint ουσιαστικά δεν είναι ένας απλός fileserver αλλά πολλά πολλά περισσότερα, οι δυνατότητες του είναι τεράστιες. Workflows,Document Libraries,IRM,κλπ ο μόνος περιορισμός είναι το τι θέλει να κάνει ο administrator και φυσικά επιφέρουν και το ανάλογο challenge υλοποίησης από μία “χαώδη” κατάσταση σε κάτι πολύ πιο λειτουργικό και αποδοτικό.
     
    Παρόλο τα προβλήματα που μπορεί να έχουμε και να αντιμετωπίσουμε κατά την μετάβαση , το σύννεφο είναι εδώ και θα μείνει . Το Microsoft’s Business Productivity Online Suite παρέχει ένα πλήρες σετ εργαλείων για την διαχείρηση και λειτουργία ( μέχρι ενός σημείου ακόμα ) όλως των IT operations απο το σύννεφο .
  8. i-away
    This cumulative update includes fixes for nonsecurity issues and all previously released fixes for security and nonsecurity issues.
    Known issues in this cumulative update
    In multidomain Active Directory forests in which Exchange is installed or has been prepared previously by using the /PrepareDomain option in SETUP, this action must be completed after the /PrepareAD command for this cumulative update has been completed and the changes are replicated to all domains. Setup will try to execute the /PrepareAD command during the first server installation. Installation will finish only if the user who initiated SETUP has the appropriate permissions. The Set-SendConnector cmdlet does not work for Exchange Server 2016 in hybrid scenarios that have a Edge server installed. For more information, see KB 4523519. Issues that this cumulative update fixes
    This cumulative update fixes the issues that are described in the following Microsoft Knowledge Base articles: 
    4502154 Providing information to administrators when auto forward limit is reached in Exchange Server 2016 4502155 “The primary SMTP address must be specified when referencing a mailbox” error when using impersonation in Exchange Server 2016 4502156 Audit logs aren’t updated when “-WhatIf” is used as $false in the command in Exchange Server 2016 4502157 The Find command not returning the HasAttachments element in Exchange Server 2016 4502158 SyncFolderItems contains duplicated ReadFlagChange items in Exchange Server 2016 4502131 “TLS negotiation failed with error UnknownCredentials” error after updating TLSCertificateName on Office 365 send connector in Exchange Server 2016 hybrid environment 4502132 Can’t reply to old emails after migration even though old legacyExchangeDN is set to migrated mailbox in Exchange Server 2016 4502136 The response of FETCH (BODYSTRUCTURE) command of IMAP violates RFC 3501 in Exchange Server 2016 4502140 Can’t preview an eDiscovery search when there are multiple domains in Exchange Server 2016 4502141 Appointment that’s created by responding to an email message doesn’t show in any of Outlook calendar views in Exchange Server 2016 4502133 Can’t use Outlook on the web to reply a partner email through mutual TLS in Exchange Server 2016 4488396 Can’t search any results in manually added shared mailbox in Outlook in Exchange Server 2016 4488078 Public folder contact lists don’t show contact’s profile picture in Outlook on the web in Exchange Server 2016 4499503 Heavy organizational forms traffic due to materialized restriction when organization forms library has more than 500 items in Exchange Server 2016 4503027 Description of the security update for Microsoft Exchange Server 2019 and 2016: June 11, 2019

  9. i-away
    This cumulative update includes fixes for nonsecurity issues and all previously released fixes for security and nonsecurity issues
    Known issues in this cumulative update
    In multidomain Active Directory forests in which Exchange is installed or has been prepared previously by using the /PrepareDomain option in Setup, this action must be completed after the /PrepareAD command for this cumulative update has been completed and the changes are replicated to all domains. Setup will try to run the /PrepareAD command during the first server installation. Installation will finish only if the user who initiated Setup has the appropriate permissions.
    Notes: If you are upgrading from Cumulative Update 13 for Exchange Server 2016 to Cumulative Update 14 for Exchange Server 2016, then there’s no need to run the /PrepareAD or /PrepareDomain. No additional actions (prepareAD, prepareDomain, or assigning permissions) are required. If you has ever skipped a Cumulative Update (for example, you are upgrading from an earlier version before Cumulative Update 13 for Exchange Server 2016), or this is a first Exchange Server installation in the AD, then this Known Issue section should be taken care of.
    a. About the /PrepareDomain operation in multidomain:
    The /PrepareDomain operation automatically runs in the Active Directory domain in which the /PrepareAD command is run. However, it may be unable to update other domains in the forest. Therefore, a domain administrator should run the /PrepareDomain in other domains in the forest.
    b. About the permission question:
    As the /PrepareAD is triggered in Setup, if the user who initiates Setup isn’t a member of Schema Admins and Enterprise Admins, the readiness check will fail and you receive the following error messages:To avoid the error messages, either the user should join Schema Admins and Enterprise Admins groups, or another user in Schema Admins and Enterprise Admins groups manually runs the /PrepareAD for this Cumulative Update first. Then the Exchange admin user can start Setup.
    The Set-SendConnector cmdlet does not work for Exchange Server 2016 in hybrid scenarios that have a Edge server installed. For more information, see KB 4523519.  Autodiscover Event ID 1 after installing Cumulative Update 14 for Exchange Server 2016. For more information, see KB 4532190. Issues that this cumulative update fixes
    This cumulative update fixes the issues that are described in the following Microsoft Knowledge Base articles:
    4515255 “X-InnerException: Microsoft.Mapi.MapiExceptionRpcServerTooBusy” error when you try to use a mailbox in Exchange Server 2016 4515254 Event 1009 frequently occurs in application logs for lagged database copies in Exchange Server 2016 4502159 Adding or removing mailbox permission in EAC doesn’t address the msExchDelegateListLink attribute in Exchange Server 2016 4515276 Room mailbox accepts a meeting as “Free” if a booking delegate is set in Exchange Server 2016 4515275 Enable Get/Restore-RecoverableItems to work with Purges folder in Exchange Server 2016 4515274 AutodiscoverV2 request returns REST API endpoint not AutoDiscoverV1 endpoint in Exchange Server 2016 4515269 SentToMemberOf shows every recipient type not distribution groups when creating transport rule in Exchange Server 2016 4515272 Message is blocked in “SMTP Delivery to Mailbox” queue if exchange server is added in groups of a child domain in Exchange Server 2016 4515271 Can’t convert a migrated remote user mailbox to shared in Exchange Server 2016 4515270 SubmissionQueueLengthMonitor shows “System.ArgumentException: Transition timeout…” in Exchange Server 2016 4515267 NDR occurs when you resend message from alternate journaling mailbox to journaling mailbox in Exchange Server 2016 4515265 Removing In-Place Hold doesn’t work for mailboxes in different domains in Exchange Server 2016 4515264 FindPeople request from Skype for Business on Mac fails with “Invalid Shape Specification” in Exchange Server 2016 4515263 Hide the “Validate-MailFlowThroughFrontDoor” command for Exchange Server 2016 4515262 Enable Remove-MobileDevice to delete mobile devices after migrating to Office 365 from Exchange Server 2016 4515261 Can’t copy eDiscovery search results for mailboxes with Exchange online archives in Office 365 in Exchange Server 2016 4515273 Mailbox auditing fails when you use SHA1Managed in Exchange Server 2016 4515266 Infinite loop in Recurrence.GetNumberOfYearsBetween() with the Japanese calendar in Exchange Server 2016 4520319 S/MIME signed reply draft behaves like the first message in conversation in Exchange Server 2016 4515832 Description of the security update for Microsoft Exchange Server 2019 and 2016: September 10, 2019

  10. i-away
    This cumulative update includes fixes for nonsecurity issues and all previously released fixes for security and nonsecurity issues
    Known issues in this cumulative update
    In multidomain Active Directory forests in which Exchange is installed or has been prepared previously by using the /PrepareDomain option in Setup, this action must be completed after the /PrepareAD command for this cumulative update has been completed and the changes are replicated to all domains. Setup will try to run the /PrepareAD command during the first server installation. Installation will finish only if the user who initiated Setup has the appropriate permissions.
    Notes: If you are upgrading from Cumulative Update 13 for Exchange Server 2016 to Cumulative Update 14 for Exchange Server 2016, then there’s no need to run the /PrepareAD or /PrepareDomain. No additional actions (prepareAD, prepareDomain, or assigning permissions) are required. If you has ever skipped a Cumulative Update (for example, you are upgrading from an earlier version before Cumulative Update 13 for Exchange Server 2016), or this is a first Exchange Server installation in the AD, then this Known Issue section should be taken care of.
    a. About the /PrepareDomain operation in multidomain:
    The /PrepareDomain operation automatically runs in the Active Directory domain in which the /PrepareAD command is run. However, it may be unable to update other domains in the forest. Therefore, a domain administrator should run the /PrepareDomain in other domains in the forest.
    b. About the permission question:
    As the /PrepareAD is triggered in Setup, if the user who initiates Setup isn’t a member of Schema Admins and Enterprise Admins, the readiness check will fail and you receive the following error messages:To avoid the error messages, either the user should join Schema Admins and Enterprise Admins groups, or another user in Schema Admins and Enterprise Admins groups manually runs the /PrepareAD for this Cumulative Update first. Then the Exchange admin user can start Setup.
    The Set-SendConnector cmdlet does not work for Exchange Server 2016 in hybrid scenarios that have a Edge server installed. For more information, see KB 4523519.  Autodiscover Event ID 1 after installing Cumulative Update 14 for Exchange Server 2016. For more information, see KB 4532190. Issues that this cumulative update fixes
    This cumulative update fixes the issues that are described in the following Microsoft Knowledge Base articles:
    4515255 “X-InnerException: Microsoft.Mapi.MapiExceptionRpcServerTooBusy” error when you try to use a mailbox in Exchange Server 2016 4515254 Event 1009 frequently occurs in application logs for lagged database copies in Exchange Server 2016 4502159 Adding or removing mailbox permission in EAC doesn’t address the msExchDelegateListLink attribute in Exchange Server 2016 4515276 Room mailbox accepts a meeting as “Free” if a booking delegate is set in Exchange Server 2016 4515275 Enable Get/Restore-RecoverableItems to work with Purges folder in Exchange Server 2016 4515274 AutodiscoverV2 request returns REST API endpoint not AutoDiscoverV1 endpoint in Exchange Server 2016 4515269 SentToMemberOf shows every recipient type not distribution groups when creating transport rule in Exchange Server 2016 4515272 Message is blocked in “SMTP Delivery to Mailbox” queue if exchange server is added in groups of a child domain in Exchange Server 2016 4515271 Can’t convert a migrated remote user mailbox to shared in Exchange Server 2016 4515270 SubmissionQueueLengthMonitor shows “System.ArgumentException: Transition timeout…” in Exchange Server 2016 4515267 NDR occurs when you resend message from alternate journaling mailbox to journaling mailbox in Exchange Server 2016 4515265 Removing In-Place Hold doesn’t work for mailboxes in different domains in Exchange Server 2016 4515264 FindPeople request from Skype for Business on Mac fails with “Invalid Shape Specification” in Exchange Server 2016 4515263 Hide the “Validate-MailFlowThroughFrontDoor” command for Exchange Server 2016 4515262 Enable Remove-MobileDevice to delete mobile devices after migrating to Office 365 from Exchange Server 2016 4515261 Can’t copy eDiscovery search results for mailboxes with Exchange online archives in Office 365 in Exchange Server 2016 4515273 Mailbox auditing fails when you use SHA1Managed in Exchange Server 2016 4515266 Infinite loop in Recurrence.GetNumberOfYearsBetween() with the Japanese calendar in Exchange Server 2016 4520319 S/MIME signed reply draft behaves like the first message in conversation in Exchange Server 2016 4515832 Description of the security update for Microsoft Exchange Server 2019 and 2016: September 10, 2019
  11. i-away
    This cumulative update includes fixes for nonsecurity issues and all previously released fixes for security and nonsecurity issues
    Known issues in this cumulative update
    In multidomain Active Directory forests in which Exchange is installed or has been prepared previously by using the /PrepareDomain option in Setup, this action must be completed after the /PrepareAD command for this cumulative update has been completed and the changes are replicated to all domains. Setup will try to run the /PrepareAD command during the first server installation. Installation will finish only if the user who initiated Setup has the appropriate permissions.
    Notes: If you are upgrading from Cumulative Update 13 for Exchange Server 2016 to Cumulative Update 14 for Exchange Server 2016, then there’s no need to run the /PrepareAD or /PrepareDomain. No additional actions (prepareAD, prepareDomain, or assigning permissions) are required. If you has ever skipped a Cumulative Update (for example, you are upgrading from an earlier version before Cumulative Update 13 for Exchange Server 2016), or this is a first Exchange Server installation in the AD, then this Known Issue section should be taken care of.
    a. About the /PrepareDomain operation in multidomain:
    The /PrepareDomain operation automatically runs in the Active Directory domain in which the /PrepareAD command is run. However, it may be unable to update other domains in the forest. Therefore, a domain administrator should run the /PrepareDomain in other domains in the forest.
    b. About the permission question:
    As the /PrepareAD is triggered in Setup, if the user who initiates Setup isn’t a member of Schema Admins and Enterprise Admins, the readiness check will fail and you receive the following error messages: To avoid the error messages, either the user should join Schema Admins and Enterprise Admins groups, or another user in Schema Admins and Enterprise Admins groups manually runs the /PrepareAD for this Cumulative Update first. Then the Exchange admin user can start Setup.
    The Set-SendConnector cmdlet does not work for Exchange Server 2016 in hybrid scenarios that have a Edge server installed. For more information, see KB 4523519.  Autodiscover Event ID 1 after installing Cumulative Update 14 for Exchange Server 2016. For more information, see KB 4532190. Issues that this cumulative update fixes
    This cumulative update fixes the issues that are described in the following Microsoft Knowledge Base articles:
    4515255 “X-InnerException: Microsoft.Mapi.MapiExceptionRpcServerTooBusy” error when you try to use a mailbox in Exchange Server 2016 4515254 Event 1009 frequently occurs in application logs for lagged database copies in Exchange Server 2016 4502159 Adding or removing mailbox permission in EAC doesn’t address the msExchDelegateListLink attribute in Exchange Server 2016 4515276 Room mailbox accepts a meeting as “Free” if a booking delegate is set in Exchange Server 2016 4515275 Enable Get/Restore-RecoverableItems to work with Purges folder in Exchange Server 2016 4515274 AutodiscoverV2 request returns REST API endpoint not AutoDiscoverV1 endpoint in Exchange Server 2016 4515269 SentToMemberOf shows every recipient type not distribution groups when creating transport rule in Exchange Server 2016 4515272 Message is blocked in “SMTP Delivery to Mailbox” queue if exchange server is added in groups of a child domain in Exchange Server 2016 4515271 Can’t convert a migrated remote user mailbox to shared in Exchange Server 2016 4515270 SubmissionQueueLengthMonitor shows “System.ArgumentException: Transition timeout…” in Exchange Server 2016 4515267 NDR occurs when you resend message from alternate journaling mailbox to journaling mailbox in Exchange Server 2016 4515265 Removing In-Place Hold doesn’t work for mailboxes in different domains in Exchange Server 2016 4515264 FindPeople request from Skype for Business on Mac fails with “Invalid Shape Specification” in Exchange Server 2016 4515263 Hide the “Validate-MailFlowThroughFrontDoor” command for Exchange Server 2016 4515262 Enable Remove-MobileDevice to delete mobile devices after migrating to Office 365 from Exchange Server 2016 4515261 Can’t copy eDiscovery search results for mailboxes with Exchange online archives in Office 365 in Exchange Server 2016 4515273 Mailbox auditing fails when you use SHA1Managed in Exchange Server 2016 4515266 Infinite loop in Recurrence.GetNumberOfYearsBetween() with the Japanese calendar in Exchange Server 2016 4520319 S/MIME signed reply draft behaves like the first message in conversation in Exchange Server 2016 4515832 Description of the security update for Microsoft Exchange Server 2019 and 2016: September 10, 2019
  12. i-away
    This cumulative update includes fixes for nonsecurity issues and all previously released fixes for security and nonsecurity issues

    Known issues in this cumulative update
    In multidomain Active Directory forests in which Exchange is installed or has been prepared previously by using the /PrepareDomain option in Setup, this action must be completed after the /PrepareAD command for this cumulative update has been completed and the changes are replicated to all domains. Setup will try to run the /PrepareAD command during the first server installation. Installation will finish only if the user who initiated Setup has the appropriate permissions.
    Notes If you are upgrading from Cumulative Update 13 for Exchange Server 2016 or a later cumulative update for Exchange Server 2016 to Cumulative Update 16 for Exchange Server 2016, then there’s no need to run the /PrepareAD or /PrepareDomain. No additional actions (prepareAD, prepareDomain, or assigning permissions) are required. If you have ever skipped a Cumulative Update (for example, you are upgrading from an earlier version before Cumulative Update 13 for Exchange Server 2016), or this is a first Exchange Server installation in the AD, then this Known Issue section should be taken care of. About the /PrepareDomain operation in multidomain:
    The /PrepareDomain operation automatically runs in the Active Directory domain in which the /PrepareAD command is run. However, it may be unable to update other domains in the forest. Therefore, a domain administrator should run the /PrepareDomain in other domains in the forest. About the permission question:
    As the /PrepareAD is triggered in Setup, if the user who initiates Setup isn’t a member of Schema Admins and Enterprise Admins, the readiness check will fail and you receive the following error messages.To avoid the errors, either the user should join Schema Admins and Enterprise Admins groups or another user in Schema Admins and Enterprise Admins groups manually runs the /PrepareAD for this Cumulative Update first. Then the Exchange admin user can start Setup.
    Autodiscover Event ID 1 occurs after you install Cumulative Update 14 for Exchange Server 2016. For more information, see KB 4532190. Issues that this cumulative update fixes
    This cumulative update fixes the issues that are described in the following Microsoft Knowledge Base articles:
    4547705 Authentication loop between msft.sts.microsoft.com/adfs and OWA in Exchange Server 2016 4547706 Birthday isn’t correctly synced to iOS native mail app in Exchange Server 2016 4547708 Elevation of privileges possible when Active Directory permissions role is granted in Exchange Server 2016 4547709 InternetWebProxyBypassList is ignored by Mailbox Replication service in Exchange Server 2016 4547710 New-MailboxSearch with In-Place Hold enabled replaces all values in msExchUserHoldPolicies if adding a value in Exchange Server 2016 4547711 Public folder permissions aren’t applied from Outlook in Exchange Server 2016 hybrid environment 4547712 Outlook on the web (OWA) exposes junk operations even if disabled via OwaMailboxPolicy in Exchange Server 2016 4547713 IsOnlineMeeting is always false for Teams-only meetings in Exchange Server 2016 4547714 Can’t add remote shared mailbox by using ECP into distribution group in Exchange Server 2016 hybrid environment 4547715 New created search folder retention policy is changed in Exchange Server 2016 4547722 Can’t go from Office 365 to Enterprise in Exchange Server 2016 Exchange admin center (EAC) if Chrome SameSite Cookie is enabled 4547723 Can’t sign in to Office 365 if configuring hybrid with Chrome SameSite Cookie enabled in Exchange Server 2016 4547716 Event ID 1325 and Test-ExchangeSearch crashes application pool with NullReferenceException in Exchange Server 2016 4536987 Description of the security update for Microsoft Exchange Server 2016: February 11, 2020 4540123 Description of the security update for Microsoft Exchange Server 2016: March 10, 2020

  13. i-away
    This cumulative update includes fixes for nonsecurity issues and all previously released fixes for security and nonsecurity issues

    Known issues in this cumulative update
    In multidomain Active Directory forests in which Exchange is installed or has been prepared previously by using the /PrepareDomain option in Setup, this action must be completed after the /PrepareAD command for this cumulative update has been completed and the changes are replicated to all domains. Setup will try to run the /PrepareAD command during the first server installation. Installation will finish only if the user who initiated Setup has the appropriate permissions.
    Notes If you are upgrading from Cumulative Update 13 for Exchange Server 2016 or a later cumulative update for Exchange Server 2016 to Cumulative Update 16 for Exchange Server 2016, then there’s no need to run the /PrepareAD or /PrepareDomain. No additional actions (prepareAD, prepareDomain, or assigning permissions) are required. If you have ever skipped a Cumulative Update (for example, you are upgrading from an earlier version before Cumulative Update 13 for Exchange Server 2016), or this is a first Exchange Server installation in the AD, then this Known Issue section should be taken care of. About the /PrepareDomain operation in multidomain:
    The /PrepareDomain operation automatically runs in the Active Directory domain in which the /PrepareAD command is run. However, it may be unable to update other domains in the forest. Therefore, a domain administrator should run the /PrepareDomain in other domains in the forest. About the permission question:
    As the /PrepareAD is triggered in Setup, if the user who initiates Setup isn’t a member of Schema Admins and Enterprise Admins, the readiness check will fail and you receive the following error messages.To avoid the errors, either the user should join Schema Admins and Enterprise Admins groups or another user in Schema Admins and Enterprise Admins groups manually runs the /PrepareAD for this Cumulative Update first. Then the Exchange admin user can start Setup.
    Autodiscover Event ID 1 occurs after you install Cumulative Update 14 for Exchange Server 2016. For more information, see KB 4532190. Issues that this cumulative update fixes
    This cumulative update fixes the issues that are described in the following Microsoft Knowledge Base articles:
    4547705 Authentication loop between msft.sts.microsoft.com/adfs and OWA in Exchange Server 2016 4547706 Birthday isn’t correctly synced to iOS native mail app in Exchange Server 2016 4547708 Elevation of privileges possible when Active Directory permissions role is granted in Exchange Server 2016 4547709 InternetWebProxyBypassList is ignored by Mailbox Replication service in Exchange Server 2016 4547710 New-MailboxSearch with In-Place Hold enabled replaces all values in msExchUserHoldPolicies if adding a value in Exchange Server 2016 4547711 Public folder permissions aren’t applied from Outlook in Exchange Server 2016 hybrid environment 4547712 Outlook on the web (OWA) exposes junk operations even if disabled via OwaMailboxPolicy in Exchange Server 2016 4547713 IsOnlineMeeting is always false for Teams-only meetings in Exchange Server 2016 4547714 Can’t add remote shared mailbox by using ECP into distribution group in Exchange Server 2016 hybrid environment 4547715 New created search folder retention policy is changed in Exchange Server 2016 4547722 Can’t go from Office 365 to Enterprise in Exchange Server 2016 Exchange admin center (EAC) if Chrome SameSite Cookie is enabled 4547723 Can’t sign in to Office 365 if configuring hybrid with Chrome SameSite Cookie enabled in Exchange Server 2016 4547716 Event ID 1325 and Test-ExchangeSearch crashes application pool with NullReferenceException in Exchange Server 2016 4536987 Description of the security update for Microsoft Exchange Server 2016: February 11, 2020 4540123 Description of the security update for Microsoft Exchange Server 2016: March 10, 2020
  14. i-away
    This cumulative update includes fixes for nonsecurity issues and all previously released fixes for security and nonsecurity issues

    Known issues in this cumulative update
    In multidomain Active Directory forests in which Exchange is installed or has been prepared previously by using the /PrepareDomain option in Setup, this action must be completed after the /PrepareAD command for this cumulative update has been completed and the changes are replicated to all domains. Setup will try to run the /PrepareAD command during the first server installation. Installation will finish only if the user who initiated Setup has the appropriate permissions.
    Notes If you are upgrading from Cumulative Update 13 for Exchange Server 2016 or a later cumulative update for Exchange Server 2016 to Cumulative Update 16 for Exchange Server 2016, then there’s no need to run the /PrepareAD or /PrepareDomain. No additional actions (prepareAD, prepareDomain, or assigning permissions) are required. If you have ever skipped a Cumulative Update (for example, you are upgrading from an earlier version before Cumulative Update 13 for Exchange Server 2016), or this is a first Exchange Server installation in the AD, then this Known Issue section should be taken care of. About the /PrepareDomain operation in multidomain:
    The /PrepareDomain operation automatically runs in the Active Directory domain in which the /PrepareAD command is run. However, it may be unable to update other domains in the forest. Therefore, a domain administrator should run the /PrepareDomain in other domains in the forest. About the permission question:
    As the /PrepareAD is triggered in Setup, if the user who initiates Setup isn’t a member of Schema Admins and Enterprise Admins, the readiness check will fail and you receive the following error messages. To avoid the errors, either the user should join Schema Admins and Enterprise Admins groups or another user in Schema Admins and Enterprise Admins groups manually runs the /PrepareAD for this Cumulative Update first. Then the Exchange admin user can start Setup.
    Autodiscover Event ID 1 occurs after you install Cumulative Update 14 for Exchange Server 2016. For more information, see KB 4532190. Issues that this cumulative update fixes
    This cumulative update fixes the issues that are described in the following Microsoft Knowledge Base articles:
    4547705 Authentication loop between msft.sts.microsoft.com/adfs and OWA in Exchange Server 2016 4547706 Birthday isn’t correctly synced to iOS native mail app in Exchange Server 2016 4547708 Elevation of privileges possible when Active Directory permissions role is granted in Exchange Server 2016 4547709 InternetWebProxyBypassList is ignored by Mailbox Replication service in Exchange Server 2016 4547710 New-MailboxSearch with In-Place Hold enabled replaces all values in msExchUserHoldPolicies if adding a value in Exchange Server 2016 4547711 Public folder permissions aren’t applied from Outlook in Exchange Server 2016 hybrid environment 4547712 Outlook on the web (OWA) exposes junk operations even if disabled via OwaMailboxPolicy in Exchange Server 2016 4547713 IsOnlineMeeting is always false for Teams-only meetings in Exchange Server 2016 4547714 Can’t add remote shared mailbox by using ECP into distribution group in Exchange Server 2016 hybrid environment 4547715 New created search folder retention policy is changed in Exchange Server 2016 4547722 Can’t go from Office 365 to Enterprise in Exchange Server 2016 Exchange admin center (EAC) if Chrome SameSite Cookie is enabled 4547723 Can’t sign in to Office 365 if configuring hybrid with Chrome SameSite Cookie enabled in Exchange Server 2016 4547716 Event ID 1325 and Test-ExchangeSearch crashes application pool with NullReferenceException in Exchange Server 2016 4536987 Description of the security update for Microsoft Exchange Server 2016: February 11, 2020 4540123 Description of the security update for Microsoft Exchange Server 2016: March 10, 2020
  15. i-away
    This cumulative update includes fixes for nonsecurity issues and all previously released fixes for security and nonsecurity issues.

    Known issues in this cumulative update
    In multidomain Active Directory forests in which Exchange is installed or has been prepared previously by using the /PrepareDomain option in Setup, this action must be completed after the /PrepareAD command for this cumulative update has been completed and the changes are replicated to all domains. Setup will try to run the /PrepareAD command during the first server installation. Installation will finish only if the user who initiated Setup has the appropriate permissions.
    Notes If you are upgrading from Cumulative Update 13 for Exchange Server 2016 or a later cumulative update for Exchange Server 2016 to Cumulative Update 17 for Exchange Server 2016, then there’s no need to run the /PrepareAD or /PrepareDomain. No additional actions (prepareAD, prepareDomain, or assigning permissions) are required. If you have ever skipped a Cumulative Update (for example, you are upgrading from an earlier version before Cumulative Update 13 for Exchange Server 2016), or this is a first Exchange Server installation in the AD, then this Known Issue section should be taken care of. About the /PrepareDomain operation in multidomain:
    The /PrepareDomain operation automatically runs in the Active Directory domain in which the /PrepareAD command is run. However, it may be unable to update other domains in the forest. Therefore, a domain administrator should run the /PrepareDomain in other domains in the forest. About the permission question:
    As the /PrepareAD is triggered in Setup, if the user who initiates Setup isn’t a member of Schema Admins and Enterprise Admins, the readiness check will fail and you receive the following error messages.To avoid the errors, either the user should join Schema Admins and Enterprise Admins groups or another user in Schema Admins and Enterprise Admins groups manually runs the /PrepareAD for this Cumulative Update first. Then the Exchange admin user can start Setup.
    Autodiscover Event ID 1 occurs after you install Cumulative Update 14 for Exchange Server 2016. For more information, see KB 4532190. Issues that this cumulative update fixes
    This cumulative update fixes the issues that are described in the following Microsoft Knowledge Base articles:
    4559444 Conversion from HTML to RTF removes non-breaking space in Exchange Server 2016 4559435 Introduce an OrganizationConfig flag to enable or disable recipient read session in Exchange Server 2016 4547707 Enable piping for Restore-RecoverableItems in Exchange Server 2019 and 2016 4559436 Attachments with properties (like Azure Information Protection labels) don’t always match in Exchange Server 2016 4559437 PR_RECIPIENT_ENTRYID is computed if no email address or type in Exchange Server 2016 4559438 Edge Transport server hangs in Exchange Server 2016 4559439 EAS creates failure report if a message with unknown recipients is in Drafts in Exchange Server 2016 4559440 Export to a PST for an eDiscovery search fails in Exchange Server 2016 4559441 Foreign language characters set in RejectMessageReasonText of a transport rule aren’t shown correctly in Exchange Server 2016 4559442 2080 Events caused by empty values in HKLM\SYSTEM\CurrentControlSet\Services\MSExchange ADAccess\Instance0 in Exchange Server 2016 4549689 HMA EvoSTS certificate rollover causes authentication prompts due to stalled key on worker process spawn (warmup phase) in Exchange Server 2016 4559443 Managed Folder Assistant fails with Event ID 9004 NotInBagPropertyErrorException in Exchange Server 2016 4559446 Changes to Outlook on the web blocked file extensions and MIME types in Exchange Server 2016
  16. i-away
    This cumulative update includes fixes for nonsecurity issues and all previously released fixes for security and nonsecurity issues.

    Known issues in this cumulative update
    In multidomain Active Directory forests in which Exchange is installed or has been prepared previously by using the /PrepareDomain option in Setup, this action must be completed after the /PrepareAD command for this cumulative update has been completed and the changes are replicated to all domains. Setup will try to run the /PrepareAD command during the first server installation. Installation will finish only if the user who initiated Setup has the appropriate permissions.
    Notes If you are upgrading from Cumulative Update 13 for Exchange Server 2016 or a later cumulative update for Exchange Server 2016 to Cumulative Update 17 for Exchange Server 2016, then there’s no need to run the /PrepareAD or /PrepareDomain. No additional actions (prepareAD, prepareDomain, or assigning permissions) are required. If you have ever skipped a Cumulative Update (for example, you are upgrading from an earlier version before Cumulative Update 13 for Exchange Server 2016), or this is a first Exchange Server installation in the AD, then this Known Issue section should be taken care of. About the /PrepareDomain operation in multidomain:
    The /PrepareDomain operation automatically runs in the Active Directory domain in which the /PrepareAD command is run. However, it may be unable to update other domains in the forest. Therefore, a domain administrator should run the /PrepareDomain in other domains in the forest. About the permission question:
    As the /PrepareAD is triggered in Setup, if the user who initiates Setup isn’t a member of Schema Admins and Enterprise Admins, the readiness check will fail and you receive the following error messages.To avoid the errors, either the user should join Schema Admins and Enterprise Admins groups or another user in Schema Admins and Enterprise Admins groups manually runs the /PrepareAD for this Cumulative Update first. Then the Exchange admin user can start Setup.
    Autodiscover Event ID 1 occurs after you install Cumulative Update 14 for Exchange Server 2016. For more information, see KB 4532190. Issues that this cumulative update fixes
    This cumulative update fixes the issues that are described in the following Microsoft Knowledge Base articles:
    4559444 Conversion from HTML to RTF removes non-breaking space in Exchange Server 2016 4559435 Introduce an OrganizationConfig flag to enable or disable recipient read session in Exchange Server 2016 4547707 Enable piping for Restore-RecoverableItems in Exchange Server 2019 and 2016 4559436 Attachments with properties (like Azure Information Protection labels) don’t always match in Exchange Server 2016 4559437 PR_RECIPIENT_ENTRYID is computed if no email address or type in Exchange Server 2016 4559438 Edge Transport server hangs in Exchange Server 2016 4559439 EAS creates failure report if a message with unknown recipients is in Drafts in Exchange Server 2016 4559440 Export to a PST for an eDiscovery search fails in Exchange Server 2016 4559441 Foreign language characters set in RejectMessageReasonText of a transport rule aren’t shown correctly in Exchange Server 2016 4559442 2080 Events caused by empty values in HKLM\SYSTEM\CurrentControlSet\Services\MSExchange ADAccess\Instance0 in Exchange Server 2016 4549689 HMA EvoSTS certificate rollover causes authentication prompts due to stalled key on worker process spawn (warmup phase) in Exchange Server 2016 4559443 Managed Folder Assistant fails with Event ID 9004 NotInBagPropertyErrorException in Exchange Server 2016 4559446 Changes to Outlook on the web blocked file extensions and MIME types in Exchange Server 2016

  17. i-away
    This cumulative update includes fixes for nonsecurity issues and all previously released fixes for security and nonsecurity issues.

    Known issues in this cumulative update
    In multidomain Active Directory forests in which Exchange is installed or has been prepared previously by using the /PrepareDomain option in Setup, this action must be completed after the /PrepareAD command for this cumulative update has been completed and the changes are replicated to all domains. Setup will try to run the /PrepareAD command during the first server installation. Installation will finish only if the user who initiated Setup has the appropriate permissions.
    Notes If you are upgrading from Cumulative Update 13 for Exchange Server 2016 or a later cumulative update for Exchange Server 2016 to Cumulative Update 17 for Exchange Server 2016, then there’s no need to run the /PrepareAD or /PrepareDomain. No additional actions (prepareAD, prepareDomain, or assigning permissions) are required. If you have ever skipped a Cumulative Update (for example, you are upgrading from an earlier version before Cumulative Update 13 for Exchange Server 2016), or this is a first Exchange Server installation in the AD, then this Known Issue section should be taken care of. About the /PrepareDomain operation in multidomain:
    The /PrepareDomain operation automatically runs in the Active Directory domain in which the /PrepareAD command is run. However, it may be unable to update other domains in the forest. Therefore, a domain administrator should run the /PrepareDomain in other domains in the forest. About the permission question:
    As the /PrepareAD is triggered in Setup, if the user who initiates Setup isn’t a member of Schema Admins and Enterprise Admins, the readiness check will fail and you receive the following error messages. To avoid the errors, either the user should join Schema Admins and Enterprise Admins groups or another user in Schema Admins and Enterprise Admins groups manually runs the /PrepareAD for this Cumulative Update first. Then the Exchange admin user can start Setup.
    Autodiscover Event ID 1 occurs after you install Cumulative Update 14 for Exchange Server 2016. For more information, see KB 4532190. Issues that this cumulative update fixes
    This cumulative update fixes the issues that are described in the following Microsoft Knowledge Base articles:
    4559444 Conversion from HTML to RTF removes non-breaking space in Exchange Server 2016 4559435 Introduce an OrganizationConfig flag to enable or disable recipient read session in Exchange Server 2016 4547707 Enable piping for Restore-RecoverableItems in Exchange Server 2019 and 2016 4559436 Attachments with properties (like Azure Information Protection labels) don’t always match in Exchange Server 2016 4559437 PR_RECIPIENT_ENTRYID is computed if no email address or type in Exchange Server 2016 4559438 Edge Transport server hangs in Exchange Server 2016 4559439 EAS creates failure report if a message with unknown recipients is in Drafts in Exchange Server 2016 4559440 Export to a PST for an eDiscovery search fails in Exchange Server 2016 4559441 Foreign language characters set in RejectMessageReasonText of a transport rule aren’t shown correctly in Exchange Server 2016 4559442 2080 Events caused by empty values in HKLM\SYSTEM\CurrentControlSet\Services\MSExchange ADAccess\Instance0 in Exchange Server 2016 4549689 HMA EvoSTS certificate rollover causes authentication prompts due to stalled key on worker process spawn (warmup phase) in Exchange Server 2016 4559443 Managed Folder Assistant fails with Event ID 9004 NotInBagPropertyErrorException in Exchange Server 2016 4559446 Changes to Outlook on the web blocked file extensions and MIME types in Exchange Server 2016
  18. i-away
    This cumulative update is a security update. It includes fixes for nonsecurity issues and all previously released fixes for security and nonsecurity issues.

    Issues that this cumulative update fixes
    4502134 Can’t get all the emails when searching mailbox by using an end date that’s different from today in Exchange Server 2019 4502135 Correct the error message that you receive when installing Exchange Server 2019 in an organization that has Exchange Server 2010 installed 4502154 Providing information to administrators when auto forward limit is reached in Exchange Server 2019 and 2016 4502155 “The primary SMTP address must be specified when referencing a mailbox” error when you use impersonation in Exchange Server 2019 and 2016 4502156 Audit logs aren’t updated when “-WhatIf” is used as $false in the command in Exchange Server 2019 and 2016 4502157 The Find command not returning the HasAttachments element in Exchange Server 2019 and 2016 4502158 SyncFolderItems contains duplicated ReadFlagChange items in Exchange Server 2019 and 2016 4502131 “TLS negotiation failed with error UnknownCredentials” error after you update TLSCertificateName on Office 365 send connector in Exchange Server 2019 hybrid environment 4502132 Can’t reply to old emails after migration even though old legacyExchangeDN is set to migrated mailbox in Exchange Server 2019 and 2016 4502136 The response of FETCH (BODYSTRUCTURE) command of IMAP violates RFC 3501 in Exchange Server 2019 and 2016 4502140 Can’t preview an eDiscovery search when there are multiple domains in Exchange Server 2019 and 2016 4502141 Appointment that’s created by responding to an email message doesn’t show in any Outlook calendar views in Exchange Server 2019 and Exchange Server 2016 4502133 Can’t use Outlook on the web to reply a partner email through mutual TLS in Exchange Server 2019 and 2016 4488396 Can’t search any results in manually added shared mailbox in Outlook in Exchange Server 2019 and 2016 4488078 Public folder contact lists don’t show contact’s profile picture in Outlook on the web in Exchange Server 2019 and 2016 4499503 Heavy organizational forms traffic because of materialized restriction when organization forms library has more than 500 items in Exchange Server 2019 and 2016 4503027 Description of the security update for Microsoft Exchange Server 2019 and 2016: June 11, 2019

  19. i-away
    This cumulative update is a security update. It includes fixes for nonsecurity issues and all previously released fixes for security and nonsecurity issues.

    Issues that this cumulative update fixes
    4502134 Can’t get all the emails when searching mailbox by using an end date that’s different from today in Exchange Server 2019 4502135 Correct the error message that you receive when installing Exchange Server 2019 in an organization that has Exchange Server 2010 installed 4502154 Providing information to administrators when auto forward limit is reached in Exchange Server 2019 and 2016 4502155 “The primary SMTP address must be specified when referencing a mailbox” error when you use impersonation in Exchange Server 2019 and 2016 4502156 Audit logs aren’t updated when “-WhatIf” is used as $false in the command in Exchange Server 2019 and 2016 4502157 The Find command not returning the HasAttachments element in Exchange Server 2019 and 2016 4502158 SyncFolderItems contains duplicated ReadFlagChange items in Exchange Server 2019 and 2016 4502131 “TLS negotiation failed with error UnknownCredentials” error after you update TLSCertificateName on Office 365 send connector in Exchange Server 2019 hybrid environment 4502132 Can’t reply to old emails after migration even though old legacyExchangeDN is set to migrated mailbox in Exchange Server 2019 and 2016 4502136 The response of FETCH (BODYSTRUCTURE) command of IMAP violates RFC 3501 in Exchange Server 2019 and 2016 4502140 Can’t preview an eDiscovery search when there are multiple domains in Exchange Server 2019 and 2016 4502141 Appointment that’s created by responding to an email message doesn’t show in any Outlook calendar views in Exchange Server 2019 and Exchange Server 2016 4502133 Can’t use Outlook on the web to reply a partner email through mutual TLS in Exchange Server 2019 and 2016 4488396 Can’t search any results in manually added shared mailbox in Outlook in Exchange Server 2019 and 2016 4488078 Public folder contact lists don’t show contact’s profile picture in Outlook on the web in Exchange Server 2019 and 2016 4499503 Heavy organizational forms traffic because of materialized restriction when organization forms library has more than 500 items in Exchange Server 2019 and 2016 4503027 Description of the security update for Microsoft Exchange Server 2019 and 2016: June 11, 2019
  20. i-away
    This cumulative update is a security update. It includes fixes for nonsecurity issues and all previously released fixes for security and nonsecurity issues.

    Issues that this cumulative update fixes
    4502134 Can’t get all the emails when searching mailbox by using an end date that’s different from today in Exchange Server 2019 4502135 Correct the error message that you receive when installing Exchange Server 2019 in an organization that has Exchange Server 2010 installed 4502154 Providing information to administrators when auto forward limit is reached in Exchange Server 2019 and 2016 4502155 “The primary SMTP address must be specified when referencing a mailbox” error when you use impersonation in Exchange Server 2019 and 2016 4502156 Audit logs aren’t updated when “-WhatIf” is used as $false in the command in Exchange Server 2019 and 2016 4502157 The Find command not returning the HasAttachments element in Exchange Server 2019 and 2016 4502158 SyncFolderItems contains duplicated ReadFlagChange items in Exchange Server 2019 and 2016 4502131 “TLS negotiation failed with error UnknownCredentials” error after you update TLSCertificateName on Office 365 send connector in Exchange Server 2019 hybrid environment 4502132 Can’t reply to old emails after migration even though old legacyExchangeDN is set to migrated mailbox in Exchange Server 2019 and 2016 4502136 The response of FETCH (BODYSTRUCTURE) command of IMAP violates RFC 3501 in Exchange Server 2019 and 2016 4502140 Can’t preview an eDiscovery search when there are multiple domains in Exchange Server 2019 and 2016 4502141 Appointment that’s created by responding to an email message doesn’t show in any Outlook calendar views in Exchange Server 2019 and Exchange Server 2016 4502133 Can’t use Outlook on the web to reply a partner email through mutual TLS in Exchange Server 2019 and 2016 4488396 Can’t search any results in manually added shared mailbox in Outlook in Exchange Server 2019 and 2016 4488078 Public folder contact lists don’t show contact’s profile picture in Outlook on the web in Exchange Server 2019 and 2016 4499503 Heavy organizational forms traffic because of materialized restriction when organization forms library has more than 500 items in Exchange Server 2019 and 2016 4503027 Description of the security update for Microsoft Exchange Server 2019 and 2016: June 11, 2019
  21. i-away
    This cumulative update includes fixes for nonsecurity issues and all previously released fixes for security and nonsecurity issues.

    Known issues
    The Set-SendConnector cmdlet does not work for Exchange Server 2013 in hybrid scenarios that have a Edge server installed. For more information, see KB 4523519.
    Issues that this cumulative update fixes
    This cumulative update fixes the issues that are described in the following Microsoft Knowledge Base articles:
    4502131 “TLS negotiation failed with error UnknownCredentials” error after updating TLSCertificateName on Office 365 send connector in Exchange Server 2013 hybrid environment
    4503028 Description of the security update for Microsoft Exchange Server 2013 and 2010: June 11, 2019


  22. i-away
    This cumulative update includes fixes for nonsecurity issues and all previously released fixes for security and nonsecurity issues.

    Known issues
    The Set-SendConnector cmdlet does not work for Exchange Server 2013 in hybrid scenarios that have a Edge server installed. For more information, see KB 4523519.
    Issues that this cumulative update fixes
    This cumulative update fixes the issues that are described in the following Microsoft Knowledge Base articles:
    4502131 “TLS negotiation failed with error UnknownCredentials” error after updating TLSCertificateName on Office 365 send connector in Exchange Server 2013 hybrid environment
    4503028 Description of the security update for Microsoft Exchange Server 2013 and 2010: June 11, 2019
  23. i-away
    This cumulative update includes fixes for nonsecurity issues and all previously released fixes for security and nonsecurity issues.

    Known issues
    The Set-SendConnector cmdlet does not work for Exchange Server 2013 in hybrid scenarios that have a Edge server installed. For more information, see KB 4523519.
    Issues that this cumulative update fixes
    This cumulative update fixes the issues that are described in the following Microsoft Knowledge Base articles:
    4502131 “TLS negotiation failed with error UnknownCredentials” error after updating TLSCertificateName on Office 365 send connector in Exchange Server 2013 hybrid environment
    4503028 Description of the security update for Microsoft Exchange Server 2013 and 2010: June 11, 2019
  24. i-away
    This cumulative update is a security update. It includes fixes for nonsecurity issues and all previously released fixes for security and nonsecurity issues.

    Known issues in this cumulative update
    In multidomain Active Directory forests in which Exchange is installed or has been prepared previously by using the /PrepareDomain option in Setup, this action must be completed after the /PrepareAD command for this cumulative update has been completed and the changes are replicated to all domains. Setup will try to run the /PrepareAD command during the first server installation. Installation will finish only if the user who initiated Setup has the appropriate permissions.
    Notes:If you are upgrading from Cumulative Update 2 for Exchange Server 2019 to Cumulative Update 3 for Exchange Server 2019, then there’s no need to run the /PrepareAD or /PrepareDomain. No additional actions (prepareAD, prepareDomain, or assigning permissions) are required. If you has ever skipped a Cumulative Update (for example, you are upgrading from an earlier version before Cumulative Update 2 for Exchange Server 2019), or this is a first Exchange Server installation in the AD, then this Known Issue section should be taken care of.

    a. About the /PrepareDomain operation in multidomain:

    The /PrepareDomain operation automatically runs in the Active Directory domain in which the /PrepareAD commandis run. However, it may be unable to update other domains in the forest. Therefore, a domain administrator should run the /PrepareDomain in other domains in the forest.

    b. About the permission question:

    As the /PrepareAD is triggered in Setup, if the user who initiates Setup isn’t a member of Schema Admins and Enterprise Admins, the readiness check will fail and you receive the following error messages:


    To avoid the error messages, either the user should join Schema Admins and Enterprise Admins groups, or another user in Schema Admins and Enterprise Admins groups manually runs the /PrepareAD for this Cumulative Update first. Then the Exchange admin user can start Setup. The Set-SendConnector cmdlet does not work for Exchange Server 2019 in hybrid scenarios that have a Edge server installed. For more information, see KB 4523519.  Autodiscover Event ID 1 after installing Cumulative Update 3 for Exchange Server 2019. For more information, see KB 4532190. Issues that this cumulative update fixes
    This cumulative update also fixes the issues that are described in the following Microsoft Knowledge Base articles:
    4515257 Hash mismatch is reported for Exchange DLLs in the bin directory of Exchange Server 2019 4513500 Can’t sign in to OWA or EAC after you install Exchange Server 2019 CU2 with AD FS 4502159 Adding or removing mailbox permission in EAC doesn’t address the msExchDelegateListLink attribute in Exchange Server 2019 and 2016 4515276 Room mailbox accepts a meeting as “Free” if a booking delegate is set in Exchange Server 2019 and 2016 4515275 Enable Get/Restore-RecoverableItems to work with Purges folder in Exchange Server 2019 and 2016 4515274 AutodiscoverV2 request returns REST API endpoint not AutoDiscoverV1 endpoint in Exchange Server 2019 and 2016 4515269 SentToMemberOf shows every recipient type not distribution groups when you create transport rule in Exchange Server 2019 and 2016 4515272 Message is blocked in “SMTP Delivery to Mailbox” queue if exchange server is added in groups of a child domain in Exchange Server 2019 and 2016 4515271 Can’t convert a migrated remote user mailbox to shared in Exchange Server 2019 and 2016 4515270 SubmissionQueueLengthMonitor shows “System.ArgumentException: Transition timeout…” in Exchange Server 2019 and 2016 4515267 NDR occurs when you resend message from alternate journaling mailbox to journaling mailbox in Exchange Server 2019 and 2016 4515265 Removing In-Place Hold doesn’t work for mailboxes in different domains in Exchange Server 2019 and 2016 4515264 FindPeople request from Skype for Business on Mac fails with “Invalid Shape Specification” in Exchange Server 2019 and 2016 4515263 Hide the “Validate-MailFlowThroughFrontDoor” command for Exchange Server 2019 and 2016 4515262 Enable Remove-MobileDevice to delete mobile devices after migrating to Office 365 from Exchange Server 2019 and 2016 4515261 Can’t copy eDiscovery search results for mailboxes with Exchange online archives in Office 365 in Exchange Server 2019 and 2016 4515273 Mailbox auditing fails when using SHA1Managed in Exchange Server 2019 and 2016 4515266 Infinite loop in Recurrence.GetNumberOfYearsBetween() with the Japanese calendar in Exchange Server 2019 and 2016 4520319 S/MIME signed reply draft behaves like the first message in conversation in Exchange Server 2019 and 2016 4515832 Description of the security update for Microsoft Exchange Server 2019 and 2016: September 10, 2019

  25. i-away
    This cumulative update is a security update. It includes fixes for nonsecurity issues and all previously released fixes for security and nonsecurity issues.

    Known issues in this cumulative update
    In multidomain Active Directory forests in which Exchange is installed or has been prepared previously by using the /PrepareDomain option in Setup, this action must be completed after the /PrepareAD command for this cumulative update has been completed and the changes are replicated to all domains. Setup will try to run the /PrepareAD command during the first server installation. Installation will finish only if the user who initiated Setup has the appropriate permissions.
    Notes:If you are upgrading from Cumulative Update 2 for Exchange Server 2019 to Cumulative Update 3 for Exchange Server 2019, then there’s no need to run the /PrepareAD or /PrepareDomain. No additional actions (prepareAD, prepareDomain, or assigning permissions) are required. If you has ever skipped a Cumulative Update (for example, you are upgrading from an earlier version before Cumulative Update 2 for Exchange Server 2019), or this is a first Exchange Server installation in the AD, then this Known Issue section should be taken care of.

    a. About the /PrepareDomain operation in multidomain:

    The /PrepareDomain operation automatically runs in the Active Directory domain in which the /PrepareAD commandis run. However, it may be unable to update other domains in the forest. Therefore, a domain administrator should run the /PrepareDomain in other domains in the forest.

    b. About the permission question:

    As the /PrepareAD is triggered in Setup, if the user who initiates Setup isn’t a member of Schema Admins and Enterprise Admins, the readiness check will fail and you receive the following error messages:


    To avoid the error messages, either the user should join Schema Admins and Enterprise Admins groups, or another user in Schema Admins and Enterprise Admins groups manually runs the /PrepareAD for this Cumulative Update first. Then the Exchange admin user can start Setup. The Set-SendConnector cmdlet does not work for Exchange Server 2019 in hybrid scenarios that have a Edge server installed. For more information, see KB 4523519.  Autodiscover Event ID 1 after installing Cumulative Update 3 for Exchange Server 2019. For more information, see KB 4532190. Issues that this cumulative update fixes
    This cumulative update also fixes the issues that are described in the following Microsoft Knowledge Base articles:
    4515257 Hash mismatch is reported for Exchange DLLs in the bin directory of Exchange Server 2019 4513500 Can’t sign in to OWA or EAC after you install Exchange Server 2019 CU2 with AD FS 4502159 Adding or removing mailbox permission in EAC doesn’t address the msExchDelegateListLink attribute in Exchange Server 2019 and 2016 4515276 Room mailbox accepts a meeting as “Free” if a booking delegate is set in Exchange Server 2019 and 2016 4515275 Enable Get/Restore-RecoverableItems to work with Purges folder in Exchange Server 2019 and 2016 4515274 AutodiscoverV2 request returns REST API endpoint not AutoDiscoverV1 endpoint in Exchange Server 2019 and 2016 4515269 SentToMemberOf shows every recipient type not distribution groups when you create transport rule in Exchange Server 2019 and 2016 4515272 Message is blocked in “SMTP Delivery to Mailbox” queue if exchange server is added in groups of a child domain in Exchange Server 2019 and 2016 4515271 Can’t convert a migrated remote user mailbox to shared in Exchange Server 2019 and 2016 4515270 SubmissionQueueLengthMonitor shows “System.ArgumentException: Transition timeout…” in Exchange Server 2019 and 2016 4515267 NDR occurs when you resend message from alternate journaling mailbox to journaling mailbox in Exchange Server 2019 and 2016 4515265 Removing In-Place Hold doesn’t work for mailboxes in different domains in Exchange Server 2019 and 2016 4515264 FindPeople request from Skype for Business on Mac fails with “Invalid Shape Specification” in Exchange Server 2019 and 2016 4515263 Hide the “Validate-MailFlowThroughFrontDoor” command for Exchange Server 2019 and 2016 4515262 Enable Remove-MobileDevice to delete mobile devices after migrating to Office 365 from Exchange Server 2019 and 2016 4515261 Can’t copy eDiscovery search results for mailboxes with Exchange online archives in Office 365 in Exchange Server 2019 and 2016 4515273 Mailbox auditing fails when using SHA1Managed in Exchange Server 2019 and 2016 4515266 Infinite loop in Recurrence.GetNumberOfYearsBetween() with the Japanese calendar in Exchange Server 2019 and 2016 4520319 S/MIME signed reply draft behaves like the first message in conversation in Exchange Server 2019 and 2016 4515832 Description of the security update for Microsoft Exchange Server 2019 and 2016: September 10, 2019
×
×
  • Create New...