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
    Earlier today the Exchange CXP team released Update Rollup 1 for Exchange Server 2010 SP2 to the Download Center.

    This update contains a number of customer-reported and internally found issues since the release of RU1. See KB 2645995: Description of Update Rollup 1 for Exchange Server 2010 Service Pack 2' for more details.

    Note: If some of the following KB articles do not work yet, please try again later.

    We would like to specifically call out the following fixes which are included in this release:

    New updates for Dec DST - Exchange 2010 - SP2 RU1 - Display name for OWA. 2616230
    Exchange 2010 CAS server treats UTF-7 encoding NAMESPACE string from
    CHS Exchange 2003 BE server as ASCII, caused IMAP client fails to login. 2599663 RCA crashes when recipient data is stored in bad format. 2492082 Freebusy publish to Public Folders fails with 8207 event. 2666233 Manage hybrid configuration wizard won't accept domains starting with a numeral for FOPE outbound connector FQDN. 2557323 "UseLocalReplicaForFreeBusy" functionality needed in Exchange 2010. 2621266 Exchange 2010 Mailbox Databases not reclaiming space. 2543850 Exchange 2010 GAL based Outlook rule not filtering emails correctly.
    General Notes:

    For DST Changes: http://www.microsoft.com/time.

    Note for Forefront Protection for Exchange users 
    For those of you running Forefront Protection 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.


    Source

  2. i-away
    Μετά απο ενδελεχή έλεγχο της ομάδας του Exchange το συγκεκριμένο update είναι ασφαλές για εγκατάσταση και προτείνεται να εγκατασταθεί το ταχύτερο δυνατό στους Exchange Servers
     
    Η σχετική ανακοίνωση είναι εδώ
     
  3. i-away
    1η Ιανουαρίου ώρα 16:30 : Αρχίζω να κοιτάζω τα mail μου περιμένοντας είτε ένα ευχάριστο mail είτε ένα δυσάρεστο.
     
    16:50 : Ακόμα τίποτα...
     
    17:30 : Δεν έχει έρθει τίποτα ακόμα... Δεν μπορεί σκέφτομαι.. πρέπει να έρθει ένα mail..
     
    17:32 : Συνειδητοποιώ ότι έχει έρθει στα junk ένα mail...
     
    Και όντως :
     
    ""Dear George Andritsos,
     
     
     
    Congratulations! We are pleased to present you with the 2012 Microsoft® MVP
    Award! This award is given to exceptional technical community leaders who
    actively share their high quality, real world expertise with others "
     
     
    Με
    αυτή την ευκαιρία θα ήθελα για άλλη μια φορά να ευχαριστήσω όλους τους
    ανθρώπους που ο καθένας με τον τρόπο του κάνουν δυνατή την ύπαρξη της
    κοινότητας, και μας δίνουν τη δυνατότητα να επικοινωνούμε, να
    μοιραζόμαστε σκέψεις, απόψεις, απορίες και λύσεις.

    Εύχομαι ολόψυχα το 2012 να μπορέσει ο καθένας να
    το περάσει με τον καλύτερο δυνατό τρόπο, και πιστεύω πως έχει έρθει ο
    καιρός -υπό την πίεση των περιστάσεων- να κάνουμε όλοι μια
    επαναξιολόγιση των προτεραιωτήτων μας, να αναζητήσουμε άλλους -πολλές
    φορές ξεχασμένους- τρόπους να εκφραστούμε και να χαρούμε, ώστε να
    ξεπεράσουμε με τον καλύτερο τρόπο τις δυσκολίες, αλλά και τις προκλήσεις
    που θα βρούμε αναπόφευκτα μπροστά μας.
    ΚΑΛΗ ΧΡΟΝΙΑ ΣΕ ΟΛΟΥΣ!!!
  4. i-away
    Πολύ καλό και επεξηγηματικό άρθρο απο τον συνήθη ύποπτο Ben Appleby :
     

    During the beta of Office 365 for Enterprises, we received great
    feedback from our customers and wanted to vastly simplify the process
    for configuring Exchange in a hybrid deployment with Office 365. We are
    introducing the Hybrid Configuration Wizard in Exchange 2010 Service Pack 2 to refine the deployment process as a result of that feedback.

    What is the Hybrid Configuration Wizard?

    The Hybrid Configuration Wizard consists of:

    A new Exchange Management Console (EMC) wizard that guides you through the end-to-end process for configuring a hybrid deployment.
    A set of Exchange Management Shell (EMS) cmdlets that orchestrate the configuration process (as always, the EMC executes these Shell
    cmdlets).
    Improvements to the manageability of some of the underlying hybrid features (no more exchangedelegation.contoso.com or service.contoso.com
    domains – Yay!)

    What does it do?

    The hybrid configuration cmdlets take inputs from the wizard, analyze
    the state of your existing on-premises and cloud organizations, and
    calculate the required steps to correctly configure both organizations
    correctly. You can learn more about this process here.

    This friendly wizard replaces approximately 50 manual steps
    with just a few inputs and several clicks of your mouse. Here are some
    of the top tasks that the Hybrid Configuration Wizard will automatically
    verify and configure for you:

    Verifies that your on-premises and Office 365 organizations meet the prerequisites for a hybrid deployment. Provisions your on-premises Exchange federation trust. Creates mutual organization relationships between your on-premises and Exchange Online organizations. Modifies e-mail address policies to ensure that mailboxes can be moved successfully to Exchange Online in Office 365. Enables and configures free/busy calendar sharing, message tracking and MailTips for both your on-premises and Exchange Online
    organizations.
    Configures secure mail flow between your on-premises and Exchange Online organizations. You can even choose to have the wizard
    automatically configure Exchange Online organization to route mail
    through your on-premises Exchange organization to meet any additional
    business or compliance requirements.
    Enables support for Exchange Online Archiving for on-premises mailboxes for those customers that have chosen to include archiving in their Office 365 service plan.
    Once the hybrid deployment configuration process is complete, the
    following features are available between your on-premises Exchange
    organization and Exchange Online:

    Feature Description Native mailbox move Online mailbox moves with automatic Outlook reconfiguration Free/busy and calendar sharing Free/busy and calendar sharing between on-premises and Exchange Online mailboxes Secure mail TLS-encrypted and authenticated mail flow between your on-premises and Exchange Online organizations Exchange Online Archiving Provide unlimited cloud-based archive storage for your on-premises mailboxes Message tracking Integrated message tracking logs across on-your on-premises and Exchange Online organizations Multi-mailbox search Create a single search request that automatically queries both on-premises and Exchange Online mailboxes Outlook Web App redirection Redirect OWA logons for users that have been moved to Exchange Online Mailtips Ensures that MailTips are available for both your on-premises and Exchange Online organizations  


    If you've used the Exchange Server Deployment Assistant
    to configure a previous hybrid deployment, please note that we’re busy
    updating the current scenarios to provide guidance based on the
    automatic configuration process using the Hybrid Configuration Wizard.
    Watch this blog for announcements when the Deployment Assistant is
    updated.

    With that in mind, we'll be retiring the manual hybrid deployment configuration guidance provided with SP1
    and we strongly encourage you use the wizard wherever possible.
    Although we'll continue to support manually configured hybrid
    deployments, we believe that using the new wizard is the easiest, most
    reliable way of getting deployed and staying correctly configured.

     
  5. i-away
    Over the next several months Microsoft will deploy the December 2011
    Exchange Online Service Update. As a part of this update, we will also
    make high availability architecture enhancements in all datacenters that
    host Office 365 tenant domains. These updates will be staggered
    globally, beginning in December 2011, and we expect full deployment to
    complete within six months. Approximately one week before the service
    update is deployed to your region we will post more information in
    the Planned Maintenance section in your Service Health Dashboard portal.
    Please check this resource for awareness of when your update is scheduled to begin.
    The changes contained in this update are summarized below.

    High Availability Architecture Enhancements:
    We are extending our high availability architecture across additional
    sites to provide greater resilience in the event of network failures.
    Administrators and end users may notice changes to server names in URLs
    and in protocol settings. The connection for client applications and
    devices, including those configured to connect directly to server
    addresses, will automatically redirect when the mailbox is migrated to
    the latest software. A very small percentage of mobile devices are not
    100% compliant and may have to be reconfigured to connect to a changed
    pod address. Please refer users to the Mobile Phone Setup Wizard for connection procedures. Sender Photos in Outlook Web App:
    You can now match faces to names in your organization with photos
    displayed next to sender information in emails. Display of photos is
    enabled by default, but you can modify the settings of your Outlook Web
    App mailbox policy to disable this feature. Outlook Web App in Internet Explorer 9 App Mode:
    Outlook Web App can now be pinned to the task bar using Internet
    Explorer 9 App Mode. This gives you the ability to launch Outlook Web
    App with one click and run it with fewer distractions, separated from
    other browsing sessions. It also keeps you informed of incoming email
    and IM when minimized or hidden and offers quick access to common
    Outlook Web App commands from the taskbar. Group Naming Policy:
    You can now standardize and manage the names of distribution groups,
    also known as public groups, created by users in your organization. You
    can require a specific prefix and suffix be added to the name for a
    distribution group when it's created, and you can block specific words
    from being used. This helps you minimize the use of inappropriate words
    in group names. Retention Policy and Tag Management:
    We have made it easier than ever to manage retention settings for the
    user mailboxes in your organization. You can now use the mail control
    settings in Exchange Control Panel to create and manage retention tags
    and policies. Multi-Mailbox Search Enhancements:
    You can now launch a separate window to preview message hits and
    statistics for each query. Search performance has also been improved
    with reduced impact of retried query failures, as well as enhancements
    to scalability and availability. Migration Enhancements: Two new enhancements to migration features will bring greater efficiency to e-mail migrations. Enhanced Management Capabilities:
    The new Exchange Online migration dashboard helps to improve
    administrative efficiency during a cutover Exchange migration, a staged
    Exchange migration, or an IMAP migration. Tenant administrators can
    schedule multiple migration batches, obtain migration status information
    for migration batches, view per user details, and see skipped items.
    Improved reporting and diagnostics tools provide an improved
    troubleshooting experience. Number of Concurrent Migrations: Administrators can now use Exchange Management Shell to increase the value for a migration batch to as high as 50. Exchange Hybrid Configuration Wizard:
    This wizard will help streamline the hybrid deployment process by
    simplifying configuration of features and services such as calendar and
    free/busy information sharing, mailbox moves, secure mail flow and
    Exchange Online Archiving. This feature is not included as part of the
    December 2011 Exchange Online Service Update, but will be available in
    December 2011 as part of the Exchange Server 2010 SP2 release.



    Source

  6. i-away
    In early August of this year, the Windows SE team released the
    following Knowledge Base (KB) article and accompanying software hotfix
    regarding an issue in Windows Server 2008 R2 failover clusters:

    KB2550886 - A transient communication failure causes a Windows Server 2008 R2 failover cluster to stop working

    This hotfix is strongly recommended for all databases availability
    groups that are stretched across multiple datacenters. For DAGs that are
    not stretched across multiple datacenters, this hotfix is good to have,
    as well. The article describes a race condition and cluster database
    deadlock issue that can occur when a Windows Failover cluster encounters
    a transient communication failure. There is a race condition within the
    reconnection logic of cluster nodes that manifests itself when the
    cluster has communication failures. When this occurs, it will cause the
    cluster database to hang, resulting in quorum loss in the failover
    cluster.

    As described on TechNet,
    a database availability group (DAG) relies on specific cluster
    functionality, including the cluster database. In order for a DAG to be
    able to operate and provide high availability, the cluster and the
    cluster database must also be operating properly.

    Microsoft has encountered scenarios in which a transient network
    failure occurs (a failure of network communications for about 60
    seconds) and as a result, the entire cluster is deadlocked and all
    databases are within the DAG are dismounted. Since it is not very easy
    to determine which cluster node is actually deadlocked, if a failover
    cluster deadlocks as a result of the reconnect logic race, the only
    available course of action is to restart all members within the entire
    cluster to resolve the deadlock condition.

    The problem typically manifests itself in the form of cluster quorum
    loss due to an asymmetric communication failure (when two nodes cannot
    communicate with each other but can still communicate with other nodes).
    If there are delays among other nodes in the receiving of cluster
    regroup messages from the cluster’s Global Update Manager (GUM), regroup
    messages can end up being received in unexpected order. When that
    happens, the cluster loses quorum instead of invoking the expected
    behavior, which is to remove one of the nodes that experienced the
    initial communication failure from the cluster.

    Generally, this bug manifests when there is asymmetric latency (for
    example, where half of the DAG members have latency of 1 ms, while the
    other half of the DAG members have 30 ms latency) for two cluster nodes
    that discover a broken connection between the pair. If the first node
    detects a connection loss well before the second node, a race condition
    can occur:

    The first node will initiate a reconnect of the stream between the
    two nodes. This will cause the second node to add the new stream to its
    data. Adding the new stream tears down the old stream and sets its failure
    handler to ignore. In the failure case, the old stream is the failed
    stream that has not been detected yet. When the connection break is detected on the second node, the second
    node will initiate a reconnect sequence of its own. If the connection
    break is detected in the proper race window, the failed stream's failure
    handler will be set to ignore, and the reconnect process will not
    initiate a reconnect. It will, however, issue a pause for the send
    queue, which stops messages from being sent between the nodes. When the
    messages are stopped, this prevents GUM from operating correctly and
    forces a cluster restart.
    If this issue does occur, the consequences are very bad for DAGs. As a
    result, we recommend that you deploy this hotfix to all of your Mailbox
    servers that are members of a DAG, especially if the DAG is stretched
    across datacenters. This hotfix can also benefit environments running
    Exchange 2007 Single Copy Clusters and Cluster Continuous Replication
    environments.

    In addition to fixing the issue described above, KB2550886 also
    includes other important Windows Server 2008 R2 hotfixes that are also
    recommended for DAGs:

    http://support.microsoft.com/kb/2549472 - Cluster node cannot rejoin the cluster after the node is restarted or removed from the cluster in Windows Server 2008 R2 http://support.microsoft.com/kb/2549448
    - Cluster service still uses the default time-out value after you
    configure the regroup time-out setting in Windows Server 2008 R2 http://support.microsoft.com/kb/2552040 - A Windows Server 2008 R2 failover cluster loses quorum when an asymmetric communication fail
  7. 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





  8. i-away
    It’s been a few months since we announced some major changes to our virtualization support statements for Exchange 2010 (see Announcing Enhanced Hardware Virtualization Support for Exchange 2010).
    Over that time, I’ve received quite a few excellent questions about
    particular deployment scenarios and how the changes to our support
    statements might affect those deployments. Given the volume of
    questions, it seemed like an excellent time to post some additional
    information and clarification.
    First of all, a bit of
    background. When we made the changes to our support statements, the
    primary thing we wanted to ensure was that our customers wouldn’t get
    into a state where Exchange service availability might be reduced as a
    result of using a virtualized deployment. To put it another way, we
    wanted to make sure that the high level of availability that can be
    achieved with a physical deployment of the Exchange 2010 product would
    not in any way be reduced by deploying on a virtualization platform. Of
    course, we also wanted to ensure that the product remained functional
    and that we verified that the additional functionality provided by the
    virtualization stack would not provide an opportunity for loss of any
    Exchange data during normal operation.
    Given these points, here’s a quick overview of what we changed and what it really means.
    Let’s go over some definitions to make sure we are all thinking about the terms in those support statements in the same way.
    Cold boot
    This refers to the action of bringing up a system from a power-off
    state into a clean start of the operating system. No operating system
    state has been persisted in this case. Saved state
    When a virtual machine is powered off, hypervisors typically have the
    ability to save the state of the virtual machine at that point in time
    so that when the machine is powered back on it will return to that state
    rather than going through a “cold boot” startup. “Saved state” would be
    the result of a “Save” operation in Hyper-V. Planned migration
    When a system administrator initiates the move of a virtual machine
    from one hypervisor host to another we call this a planned migration.
    This could be a single migration, or a system admin could configure some
    automation that is responsible for moving the virtual machine on a
    timed basis or as a result of some other event that occurs in the system
    other than hardware or software failure. The key point here is that the
    Exchange virtual machine is operating normally and needs to be
    relocated for some reason – this can be done via a technology like Live
    Migration or vMotion. If the Exchange virtual machine or the hypervisor
    host where the VM is located experiences some sort of failure condition,
    then the result of that would not be “planned”. Virtualizing Unified Messaging Servers
    One
    of the changes made was the addition of support for the Unified
    Messaging role on Hyper-V and other supported hypervisors. As I
    mentioned at the beginning of this article, we did want to ensure that
    any changes we made to our support statement resulted in the product
    remaining fully functional and providing the best possible service to
    our users. As such, we require Exchange Server 2010 SP1 to be deployed
    for UM support. The reason
    for this is quite straightforward. The UM role is dependent on a media
    component provided by the Microsoft Lync team. Our partners in Lync did
    some work prior to the release of Exchange 2010 SP1 to enable high
    quality real-time audio processing in a virtual deployment, and in the
    SP1 release of Exchange 2010 we integrated those changes into the UM
    role. Once that was accomplished, we did some additional testing to
    ensure that user experience would be as optimal as possible and modified
    our support statement.
    As you’ll notice, we do have specific
    requirements around CPU configuration for virtual machines (and
    hypervisor host machines) where UM is being run. This is additional
    insurance against poor user experience (which would show up as poor
    voice quality).
    Host-based Failover Clustering & Migration
    Much
    of the confusion around the changed support statement stems from the
    details on combination of host-based failover clustering & migration
    technology with Exchange 2010 DAGs). The guidance here is really quite simple.
    First, let’s talk about whether we support third-party migration technology
    (like VMware’s vMotion). Microsoft can’t make “support” statements for
    the integration of 3rd-party hypervisor products using these
    technologies with Exchange 2010, as these technologies are not part of
    the Server Virtualization Validation Program
    (SVVP) which covers the other aspects of our support for 3rd-party
    hypervisors. We make a generic statement here about support, but in
    addition you need to ensure that your hypervisor vendor supports the
    combination of their migration/clustering technology with Exchange 2010.
    To put it as simply as possible: if your hypervisor vendor supports
    their migration technology with Exchange 2010, then we support Exchange
    2010 with their migration technology.
    Second, let’s talk about how we define host-based failover clustering. This refers to any
    sort of technology that provides automatic ability to react to
    host-level failures and start affected VMs on alternate servers.
    Use of this technology is absolutely supported within the provided
    support statement given that in a failure scenario, the VM will be
    coming up from a cold boot on the alternate host. We want to ensure that
    the VM will never come up from saved state that is persisted on disk,
    as it will be “stale” relative to the rest of the DAG members.
    Third, when it comes to migration technology in the support statement, we are talking about any sort of technology that allows a planned move of a VM from one host machine to another.
    Additionally, this could be an automated move that occurs as part of
    resource load balancing (but is not related to a failure in the system).
    Migrations are absolutely supported as long as the VMs never come up
    from saved state that is persisted on disk. This means that technology
    that moves a VM by transporting the state and VM memory over the network
    with no perceived downtime are supported for use with Exchange 2010.
    Note that a 3rd-party hypervisor vendor must provide support for the
    migration technology, while Microsoft will provide support for Exchange
    when used in this configuration. In the case of Microsoft Hyper-V, this
    would mean that Live Migration is supported, but Quick Migration is not.

    With Hyper-V, it’s important to be aware that the default behavior when selecting the “Move” operation on a VM is actually to perform a Quick Migration. To stay in a supported state with Exchange 2010 SP1 DAG
    members, it’s critical that you adjust this behavior as shown in the VM
    settings below (the settings displayed here represent how you should
    deploy with Hyper-V):

    Figure 1: The correct Hyper-V virtual machine behavior for Database Availability Group members Let’s
    review. In Hyper-V, Live Migration is supported for DAG members, but
    Quick Migration is not. Visually, this means that this is supported:

    Figure 2: Live Migration of Database Availability Group member in Hyper-V is supported (see large screenshot) And this is not supported:

    Figure 3: Quick Migration of Database Availability Group members is not supported Hopefully
    this helps to clarify our support statement and guidance for the SP1
    changes. We look forward to any feedback you might have!


    Source





  9. i-away
    Όσοι απο εσάς έχουν χρήστες που χρησιμοποιούν Blackberry και έχουν εγκατεστημένο BES θα έχουν παρατηρήσει ότι υπάρχει η επιλογή Resend Service Books. Τι είναι τα service books όμως?

    Service Book κατά RIM : “A service book contains information that configures how your BlackBerry smartphone interacts with the BlackBerry® Infrastructure. It also turns on specific services for your BlackBerry smartphone. The selection of service books on your BlackBerry smartphone depends upon the features provided by your wireless service provider and the IT policies set up by your organization”

    Συνήθως όταν κάποιος χρήστης μας παραπονιέται ότι έχει θέμα με την συσκευή του αυτό που κάνουμε είναι να ξαναστείλουμε τα service books απο τον BES.
    Στον παρακάτω πίνακα θα δείτε αναλυτικά τα στοιχεία του service book.

    Service Book Functionality 5 Click [browserConfig] Contains settings that are used by the E-mail Settings icon to create a new BlackBerry® Internet Service account or maintain an existing one. 5 Click [iPPP] or 5 Click [WAP] Contains routing information that is used by the E-mail Settings icon for BlackBerry Internet Service accounts. Browserconfig for IPPP [browserConfig] Contains settings for the BlackBerry Internet Browser Service such as a preconfigured homepage or bookmarks. IPPP for BIBS [iPPP] Contains information about BlackBerry Internet Browser Service routing information. Desktop [ALP] or BlackBerry [ALP]* Contains information that is required to perform wireless Global Address Book searches. Desktop [bBIM] or BlackBerry [bBIM]* Contains the record information that is used to send instant messages with an enterprise instant messaging service such as Microsoft® Live Communications Server. Desktop [browserConfig] or BlackBerry [browserConfig]* Contains settings for the BlackBerry® Browser such as preconfigured homepage or bookmarks. Desktop [CICAL] or BlackBerry [CICAL]* Contains information that is required for BlackBerry wireless calendar operations. Desktop [CMIME] or BlackBerry [CMIME]* Contains information that is required to send messages and perform functions such as wireless email message reconciliation. Desktop [iPPP] or BlackBerry [iPPP]* Contains information that is required to use and browse the Internet using the BlackBerry® Mobile Data System (BlackBerry MDS). Desktop [sYNC] or BlackBerry [sYNC]* Contains information that is used to wirelessly synchronize organizer databases and to wirelessly backup and restore BlackBerry smartphone data.
    Note: The BlackBerry smartphone must be running BlackBerry® Device Software 4.0 or later and be connected to a BlackBerry® Enterprise Server software version 4.0 or later.
    Provisioning [Provisioning] Contains information that is used to turn on or off the Enterprise Activation icon for BlackBerry Device Software 4.0 and later. MMS Transport [WAP] Contains information that is required to send Multimedia Messaging Service (MMS) messages over Wireless Application Protocol (WAP) 1.x. MMS Transport [WPTCP] Contains infromation that is required to send MMS messages over WAP 2.x. MMS client [MMS] Contains information regarding the wireless provider’s MMS settings. WAP Browser [browserConfig] Contains settings for the WAP Browser such as a preconfigured homepage or bookmarks. WAP Transport [WAP] Contains information that is required to connect to a wireless provider’s WAP 1.x gateway. WAP2 Transport [WPTCP] Contains information that is required to connect to a wireless provider’s WAP 2.x gateway. WAP Push Config [WAPPushConfig] Contains information that is used to setup a WAP-push connection on a BlackBerry smartphone for WAP dependent applications and is also used for new MMS message notifications sent using WAP Push. Web Client [CMIME] Contains information that is required to send messages and perform functions such as wireless email reconciliation with the BlackBerry Internet Service 1.8.
    Note: BlackBerry Internet Service 1.8 is no longer available and has been replaced by the BlackBerry Internet Service 2.x.
    Yahoo Messenger [YHO] Contains the record information that is used to send instant messages using the Yahoo!® Messenger client.
    Note: This service book is available from the wireless service provider.
    <Retail_Instant_Messaging_Application> [bBIMConfig] Contains configuration and carrier information for a retail instant messaging application and is also used in the creation of the [KEYNOGO] service book. <Retail_Instant_Messaging_Application> [bBIM] Contains information that is required for sending instant messages with a retail instant messaging application. <Retail_Instant_Messaging_Application> [KEYNOGO] Contains information that is used for the encryption and decryption of instant messages that are sent using a retail instant messaging application.
    For example, the algorithm used by Google Talk™ is Advanced Encryption Standard (AES) 256 bits.
    <your_email_address> [CMIME] Contains information that is required to send email messages and perform functions such as wireless email reconciliation with the BlackBerry Internet Service. <your_email_address> [CICAL] Contains information that is required for BlackBerry wireless calendar operations with the BlackBerry Internet Service running BlackBerry Device Software 4.2 or later.
  10. i-away
    Στο τελευταίο autoexec event στην Θεσσαλονίκη αναφέρθηκα στην δύναμη και την ευκολία που προσφέρει το powershell στην διαχείρηση του Exchange. Επειδή ο χρόνος ήταν λίγος αποφάσισα να συνοψίσω κάποιες βασικές αλλά χρήσιμες εντολές. Ξεκινάμε λοιπόν:
     
    1) Πως μπορούμε να δούμε τα properties του κάθε mailbox object
    Get-Mailbox | ForEach { $_.Name }
    2) Όλα τα services που τρέχουν στον Exchange:
    Get-Service | where {$_.Status -eq ”Running”}
    3) Τα event logs του Exchange:
    Get-EventLog Application | Where { $_.Source -Ilike “*Exchange*” }
    4) Μια λίστα με τα ονόματα και τα mailboxes:
    Get-Mailbox | ForEach { $_.Name } | out-file Mailboxes.txt.
    5) Να ορίσουμε μαζικά μεγέθη quota πχ. :
    Set-Mailbox “mailboxname or txt file” -ProhibitSendQuota 200MB
    6) Που είναι και σε τι κατάσταση είναι μια βάση:
    Get-MailboxDatabase -Status | Format-Table Name, Server, Mounted
    7) Το backup status των βάσεων μας :
    Get-MailboxDatabase -Status | Format-Table Name, Server, *Backup*
    8) Τα mobiles devices που εχει ο χρήστης και την κατάσταση συγχρονισμού τους.
    Get-ActiveSyncDeviceStatistics

    Ο κόσμος του powershell είναι μεγάλος και οι δυνατότητες του απεριόριστες. Εξερευνήστε τον και θα μείνετε έκπληκτοι
  11. i-away
    You've been asking us about an Exchange 2010 version of the popular Exchange 2007 Component Architecture poster. We're pleased to let you know that the Exchange Server 2010 Architecture Poster is now available for download in all its 36" x 24" goodness! Here's a preview:

    The poster helps you understand how the major components of Exchange 2010 work and serves as a quick reminder and a learning tool. The printed version also looks really impressive on your wall!
    Head over to the Download Center to download the Exchange Server 2010 Architecture Poster (PDF).
    Those of you headed to Berlin for TechEd Europe next month, you'll be able to pick up your very own full-size glossy version from the Unified Communications booth. Wir sehen uns in Berlin!
  12. i-away
    Hello Exchange Developers! We've just released updated Software Development Kits for Exchange 2010 SP1. If you develop applications for Exchange Server, grab these SDKs from the Download Center.
    Microsoft Exchange Server 2010 SP1 Web Services SDK October 2010
    This release of the Exchange 2010 Service Pack 1 (SP1) Web Services Software Development Kit (SDK) provides new and updated documentation and samples for building applications that use Web services in Exchange 2010 SP1 . Use this SDK to help you develop collaborative Web services-based enterprise applications. Download
    Microsoft Exchange Server 2010 SP1 Backup and Restore SDK October 2010
    This release of the Exchange Server 2010 Service Pack 1 (SP1) Backup and Restore SDK provides information about how to create applications that back up, restore, and recover Exchange 2010 databases. Download
    Microsoft Exchange Server 2010 SP1 Transport Agents SDK October 2010
    This release of the Exchange 2010 Service Pack 1 (SP1) Transport Agents Software Development Kit (SDK) provides new and updated documentation and samples for building applications that use Microsoft Exchange transport agents. Use this SDK to help you develop collaborative enterprise applications for Exchange transport. Download
  13. i-away
    As a member of MCS that focuses on Exchange design and implementations, one of the tasks that I ensure each customer performs prior to deploying Exchange is to validate the storage platform using Jetstress. To that end, I have created a whitepaper that explains the process and requirements for validating an Exchange storage solution prior to releasing an Exchange deployment into production. The whitepaper explains how Jetstress works, how to plan for and perform a Jetstress test, and how to automate the process. You can use this whitepaper with any version of Exchange you plan to deploy.
    You can download the whitepaper here.
    Neil Johnson
  14. i-away
    Earlier today the Exchange CXP team released a number of Update Rollups for versions of Exchange Server to the Download Center and via Microsoft Update.
    Update Rollup 2 for Exchange Server 2010 Service Pack 1 Update Rollup 2 for Exchange Server 2007 Service Pack 3 Update Rollup 5 for Exchange Server 2010 RTM Update Rollup 5 for Exchange Server 2007 Service Pack 2 Update Rollup 2 for Exchange Server 2010 SP1
    This update contains a number of customer reported and internally found issues since the release of RU1. In particular we would like to specifically call out the following fixes which are included in this release:
    2322161 Passive DAG Copy Doesn't Replay Logs if "Don't mount this database at startup" is Checked 2431500 Cannot connect using Outlook Anywhere as the same user from multiple XP Clients 2409597 Implement OpenFlags.AlternateServer for PublicLogon Update Rollup 3 for Exchange Server 2010 Service Pack 1 is currently scheduled to release in February.
    Update Rollup 2 for Exchange Server 2007 SP3
    This update contains a number of customer reported and internally found issues since the release of RU1. In particular we would like to specifically call out the following fixes which are included in this release:
    972186 Need to include the server service as a required service for Exchange 2007 running on Server 2008 2290105 OWA Sharepoint/UNC Access is broken after SP3 Update Rollup 3 for Exchange Server 2007 Service Pack 3 is currently scheduled to release in February.
    Update Rollup 5 for Exchange Server 2010 RTM
    This update contains an internally found issue which can impact upgrades from RTM RU4 to Service Pack 1. We have opted to release an out-of-band update rollup for Exchange 2010 RTM proactively to ensure customers have as smooth an upgrade experience as possible.
    2266458 Setup cannot perform a mode:/uninstall on a HT role server since RU2 delivered MSFTE.msi Currently, we have no plans to release future update rollups for Exchange Server 2010 RTM. We strongly recommend customers upgrade to Service Pack 1 with the latest Update Rollup after installing this update.
    Update Rollup 5 for Exchange Server 2007 SP2
    This security update was released earlier this morning via the Microsoft Security Response Center. Details of this bulletin and it's fix can be found below:
    MSRC 10-024 Currently, we have no plans to release future update rollups for Exchange Server 2007 SP2. Instead, we strongly recommend customers upgrade to Service Pack 3 with the latest Update Rollup.
    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. Due to the timing of RU1 we were unable to complete this work in time.
    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, 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 back up. You will need to disable ForeFront via "fscutility /disable" before installing the patch and then re-enable after the patch by running "fscutility /enable" to start it up again post installation.
  15. i-away
    NOTE: The Exchange IPD Guide was updated to version 1.1 on July 11, 2011. The updates include content bug fixes, and updates related to the Exchange virtualization support changes. The download links are the same as Exchange IPD 1.0, so simply re-download the file to obtain the updated version.
    The Solution Accelerators team has released a new guide for Microsoft Exchange Server 2010 with Service Pack 1.
    The Infrastructure Planning and Design (IPD) Guide for Microsoft Exchange Server 2010 with Service Pack 1takes the IT architect through a step-by-step process for successfully designing an Exchange Server 2010 infrastructure. Exchange Server 2010 supports a variety of infrastructure topologies that enable IT departments to deploy the messaging architecture that best suits their business needs. This guide will help organizations make informed decisions about the design of fault tolerance and scalability so that their overall requirements are met.
    The guide covers these key steps in the Exchange Server 2010 infrastructure design process:
    Defining the project scope by identifying your individual business and IT requirements for a messaging infrastructure. Mapping features and functionality based on the defined scope to develop the appropriate Exchange Server 2010 design. Designing the infrastructure and role requirements for the proposed Exchange Server 2010 architecture. Determining the sizing, fault tolerance, and physical placement of Exchange Server 2010 roles. The IPD Guide for Microsoft Exchange Server 2010 with Service Pack 1 can help you reduce planning time and costs, and ensure a successful rollout of Exchange Server 2010 - helping your organization to more quickly benefit from this flexible and reliable messaging platform.
    Next Steps
    Download the FREE Exchange Server 2010 guide (ZIP - 2.94 MB) Download other best practices from the Infrastructure Planning and Design series for products such as Microsoft Forefront Unified Access Gateway, Windows Server 2008 R2, Hyper-V, SQL Server 2008, Exchange Online, SharePoint Online, System Center, and much more from the IPD site on TechNet. Visit the Exchange Server 2010 site on microsoft.com to learn more. Check out other Solution Accelerators to help you solve your deployment, planning, and operational IT problems. More information about the IPD series
    Planning the next generation of technical infrastructure for corporations can be a complex and daunting task. The success of any infrastructure is measured in how well the design choices match business objectives. Although plenty of product documentation is available, it can be difficult to find guidance on how to appropriately plan the core infrastructure for an organization. The Infrastructure Planning and Design series is designed to present the technical decision maker with the most concise planning guidance for Microsoft technologies. It also provides a means to validate design decisions to ensure that the selected solution meets the requirements of both business and IT stakeholders.
    The IPD documents are designed to be used by the following IT personnel:
    Infrastructure architects and planners who have a firm operational grasp of the technology Partners and consultants who design infrastructure solutions Business managers who want to understand how the decisions being made about technology both support and affect the business Check out all the Infrastructure Planning and Design team has to offer! For additional information, including our most recent guides, visit the IPD page on TechNet — http://www.microsoft.com/IPD.
    We appreciate your comments and feedback; please send mail to [email protected].
  16. 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
  17. i-away
    Στα περιβάλλοντα που εργαζόμαστε οι περισσότεροι έχουμε ρυθμίσει το Outlook να εργάζετε στο λεγόμενο Cached Exchange Mode. Η ενημέρωση του Offline Address Book γίνεται απο default 1 φορά ανά 24 ώρες. Ο συνδυασμός αυτών των 2 λειτουργιών προκαλεί κάποιες φορές 2 σημαντικά προβλήματα:
     
    1) Οι αλλαγές που κάνουμε στο Active Directory δεν εμφανίζονται στους clients
    2) Δημιουργούνται Sync Errors ( Sync Issues Folder)
     
    Ποιά είναι λοιπόν η διαδικασία που πρέπει να ακολουθήσουμε όταν παρατηρούμε τέτοια συμπεριφορά?.
     
    1) Βεβαιωνόμαστε ότι η GAL (Global Address Book) είναι όντως ενημερωμένη. Αυτό γίνεται στον Exchange 2003 πηγαίνοντας στον Exchange System Manager στον 'Recipients' folder επιλέγοντας 'All Global Address Lists' - 'Default Global Address List' - 'Properties' και πατώντας 'Preview'. Στον Exchange 2007/2010 αυτό θα πρέπει να γίνει χρησιμοποιώντας το OWA.
    Σε Outlook 2003, 2007,2010 που δουλεύουν σε cached mode ή με Offline folders χρησιμοποιείται το OAB που γίνεται download απο τον Exchange Server 1 φορά ανά 24 ώρες ή κάθε φορά που ξεκινάει το Outlook. Για να δούμε πως μπορούμε να επηρεάσουμε και να επιταχύνουμε την διαδικασία.
     
    1α. Με το Rebuild του Address Book.
    Στον Exchange 2003 αυτό γίνεται απο τον 'Exchange System Manager' στο tab 'Recipients' folder, επιλέγοντας rebuild απο την καρτέλα 'Offline Address Book'.
    Στον Exchange 2007/2010 γίνεται με από το 'Exchange Management Shell' με την: get-offlineaddressbook | update-offlineaddressbook
    2α. Ξανακατεβάζοντας χειροκίνητα το ΟΑΒ στο Outlook. Αυτό γίνεται από το 'Tools' - 'Send Recieve' - 'Download Address Book'.
    2) Μπορούμε να επιταχύνουμε το χρόνο που ο Exchange Server κάνει Update την ΟΑΒ πειράζοντας το 'Update Interval' από το 'Exchange System Manager' – 'Recipients' - 'Offline Address Lists' .
    Με την παραπάνω διαδικασία μπορούμε να ξαναδημιουργήσουμε και να ενημερώσουμε την OAB τόσο στον server όσο και στους clients.
  18. i-away
    To Single Item Recovery είναι ένα “κρυφό” feature του  Exchange 2010 που ανήκει στο Exchange 2010’s Native Data Protection concept και μας επιτρέπει προστασία mailboxes χωρίς την ανάγκη ύπαρξης κάποιου Volume Shadow Copy Service (VSS) backup. Η συγκεκριμένη δυνατότητα υπήρχε και στις προηγούμενες εκδόσεις του Exchange και ήταν γνωστό ως dumpster , στον 2010 όπως θα δούμε έχει βελτιωθεί αισθητά αποκτώντας νέες δυνατότητες και λειτουργίες.
    Για όσους δεν θυμούνται την λειτουργία του dumpster όταν ο χρήστης έσβηνε ένα mail χωρίς shift+delete αυτό πήγαινε στον Deleted Items folder όταν αυτός γινόταν purge το mail εξαφανιζόταν τελέιως απο το mailbox του χρήστη. Παρόλα αυτά ο χρήστης μπορούσε να το επανακτήσει μέσα σε ένα χρονικό διάστημα που οριζόταν απο τον administrator.
    Ο χρήστης μπορούσε να το επανακτήσει απο τον Recover Deleted Items folder. Τα μειονεκτήματα αυτής της διαδικασίας ήταν ότι το μέγεθος του dumpster δεν μετρούσε το συνολικό mailbox size και δεν μεταφερόταν κατά την διαδικασία mailbox move ( όπως πχ σε exchange migration ).
    Το κύριο χαρακτηριστικό του Single Item Recovery είναι ο Recoverable Items folder ο οποίος δεν είναι ορατός στους χρήστες μέσω του Outlook. Μπορούμε να δούμε τα περιεχόμενα του μέσω του MFCMapi tool. Όπως βλέπουμε απαρτίζεται απο 3 υποφακέλους.

     
     
    Ακολουθώντας την ίδια διαδικασία διαγραφής μηνύματος βλέπουμε ότι το μήνυμα ακολουθεί την ίδια διαδρομή με το χρήστη να μπορεί να επαναφέρει τα μηνύματα. Η διαφορά έγκειται στο ότι αν ο χρήστης αδειάσει τον Recover Deleted Items folder τα μηνύματα μεταφέρονται στον Purges sub-folder όπου και παραμένουν αόρατα απο τον χρήστη , εμφανίζονται όμως κανονικά σε κάποιον που έχει τον ρόλο του compliance officer καθώς είναι και indexed αλλά και  discoverable και επίσης μεταφέρονται κατά την διαδικασία του mailbox move. Τα μηνύματα διαγράφονται τελείως μόλις περάσει το deleted item retention period ή το mailbox έχει τεθεί σε Legal Hold.
    Το Single Item Recovery εμφανίζεται και στον  Mailbox Role Requirements Calculator επηρεάζοντας μάλιστα δραματικά τα μεγέθη των βάσεων ανάλογα με τις παραμέτρους που θα χρησιμοποιήσουμε.
    Απο default δεν είναι ενεργοποιημένο στον Exchange 2010 και ενεργοποιείται με την Set-Mailbox mailboxname –SingleItemRecoveryEnabled $true και όπως μας προείδοποιεί χρειάζεται μέχρι και 60 λεπτά για να ενεργοποιηθεί.
    Με την ανανεωμένο αυτό feature μειώνουμε κατά πολύ τον χρόνο ανάκτησης ενός μόνο χαμένου μηνύματος χωρίς να ανατρέχουμε σε point-in-time backups.
  19. i-away
    With the release of Exchange Server 2010 SP2 later this year, we will add a new feature known as Address Book Policies. Following this addition, hosters who wish to deploy the standard on-premises configuration of Exchange and use ABP will be supported.
    As you may have read in a recent post over on the Exchange Partner Marketing blog, our view on whether to host Exchange using Hosting Mode
    or the standard on-premises configuration is changing in response to
    feedback we’ve had from both hosters and customers. We recognize that
    the Hosting Mode configuration of Exchange we released as part of SP1
    provides a more robust multi-tenant solution, but lacks some of the features
    available in the standard on-premises configuration. Many of these are
    key features which customers are asking for, like Exchange Unified
    Messaging. We want to enable our hosting partners to offer the same rich
    feature set that our on-premises customers are used to. As such, with
    the release of SP2 for Exchange Server 2010, we intend to broaden our
    support stance to include hosting the on-premises configuration of
    Exchange in a multi-tenant environment.
    To be eligible for
    support, hosters will need to adhere to a few configuration guidelines; a
    framework we will publish in conjunction with SP2. The framework will
    outline the configuration challenges of hosting Exchange in a
    multi-tenant environment which need to be solved, and provide general
    direction for developing solutions in the most supportable way. Let’s
    consider a couple of examples:
    As I
    mentioned earlier, the Address Book Policy feature is a key reason that
    we will be able to support hosters using the on-premises configuration
    if they are using SP2. The framework will specify that directory
    segmentation should be done using Address Book Policies, not by a series
    of Allow/Deny ACE’s on Address List objects. For
    provisioning, the framework will specify that the creation of objects
    (such as a tenant organization or a mailbox) in Active Directory and
    Exchange should use our standard built-in tools, PowerShell cmdlets, and
    documented APIs. Code should not be written to create objects directly in Active Directory or Exchange, bypassing these standard tools. An
    automation vendor or a hoster, should they choose to, will be able to
    build their own automation tools using this framework. The easiest and
    quickest route to support for most hosters, though, will likely be
    through engaging with a hosting automation vendor whose solution adheres
    to the guidelines. In order to help service providers quickly find the
    right automation software, in the SP2 timeframe we will publish a list
    of solutions which follow the framework (and thus are eligible for
    support). These solutions will be validated by Microsoft in much the
    same way that we currently validate load balancing solutions.
    I’ll hasten to add that this will not be a formal certification
    process, but instead will be an assurance to our customers that we have
    worked with the vendor and are satisfied that it conforms to the
    framework.
    So, what does this mean for you today
    if you want to use the on-premises configuration of Exchange to host
    mailboxes for your customers in a multi-tenant environment?
    If
    you need to deploy prior to SP2, we recommend that you work with an
    automation vendor and use their solution. Your vendor of choice will be
    your only source of support. Your vendor will hopefully have plans to
    update their solution for SP2 per the soon-to-be-published framework, at
    which time you will have a path to being supported by Microsoft once
    you’ve upgraded your infrastructure. If you plan to deploy
    post SP2, and you intend to use an automation solution from an
    automation vendor, you should ensure your chosen vendor is working with
    us to validate their solution and deploy when that solution is ready. If
    you plan on building your own solution using the standard on-premises
    configuration of Exchange, you should consider waiting for SP2 to ship
    and then develop your solution following the framework to ensure you
    receive the best level of support from Microsoft. We hope
    this announcement is good news for those hosting Exchange, as it
    provides you with more options in your deployment and will help you
    obtain support when you need it.
    We look forward to hearing your feedback and as you know, we do act on it.


    Source

  20. i-away
    Earlier today the Exchange CXP team released Update Rollup 5 for Exchange Server 2010 SP1 to the Download Center.
    This update contains a number of customer-reported and internally found issues since the release of SP1. See 'KB 2582113: Description of Update Rollup 5 for Exchange Server 2010 Service Pack 1' for more details.
    We want to let you know this rollup contains the Exchange 2010 SP1 version of the change described in this KB article:
    2543879
    PDF attachment from a Mac Mail client is not displayed when you use
    Outlook 2010 to open the email message in an Exchange Server 2007 SP3
    environmentWe would also like to specifically call out the following fixes which are included in this release:
    2556352 MoveItem returning empty ChangeKey 2555850 Unable to delete a folder whose name has a particular character code 2490134 OWA's zip-download does not work for some messages due to invalid chars in the subject 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.
    Availability of this update on Microsoft Update is
    planned for late September. Update Rollup 6 for Exchange Server 2010
    Service Pack 1 is currently scheduled to release in October 2011.
    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.


    Source: Exchange Team Blog


    Προσοχή όπως πάντα στο Antivirus.

  21. 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.
  22. 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.
  23. i-away
    Struggling to find an overview of how what the latest EAS features
    are? Planning your migration from Exchange 2003 and looking for a basic
    introduction to Database Availability Groups? These videos are for
    you!
    The Microsoft Exchange team has produced a new portfolio of
    videos designed to give customers a fundamental technical education on
    Exchange Server 2010. There are currently seven videos in the series
    covering the following topics:
    Archiving and Discovery Mailbox Resiliency Management Mobility Outlook and Exchange Outlook Web App Unified Messaging The
    objective of the video series is to provide an introductory curriculum
    for IT professionals to learn more about the benefits of Exchange Server
    2010. While TechNet provides great technical documentation at a more
    granular level, this video series should help bridge the gap for those
    who are new to Exchange 2010 and still trying to learn about the
    technical fundamentals of the product.
    Each
    video runs 20-30 minutes long and includes an overview of the workload
    as well as a technical demonstration of 3-4 core scenarios related to
    that workload. The “Exchange Server 2010 Technical Video Series” is
    hosted by Ann Vu and presented by subject matter experts from the
    Microsoft Exchange team. You can find these videos on the front page of
    Exchange Server TechCenter on TechNet.
    Please
    help us evangelize these videos to anyone who wants to learn more about
    Exchange Server 2010 and let us know your thoughts. As always, your
    feedback is extremely valuable to us. Many thanks in advance!


    Source:Steven Chew
  24. i-away
    We’ve been sharing updates on Windows Thin PC (WinTPC) for
    some time now and are excited to announce that today WinTPC reached its RTM
    milestone and will become generally available for download on July 1, 2011.

    As we’ve been talking about, customers told us that they want an easy way to
    repurpose their existing PCs as thin clients. WinTPC makes this a reality and
    plays a part in our broader desktop virtualization strategy , which is to
    deliver the flexibility to work from everywhere, improve compliance and business
    continuity, and simplify management so that IT professionals can deliver better
    service to employees.

    With the above goal in mind we created WinTPC to help customers repurpose
    their PCs as thin clients, thereby driving down the cost of VDI. We used
    additional feedback gathered from customers in our Community Technology Preview
    (CTP) to add a few features in the RTM.


    Keyboard Filter: WinTPC will have the capability to allow customers
    to lock certain key combinations, such as Ctrl +Alt + Delete, from being
    utilized and taking effect on a Windows Thin PC device, thereby providing
    customers with greater level of security and control over user interaction with
    their WinTPCs.
    International IMEs (Input Method Editor) support: WinTPC will now
    include the option to support international keyboards.
    Key Management Server (KMS)/Multiple Activation Key (MAK): WinTPC
    will now be able to activate against a customer’s existing KMS server or use MAK
    keys, which enables quick and easy activation mechanisms that customers already
    use for their Windows desktops today.
    Ultimately, the goal with the final version of WinTPC is to enable customers
    to extend existing investments in hardware and software for their VDI
    environments, so that, where appropriate, thin client computing becomes a
    natural part of their overall desktop strategy. And there is demand in the
    industry for this capability, according to recent survey published by Gartner
    nearly 60% of respondents indicated that they are interested in reconfiguring
    existing PCs as thin clients when asked “Is your organization planning to use
    existing clients/PCs for HVD, or will they purchase new client hardware?”
    (Source: Gartner, Survey Analysis: 2010 Data Center Conference, x86
    Virtualization and Hosted Virtual Desktops Driven by Business Agility, Not by
    Cost Savings. February 2011, Note: Number of respondents equals 182 -
    multiple responses allowed).

    With the customer feedback through our CTP, we also had the opportunity to
    work with a few customers to test WinTPC and put it through the paces. One was
    Deluxe Corporation, a $1.4 billion financial services company with locations in
    the United States, Canada and Ireland, who worked closely with us during product
    development. Deluxe is known as a dynamic organization that combines innovation
    with integrity and found that WinTPC was exactly what they were looking for.


    We talked with Scott Valeri, Manager of Enterprise Desktop & Mobile
    Architecture & Engineering at Deluxe who said, "WinTPC is a strategic tool
    within our desktop deployment model and is the next natural step in our thin
    client computing strategy, as we evaluate ways to providing a rich Windows
    experience from both fixed and mobile thin PCs. WinTPC enables [us] to leverage
    existing investments in PCs as well as new investments in Thin PCs equipped with
    Atom CPUs. As Deluxe Corporation migrates additional users to virtual desktops,
    WinTPC will be the primary operating system used to reach virtual desktops."

    In addition to Deluxe Corporation, we also received feedback from other
    customers. We have tried to answer a lot of your questions through the WinTPC site, but would like to touch upon a few
    frequently asked questions that have come up over the course of the beta
    program.

    Q: Will WinTPC be supported by Forefront Endpoint Protection
    (FEP)?

    A: Another key piece of feedback we received from customers is the
    need for Forefront Endpoint Protection (FEP) support for WinTPC. Today, I am
    happy to announce that FEP support will be coming to WinTPC in Q3 CY2011, which
    is in the same quarter as the GA for WinTPC. Customers will be able to extend
    their investments with FEP to WinTPC, unifying their anti-malware strategy
    across PCs and WinTPCs.

    Q: Will customers be able to run applications on WinTPC?

    A: WinTPC is designed to be a thin client device, and therefore only
    applications that fall into the certain categories are enabled. These categories
    include security, management, terminal emulation, Remote Desktop and similar
    technologies, web browsers, media players, instant messaging clients, document
    viewers, NET Framework and Java Virtual Machine. If customers want to locally
    run productivity applications such as Microsoft Office, or any other application
    that does not fall into the categories mentioned above, they would be better off
    using a PC, as thin client computing may not be the best fit for their
    scenarios.

    Q: How can I extend my management to WinTPC?

    A: Management is a critical component of any desktop virtualization
    strategy and you should be able to leverage existing infrastructure wherever you
    can to reduce complexity and we believe this holds true for the access device as
    well. WinTPC can be managed using your existing System Center Configuration
    Manager deployment, thereby ensuring that you are able to leverage existing
    investments in technology, processes and expertise. Additionally, the new Windows Embedded Device Manager 2011 helps simplify
    management of devices where write filters are turned on.

    Q: Will I be able to use Citrix Receiver with WinTPC?

    A: As discussed in previous posts, Microsoft and Citrix work closely
    together to bring you a complete desktop virtualization solution and WinTPC is
    no different. We are happy to let you know that our partnership is here for you
    once again and we’ve made sure the WinTPC and Citrix’s Receiver technology work
    together, so if you’re accessing XenApp or Xendesktop via WinTPC you’ll have a
    great experience!

    We want to say thank you to everyone for the interest in WinTPC over the past
    few months – we value the feedback and encourage you to continue giving us your
    thoughts in the comment section below. For more information, check out the WinTPC site.

    Also, if you didn’t enroll in the beta program but can’t wait until it
    becomes generally available to try it out, no need to worry. You can still
    register and download the beta software from http://connect.micrsoft.com until July 1.v
     
    Source.
     
    Ps: Future Forecast : Thin Weather and Clouds...Stay Tuned!
  25. i-away
    Recently, some customers reported that when they create a DAG, they get a
    warning message that states the following:




    The Exchange Trusted Subsystem is not
    a member of the local Administrators group on specified witness server
    <ServerName>.

    In these cases, the customer’s intended witness server was not an Exchange
    2010 server. As documented in TechNet, if the witness server you specify isn't an Exchange
    2010 server, you must add the Exchange Trusted Subsystem (ETS) universal
    security group (USG) to the local Administrators group on the witness server.
    These security permissions are necessary to ensure that Exchange can create a
    directory and share on the witness server as needed.

    After some inspection, the customers confirmed that, contrary to the error
    message, the ETS USG was a member of the local administrators group on their
    intended witness server. Moreover, even though this warning appeared, there
    were no ill effects in functionality. The directory and share on the witness
    server were created as needed, the file share witness cluster resource was
    online, and the DAG passed all replication health checks.

    After hearing about this, I went to my lab to test this, and I was able to
    reproduce the issue. I added the ETS USG to the local administrators group on
    my witness server (a Windows 2008 file server) and ran
    New-DatabaseAvailabilityGroup, specifying my witness server. I received the
    same warning message, and verified that despite the message, all was perfectly
    healthy with the DAG, and there were no permission problems, witness server or
    cluster problems or other issues.

    Even though it appeared as though this warning message could be safely
    ignored, I wondered why we were getting it in the first place. So I went
    digging into the source code to find out.

    Let me describe what is happening and why you, too, can safely ignore the
    warning message.

    During various DAG-related tasks that configure witness server properties
    (namely, New-DatabaseAvailabilityGroup, Set-DatabaseAvailabilityGroup and
    Restore-DatabaseAvailabilityGroup), the code is actually checking to see if the
    witness server is a member of the Exchange Trusted Subsystem USG.

    As you may know, there is no requirement that the witness server be a
    member of the ETS USG. Nonetheless, the code for these tasks does check for
    this, and if it finds that the witness server is not a member of the ETS USG, it
    issues a warning message.

    Unfortunately, to confuse things even more, the warning message says:




    The Exchange Trusted Subsystem is not
    a member of the local Administrators group on specified witness server
    <ServerName>.

    It says nothing about the witness server not being a member of the ETS USG,
    even though the code is checking for that. Instead, it makes it appear as
    though the permission perquisites have not been satisfied, even though they
    actually have.

    But, even though the message does not pertain to the actual check that
    failed, that does not make this a string bug. This is a code bug, as there is
    no requirement that the witness server be a member of the ETS USG. Thus, the
    code should not be checking for this condition. If this bug is fixed and the
    check is removed, the string will be removed with it. Unless and until that
    happens, if you are seeing this warning message
    when you are using any of the above-mentioned tasks, and you have verified that
    the ETS USG is a member of the local administrators group on your witness
    server, then you can likely safely ignore the warning message.
    You should run Test-ReplicationHealth to verify
    the health of the DAG once members have been added to it.

    Because we are doing this check in code, you can of course add the witness
    server to the ETS group, and also make the ETS group a member of the local
    administrators group on the witness server, and all of these tasks will complete
    without this warning message. But, don't do that in production because (1) it
    is not needed and (2) it gives the witness server way more permissions
    than it should ever have (unless of course, the witness server is an
    Exchange 2010 server).
×
×
  • Create New...