Jump to content

Catastrophic Failure

Members
 View Profile  See their activity

  • Posts

    562

  • Joined

  • Last visited

 Content Type 

Blog Entries posted by Catastrophic Failure

  2. Catastrophic Failure
    The most of you start wander “Where is the EMC (Exchange Management
    Console) in Exchange Server 2013?” Well, some things remain the same as login
    in the new Exchange Server 2013, and other things change (this is the
    technology). Let’s see together which are the things are new in Exchange Server
    2013, one of those is the EMC (Exchange Management Console).
    Where
    is the EMC (Exchange Management Console) and how where we can find it?
    Almost everything in new Exchange 2013 is web-based management console, not EMC
    (Exchange Management Console) but EAC (Exchange Administration Center), that
    allows for ease of use and is optimized for on-premises, online, or hybrid
    Exchange deployments. The EAC replaces the Exchange Management Console (EMC)
    and the Exchange Control Panel (ECP), which were the two interfaces that were
    used to manage Exchange Server 2010. One of the advantages of having the
    web-based EAC is that you can partition access from the Internet/Intranet from
    within the ECP IIS virtual directory to allow or disallow management features.
    This allows you to permit or deny access to users trying to access the EAC from
    the Internet outside of your organizational environment, while still allowing
    access to an end-user’s Outlook Web App Options.
    How can I login to EAC?
    If we navigate to IE (Internet Explorer) and type http://server
    FQDN/ecp (in my scenario is https://e2013.cloud.com/ecp

    and voila, you are now logged in the new EAC old EMC console..

    Supported browsers
    For the best experience with the EAC, use one of the operating system and browser combinations labeled “Premium”.
    Premium: All functional features are well-supported and fully tested. Supported: Has same functional feature support as premium; however, supported browsers will be missing features that the browser and operating system combination doesn’t support. Unsupported: The browser and operating system isn’t supported or tested. Be in tune...
  3. Catastrophic Failure
    As we mention in Part1, Exchange Server 2013 has 2 server roles, Mailbox Server role and Client Access Server role. We have the option to install either single server role or both the roles on the same computer.
    In any case of installation role, CAS Role or both servers roles (CAS and Mailbox), Exchange Management Tools will be
    installed together.
    After you extract the Exchange-x64.exe file, start the exchange 2013 installation by click on the setup file available on the installation file. Below window appears up, check the option “Connect to the Internet and check for Updates” and click next to
    continue.

    On the Introduction page, read the information and click next to continue. If you plan
    to use to Deployment assistant click on the necessary option.

    Accept on the License Agreement page and click Next to continue

    On the Error Reporting Window, Click Yes and Click Next to continue

    Next step will automatically check for the required software if is installed in the Server, if any issue appear, it will prompt you to fix it. If no error click Next to Continue

    On the Server Role Selection Windows, if it is standalone installation select both the Mailbox and Client Access Server role and click Next to continue

    Installation Space and Location windows will allow an option to change the installation path, make necessary change or leave the default path and click Next

    Type the Exchange Organization name and click Next

    Malware Protection Setting, this option is new in Exchange 2013 which will by default scan all the emails, if you are using other option disable the option and click Next to continue

    If this Exchange 2013 server is an internet facing client access server then check the option and enter the internet domain name. If not leave it as it is and click Next to continue.

    On the Customer Experience Improvement Program, read the information, choose the required option and click Next to continue.

    Readiness check windows will check of the all the options prior to install the Exchange
    Server 2013. If everything is normal, then the installation will start.

    Once the readiness check is completed Exchange Server 2013 installation will happen. Once it is completed, click finish is complete the installation.

    Enjoy..
  4. Catastrophic Failure
    Γι’ αυτούς που αγαπούν το διάβασμα, την γνώση και την αγάπη τους γι’ αυτό που κάνουν, στους ακόλουθους συνδέσμους θα βρουν διάφορα Developer's Guides και Training Kit from Microsoft..

    Developing an Advanced Windows Phone 7.5 App that Connects to the Cloud


    Developing Applications for the Cloud, 2nd Edition


    Building Hybrid Applications in the Cloud on Windows Azure


    Building Elastic and Resilient Cloud Applications - Developer's Guide to the Enterprise Library 5.0 Integration Pack for Windows Azure


    Technical reference for Microsoft SharePoint Server 2010


    Getting started with Microsoft SharePoint Foundation 2010


    Deployment guide for SharePoint 2013 Preview


    Deployment guide for Duet Enterprise for Microsoft SharePoint and SAP Server 2.0 Preview
     

    Microsoft Dynamics GP 2010 Guides: Financials


    Microsoft Dynamics CRM 2011 User's Guide


    Dynamics CRM 2011 Developer Training Kit


    Microsoft Dynamics CRM 2011 Implementation Guide


    Deployment guide for Office 2013 Preview


    Office 2010 Developer Training Kit


    Office 365 Developer Training Kit


    Office 365 Guides for professionals and small businesses

    Lync for Mac 2011 Deployment Guide


    Microsoft Lync Server 2010 Resource Kit Tools


    Microsoft Lync Server 2010 Resource Kit


    Microsoft Lync Server 2010 Security Guide


    Microsoft Lync Server 2010 Security Guide

    Visual Studio LightSwitch Training Kit


    SQL Server 2012 Developer Training Kit

    "Own Your Space--Keep Yourself and Your Stuff Safe Online" Digital Book for Teens
  5. Catastrophic Failure
    Last month we released the Outlook Configuration Analyzer Tool (OCAT) on the Microsoft Download Center site.
    OCAT was developed by two Microsoft support engineers with over 30 years of combined experience in Outlook, Exchange and Office support. Based on their support experience, they compiled a set of detection rules that look for Outlook configurations that have historically been potential sources of problems in Outlook. The tool looks and feels like Microsoft Exchange Best Practices Analyzer (ExBPA) - the same infrastructure used by ExBPA was chosen for the development and final implementation of OCAT.

    Figure 1: Microsoft Outlook Configuration Analyzer Tool (OCAT)
    You can use OCAT to check Outlook configuration on your users' computers and look for known issues (for example, a PST file located on a network share). We recommend running it if you suspect a user's Outlook profile or configuration to be a part of the problem. You can also run the tool proactively to detect Outlook configuration issues. The tool allows you to:
    Run a scan on your computer Open a previously run scan on your computer Import a scan from another computer Use several reporting formats to view the scan results Start the Exchange Remote Connectivity Analyzer tool Send feedback to the OCAT team We're working on an updated version of OCAT that includes new functionality such as automatic downloading of new detection rules, scanning calendar items (using code from the new CalCheck tool) and offline scanning for Outlook 2003 clients. Since OCAT utilizes MrMapi to collect a few configuration settings, we are also working with its developer (another Microsoft support engineer) to improve data collection capabilities in OCAT.
    You can follow the OCAT team on Twitter to receive news of OCAT updates.
    System requirements
    Before you install OCAT, make sure that your computer meets the following OCAT system requirements:
    Supported operating systems: Windows 7 Windows Vista Service Pack 2 Windows XP Service Pack 3 OCAT requires Microsoft Outlook. The following versions of Outlook are supported: Microsoft Office Outlook 2007 Microsoft Outlook 2010 (32-bit or 64-bit) Microsoft .NET Framework Version 2.0 or higher .NET Programmability Support (as part of your Microsoft Office installation) Note Outlook 2003 is not a supported version of Outlook with the OCAT tool. If you try to perform a scan on a client that has Outlook 2003 installed, you receive the following error message:
    Error starting scan, please try again. If error persists, please send mail to ocatsupp @ microsoft DOT com.
    You can also download a complete OCAT user guide from the download page. We highly recommend that you read this document before installing and using OCAT. See OCAT Supplemental Information.
    OCAT Functionality overview
    Here's an overview of the functionality provided by OCAT.
    Generating an OCAT scan report
    To generate an OCAT report for your Outlook profile, simply click Start a scan in the left panel.
    Be aware that you must make sure that Outlook is running before you start an OCAT scan.

    Figure 2: Starting an OCAT scan
    If you can't keep Outlook running long enough to start an OCAT scan, you can still perform a basic scan. To do this, in the Task drop-down list, select Offline Scan and then click Start scanning.

    Figure 3:Starting an offline scan
    The report that an offline scan generates contains only information that's available on your computer, such as registry data, Application event log details, a list of installed updates and local file details. Although an offline scan doesn't contain as many profile details as an online scan, it may still provide enough information to help you resolve any problems that you are experiencing with Outlook.
    Viewing your scan report
    The report that OCAT generates can, in most cases, provide a lot of information about your Outlook profile and show you known problems in your profile with links to relevant Knowledge Base articles.
    List Reports The List Reports view is the default presentation of your scan data.

    In the List Reports view, there are up to three tabs that are available to view different snapshots of this data: 1) Informational Items 2) All Issues and 3) Critical Issues
    Tree Reports The Tree Reports view of your scan report provides tree-control functionality to view your scan results.

    In the tree report view, two tabs are available to view different snapshots of this data: 1) Detailed View and 2) Summary View
    How to view a report that was created on another computer
    You can view an OCAT scan report generated on another computer.
    Start OCAT on the user's machine. In the left panel, click Select a Configuration scan to view and then select the scan you want to view from the list of available scans. Click Export this scan. In the Export this scan dialog box, specify a file name and a folder location. Copy the XML file that you saved in step 5 to the computer from which you want to view the report. On the computer to which you copied the file in step 6, start OCAT. On the Welcome page, click Select a Configuration scan to view. On the Select a Configuration scan to view page, click Import scan. Browse to the folder that contains the XML file that you copied in step 6, and then click Open. The scan is opened automatically for viewing.
    OCAT download Documentation download Source: MSExchange Team

  6. Catastrophic Failure
    Part 2 of this series (Part 1 is here) breaks down the events that take place during the backup of a mounted and active replicated database in an Exchange 2010 Database Availability Group called, simply enough, “DAG”. In this example the backup server is asked to create a full backup of database DB1 on server ADA-MBX1, using non-persistent COW snapshots:
    (please click thumbnails for full size version of graphics in this post)

    Event 9606 indicates that the VSS requestor has engaged the Exchange writer, and reports the instance GUID for the backup job that is starting. In this case the instance is 830705de-32d9-4059-94ea-b9e9aad38615. This instance GUID persists throughout each job, and changes with each subsequent one. You can therefore use it to track the sequence of events for each individual job. At this time that the Exchange Writer provides metadata about the databases and logs present to the backup application.

    Events 2005 and 9811 indicate an instance number assignment for ESE. So along with the writer instance GUID event 9606 we can also track a job’s progress using these ESE instance numbers which increment by one with each job. At this stage the database is marked with “backup in progress” in the Information Store Service's memory space.

    Just after the backup application has determined which disks need snapshots created, based on the data locations provided by the Exchange Writer metadata, it goes ahead and requests those snapshots. As the snapshot requests arrive event 9608 gets generated, indicating the Exchange writer’s acknowledgment of what’s about to happen. It then must halt disk writes to the database(s) and logs, also known as a “freeze” for the duration of the snapshot generation process.
    When event 2001 is logged the current transaction log is closed, and the freeze begins. Writes from STORE.exe to the disks are held in memory.

    Once these events appear we know the snapshot(s) have been created, and writes are allowed to database data blocks again.

    Once the snapshots are created the backup application can copy blocks of data from the VSS subsystem, getting blocks of data from shadow storage if they’ve been preserved due to a change, or from the actual disk volume if they haven’t. The Exchange Writer waits for the signal that the transfer of data is complete. This flow of data is represented by the purple arrows, which in this case indicates data getting copied out of the snapshots in storage, through I/O of the Exchange server, and on to the backup server.

    Once the backup application finishes copying data it will signal VSS that it’s done. VSS in turn signals the Exchange writer, which then initiates post-backup steps, signified by the above events. Event 225 appears to state that log truncation won’t occur, but that event is misleading. For a standalone database, upon backup completion, ESE would go ahead and clear logs accordingly. However, when a DAG replicated database is involved a check of other database copies must be performed in coordination with the Exchange Replication Service to ensure log truncation can continue. Once that check is complete the logs eligible for truncation are deleted. The database header is marked with information about the backup and the backup in progress bit is switched off in memory. In this case the snapshots used for the job are destroyed as part of the completion. In other types of backups, such as incremental, the persistence of the snapshot varies, but in this case they are removed.
    In the next post in this series we'll look next at breaking down the backup of a passive DAG replicated database copy.
    Source: MSExchange Team
  7. Catastrophic Failure
    If you find the inner workings of Exchange data backups using Volume Shadown Copy (VSS) a bit mystifying take comfort in not being alone. Administrators may ask, “What’s all the “freezing” and “thawing” I’m seeing in my event logs? What is the Exchange VSS Writer really, and what is it doing to my databases? How does it create a snapshot of a 135GB database in less than 60 seconds?”
    If you ever asked these questions but only felt more confused with the answers, here’s a guide to clear some of that up. To understand how a VSS backup of Exchange works it’s critical to understand the basics of VSS itself. There is some excellent documentation on TechNet and MSDN on this, as well as the Windows Server Core Team blog, “Ask the Core Team.” My esteemed colleague Randy Monteleone sums up the basics of VSS very nicely early in his post, while also providing links (repeated here) to some good TechNet primers on VSS:
    How To: VSS Tracing – Randy Monteleone
    http://blogs.technet.com/b/askcore/archive/2012/04/29/how-to-vss-tracing.aspx
    How Volume Shadow Copy Service Works
    http://technet.microsoft.com/en-us/library/cc785914(WS.10).aspx
    Volume Shadow Copy Service
    http://technet.microsoft.com/en-us/library/ee923636.aspx
    If you’re already familiar with at least the basics of VSS, then look forward to Part 2 in this series, where we will break down the events that occur in a VSS Exchange backup, and how Exchange logs them in the application event log.
    If you need a quick primer or refresher on VSS basics and the Exchange Writer I’ve condensed them into some visual points below to complement the references above.
    Snapshots
    Bear in mind that VSS solutions for Exchange, and for all applications, vary greatly between different hardware and software configurations. There are clone and COW snapshots, hardware and software solutions, just a very wide variety of technologies based on the core VSS subsystem. For the purposes of understanding Exchange backups we’re only going to illustrate one specific type of solution out of the multitude. Detailed below is what’s called “copy-on-write”, or “COW” snapshots.
    In a COW snapshot-based VSS backup of Exchange we have the creation of snapshots of the disks where Exchange data is hosted. No matter what is getting backed up, even if it’s a single database file and a few logs, VSS creates a snapshot of the entire disk where any data is stored. If the data resides across multiple disks, such as when an Exchange database is on one disk, and the logs are on another, VSS will create snapshots of any and all of those disks.
    So what is a “snapshot”? A volume snapshot is an area of space inside what’s called “shadow storage”, which is itself a typically small area of space on the disk located in its System Volume Information folder.
    After a disk snapshot is created a change to any data block from that time forward cannot get written until a copy of that block’s data before the change (as it was when the snapshot was created) gets written to the differencing area in shadow storage. In this way the data on the disk at the time the snapshot was created is preserved, block by block, in the shadow storage area. The snapshot data is then available either from the original disk, if the data blocks requested haven’t changed, or from the differencing area if they have. The fundamentals of this are illustrated below:
    Disk E: has a snapshot created at 1PM:

    A minute later one of the blocks gets written to, but not before the data as it was at 1PM gets preserved in the differencing area:

    As the actual disk changes the data as it was at 1PM gets written into shadow storage, preserving a record of the disk as it was in that moment:

    The following step:

    In the figure above a backup server requests data from the snapshot of blocks 2 and 53. Block 53 from 1PM is preserved in the snapshot, so it’s copied directly from shadow storage. Block 2 is unchanged since 1PM, so it is copied via the VSS driver VOLSNAP.SYS, which operates much like a filter driver underneath the NTFS.SYS file system driver. By working in the IRP stack (the part of kernel memory that manages disk I/O) underneath the file system it can read blocks of data without NTFS objecting that a file is in use. VOLSNAP.SYS is also responsible for ensuring blocks are copied over to shadow storage if a write is requested to them, hence the name “Copy On Write”. Here is more about VOLSNAP.SYS from Tim McMichael:
    Exchange / VSS / and differential block size…
    http://blogs.technet.com/b/timmcmic/archive/2011/07/12/exchange-vss-and-differential-block-size.aspx
    Now that we’ve got the basics of a COW snapshot down let’s look at how it works with Exchange, along with some other major concepts:
    Microsoft Exchange Writer
    So we know that any disk that stores Exchange data gets a snapshot created of it by VSS. How exactly, though, does a backup application find out which disks those are? Oftentimes an administrator selects databases for backup without specifying anything about what disks their data files are stored in. So something is required to provide the information about where the data files are, and therefore what disks VSS needs to create snapshots of. This information also tells a backup application, also known as a VSS requestor, what specific data files should be copied out of the snapshots for preservation on backup media, as we don’t want to copy out anything from the disk we don't need.
    The mechanism at work here is the Microsoft Exchange VSS Writer. Like any application’s VSS writer (there are many, just run VSSADMIN LIST WRITERS to see them) its first job is to tell the backup application about the data needed for backup, especially the EDB file, logs, and checkpoint file for each database requested. The information about these specific Exchange data files is known as writer metadata.

    (click thumbnail for full size version)
    In the figure above we see the initial steps of an Exchange backup. The Exchange Writer tells the backup server (the requestor) that there is a database located in a folder on volume E:, and that transaction logs for that database are in a folder on D:. Based on that information the backup application will request snapshots of the D: and E: volumes when the job progresses.
    The Exchange VSS Writer serves another critical role besides providing metadata to VSS requestors. It also has the job of stopping writes to the databases and logs on disk, or “freezing” them, for the time it takes to create the necessary snapshots. A COW snapshot typically takes a small amount of time to create, as all it consists of initially is the designation of an area in shadow storage for blocks to be preserved in when they change on the actual disk. Despite this relatively quick operation it can still take up to a minute, which is plenty of time for blocks of data to change on a disk between the start and the end of its snapshot creation process. If blocks of data change but don't have the originals preserved from the exact time the snapshot creation begins those blocks may become inconsistent with other snapshot data, especially between logs, database, and checkpoint files. Hence, the Exchange Writer prevents the Information Store Service, or the MS Exchange Replication Service, from writing what’s in RAM to the frozen database files. In the case of the Information Store Service, the current transaction log file (Exx.log) gets rolled and closed out before the Exchange Writer allows VSS to take the snapshot. This ensures nothing changes in the file data between the beginning of the snapshot and the completion, at which point the databases are “thawed”. When databases are thawed write I/O held in RAM is allowed to go to disk again.
    Here's more information on how an application's VSS writer interacts with VSS with regards to freeze, thaws, and the time needed to get a snapshot completed:
    CVssWriter::OnFreeze method
    http://msdn.microsoft.com/en-us/library/windows/desktop/aa381563(v=vs.85).aspx
    The last major responsibility of the Exchange Writer is to tell the Information Store Service (MS Exchange Replication Service in the case of a passive copy backup) that the backup was completed and, if applicable, carry out post-backup tasks like log truncation, marking the database as no longer with a backup in progress, etc.
    In the part two and part three of this series we’ll look at a play-by-play breakdown of how the elements described above all come together in an Exchange backup, the application log events that get generated, and compare the process for a mounted database to that for a passive database copy.
    Thanks go out for the collaboration on the content in these posts to Michael Blanton, Tim McMichael, Randy Monteleone, Dave Vespa, and Tom Kern.
     
    Source: MSExchangeTeam
  8. Catastrophic Failure
    Wanted to write a quick post about a tool that can help you find and catalogue various PowerShell scripts that are scattered on various online communities or – possibly – your internal company network shares.
    The tool is called Microsoft Script Explorer for Windows PowerShell and has entered the public Beta 1 stage now.
    Download Microsoft Script Explorer for Windows PowerShell (pre-release) User guide Script Explorer Forum Just to give you a taste of how it looks…

    You can search scripts by category, with keywords or various other options. You can also dive directly into categories, which allows you to see scripts by product.
     
    Source: Nino Bilic
  9. Catastrophic Failure
    Exchange CXP team released Update Rollup 6 for Exchange Server 2007 SP3 to the Download Center.
    This update contains a number of customer-reported and internally found issues since the release of RU5. See KB 2608656: Description of Update Rollup 6 for Exchange Server 2007 Service Pack 3' for more details.
    We would like to specifically call out the following fixes which are included in this release:
    DST Cadence Release for Dec 2011 - Exchange 2007 22656040 An Exchange Server 2007 Client Access server may respond slowly or stop responding when users try to synchronize the Exchange ActiveSync devices with their mailboxes 2498852 "0x80041606" error message when you perform a prefix search by using Outlook in online mode in an Exchange Server 2007 environment 22653334 The reseed process is unsuccessful on the SCR passive node when the circular logging feature is enabled in an Exchange Server 2007 environment 22617784 Journal reports are expired or lost when the Microsoft Exchange Transport service is restarted in an Exchange Server 2007 environment 2289607 The week numbers displayed in OWA do not match the week numbers displayed in Outlook for English users and French users in an Exchange Server 2007 environment
    Important:
    Before proceed with Update Rollup 6 for Exchange 2007 Service Pack 3 installation on physical machine, proceed to install it first on a Lab for test reasons.
     
    Source: MSExchange Team
  10. Catastrophic Failure
    Happy New Year 2012 to everyone….
    In this Post, will see the step by step installation of Exchange 2010 SP2 and highlighting few things that you should know before installing Exchange Server 2010 SP2 in your production. First thing is to Test it in lab environment before installing in production environment.
    What you must know before installing Exchange 2010 SP2:
    SP2 includes schema changes
    With certain new features, Exchange 2010 SP2 updates the schema. To understand what changes happen when you run Exchange 2010 SP2 read the Exchange Server Active Directory Schema Changes Reference, November 2011
    Since, the installer will be requiring modifications to Schema, user account used for installation of SP2 must be a member of Schema Admins group in active directory. As a best practice, make sure that this user account is removed from the group once the schema extension is complete.
    Windows Server Features are required for CAS Role
    In Exchange Server 2010 CAS is the primary entry point for clients to any Exchange Server 2010 Environment. With this release, a few more features are added in the CAS server role which makes on premise and Office 365 integration a better experience and also an improvement that makes the silent redirection better within cross site CAS roles. A new feature called Mini Outlook Web App now exists that works on no cookies, no scripts model.
    Below are Windows Server Role Features that you need to install before installing SP2 on CAS Role.
    IIS 6 WMI Compatibility ASP.NET ISAPI Filters Client Certificate Mapping Authentication Directory Browsing HTTP Errors HTTP Logging HTTP Redirection Tracing Request Monitor Static Content


    After we finish with adding Windows Server Role Features which required to proceed with SP2 installation we run Setup.
    1. Go to the folder which you have download from Microsoft site the Exchange 2010 SP2, unzip the Exchange 2010 SP2 package first, then launch setup program.


    2. Follow the wizard, start to install SP2, read through the introduction and click Next button


    3. Read through the license agreement, accept it and click Next button.


    4. Next step Readiness Checks, Setup wizard finished successfully click Install.


    5. Completion and final step is completed successfully, choose Finish.


    6. After the installation is complete, we’ll see the following message, which informs us that we need to reboot the system for changes to take effect.


    7. After reboot we can see that our Exchange Server was installed successfully SP2, Build number 14.2 (Build 247.5)

    Installing Updates on DAG is not a normal exercise
    Many of us run DAG because of its proven reliability and ability to make a highly available mailbox database system. Installing updates on a member of a DAG is not a regular installation though, for that reason please visits the link bellow in case you have DAG and you want to upgrade to SP2.
    Upgrade Exchange 2010 to Exchange 2010 SP1 or Exchange 2010 SP2
    http://technet.microsoft.com/en-us/library/bb629560.aspx

  11. Catastrophic Failure
    Αρχικά να ευχηθώ να έχουμε ένα ευτυχισμένο και δημιουργικό 2012!!
    Για εμένα το 2012 ξεκίνησε πάρα μα πάρα πολύ καλά, για δεύτερη χρονιά μου απονεμήθηκε ο τίτλος του MVP στον Exchange Server. Τα λόγια είναι περιττά σε στιγμές σαν κι αυτές, Ευχαριστώ θερμά όλους εσάς τους ανθρώπους της κοινότητας μας που καθημερινά μας υποστηρίζετε.. Με αυτά σαν εφόδια, θα συνεχίσω το 2012 με περισσότερο ζήλο, αγάπη και προσφορά στην κοινότητα μας.
    Καλή Χρονιά με Υγεία και πολλές επιτυχίες!!!
  13. Catastrophic Failure
    Διαθέσιμο για download το SP2 για τον Exchange Server 2010 στο Download Center της Microsoft.
    Κατεβάστε το Exchange 2010 SP2 εδώ.

    Overview
    Microsoft Exchange Server 2010 SP2 helps IT Professionals achieve new levels of reliability with greater flexibility, enhanced user experiences, and increased protection for business communications.
    Flexible and reliable - Exchange Server 2010 SP2 gives you the flexibility to tailor your deployment based on your company's unique needs and a simplified way to keep e-mail continuously available for your users. Anywhere access - Exchange Server 2010 SP2 helps your users get more done by giving them the freedom to securely access all their communications - e-mail, voice mail, instant messaging, and more - from virtually any platform, Web browser, or device. Protection and compliance - Exchange Server 2010 SP2 delivers integrated information loss prevention, and compliance tools aimed at helping you simplify the process of protecting your company's communications and meeting regulatory requirements. Important: The SP2 sets new pre-requirements to Windows, to install and upgrade from SP1. It requires an additional Windows role, which was not part of the SP1 pre-requirements. Which is: IIS 6 WMI Compatibility not being installed.
    To install this before starting the SP2 install/upgrade, start a PowerShell and run:
    · Import-Module ServerManager
    · Add-WindowsFeature Web-WMI
    This Windows role is required for Mailbox and CAS roles.

  14. Catastrophic Failure
    Στο σημερινό μας post θα δούμε την εγκατάσταση και την ρύθμιση του Exchange 2010 Edge Transport Server ρόλου. O Edge Transport Role στον Exchange Server 2010 παρέχει ένα υψηλό επίπεδο security μεταξύ external και internal επικοινωνίας. Με λίγα λόγια, ο Edge server σαν «φίλτρο» προστασίας της αλληλογραφίας (εσωτερικής και εξωτερικής). Ο Edge role θα πρέπει να εγκατασταθεί σε ξεχωριστό μηχάνημα « server» από τον server που είναι εγκατεστημένοι οι υπόλοιποι ρόλοι του Exchange Server 2010 HT, CAS, ΜΒ.

    Τα προαπαιτούμενα «prerequisites» πριν την εγκατάσταση του Edge Transport Role είναι τα ακόλουθα:
    · OS: Windows Server 2008 x64 SP 2 or Windows Server 2008 R2
    · Microsoft .NET Framework 3.5
    · Windows Remote Management 2.0
    · Windows PowerShell V2
    · Active Directory Lightweight Directory Services (AD LDS)
    Προτού προχωρήσουμε με την εγκατάσταση του Edge Transport Role, αφού έχουμε ήδη ρυθμίσει τον Edge Transport σε DMZ (Demilitarized zone ή αλλιώς perimeter network) θα πρέπει να βεβαιωθούμε ότι το DNS suffix έχει προστεθεί για το “domain. Local”, στην περίπτωση μου είναι “emea.com”.

    Μετά την ρύθμιση του DNS suffix θα σας ζητηθεί να επανεκκινήσετε «reboot» τον server. Εφόσον ξεκινήση server θα προχωρήσουμε σε εγκατάσταση του Edge Role, επιλέγουμε από το DVD του Exchange Server 2010 setup.com (Run as administrator).
    Ο Wizard της εγκατάστασης ξεκινά..

    Step1

    Step2


    Step3
    Θα επιλέξουμε Custom εγκατάσταση για να μπορέσουμε να επιλέξουμε τον Edge Role

    Step4

    Step5
    Η εγκατάσταση συνεχίζετε και το Readiness Checks ολοκληρώνετε, επιλέγουμε Install για να συνεχίσουμε.

    Step6
    Η διαδικασία εγκατάστασης του Edge Role ολοκληρώνεται με επιτυχία και επιλέγουμε Finish για να ολοκληρωθεί.

    Step7
    Μετά από την ολοκλήρωση της εγκατάστασης θα μα ζητηθεί να κάνουμε Restart για να εφαρμοστούν όλες οι αλλαγές.

    Έφτασε η στιγμή να ρυθμίσουμε τον Edge Role να «μιλάει» με τον HUB Role, πάμε λοιπόν να δούμε την διαδικασία. Παραμένουμε στον Edge Server για να μπορέσουμε να δημιουργήσουμε το the Edge Subscription file μέσω της κονσόλας EMS (Exchange Management Shell) Run as administrator.
    Πληκτρολογούμε την εντολή:
    New-EdgeSubscription –Filename “C:\edge.xml”

    Επόμενο βήμα μας είναι να αντιγράψουμε το xml αρχείο που δημιουργήσαμε στον Edge και να το κάνουμε import στον HUB transport server. Στην δική μου περίπτωση έχω έναν Exchange 2010 multi-role server (CAS/HUB/MBX).
    Στον HUB transport server μας θα πάμε να ανοίξουμε την κονσόλα EMC àOrganization Configuration à Hub Transport à Edge Subscriptions και πραγματοποιώντας δεξί κλικ επιλέγουμε New EdgeSubscription.

    Επιλέγουμε το AD Site όπου ο Edge θα πρέπει να γίνει subscribed και επιλέγουμε browse για να κάνουμε import το xml file που δημιουργήσαμε πρωτύτερα.


    Σημείωση: Για να μπορέσουμε με επιτυχία να συγχρονίσουμε τον Edge server «Edgesync» θα πρέπει η πόρτα 50636 (TCP) να είναι ανοιχτεί στον HUB server(s) προς τον Edge server.
    Εξ’ ορισμού ο Edge server ακούει στην πόρτα 50389.
    Μόλις η διαδικασία του subscription ολοκληρωθεί με επιτυχία θα πρέπει να εμφανίζετε όπως στην ακόλουθη εικόνα.

    Είναι ώρα να ξεκινήσουμε τον συγχρονισμό του Edge server Edgesync, την εντολή θα την εκτελέσουμε από τον Hub Server.















    Επιπρόσθετες Πληροφορίες:
    · Exchange port reference
    · Overview of the Edge Transport Server Role


  15. Catastrophic Failure
    Στο σημερινό post θα δούμε την διαδικασία μεταφοράς ενός Exchange Server 2010 mailbox σε διαφορετική βάση (Database). Στον Exchange Server 2010 υπάρχουν δύο διαδικασίες μεταφοράς mailbox:
    Local Move – Η διαδικασία Local μας παρέχει την δυνατότητα μεταφοράς ενός mailbox από μια database σε μια άλλη (στον ίδιο ή διαφορετικό server, με την προϋπόθεση ο server να βρίσκετε στο ίδιο exchange organization). Remote Move - Η διαδικασία Remote μας παρέχει την δυνατότητα μεταφοράς ενός mailbox από μια database σε μια άλλη σε διαφορετικό forest. Σημείωση: Δεν υποστηρίζετε η δυνατότητα μεταφοράς ενός mailbox από Exchange 2000 και 2007 SP1 σε 2010.
    Για να πραγματοποιήσουμε την μεταφορά ενός mailbox από μια database σε μια άλλη στο ίδιο organization ακολουθούμε τα παρακάτω βήματα:
    1. Θα μεταβούμε στην κονσόλα EMC (Exchange Management Console)
    2. Επιλέγουμε Recipient Configuration και Mailboxes
    3. Κάνουμε δεξί κλικ στο mailbox που θέλουμε να μεταφέρουμε και επιλέγουμε “New Local Move Request”.

    Στο επόμενο βήμα θα επιλέξουμε την Database που θέλουμε να μεταφέρουμε το mailbox μας (στο παράδειγμα μας επιλέγουμε την MBDB01).

    Επόμενο βήμα είναι να επιλέξουμε εάν θέλουμε να κάνουμε skip την διαδικασία μεταφοράς του mailbox σε περίπτωση που υπάρχουν κατεστραμμένα messages ή συνεχίζουμε την διαδικασία επιλέγοντας Next.

    Στο επόμενο μας βήμα θα δούμε μία περίληψη του mailbox που προσπαθούμε να μεταφέρουμε. Επιλέγουμε New για να συνεχίσουμε.

    Τελευταίο μας βήμα, η διαδικασία Move Request ολοκληρώνεται και επιλέγουμε Finish.

    Ο Exchange δεν έχει ολοκληρώσει την διαδικασία μεταφορά του mailbox, απλά έλαβε μονάχα το request για μεταφορά. Για να επιβραβεύσουμε το status της μεταφοράς του mailbox, θα πάμε να το δούμε μέσα από την κονσόλα EMC (Exchange Management Console) στην επιλογή Move Request όπου εμφανίζετε η λίστα και το status της μεταφοράς του mailboxes. Όπως θα παρατηρήσετε και στην εικόνα μας, η διαδικασία ολοκληρώθηκε και το status μας λέει Completing.

    Χρήσιμα Link
    Managing Move Requests
    http://technet.microsoft.com/en-us/library/bb124797.aspx

  16. Catastrophic Failure
    Η Microsoft έκανε released το Service Pack 2 (SP2) για τον TMG 2010 Standard και Enterprise editions.

    Το Service Pack 2 περιέχει τις ακόλουθες νέες λειτουργίες:
    New Reports
    • The new Site Activity report displays a report showing the data transfer between users and specific websites for any user.
    Error Pages

    • A new look and feel has been created for error pages.
    • Error pages can be more easily customized and can include embedded objects.
    Kerberos Authentication

    • You can now use Kerberos authentication when you deploy an array using network load balancing (NLB).
    Για να διαβάσετε τα release notes, δείτε εδώ Forefront TMG Release Notes (SP2).
    Για να πραγματοποιήσετε λήψη του Microsoft Forefront Threat Management Gateway (TMG) 2010 Service Pack 2 πατήστε εδώ.
  17. Catastrophic Failure
    Μπορεί να μην πήγαμε στο TechEd Australia 2011 , αλλά φέραμε το TechEd Australia 2011 εδώ με μερικά Exchange Sessions. Αξίζει τον κόπο να τα παρακολουθήσετε…
    Upgrading to Exchange 2010: Notes from Field - In this session Sofiane and Colin will provide notes from the field as they take you on a journey to upgrading your legacy Exchange environment. They will highlight the best practices you should consider as you plan your upgrade from Exchange 2003, Exchange 2007, as well as touch on migrating from alternative messaging platforms. Sofiane and Colin will cover the gotchas and pitfalls you are likely to encounter, and follow through with tips and tricks that experienced ITPros leveraged on a regular basis. Additionally they will look at some of the recommended tools, such as the Exchange Deployment Assistant, that will ensure you have a smooth upgrade to the latest version of Exchange. Converged Exchange: A Blueprint for 2010 deployment - With the myriad of new capabilities in Exchange 2010, organisations are looking to their solutions providers to help them not only deploy the new platform but help them manage it. In this presentation, Tim Jones investigates the challenges faced with moving to 2010, migration options, configuration of Disk Access Groups and archiving solutions. He also discusses how Microsoft and Hitachi Data Systems joint reference architecture delivers Exchange 2010 as a “converged solution in a rack”. Exchange Virtualisation - Is it right for you? - Many production Exchange Server deployments are virtualized. This is to achieve better hardware utilisation, provide operational flexibility or align with data centre deployment standards. As a business critical server application, it’s important to understand the implications of virtualising Exchange Server and ensure that deployments are aligned to Microsoft’s best practices and meet the ever changing business demands of a modern messaging service. This breakout session will cover what has been learned about the best ways to deploy Exchange Server in a virtual environment, the various virtualisation technologies that can impact Exchange Server user experience, and scenarios where virtualisation may not be the best choice. Also the differences between Exchange Server native data protection and the high availability and failover features offered by virtualisation stacks will be examined to help you make informed design decisions. Load Balancing with Microsoft Exchange Server 2010 - Understand the Exchange 2010 requirements for load balancing. Review the pros and cons of current hardware-based load balancing solutions. Discuss the nuances of high-end/high-scale load balancing and the impact to Microsoft Exchange Server 2010. Exchange Server 2010: High Availability Deep Dive - Go beyond the basics of Exchange High Availability and learn what’s really going on under the hood in an Exchange 2010 database availability group (DAG). This session covers the inner workings of DAGs, including a deep dive discussion on how DAGs rely on quorum and how the DAG witness and witness server are used. You’ll also gain a solid understanding of the inner workings of Active Manager and its best copy selection process. Exchange Server 2010: High Availability Concepts - This session covers the basics of the new technologies, concepts, terms and methods used to plan, design, manage and troubleshoot Exchange high availability. Learn how settings like AutoDatabaseMountDial and Activation Preference work. Get an understanding of the basic functions of Active Manager, learn the difference between the Witness Server and the Alternate Witness Server, and more! Microsoft Office 365: From Simple Migration to a Hybrid Environment - Whether you’re looking to migrate all of your mailboxes to the cloud or planning to run a hybrid environment then this is the session for you. This presentation will cover how and when to take advantage of Simple Exchange Migration which supports migrating existing Exchange on-premise customers who want to move all of their mailboxes to the cloud with full data fidelity. You will also learn how rolling out an Exchange 2010 server in your current Exchange environment prepares you for seamless integration with Exchange Online. Whether you are piloting a few users or moving a large part of your workforce to the cloud, we give you the technical details on Exchange-to-cloud integration that you need to be successful.
  18. Catastrophic Failure
    Νωρίς σήμερα, η ομάδα του Exchange CXP έκανε release το Update Rollup 5 για τον Exchange Server 2007 SP3 το οποίο είναι διαθέσιμο προς λήψη στο Download Center.
    Update Rollup 5 για τον Exchange Server 2007 SP3
    Το παρόν Rollup περιέχει ένα μεγάλο αριθμό αναφορών των συνεργατών της Microsoft και διαφόρων εσωτερικών αναφορών από τους μηχανικούς της Microsoft, από το πρώτο release RU5. Μερικά από τα fixes που περιλαμβάνονται στο RU5 είναι τα ακόλουθα :
    DST: New updates for August DST - Exchange 2007 2536695 "Some items cannot be deleted" error message when you try to delete or modify an email message in a public folder in an Exchange Server 2007 environment 2292150 A deleted hyperlink remains in the HTML source of an email message if you create the email message by using OWA in an Exchange Server 2007 environment (article not yet live) Το Update Rollup 6 για τον Exchange Server 2007 Service Pack 3 έχει προγραμματιστεί να γίνει release τον Απρίλιο του 2012.
    Σημείωση για τους χρήστες Forefront:
    Για όσους από εσάς χρησιμοποιείτε Forefront, πρέπει να εκτελέσετε αυτά τα σημαντικά βήματα από τη γραμμή εντολών «command line» στο Forefront directory πριν και μετά τη διαδικασία της εγκατάστασης του rollup. Στην περίπτωση που δεν πραγματοποιηθούν αυτά τα βήματα, τα Exchange services για το Exchange Information Store και Transport δεν θα μπορέσουν να ξεκινήσουν. Θα χρειαστεί να απενεργοποιήσετε το Forefront μέσω «fscutility /disable» προτού εγκαταστήσετε το patch και στη συνέχεια ενεργοποιήστε το ξανά μετά την εγκατάσταση του patch με την εκτέλεση της εντολής «fscutility /enable» να ξεκινήσει και πάλι μετά την εγκατάσταση.
    Source: MSExchange Team
  19. Catastrophic Failure
    The Microsoft Exchange team is pleased to present the newest addition to the Exchange Server 2010 Technical Video Series – “Information Protection and Control” hosted by Greg Smiley and Ann Vu. In this video, Greg and Ann talk about the benefits of Security in Exchange 2010. The video includes demonstrations of three common scenarios related to Information Protection and Control: 1) Transport Rules 2) On-Premises Protection, and 3) Cloud Based Protection.
    Video: Exchange Technical Video Series (Information Protection and Control)

    For more information on the Exchange Server 2010 Technical Video Series, check out our previous post. You can also access the rest of the videos in the series directly using the following links:
    Archiving and Discovery Mailbox Resiliency Management Mobility Outlook and Exchange Outlook Web App Unified Messaging Low bandwidth versions of each of the videos are now provided in the “Related Links” area for those on slower connections.
    As always, please help us evangelize these videos to anyone who wants to learn more about Exchange Server 2010, and let us know your thoughts. Your feedback is extremely valuable to us. Many thanks in advance.
    Source: MSExchange Team
  20. Catastrophic Failure
    Θέλετε να ταξιδέψετε και να εξερευνήσετε τον μαγικό κόσμο του Office 365?
    Microsoft Press προσφέρει δωρεάν για download το ebook «Microsoft Office 365: Connect and Collaborate Virtually Anywhere, Anytime». Γραμμένο από την Katherine Murray, το βιβλίο μας εισάγει στον κόσμο του cloud computing, ενώ μας αναλύει τα πλεονεκτήματα του Microsoft Office 365 και πώς μπορούμε να τα εκμεταλλευτούμε….

    Μερικά απο τα topic:
    Set up your Office 365 site, manage access, and add mobile devices Create, edit, and share documents Share calendar, files, and updates from your team site Manage email, contacts, and appointments using Outlook Web App Always connected — Learn instant messaging, social media, voice and chat Create a website to share information with customers Use work-flows to collectively track project tasks and progress
  21. Catastrophic Failure
    For many companies, the robust messaging and calendaring features offered by Office 365 for enterprises presents an opportunity to transition all messaging functionality from the on-premises organization into the cloud. Office 365 for enterprises includes a full suite of e-mail migration tools.
    However, there are dependencies and restrictions on the migration tools that you may be able to use with Office 365. Variables such as your on-premises Exchange Server version, the number of mailboxes you want to move, and how you want to handle user identity will dictate the tools and processes you can use to migrate to the cloud.

    Figure 1 : A screen shot from the new "Cloud Only" scenario in the Deployment Assistant
    To help you sort through the available options and plan your migration to the cloud, we’re happy to announce the “Cloud Only” option in the latest release of the Exchange Server Deployment Assistant. Like the other scenarios in the Deployment Assistant, the “Cloud Only” option allows you to step through a wizard that asks you questions about your current infrastructure and your migration goals. The Deployment Assistant will provide a migration solution that is based on your answers.
    Your feedback is very important for the continued improvement of this tool. Give us your feedback on this new scenario and any other area of the Deployment Assistant. Feel free to post comments on this blog post, provide feedback in the Office 365 community migration and coexistence forum, or send an email to [email protected] via the 'Feedback' link located in the header of every page of the Deployment Assistant.
    Source: MSExchange Team
  22. Catastrophic Failure
    In Exchange 2010, you can use Retention Policies to manage message retention. Retention Policies consist of delete tags, i.e. retention tags with either Delete and Allow Recovery or Permanently Delete actions, or archive tags, i.e. retention tags with the Move To Archive action, which move items to the user's archive mailbox.
    Depending on how they're applied to mailbox items, retention tags are categorized as the following three types:
    Default Policy Tags (DPTs), which apply to untagged items in the mailbox – untagged items being items that don't have a retention tag applied directly or by inheritance from parent folder. You can create three types of DPTs: an archive DPT, a delete DPT and a DPT for voicemail messages. Retention Policy Tags (RPTs), which are retention tags with a delete action, created for default folders such as Inbox and Deleted Items. Not all default folders are supported. You can find a table showing the default folders supported for RPTs in Understanding Retention Tags and Retention Policies. Notably, Calendar, Tasks and Contacts folders aren't supported. Personal Tags, which are retention tags that users can apply to items and folders in Outlook 2010 and Outlook Web App. Personal tags can either be delete tags or archive tags. They're surfaced in Outlook 2010 and OWA as Retention policies and Archive policies. To deploy retention tags, you add them to a retention policy and apply the policy to mailbox users.
    In Exchange 2010 SP1, we added support for the Notes folder. In Exchange 2010 RTM, items in the Notes folder aren't processed. After you upgrade to SP1, if the user's retention policy doesn't have a RPT for the Notes folder, the DPT from the user's policy will apply to items in that folder.
    In existing deployments, your users may not be used to their notes being moved or deleted.
    To prevent the DPT from being applied to a default folder, you can create a disabled RPT for that folder (or disable any existing RPT for that folder). The Managed Folder Assistant, a mailbox assistant that processes mailbox items and applies retention policies, does not apply the retention action of a disabled tag. Since the item/folder still has a tag, it's not considered untagged and the DPT isn't applied to it.

    Figure 1: Create a disabled Retention Policy Tag for the Notes default folder to prevent the Default Policy Tag from being applied to items in that folder
    Note: You can create a disabled RPT for any supported default folder.
    Why are items in the Notes folder still archived?
    If you create a disabled RPT for the Notes folder, you'll see items in that folder are not deleted, but they do continue to be moved to the archive! Why does this happen? How do you prevent it?
    It's important to understand that:
    A retention policy can have a DPT to archive items and a DPT to delete items. Both apply to untagged items. The move and delete actions are exclusive of each other. Mailbox folders and messages can have both types of tags applied - an archive tag and a delete tag. It's not an either/or proposition. If you create a disabled RPT for the Notes folder to not delete items, the archive DPT for the mailbox would still apply and move items. When it comes to archiving, there's only one archive policy that administrators can enforce – the DPT with 'Move to archive' action. You can't create a RPT with the 'Move to archive' action. This rules out using the disabled RPT approach to prevent items from being moved. Users can apply a personal tag to a folder or messages to move items sooner or later than the default archive policy for that mailbox. How do you prevent items in a default folder from being archived?
    There's no admin-controlled way of doing this, short of removing the archive DPT from a retention policy. However, removing the archive DPT would result in messages not moving to archive automatically unless the user applies a personal tag to messages or folders.
    The workaround is to have users apply the Personal never move to archive personal tag (displayed as Never under Archive Policy in Outlook/OWA) to a default folder. The tag is included in the Default Archive and Retention Policy created by Exchange Setup. You can also add this tag to any Retention Policies you create.

    Figure 2: Users can apply the Never archive policy to a default folder to prevent items in that folder from being archived
    Note: You can't use Outlook 2010 to apply an archive policy to the Notes default folder or individual notes items. Users wanting to apply an archive policy to the folder must use OWA.
    Source: MSExchange Team
  23. Catastrophic Failure
    Starting with Exchange 2007, installation of the current version of Office Filter Packs is a prerequisite. For Exchange 2007 and Exchange 2010 RTM, the pre-req was 2007 Office System Converter: Microsoft Filter Pack. In Exchange 2010 SP1, this was updated to Office 2010 Filter Packs. The filters are used by Exchange Search to index email attachments on Mailbox servers and by the transport rules agent to scan attachments on transport servers. The filters are also important for discovery searches in Exchange 2010 – Multi-Mailbox Search uses content indexes generated by Exchange Search.
    In Exchange 2010 RTM and Exchange 2007, you need to register the IFilters with Exchange Search (for Exchange 2007, see 'KB 944516 How to register Filter Pack IFilters with Exchange Server 2007'). In Exchange 2010 SP1, IFilters included in the Office 2010 Filter Pack are automatically registered by Exchange Setup. You must register any third-party filters you install.
    An updated filter pack, Service Pack 1 for Microsoft Office Filter Pack 2010 (KB2460041) 64-bit Edition is now available on Download Center. The Filter Pack has been tested with Exchange 2010 and Exchange 2007. The updated filter pack doesn’t have any fixes or updates that impact Exchange scenarios or functionality. If you have the RTM version of Office 2010 filter packs installed, you can update it but it’s not required. For new installs, we recommend going with the current versions.
    Source: Bharat Suneja
  24. Catastrophic Failure
    We are excited to announce that the Remote Connectivity Analyzer tool has been updated! In addition to the standard set of connectivity tests, we’ve added an Office 365 tab and a Single Sign-On test. The new Single Sign-On test will validate users' ability to log on to Office 365 with their on-premises credentials. It also validates some basic Active Directory Federated Services (ADFS) configurations.
    Here's an overview and video demo.
    Video: RCA ADFS Intro
    In addition to the new tests, you will see the same great tests that were always available.
    The Remote Connectivity Analyzer is available at https://www.TestExchangeConnectivity.com/.
    Tip: you can also get here by going to exrca.com. Same site… just fewer characters to type.
    We’re always excited to hear from you - please send us your feedback to ExRCAFB address.
    Remote Connectivity Analyzer Release Notes (Also available here)
    Version 1.3 (June 2011)

    Known Issues
    A couple of the tests allow you to "Ignore trusts for SSL". Checking this option only tells the tool to not fail if the certificate you are using is not in the list of Trusted Root Certificates – for example, if you were using a certificate from your own Windows CA. This option does not allow the test to be completed over a non-SSL connection. If you do not have a certificate and want to test whether Exchange ActiveSync works over port 80 - this tool cannot perform this validation. We will not be able to add this feature in the future. Note: Due to limitations in the RPC API, we are currently unable to ignore the trust requirement for SSL for the RPC over HTTP / Outlook Anywhere tests. We are looking into alternatives for future releases.
    Copy to clipboard doesn't work in Firefox by default (You have to enable it) Some localized strings are in English if they were modified during this update. These strings will be localized in the future. While performing tests, the stage of testing will no longer update while the test is being performed. This is a necessary change for the moment due to some underlying changes to the Remote Connectivity Analyzer code. Your full test results will be available once the test is complete. New / Modified Features
    Microsoft Exchange Remote Connectivity analyzer is now the Microsoft Remote Connectivity Analyzer. The future direction for this tool is to incorporate more products as we have done with Office 365. Thus dropping "Exchange" from the name made sense. There are still lots of strings where you'll see ExRCA or Exchange; we're cleaning these up in a future release. Tabbed user-interface to support multiple products and Office 365. Office 365 Single sign-on validation. This test allows you to validate identity federated scenarios with Office 365. Specifically, this new test targets the "Basic Authentication" federated scenario where a client sends credentials to Office 365 which in turn validates them against the on-premises ADFS server. Fixed an issue where ExRCA wouldn't validate certain top-level domains such as .travel and .museum. Added code so if the Enter key is pressed in the wizard, the default action is "next" instead of "previous". Previously, this didn't work for browsers other than IE. Better cross-browser support, fully supporting IE8-IE9 standards mode as well as other major browsers. Source: MSExchange Team

  25. Catastrophic Failure
    We have discovered an issue impacting some customers who have installed Exchange 2010 SP1 RU4 into their Exchange environment and as a result have removed SP1 RU4 from Download Center and recommend customers do not proceed with any planned deployments of SP1 RU4.
    A small number of customers have reported when the Outlook client is used to move or copy a folder that subfolders and content for the moved folder are deleted. After investigation we have determined that the folder and item contents do not appear in the destination folder as expected but may be recovered from the Recoverable Items folder (what was previously known as Dumpster in older versions of Exchange) from the original folder. This behavior occurs due to a customer requested change in SP1 RU4 which allowed deleted Public Folders to be recovered. Outlook and Exchange are not correctly processing the folder move and copy operations causing the folder contents to appear to be deleted. OWA and Exchange Web Services clients are not affected by this change and process the folder move or copy actions correctly.
    We will be providing an updated Exchange fix which prevents the apparent content loss in SP1 RU5, which is scheduled for release in August. In addition, we are also working with the Outlook development team to examine their code for proper behavior and identify if a fix is necessary from the client. If you have already deployed SP1 RU4, we recommend obtaining an Interim Update that resolves this issue.
    If you are a customer seeing this issue or would like to receive the Interim Update, please contact Microsoft Customer Support.
    We are commencing an internal review of our processes to determine how we can best prevent issues such as this one arising in future.
    Once again, on behalf of the Exchange Product Group, I want to thank you for the patience you continue to show us while we work through these issues. We deeply regret the impact that this issue has had on you, our customers, and as always, we continue to identify ways to better serve your needs through our regular servicing releases.
    Source: MSEXCHANGE TEAM
×
×
  • Create New...