Jump to content

i-away

Members
 View Profile  See their activity

  • Posts

    462

  • Joined

  • Last visited

 Content Type 

Blog Entries posted by i-away

  2. i-away
    Όπως έγινε γνωστό το Office 365 χρησιμοποιεί για την εξυπηρέτηση των χρηστών του τα λεγόμενα CDN ή Content Delivery Networks. Το πλεονλεκτημα της χρήσης ενός τέτοιου αποκεντρωμένου δικτύου είναι η δυνατότητα και η ταχύτητα που προσφέρει στους χρήστες τους να κατεβάζουν το περιεχόμενο που τους ενδιαφέρει γρήγορα και με μεγάλη ταχύτητα.
    Περισσότερα μπορείτε να διαβάσετε εδώ
    Filed under: Uncategorized
     
    Source
  3. i-away
    Today we reached an important milestone in the development of the new Exchange.
    Moments ago, the Exchange engineering team signed off on the Release to Manufacturing (RTM) build. This milestone means the coding and testing phase of the project is complete and we are now focused on releasing the new Exchange via multiple distribution channels to our business customers. General availability is planned for the first quarter of 2013.
    We have a number of programs that provide business customers with early access so they can begin testing, piloting and adopting Exchange within their organizations:
    We will begin rolling out new capabilities to Office 365 Enterprise customers in our next service updates, starting in November through general availability. Volume Licensing customers with Software Assurance will be able to download Exchange Server 2013 through the Volume Licensing Service Center by mid-November. These products will be available on the Volume Licensing price list on December 1. Since announcing the Preview of the new Exchange back in July, the EHLO team has been actively blogging about the features and capabilities of the new Exchange. We’re excited to start getting the finished product into the hands of our customers!


    Stay tuned....

  4. i-away
    the Exchange CXP team released Update Rollup 4 for Exchange Server 2010 SP2 to the Download Center.
    This update contains a number of customer reported and internally found issues. See KB 2706690 Description of Update Rollup 4 for Exchange Server 2010 Service Pack 2 for more details.
    In particular we would like to specifically call out the following fixes which are included in this release:
    Note: Some of the following KB articles may not be available at the time of publishing this post.
    New updates for August DST - Exchange 2010 - SP2 RU4 - Display name for OWA. 2685001 Retention policies do not work for the Calendar and Tasks folders in an Exchange Server 2010 SP1 environment 2686540 Exchange 2010 Messages are not delivered to Journal Mailbox 2701162 Granting Full Mailbox Access Does Not Allow Full Details of Free/Busy To Be Displayed 2724188 Information loss due to unexpected subject modification while copying a message in Outlook 2743871 Stop Forefront services in RU setup so no manual steps are required 2743246 MS12-058: Vulnerability in Microsoft Exchange Server WebReady document viewing could allow remote code execution For DST Changes: http://www.microsoft.com/time
    Exchange Team
  5. i-away
    This update contains a number of customer reported and internally found issues. See KB 2734323 Description of Update Rollup 8 for Exchange Server 2007 Service Pack 3.
    In particular we would like to specifically call out the following fixes which are included in this release:
    Note: Some of the following KB articles may not be available at the time of publishing this post.
    New updates for August DST - Exchange 2007 – SP3 RU8 2701037 Store.exe crash by strcat_s() to Exchange 2007 2699574 Microsoft Exchange Information Store service may stop responding when you perform a search on Exchange mailboxes in an Exchange Server 2007 environment 2743243 MS12-058: Vulnerability in Microsoft Exchange Server WebReady document viewing could allow remote code execution For DST Changes: http://www.microsoft.com/time
    Exchange Team
  6. i-away
    Ήρθε λοιπόν η ώρα να ξεκινήσουμε την εγκατάσταση του Exchange 2013 . Προτού το κάνουμε όμως αυτό ας δούμε κάποια prerequites που απαιτούνται.
    Ο Exchange μπορεί να εγκατασταθεί στα παρακάτω λειτουργικά:
    Mailbox and Client Access server roles
    Windows Server 2012 Windows Server 2008 R2 Standard with SP1 Windows Server 2008 R2 Enterprise with SP1 Windows Server 2008 R2 Datacenter RTM or later Management tools
    Windows Server 2012 Windows Server 2008 R2 Standard with SP1 Windows Server 2008 R2 Enterprise with SP1 Windows Server 2008 R2 Datacenter RTM or later 64-bit edition of Windows 8 Release Preview 64-bit edition of Windows 7 with SP1 Εδώ να σημειώσουμε ότι ανάλογα με την έκδοση του λειτουργικού απαιτούνται κάποιες παραπάνω ενέργειες.
    Στην εγκατάσταση αυτή χρησιμοιήθηκε η έκδοση 2012 του Windows Server Release Review.
    Αν και υπάρχει η δυνατότητα να γίνει απο το καινούργιο γραφικό περιβάλλον εγκατάστασης προτίμησα το παλιό παραδοσιακό command-line τρόπο.
    Στην περίπτωση μου έπρεπε να απεγκαταστήσω το Visual C++ 11 Beta Redistributable (x64) διότι η εγκατάσταση σταματούσε με error.
    Βήμα 1. Εγκατάσταση του RSAT


    Βήμα 2. Εγκατάσταση των απαραίτητων IIS στοιχείων


















    Βήμα 3. When the feature is completed. Continue with the installation of the required components, use the links below to download the components.


    .NET Framework 4.5 RC ( υπάρχει ήδη στον WS2012 )


    Windows Management Framework 4.0 ( υπάρχει ήδη στον WS2012 )


    Unified Communications Managed API 4.0, Core Runtime 64-bit


    Office 2010 Filterpack x64


    Office 2010 Filterpack SP1 x64


    KB 974405 (Windows Identity Foundation) ( υπάρχει ήδη στον WS2012 )


    KB 2619234 (RPC over HTTP)


    KB 2533623 (Remote code execution)










    Η εγκατάσταση ξεκινάει και έχουμε αναλυτικές πληροφορίες για το κάθε βήμα. Μετά το τέλος της εγκατάστασης μας ζητάει επανεκίνηση.




    Βήμα 5. Εγκατάσταση του CAS server role












    Μετά την επανεκίνηση που θα ζητηθεί η βασική εγκατάσταση του Server έχει ολοκληρωθεί.


    Στο επόμενο blog post θα συνεχίσουμε με το βασικό configuration του Exchange 2013.



  7. i-away
    Μετά απο μήνες κάτω απο βαρύ πέπλο μυστικότητας η Microsoft αποκάλυψε την Public Beta έκδοση του Exchange 2013. Πολλές και σημαντικές αλλαγές σε όλα τα επίπεδα ενσωματώνοντας παράπονα,feedback και προτάσεις του κόσμου.
    Ας ξύσουμε λίγο την επιφάνεια παρουσιάζοντας κάποια βασικά πράγματα που θα αναλύσουμε περαιτέρω προχωρόντας στα ενδότερα του server.
    Αρχιτεκτονική
    Με την εμφάνιση του Exchange Server 2007 η Microsoft χώρισε τις υπηρεσίες του Exchange Server σε πολλαπλούς ρόλους κυρίως λόγω των περιορισμένων δυνατοτήτων του hardware της εποχής. Η κατάσταση αυτή εξακολούθησε και στις αρχές του 2010 με την αλματώδη όμως ανάπτυξη του hardware τα πράγματα άλλαξαν και μπορούσαμε να συνδυάσουμε πλέον τους ρόλους.
    Τώρα όμως στον Exchange Server 2013 έρχεται η αλλαγή… Ο αριθμός και η λειτουργία των ρόλων αλλάζει άρδην. Πλέον υπάρχουν 2 ρόλοι: ο Client Access Server και ο Mailbox Server.
    Ο Client Access Server λειτουργεί μόνο ως proxy συνδυάζοντας τις λειτουργίες των άλλων ρόλων.
    Λογω αυτών των αλλαγών η σχέση μεταξύ Client Access Server και Mailbox Server γίνεται πιο χαλαρή. Το σημαντικό εδώ είναι ότι λόγω των περιορισμών του RPC protocol, πάρθηκε η απόφαση να δοθεί βάρος στο direct client connectivity. Αυτό πρακτικά σημαίνει ότι οι clients συνδέονται πλέον μόνο με HTTP (RPC over HTTP).
    Μερικά απο τα καλά αυτής της αλλαγής είναι τα ακόλουθα:
    Δεν χρειάζονται πλέον πανάκριβοι Hardware Load Balancers. Το απλό DNS Round-Robin πλέον αρκεί. Επίσης ελατώνονται κατά πολύ τα namespaces που χρησιμοποιούμε. Store improvements
    Μετά απο πολλές συζητήσεις και παράπονα για το πότε θα γίνει η πολυπόθητη μετάβαση στην SQL. Το product group ξαναέγραψε τον κώδικα του store χρησιμοποιώντας C# . Αυτό επιτρέπει μεγαλύτερο granularity για αυτό και πλέον το store ονομάζεται “Managed Store”. Ο νέος σχεδιασμός καταφέρνει να ξεπερναέι σε perfomance τον SQL σε επίπεδο typical transactions που εκτελούνται σε μια Exchange Database. Επίσης πλέον κάθε database τρέχει σε δικό της αποκλειστικό worker process πράγμα που σημαίνει ότι ενδεχόμενο πρόβλημα σε μια database δεν επηρεάζει την λειτουργία των άλλων databases ή του Exchange.
    Indexing & Searching
    Η μεγάλη αλλαγή εδώ είναι η ενσωμάτωση του FAST στο Managed Store για καλύτερη λειτουργία search & indexing.
    High Availability
    Το παλιό καλό Database Availability Group (DAG) παραμένει με κάποιες αλλαγές όσον αφορά τον έλεγχο των passive nodes και το γρηγορότερο faster fail-over.
    Management
    “Exchange Management Console is no more!”. Αυτό είναι το σύνθημα της ανανέωσης στο τομέα του Management. Η παλιά κονσόλα αντικαταστάθηκε απο την Exchange Administrative Console (EAC) η οποία είναι web-based και πλέον είναι προσβάσιμη απο παντού προσφέροντας αναβαθμισμένες δυνατότητες σε σχέση με την παλιά.
    (Modern) Public Folders
    Για πολλά χρόνια η Microsoft προσπαθούσε να πείσει τους χρήστες να εγκαταλείψουν την χρήση των Public Folders αλλά παρόλα τα μειονεκτήματα τους πολλοί εξακολουθούσαν να τους χρησιμοποιούν. Δυστυχώς όμως δεν μπορούσαν να εκμεταλλευτούν χαρακτηριστικά όπως το Database Availability Group.
    Αυτό όμως τώρα αλλάζει καθώς τα Public Folders μεταφέρονται σε Public Folder mailboxes. Αυτό πρακτικά σημαίνει ότι πλέον βρίσκονται σε mailbox databases και επομένως μπορούν να αξιοποιήσουν όλα τα χαρακτηριστικά των κανονικών βάσεων όπως για παράδειγμα το DAG protection.
    Site Mailboxes
    Τα Team Mailboxes πλέον ενοποιούν το collaboration μεταξύ του SharePoint και του Exchange Server επιτρέποντας μας την πλήρη διαχείρηση items του SharePoint απευθείας από Outlook, OWA ή SharePoint.
    Outlook Web App
    Πολλές αλλαγές έχουμε και εδώ. Πλέον το Metro-style εφαρμόζεται παντού με στόχο το ενοποιημένο περιβάλλον μεταξύ tablets,pcs και mobile devices.
    Μερικές απο τις μεγάλες αλλαγές είναι οι εξής:
    Offline Access. Αυτό μας επιτρέπει την πλήρη αποθήκευση όλου του mailbox μας στην offline cache του browser. People-centric: Κάτι παρόμοιο με το “People Hub“ των Windows Phone OWA Extensibility. 3rd-party applications για καλύετρο user experience. Ενδεικτικά υπάρχουν ήδη έτοιμα ( Linkedin,Hertz,Bing Maps,Κλπ) και ο αριθμός αυτός αυξάνεται συνέχεια.
    Compliance & Discovery Ίσως απο τις πιο σημαντικές αλλαγές-βελτιώσεις έρχονται εδώ. Πρόσφατα ανακοινώθηκε μια αλλαγή στο licensing η οποία μας δίνει την δυνατότητα multi-mailbox search χωρίς την ανάγκη ύπαρξης Enterprise CAL.
    Τι πλεονέκτημα μας δίνει αυτό:
    Search μεταξύ primary mailbox και archive στο OWA Personal tags στους default folders του OWA Improved Discovery “Federated Discovery” που επιτρέπει search μεταξύ Exchange, Lync και SharePoint.
    Και οι αλλαγές-βελτιώσεις δεν σταματούν εδώ. Στα επόμενα blog post εγκαθιστώντας και αναλύοντας τις λειτουργίες του Exchange θα κάνουμε εκτενέστερη αναφορά .

    Εδώ να τονίσω ότι τα Blog post αναφέρονται στις δυνατότητες της Public Beta έκδοσης. Λόγω NDA δεν μπορώ να αποκαλύψω περισσότερες λεπτομέρειεσ-δυνατότητες πέραν αυτόν που είναι δημόσια διαθέσιμες.

    Stay tuned.. για περισσότερα συναρπαστικά post

  8. i-away
    Πριν απο λίγο έγινε διαθέσιμη η έκδοση του Exchange 2013!! . Πολλά μα πολλά καινούργια χαρακτηριστικά έρχονται να μας αλλάξουν τα πάντα...
     
    Stay tuned....
     

    The
    next version of Exchange enables you to increase user productivity and
    keep your organization safe, while maintaining the control you need.
    How to try
    Office 365 Enterprise Preview
    Try it | Learn more Exchange Server 2013 Preview
    Try it Remain in control, online and on-premises
    Exchange
    enables you to tailor your solution based on your unique needs and
    ensures that your communications are always available, while you remain
    in control, on your own terms—online, on-premises, or a hybrid of the
    two.
    Move to the cloud on your terms with flexible options, including Exchange hybrid deployment.
    Exchange provides you tools to move to the cloud on your terms,
    whether that's onboarding to the cloud overnight or managing a hybrid
    deployment with mailboxes on-premises and online. Limit user disruption
    when mailboxes are smoothly moved across environments and enable users
    to share calendars and schedule meetings, regardless if they are online
    or on-premises. Try out upcoming enhancements in the cloud, with support
    for upgrade roll-backs and previews.
    Decrease the amount of time spent managing your messaging systems while maintaining control.
    Manage powerful capabilities, including Data Loss Prevention (DLP) and
    site mailboxes, from the Exchange Administration Center (EAC)—a single,
    easy-to-use, web-based administration interface. Role-based access
    control empowers your helpdesk and specialist users to perform specific
    tasks without requiring full administrative permissions. This
    streamlined and intuitive experience helps you manage Exchange
    efficiently, delegate tasks, and focus on driving your business forward.
    Keep all of your important data in one place with Exchange archiving, large mailboxes, and retention policies.
    Empower your users with a large mailbox to allow them the flexibility
    to retain email in their primary mailbox or move items to an in-place
    archive. With flexible and powerful retention policies, you can take
    control of your storage and compliance demands while keeping your users
    productive.
    Increase productivity
    Exchange
    enables your users to be more productive by helping them manage
    increasing volumes of communications across multiple devices and work
    together more effectively as teams.
    Give your users an intuitive, touch-enabled inbox experience.
    Your users can get more done from anywhere with a clean, uncluttered
    inbox that focuses on the relevant and important information.
    Allow your users to work better together on teams and projects.
    Site mailboxes enable your users to collaborate on projects, get up to
    speed quickly on teams they join, and share information easily.
    Co-authoring, document storage, and versioning is provided by
    SharePoint, while messaging is handled by Exchange with a complete user
    experience, including document access, within Outlook.
    Customize Exchange by integrating web-based apps for Outlook and Outlook Web App.
    Help your users spend less time switching between apps and make their
    communications experience more powerful with an extension model that
    allows you to provide easy plug-in access to web-based apps within both
    Outlook and Outlook Web App. With single sign-on to multiple apps, you
    can reduce complexity for users and give them secure, authorized access
    for each approved application.
    Keep your organization safe
    Exchange
    keeps your organization safe by enabling you to protect business
    communications and sensitive information in order to meet internal and
    regulatory compliance.
    Eliminate email threats before they reach your network. Exchange actively protects your communications with built-in defenses against viruses, spam, and phishing attacks.
    Protect your sensitive data and inform users of internal compliance policies.
    Prevent users from mistakenly sending sensitive information to
    unauthorized people. Data Loss Prevention (DLP) features identify,
    monitor, and protect sensitive data through deep content analysis, and
    PolicyTips in Outlook inform users about policy violations before
    sensitive data is sent. Built-in DLP policies are based on regulatory
    standards such as PII and PCI, plus Exchange can support other policies
    important to your business.
    Enable your compliance officers to run In-Place eDiscovery across Exchange, SharePoint, and Lync from a single interface.
    Ensure internal and regulatory compliance by using the new eDiscovery
    Center to identify, hold, and analyze your organization's data from
    Exchange, SharePoint, and Lync. The data always remains in place, so you
    never have to manage a separate store of data.
     
    http://www.microsoft.com/exchange/en-us/exchange-preview.aspx
     
  10. i-away
    We're happy to announce that the Exchange Server Deployment Assistant (ExDeploy) has been enhanced to include support for configuring hybrid deployments using Exchange 2010 SP2 and the Hybrid Configuration Wizard.
    The first in several upcoming scenario additions for configuring hybrid deployments when using the Hybrid Configuration Wizard, this new scenario is for Exchange 2003 organizations interested in maintaining some users on-premises and some users hosted in the cloud by Microsoft Office 365 for enterprises. Although limited, interim hybrid deployment configuration support for Exchange 2007 and 2010 on-premises deployments is also included with this update, complete hybrid deployment checklists for the Exchange 2007 and 2010 on-premises scenarios are in progress and will be released soon. Watch this space for announcements about upcoming Exchange 2007 and 2010 hybrid deployment scenario updates.
    The new hybrid information for Exchange 2003 environments is only available in English at this time and requires that you add Exchange 2010 SP2 servers to your current Exchange 2003 organization. If you have previously configured a hybrid deployment using the Deployment Assistant and Exchange 2010 SP1 and still need guidance; don’t worry, we haven’t forgotten about you! Previous Deployment Assistant checklists for configuring hybrid deployments with Exchange 2010 SP1 are now located here for your convenience.
    Hybrid deployments offer organizations the ability to extend the feature-rich experience and administrative control they have with their existing on-premises Microsoft Exchange organization to the cloud. It provides the seamless look and feel of a single Exchange organization between an on-premises organization and an Exchange Online organization. In addition, hybrid deployments can serve as an intermediate step to moving completely to a cloud-based Exchange Online organization. This approach is different than the simple Exchange migration (“cutover migration”) and staged Exchange migration options currently offered by Office 365 outlined here.
    About the Exchange Server Deployment Assistant
    The Exchange Server Deployment Assistant (ExDeploy) is a web-based tool that helps you upgrade to Exchange 2010 on-premises, configure a hybrid deployment between an on-premises and Exchange Online organization or migrate to Exchange Online.
    Figure 1:The Exchange Deployment Assistant generates customized instructions to help you upgrade to Exchange 2010 on-premises or in the cloud
    It asks you a small set of simple questions, and then based on your answers, it provides a checklist with instructions to deploy or configure Exchange 2010 that are customized to your environment. These environments include:
    Stand-alone on-premises Exchange installations and upgrades Hybrid deployment configurations and Cloud-only Exchange deployment scenarios. Besides getting the checklist online, you can also print instructions for individual tasks and download a PDF file of your complete configuration checklist.
    Your feedback is very important for the continued improvement of this tool. We would love your feedback on this new scenario and any other area of the Deployment Assistant. Feel free to either post comments on this blog post, provide feedback in the Office 365 community Exchange Online migration and hybrid deployment forum, or send an email to [email protected] via the Feedback link located in the header of every page of the Deployment Assistant.
    Exchange Deployment Assistant Team
     
    Source

  11. 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

  12. i-away
    Μετά απο ενδελεχή έλεγχο της ομάδας του Exchange το συγκεκριμένο update είναι ασφαλές για εγκατάσταση και προτείνεται να εγκατασταθεί το ταχύτερο δυνατό στους Exchange Servers
     
    Η σχετική ανακοίνωση είναι εδώ
     
  13. 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 να μπορέσει ο καθένας να
    το περάσει με τον καλύτερο δυνατό τρόπο, και πιστεύω πως έχει έρθει ο
    καιρός -υπό την πίεση των περιστάσεων- να κάνουμε όλοι μια
    επαναξιολόγιση των προτεραιωτήτων μας, να αναζητήσουμε άλλους -πολλές
    φορές ξεχασμένους- τρόπους να εκφραστούμε και να χαρούμε, ώστε να
    ξεπεράσουμε με τον καλύτερο τρόπο τις δυσκολίες, αλλά και τις προκλήσεις
    που θα βρούμε αναπόφευκτα μπροστά μας.
    ΚΑΛΗ ΧΡΟΝΙΑ ΣΕ ΟΛΟΥΣ!!!
  14. 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.

     
  15. 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

  16. 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
  17. i-away
    ’Οπως όλοι γνωρίζουμε το Online defrag είναι μια διαδικασία που εκτελείται συνεχώς στον Exchange Server. Τι γίνεται όμως με το offline defrag? Πρέπει να γίνεται? και αν ναι πότε?.
    Το offline defrag όπως όλοι ξέρουμε γίνεται με την εντολή eseutil /d. Το θέμα είναι όπως ανέφερα παραπάνω αξίζει το downtime που απαιτείται?
    Το σημείο αναφοράς μας είναι το event id: 1221.
    Event Type: Information
    Event Source: MSExchangeIS Mailbox Store
    Event Category: General
    Event ID: 1221
    Date: 24/10/2011
    Time: 18:36:16
    User: N/A
    Computer: EX01
    Description: The database “First Storage Group\Mailbox Store (EX01)” has 8 gigabytes of free space after online defragmentation has terminated.
    Ας εξηγήσουμε όμως τι πραγματικά συνέβη: Καθώς ο Exchange πραγματοποιούσε το καθημερινό routine maintenance του. Έσβησε όλα τα data που είχαν περάσει το delete threshold. Ο χώρος λοιπόν που έμεινε στην βάση μετά την διαγραφή ονομάζεται “white space”. Το “white space” χρησιμοποιείται απο τον Exchange, προτού αυτός προχωρήσει σε φυσική επέκταση της βάσης. Το παραπάνω σημαίνει ότι παρόλο που εμείς στον φυσικό δίσκο βλέπουμε το .edb αρχείο πχ στα 400GB τα actual data του μπορεί να είναι 280 GB. Τα υπόλοιπα GB θα χρησιμοποιηθούν απο τον Exchange καθώς μεγαλώνει η βάση μας χωρίς να απαιτείται επέκταση σε φυσικό επίπεδο.
    Bέβαια είναι καλό κατά τακτά χρονικά διαστήματα να κάνουμε και Offline defrag στην βάση μας έτσι ώστε να εκμεταλευόμαστε καλύτερα και τον φυσικό χώρο του δίσκου μας.
    Βέβαια πολλοί θα παρατηρήσετε ότι το event id 1221 δεν δείχνει πάντα τον ίδιο αριθμό. Αυτό οφείλεται στο γεγονός ότι η ροή των mail δεν είναι σταθερή και έτσι υπάρχει αυξομείωση τόσο στο white space όσο και στο Usable space της βάσης.
    Μπορούμε να δούμε το λογικό μέγεθος της βάσης με την εντολή eseutil /ms έχοντας πάντα το store offline. Συγκρίνοντας το με το φυσικό μέγεθος στον δίσκο έχουμε μια καλή ιδέα για το μέγεθος και την χρησιμοποίηση της βάσης μας.
     
    –
  18. 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





  19. i-away
    Στήνοντας έναν Exchange θα συναντήσετε σε κάποιο σημείο της εγκατάστασης τον όρο accepted domain. Στην περίπτωση που θέλετε ο Exchange σας να λαμβάνει μηνύματα απο τον έξω κόσμο θα πρέπει να ορίσετε μια διεύθυνση συνήθως της μορφής mail.company.gr. Μετά την εγκατάσταση θα παρατηρήσετε στην κονσόλα ότι υπάρχουν 3 τύποι απο Accepted Domains γεγονός που ίσως να μπερδέψει κάποιους. Ας τα δούμε λοιπόν αναλυτικά:
    Default Accepted Domain
    Όλα τα accepted domains ( ανεξαρτήτως τύπου ) τα βρίσκουμε σε 2 σημεία στον Exchange 2010:
    Στο Accepted Domains tab του Hub Transport node στο Organization Configuration Στο Accepted Domains tab του Edge Transport στον Edge Transport server role. Εάν ανοίξουμε την κονσόλα μετά το πέρας της εγκατάστασης θα παρατηρήσουμε ότι υπάρχει ήδη ένα accepted domain το οποίο δημιουργείται απο την εγκατάσταση του Exchange 2010. Θα παρατηρήσετε επίσης ότι ύπαρχει ο χαρακτηρισμός authoritative. Αυτός μαζί με τους internal relay και external relay είναι οι 3 τύποι accepted domain που μπορόυμε να έχουμε στον Exchange.
    Authoritative Domains
    To Authoritative accepted domain είναι ο πιο συνήθης τύπος που θα συναντήσουμε στον Exchange. Authoritative σημαίνει ότι για το συγκεκριμένο domain υπάρχουν mailboxes που φιλοξενούνται στον Exchange.Αυτό ουσιαστικά λέει στον Exchange αν δέχεται μηνύματα για το συγκεκριμένο domain.
    Πολλοί θα παρατηρήσουν ότι ακόμα και να μην ορίσουν αυτοί κάποιο accepted domain ό Exchange δημιουργεί αυτόματα ένα. Κατά της διάρκεια της εγκατάστασης ο Exchange δημιουργεί αυτόματα απο το forest root domain το αντίστοιχο accepted domain. Αυτό όμως πολλές φορές πρέπει να αλλάξει καθώς το εσωτερικό Domain name μας μπορεί να μην συμβαδίζει με το Εξωτερικό μας.



    Πως δημιουργούμε όμως ένα accepted domain; . Σε περίπτωση που χρειαστεί να δημιουργήσουμε ένα καινούργιο accepted domain αυτό μπορεί να γίνει εύκολα απο την Exchange Management Console στο σημείο του Organization Configuration στο σημείο των επιλογών του Hub Transport node. Επιλέγουμε New Accepted Domain και ακολουθώντας τον wizard ορίζουμε τις επιλογές που επιθυμούμε:
     
    Φυσικά όπως όλες οι Exchange ρυθμίσεις το παραπάπανω μπορεί να γίνει και με την χρήση Powershell με την εντολή:
    New-AcceptedDomain –Name Contoso –DomainName Contoso.com –DomainType (Authoritative,External Relay,Internal Relay).


  20. 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





  21. 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.
  22. 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 είναι μεγάλος και οι δυνατότητες του απεριόριστες. Εξερευνήστε τον και θα μείνετε έκπληκτοι
  23. 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.
  24. 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

  25. 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.

×
×
  • Create New...