Jump to content

Catastrophic Failure

Members
 View Profile  See their activity

  • Posts

    562

  • Joined

  • Last visited

 Content Type 

Blog Entries posted by Catastrophic Failure

  2. Catastrophic Failure
    If you already use Skype to stay in touch with friends and family in your life away from work, you'll appreciate the power and simplicity of Skype for Business where it's easy to find and connect with co-workers. And you can use the devices you already have to reach businesses through an enterprise-grade, secure, IT-managed platform. If you're coming to Skype for Business from Lync, you'll recognize all of the features you already use but in a fresh new interface with simplified controls and some great new additions:

    New look and feel

    Call from Skype for Business using your desk phone for audio

    Integration with the Skype directory

    Call Monitor

    Rate My Call

    Quick access to call controls

    Emoticons
    New look and feel
    If you’re a regular user of the commercial version of Skype, then Skype for Business will seem very familiar: the Contacts list, presence indicators, buttons and icons, and even the app sounds should make you feel right at home. Learn more.
    Of course, all the essential Lync features are still there—like the Quick Actions buttons, which let you IM or call a contact (and more) with just one click or tap.
    In the Skype Meeting window, the simplified arrangement of controls and menus makes it easy to find the command you need. In the conversation window, chat text is formatted so you can easily see who’s talking, and tabbed conversations allow you to keep track of several discussions at once.
    If you've ever had someone send you a file during an IM conversation, then file transfer preview is another feature of the new Skype for Business look and feel you'll appreciate. When someone sends you a file, select Download in the IM window to update the file's icon, or right-click or tap and hold to forward, preview, or delete it. Call from Skype for Business using your desk phone for audio
    Important This feature is available only if your organization has Skype for Business Server 2015.
    If you have a PBX (Private Branch Exchange) desk phone and your IT department has configured it to work with Skype for Business you can search for people in your organization and place calls to them from within the Skype for Business user interface, while audio for the call flows through your standard desk (PBX) phone. You can also place calls from the Skype for Business client using any phone near you (like your mobile, home, or hotel phone). The person you’re calling sees your phone number as though you were calling from your company's main phone number. When you make a Skype for Business call with audio routed through your desk phone, you get great audio, plus:

    IM—so you can do a quick copy/paste of a URL you want to share, for example

    Desktop and app sharing—so you can easily show and tell, work through problems, or explain stuff with visuals

    Attachments—send files to the other person without leaving Skype for Business
     


    Server admins enable and configure this feature for the enterprise. End users have limited configuration capabilities, which include turning the feature on or off for their individual account (once it's enabled at the enterprise level) and setting the phone number that Skype for Business should call. If the number has been set and locked by the administrator, then outgoing call options will be unavailable.
    For more information, see Make a Skype for Business call but use your PBX desk phone for audio Integration with the Skype directory
    Important This feature requires:

    Skype for Business Server 2015 or Skype for Business for Office 365

    The latest version of Skype
     

    Skype for Business users can connect over the Internet with hundreds of millions of Skype users right from the Skype for Business user interface. The first step is to search for your contact.

    In the search box on the Contacts view of the Skype for Business main window, type a name, IM address, or desk phone number (if they are in your organization). As you type, search results will start appearing below the search box and the tabs will change from Groups, Status, Relationships, and New:

    to My Contacts and Skype Directory:


    If the person you are searching for is in your organization, keep the My Contacts tab selected (that's the default). When My Contacts is selected, Skype for Business searches in your organization's address book.
    If the person you are searching for is not in your organization but you know they have a Skype account, click the Skype Directory tab to search for them among the millions of Skype users out there. Knowing their Skype ID and location helps narrow the search quickly. You can also search using their email address or Microsoft account (e.g., [email protected]).
    Note Your administrator enables or disables the Skype Directory search feature in accordance with your organization's search policy. If you don't see a Skype Directory tab like the one shown in the screen shot above, then you won't be able to search for Skype users.
     

    When you search for contacts in the Skype directory, you can add them to your contact list, have an instant messaging conversation, see their presence information, and have an audio or video call with them. Note that the Skype directory only contains contact information for Skype users, not Skype for Business users. A Skype user who wants to add a Skype for Business user to their contact list must use the Skype for Business user's full email address, such as [email protected]. Call Monitor
    Call Monitor is a popular Skype feature that's now available in Skype for Business. With Call Monitor, you can move back and forth between a full Skype for Business window, for those times when you're actively participating in the call, and a compact version that lets you continue to monitor call progress—and mute or end the call—while focusing on other tasks.
    The compact Call Monitor window appears during an audio or video call whenever the main conversation window is minimized. To show the full conversation window again, simply double-click or double-tap the Call Monitor. Rate My Call
    The Rate My Call feature lets Skype for Business Server 2015 administrators collect call data, access standard reports, and export raw data for further analysis. This feature is available for on-premises deployments only. Users are prompted to take a survey after completing a call. Quick access to call controls
    Access to the dial pad and call controls is much improved. For public switched telephone network (PSTN) calls, the dial-pad and call controls remain visible throughout the call. For non-PSTN calls, the dial-pad and call controls are accessible with one click. Emoticons
    Skype for Business now includes the same set of emoticons found in the consumer version of Skype. You can turn off emoticons in Skype for Business by going to Options > IM. No server setting is available. Related topics

    Lync Online is becoming Skype for Business

    Why do I see Skype for Business when I'm using Lync?
     

    Source: https://support.office.com/en-us/article/Lync-is-now-Skype-for-Business-%e2%80%94-see-whats-new-aba02d7e-c801-4a82-bccd-e7207240f612?ui=en-US&rs=en-US&ad=US
  3. Catastrophic Failure
    Get a first look at Exchange Server 2016, the on-premises release that we plan to ship in the second half of this year. Come learn about the innovation in Exchange Server 2016 that will help you keep up with evolving requirements for user productivity and information protection. This session will give you the starting point who want to know what’s coming from on-premises Exchange.
     

     
    Meet Exchange Server 2016
    http://channel9.msdn.com/Events/Ignite/2015/FND2204
  4. Catastrophic Failure
    Using Transport rules, you can look for specific conditions in messages that pass through your organization and take action on them. Transport rules let you apply messaging policies to email messages, secure messages, protect messaging systems, and prevent information leakage.
    Many organizations today are required by law, regulatory requirements, or company policies to apply messaging policies that limit the interaction between recipients and senders, both inside and outside the organization. In addition to limiting interactions among individuals, departmental groups inside the organization, and entities outside the organization, some organizations are also subject to the following messaging policy requirements:

    Preventing inappropriate content from entering or leaving the organization

    Filtering confidential organization information

    Tracking or archiving copying messages that are sent to or received from specific individuals

    Redirecting inbound and outbound messages for inspection before delivery

    Applying disclaimers to messages as they pass through the organization

    Overview of Transport rules
    Transport rules are similar to the Inbox rules that are available in many email clients. The main difference between Transport rules and rules you would set up in a client application such as Outlook is that Transport rules take action on messages while they’re in transit as opposed to after the message is delivered. Transport rules also contain a richer set of conditions, exceptions, and actions, which provides you with the flexibility to create a customized rule. You can create up to 100 Transport rules in order to implement your business-rule compliance.
    The following list summarizes the basic workflow for Transport rules:

    You create Transport rules to meet your business needs.

    As messages go through your organization, the Transport rules agent is invoked. The Transport rules agent is a special component that checks messages against the Transport rules you create.

    The Transport rules agent scans the message, and if the message fits the conditions you specify in a Transport rule, it takes the specified action on that message.

    Transport rule components
    Transport rules consist of the following components:

    Conditions   Use Transport rule conditions to specify the characteristics of messages to which you want to apply a Transport rule action. Conditions consist of one or more predicates that specify the parts of a message that should be examined. Some predicates examine message fields or headers, such as the To, From, or Cc fields. Other predicates examine message characteristics such as message subject, body, attachments, message size, and message classification. Most predicates require that you specify a comparison operator, such as equals, doesn’t equal, or contains, and a value to match.

    Exceptions Exceptions are based on the same predicates used to build Transport rule conditions. However, unlike conditions, exceptions identify messages to which Transport rule actions shouldn’t be applied. Exceptions override conditions and prevent actions from being applied to an email message, even if the message matches all configured conditions.

    Actions Actions are applied to messages that match the conditions and don’t match any exceptions defined in the Transport rule. Transport rules have many actions available, such as rejecting, deleting, or redirecting messages, adding additional recipients, adding prefixes in the message subject, or inserting disclaimers in the message body.

    For a complete list of Transport rule predicates, see Transport Rule Predicates. The list of predicates is also available in the Transport rule dialog in the EAC. If you use the Shell, you can retrieve the list of predicates by using the Get-TransportRulePredicate cmdlet.
    For a complete list of Transport rule actions available, see Transport Rule Actions. The list of actions is also available in the Transport rule dialog box in the EAC. If you use the Shell, you can retrieve the list of actions by using the Get-TransportRuleAction cmdlet.
    To create Transport Rules in Office 365, first must log into Office 365portal https://portal.microsoftonline.com/default.aspx and go to the following location:

    Go to Admin and choose Exchange



    2. Navigate to Mail Flow (from the left site) and choose Rules


    This is where any and all transport rules can be created and applied
    Once you are in the rules area of the O365 portal, you perform the following:

    1. Press the + sign and then select Create a new rule


    2. Choose a name for this rule and choose the rule for your condition (depends what you want to achieve)
    3. Choose the option that apply for your condition and after you finished click on Save



    4. Now, this rule is ready to be applied to all emails coming through your Office 365 tenant.
    For comprehensive information on Transport Rules as a whole, refer to the following link: http://technet.microsoft.com/en-us/library/dd351127(v=exchg.150).aspx

    Outlook Rules
    A rule is an action that Microsoft Outlook runs automatically on incoming or outgoing messages, based on conditions that you have specified.
    Rules help reduce manually filing or taking the same action when a similar message arrives. Unlike Quick Steps, rules typically are always on and run automatically. For example, when a message is received from a specified person, it’s automatically moved to the folder that you designate.
    The Rules Wizard helps you design rules to manage messages. Rules fall into one of two categories — organization and notification.



    The Rules Wizard includes templates for the most frequently used rules, which include the following:
    Stay Organized    These rules help you file and follow up on messages. For example, you can create a rule for messages from a specific sender, such as Anne Weiler, with the word “sales” in the Subject line, to be flagged for follow-up, categorized as Sales, and moved to a folder named Anne’s Sales.
    Stay Up to Date    These rules notify you in some way when you receive a particular message. For example, you can create a rule that automatically sends a message to a mobile device when you receive a message from a family member.
    Start from a blank rule    These are rules that you create without the aid of a rule template and that you can completely customize.

    Create a rule
    Outlook includes rule templates for common scenarios. Use these rule templates, or create design your own custom rules.

    1. Click the File tab, click Manage Rules & Alerts


    2. In the Rules and Alerts dialog box, on the E-mail Rules tab, click New Rule
    3. Follow the wizard and at the end click Finish


    Additional Information:
    Manage email messages by using rules
    http://office.microsoft.com/en-us/outlook-help/manage-email-messages-by-using-rules-HA102749402.aspx
  5. Catastrophic Failure
    Exchange Server 2013 SP1 Prerequisites (Exchange2013SP1Prerequisites_v1.0)
    This script automate execute steps for installing the necessary Windows Server 2012 R2 and Windows Server 2012 operating system prerequisites for the Microsoft Exchange 2013 Mailbox, Client Access, Multirole and Edge Transport server roles. The prerequisites that are needed to install Exchange 2013 on a Windows Server 2012 R2 or Windows Server 2012 computer depends on which Exchange roles you want to install.
     
    What do you need to know before you begin?
    o The Edge Transport server role is available starting with Exchange 2013 SP1.
    o Make sure that the functional level of your forest is at least Windows Server 2003, and that the schema master is running Windows Server 2003 with Service Pack 2 or later.
    o The full installation option of Windows Server 2012 R2 and Windows Server 2012 must be used for all servers running Exchange 2013 server roles or management tools.
    o You must first join the computer to the appropriate internal Active Directory forest and domain.
    o You must check and be sure your server has access to the internet
    o Some prerequisites require you to reboot the server to complete installation.
    Let’s have a quick look how to execute the script Exchange2013SP1Prerequisites_v1.0 on Windows PowerShell and what this script do for us.
     
    1. Login to Windows Server 2012 R2 and Windows Server 2012 with Enterprise Administrator credentials
    2. Start Windows PowerShell “As Administrator”
     

     
    3. Next step, copy the script Exchange2013SP1Prerequisites_v1.0 on (C:\) drive

     
    4. Let’s start with running scripts from within Windows PowerShell itself.
    In case you get weird error messages when you try to run a script, the reason is only one, security settings built into Windows PowerShell include something called the “execution policy” the execution policy determines how (or if) PowerShell runs scripts. By default, PowerShell’s execution policy is set to Restricted that means that scripts – including those you write yourself – won’t run.
    Navigate back to Windows PowerShell and set the Execution policy to unrestricted in order to be able to run the script, in that case, use this command to set your execution policy to RemoteSigned or Unrestricted
     

     
    Note: The Set-ExecutionPolicy cmdlet enables you to determine which Windows PowerShell scripts (if any) will be allowed to run on your computer.
    Windows PowerShell has four different execution policies:
    o Restricted – No scripts can be run. Windows PowerShell can be used only in interactive mode.
    o AllSigned – Only scripts signed by a trusted publisher can be run.
    o RemoteSigned – Downloaded scripts must be signed by a trusted publisher before they can be run.
    o Unrestricted – No restrictions; all Windows PowerShell scripts can be run.
    5. The most common (default) way to run a script is by calling it:
    PS C:\> & “C:\Admin\My first Script.ps1″
    If the path does not contain any spaces, then you can omit the quotes and the ‘&’ operator
    PS C:\> C:\Admin\Myscript.ps1
    If the script is in the current directory, you must indicate this using .\ (or ./ will also work)
    PS C:\> .\Myscript.ps1
     
    In our case scenario we run the script in the current directory “C:\” so, we must indicate this using .\ and we click Enter

     
    6. Our script now it starts running, select an option from the menu. In my case scenario, I will select option 3 (E2013 Multirole installation) and click Enter

     
    7. As you can easy check bellow, my Multirole Prerequisites are in progress to be download and install

     
    8. After the Prerequisites successfully installed, we have to choose the option 10 in order to restart our server

     
    9. After restart your server, login as EA and proceed to install your Microsoft Exchange Server 2013 SP1

     
    You can download the script here
    Enjoy…..
  6. Catastrophic Failure
    This script automate execute steps for installing the necessary Windows Server 2008 R2 SP1 operating system prerequisites for the Microsoft Exchange 2013 Mailbox, Client Access, Multirole and Edge Transport server roles. The prerequisites that are needed to install Exchange 2013 on a Windows Server 2008 R2 SP1 computer depends on which Exchange roles you want to install.
    What do you need to know before you begin?
    The Edge Transport server role is available starting with Exchange 2013 SP1.
    Make sure that the functional level of your forest is at least Windows Server 2003, and that the schema master is running Windows Server 2003 with Service Pack 2 or later.
    The full installation option of Windows Server 2008 R2 SP1 must be used for all servers running Exchange 2013 server roles or management tools.
    You must first join the computer to the appropriate internal Active Directory forest and domain.
    You must check and be sure your server has access to the internet
    Some prerequisites require you to reboot the server to complete installation.

    Let’s have a quick look how to execute the script Exchange2013SP1Prerequisites_W2008R2SP1_v1.0 on Windows PowerShell and what this script do for us.
    Login to Windows Server 2008 R2 SP1 with Enterprise Administrator credentials
    Start Windows PowerShell “As Administrator”


    Next step, copy the script Exchange2013SP1Prerequisites_W2008R2SP1_v1.0 on (C:\) drive

    Let’s start with running scripts from within Windows PowerShell itself.
    In case you get weird error messages when you try to run a script, the reason is only one, security settings built into Windows PowerShell include something called the “execution policy” the execution policy determines how (or if) PowerShell runs scripts. By default, PowerShell’s execution policy is set to Restricted that means that scripts – including those you write yourself – won’t run.
    Navigate back to Windows PowerShell and set the Execution policy to unrestricted in order to be able to run the script, in that case, use this command to set your execution policy to RemoteSigned or Unrestricted


    Note: The Set-ExecutionPolicy cmdlet enables you to determine which Windows PowerShell scripts (if any) will be allowed to run on your computer.
    Windows PowerShell has four different execution policies:
    Restricted – No scripts can be run. Windows PowerShell can be used only in interactive mode.
    AllSigned – Only scripts signed by a trusted publisher can be run.
    RemoteSigned – Downloaded scripts must be signed by a trusted publisher before they can be run.
    Unrestricted – No restrictions; all Windows PowerShell scripts can be run.

    The most common (default) way to run a script is by calling it:

    PS C:\> & “C:\Admin\My first Script.ps1″
    If the path does not contain any spaces, then you can omit the quotes and the ‘&’ operator
    PS C:\> C:\Admin\Myscript.ps1
    If the script is in the current directory, you must indicate this using .\ (or ./ will also work)
    PS C:\> .\Myscript.ps1
    In our case scenario we run the script in the current directory “C:\” so, we must indicate this using .\ and we click Enter

    Our script now it starts running, select an option from the menu. In my case scenario, I will select option 3 (E2013 Multirole installation) and click Enter


    As you can easy check bellow, my Multirole Prerequisites are in progress to be download and install


    After the Prerequisites successfully installed, we have to choose the option 10 in order to restart our server


    After restart your server, login as EA and proceed to install your Microsoft Exchange Server 2013 SP1


    You can download the script from TechNet Gallery Script Center
  7. Catastrophic Failure
    Today, I manage to complete the bellow script, in order some basic Office 365 User Creation and License assignment to be automate with one click.
    This script automate execute steps for Office 365 Administrator Tasks.
    By choosing only a number, you can manage your Office 365 Tasks.
    What do you need to know before you begin?
    Make sure you have already installed Windows Azure AD PowerShell
    You must check and be sure your server or your computer has access to the internet

    Let’s have a quick look how to execute the script O365Tool_v1.0 on Windows PowerShell and what this script do for us.
    Login to your computer with Administrator credentials
    Start Windows Azure AD PowerShell “As Administrator”


     
    3. Next step, copy the script O365Tool_v1.0 on (C:\O365Tool_v1.0) folder or create the O365Tool_v1.0 folder in your preferred destination

     
    4. Let’s start by running the script from Windows Azure AD PowerShell itself.
    In case you get weird error messages when you try to run a script, the reason is only one, security settings built into Windows PowerShell include something called the “execution policy” the execution policy determines how (or if) PowerShell runs scripts. By default, PowerShell’s execution policy is set to Restricted that means that scripts – including those you write yourself – won’t run.
    Navigate back to Windows PowerShell and set the Execution policy to unrestricted in order to be able to run the script, in that case, use this command to set your execution policy to RemoteSigned or Unrestricted
     

    Note: The Set-ExecutionPolicy cmdlet enables you to determine which Windows PowerShell scripts (if any) will be allowed to run on your computer.
    Windows PowerShell has four different execution policies:
    Restricted – No scripts can be run. Windows PowerShell can be used only in interactive mode.
    AllSigned – Only scripts signed by a trusted publisher can be run.
    RemoteSigned – Downloaded scripts must be signed by a trusted publisher before they can be run.
    Unrestricted – No restrictions; all Windows PowerShell scripts can be run
    The most common (default) way to run a script is by calling it:

    PS C:\> & “C:\Admin\My first Script.ps1″
    If the path does not contain any spaces, then you can omit the quotes and the ‘&’ operator
    PS C:\> C:\Admin\Myscript.ps1
    If the script is in the current directory, you must indicate this using .\ (or ./ will also work)
    PS C:\> .\Myscript.ps1
     
    Create the folders:
    Main folder: O365Tool
    Subfolder’s: Logs and Exports
     

     
    In our case scenario we run the script in the current directory “C:\O365Tool_v1.0″ so, we must indicate this using .\ and we click Enter
     

     
    5. Prepare the CSV file ” the file is included on the script zip”
     

     
    6. Type your Global Admin credentials, Username and Password in order to login

     
    7. Our script now it starts running, select an option from the menu. In my case scenario, I will select option 1, to start the creation of the new users and then to proceed with the rest of the options.

     
    Users are now created:

     
    Option 2: Set UsageLocation:

     
    Option 3: as I have only EnterprisePack:
    https://catastrophicerrors.files.wordpress.com/2015/02/clip_image0115.jpg
     
    Option 5: Export Mailboxes from Office 365:
    https://catastrophicerrors.files.wordpress.com/2015/02/clip_image0124.jpg
     
    Option 6: The script has a timer for how long the script is execute:
    https://catastrophicerrors.files.wordpress.com/2015/02/clip_image0134.jpg
     
    Enjoy…
    Download the Script here: https://gallery.technet.microsoft.com/Office-365-User-Creation-b8e48121
  8. Catastrophic Failure
    The most of you start wander “Where is the EMC (Exchange Management
    Console) in Exchange Server 2013?” Well, some things remain the same as login
    in the new Exchange Server 2013, and other things change (this is the
    technology). Let’s see together which are the things are new in Exchange Server
    2013, one of those is the EMC (Exchange Management Console).
    Where
    is the EMC (Exchange Management Console) and how where we can find it?
    Almost everything in new Exchange 2013 is web-based management console, not EMC
    (Exchange Management Console) but EAC (Exchange Administration Center), that
    allows for ease of use and is optimized for on-premises, online, or hybrid
    Exchange deployments. The EAC replaces the Exchange Management Console (EMC)
    and the Exchange Control Panel (ECP), which were the two interfaces that were
    used to manage Exchange Server 2010. One of the advantages of having the
    web-based EAC is that you can partition access from the Internet/Intranet from
    within the ECP IIS virtual directory to allow or disallow management features.
    This allows you to permit or deny access to users trying to access the EAC from
    the Internet outside of your organizational environment, while still allowing
    access to an end-user’s Outlook Web App Options.
    How can I login to EAC?
    If we navigate to IE (Internet Explorer) and type http://server
    FQDN/ecp (in my scenario is https://e2013.cloud.com/ecp

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

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

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

    Accept on the License Agreement page and click Next to continue

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

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

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

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

    Type the Exchange Organization name and click Next

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

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

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

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

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

    Enjoy..
  10. Catastrophic Failure
    Process of Exchange Server 2013 Preview installation in Windows Server 2012.
    The new Exchange Server 2013, split in 2 roles Client Access Server and Mailbox Server (In addition, Exchange 2013 Preview works with the Exchange 2010 Edge server role.) The Mailbox server includes all the traditional server components found in Exchange 2010:
    the Client Access protocols, Hub Transport service, Mailbox databases, and Unified Messaging. The Mailbox server handles all activity for a given mailbox. The Client Access server provides authentication, redirection, and proxy services. The Client Access server itself doesn't do any data rendering. The Client
    Access server is a thin and stateless server. There is never anything queued or stored on the Client Access server. The Client Access server offers all the usual client access protocols: HTTP, POP and IMAP, and SMTP.
    Before we proceed, we need to check the prerequisites for Exchange Server 2013, let’s see what we need to check before we begin:
    Make sure that the functional level of your forest is at least Windows Server 2003, and that the schema master is
    running Windows Server 2003 with SP1 or later. The full installation option of Windows Server 2012 and Windows Server 2008 R2 SP1 must be used for all servers
    running Exchange 2013 Preview server roles or management tools. You must first join the computer to the appropriate internal Active Directory forest and domain. Some prerequisites require you to reboot the server to complete installation. To prepare Active Directory for Exchange 2013 Preview, you must install the following software on the computer that will be used to prepare Active Directory:
    Microsoft .NET Framework 4.5 Windows Management Framework 3.0 After you install the software, open Windows PowerShell and install the Remote Tools
    Administration Pack.
    On a Windows Server 2012 computer, run the following command:
    Add-WindowsFeature RSAT-ADDS

    OS prerequisites for both the CAS and Mailbox roles:
    Do the following to install the required Windows roles and features:
    Open Windows PowerShell. Run the following command to install the required Windows components. Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience,NET-Framework-45-Features, RPC-over-HTTP-proxy,RSAT-Clustering,Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth,Web-Client-Auth,Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression,Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing,Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase,Web-Mgmt-Console,Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor,Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth,Web-WMI, Windows-Identity-Foundation

    After you've installed the operating system roles and features, install the following
    software in the order shown:
    Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit Microsoft Office 2010 Filter Pack 64 bit Microsoft Office 2010 Filter Pack SP1 64 bit For Exchange 2013 Preview, you must also uninstall Microsoft Visual C++ 11 Beta Redistributable
    (x64). This must be done after you've installed UCMA, but before you run Exchange 2013 Preview Setup.
    To uninstall Microsoft Visual C++ 11 Beta Redistributable (x64), do the following:
    Open Control Panel > Programs and Features. Select Visual C++ 11 Beta Redistributable (x64) - 11.0.50531 and then click Uninstall. In Microsoft Visual C++ 11 Beta setup, click Uninstall. When Microsoft Visual C++ 11 Beta is uninstalled, click Close.
    To be continue....

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

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


    Developing Applications for the Cloud, 2nd Edition


    Building Hybrid Applications in the Cloud on Windows Azure


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


    Technical reference for Microsoft SharePoint Server 2010


    Getting started with Microsoft SharePoint Foundation 2010


    Deployment guide for SharePoint 2013 Preview


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

    Microsoft Dynamics GP 2010 Guides: Financials


    Microsoft Dynamics CRM 2011 User's Guide


    Dynamics CRM 2011 Developer Training Kit


    Microsoft Dynamics CRM 2011 Implementation Guide


    Deployment guide for Office 2013 Preview


    Office 2010 Developer Training Kit


    Office 365 Developer Training Kit


    Office 365 Guides for professionals and small businesses

    Lync for Mac 2011 Deployment Guide


    Microsoft Lync Server 2010 Resource Kit Tools


    Microsoft Lync Server 2010 Resource Kit


    Microsoft Lync Server 2010 Security Guide


    Microsoft Lync Server 2010 Security Guide

    Visual Studio LightSwitch Training Kit


    SQL Server 2012 Developer Training Kit

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

    The following step:

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

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

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


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


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


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


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


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


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


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

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

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

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

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

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

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

    Step1

    Step2


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

    Step4

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

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

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

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

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

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


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

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















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


  22. Catastrophic Failure
    Νωρίς σήμερα, η ομάδα του Exchange CXP έκανε release το Update Rollup 6 για τον Exchange Server 2010 SP1.
    Update Rollup 6 για τον Exchange Server 2010 SP1
    Το παρόν Rollup περιέχει ένα μεγάλο αριθμό αναφορών των συνεργατών της Microsoft και διαφόρων εσωτερικών αναφορών από τους μηχανικούς της Microsoft.
    Μερικά από τα fixes που περιλαμβάνονται στο RU6 είναι τα ακόλουθα :
    · 2431609 (http://support.microsoft.com/kb/2431609/ ) An update is available that updates the message of a retention policy in OWA for Exchange Server 2010
    · 2449266 (http://support.microsoft.com/kb/2449266/ ) EWS drops the TCP connection to the EWS client application without any error message in a Microsoft Exchange Server 2010 environment
    · 2480474 (http://support.microsoft.com/kb/2480474/ ) A Users do not receive quota warning messages after applying SP1 for Exchange 2010
    · 2514820 (http://support.microsoft.com/kb/2514820/ ) An incoming fax message is not delivered to the recipient in an Exchange Server 2010 SP1 environment
    · 2521927 (http://support.microsoft.com/kb/2521927/ ) Disabling the Exchange ActiveSync Integration feature for OWA does not take effect in OWA Premium clients in an Exchange Server 2010 environment
    · 2528854 (http://support.microsoft.com/kb/2528854/ ) The Microsoft Exchange Mailbox Replication service crashes on a computer that has Exchange Server 2010 SP1 installed
    · 2535289 (http://support.microsoft.com/kb/2535289/ ) The Microsoft Exchange Information Store service crashes occasionally when you run an antivirus application on an Exchange Server 2010 Mailbox server
    · 2536313 (http://support.microsoft.com/kb/2536313/ ) Slow message delivery and mailbox access for journaling mailboxes on an Exchange Server 2010 server
    · 2544246 (http://support.microsoft.com/kb/2544246/ ) You receive a NRN of a meeting request 120 days later after the recipient accepted the request in an Exchange Server 2010 SP1 environment
    · 2548246 (http://support.microsoft.com/kb/2548246/ ) The Microsoft Exchange Information Store service crashes occasionally when a folder view is corrupted on an Exchange Server 2010 mailbox server
    · 2549183 (http://support.microsoft.com/kb/2549183/ ) "There are no objects to select" message when you try to use the EMC to specify a server to connect to in an Exchange Server 2010 SP1 environment
    · 2549289 (http://support.microsoft.com/kb/2549289/ ) A RBAC role assignee can unexpectedly run the Add-MailboxPermission command or the Remove-MailboxPermission command on an Exchange Server 2010 server that is outside the role assignment scope
    · 2555851 (http://support.microsoft.com/kb/2555851/ ) A mailbox does not appear in certain address lists after you run commands on the mailbox in an Exchange Server 2010 SP1 environment
    · 2559814 (http://support.microsoft.com/kb/2559814/ ) A user cannot add or remove delegates from a mailbox by using Outlook in an Exchange Server 2010 environment
    · 2561514 (http://support.microsoft.com/kb/2561514/ ) Exchange Server 2003 user cannot view the free/busy information of a user in a different federated organization
    · 2563860 (http://support.microsoft.com/kb/2563860/ ) You cannot create a new mailbox database if you already have 1000 mailbox databases in an Exchange Server 2010 environment
    · 2567409 (http://support.microsoft.com/kb/2567409/ ) Certain free/busy messages are not replicated from an Exchange Server 2010 server to an Exchange Server 2003 server
    · 2571791 (http://support.microsoft.com/kb/2571791/ ) Retention policies are applied to Contact items unexpectedly in an Exchange Server 2010 environment
    · 2572052 (http://support.microsoft.com/kb/2572052/ ) Certain properties of a recurring meeting request from external email accounts are missing in an Exchange Server 2010 SP1 environment
    · 2575005 (http://support.microsoft.com/kb/2575005/ ) You cannot start the EMC or the EMS in an Exchange Server 2010 Service Pack 1 environment
    · 2578631 (http://support.microsoft.com/kb/2578631/ ) Certain users cannot send email messages to a mail-enabled public folder in an Exchange Server 2010 environment
    · 2579172 (http://support.microsoft.com/kb/2579172/ ) Items that are deleted or moved still appear in the original folder when you use Office Outlook in online mode to access an Exchange Server 2010 mailbox
    · 2579671 (http://support.microsoft.com/kb/2579671/ ) No results returned when you use the ExpandGroup method in EWS to retrieve a list of members of a Dynamic Distribution Group in an Exchange Server 2010 environment
    · 2582095 (http://support.microsoft.com/kb/2582095/ ) The SmtpMaxMessagesPerConnection property of a send connector is not replicated to the subscribed Edge Transport server in an Exchange Server 2010 environment
    · 2600835 (http://support.microsoft.com/kb/2600835/ ) The RPC Client Access service crashes when you delete an attachment of an item by using Outlook in online mode in an Exchange Server 2010 SP1 environment
    · 2601701 (http://support.microsoft.com/kb/2601701/ ) The memory usage of the MSExchangeRepl.exe process keeps increasing when you perform a VSS backup on Exchange Server 2010 databases
    · 2616127 (http://support.microsoft.com/kb/2616127/ ) "0x80041606" error code when you use Outlook in online mode to search for a keyword against a mailbox in an Exchange Server 2010 environment
    · 2617126 (http://support.microsoft.com/kb/2617126/ ) The Store.exe process crashes when you send an email message that has attachments in an Exchange Server 2010 SP1 environment
    · 2627769 (http://support.microsoft.com/kb/2627769/ ) Some time zones in OWA are not synchronized with Windows in an Exchange Server 2010 environment
    Σημείωση για τους χρήστες Forefront:
    Για όσους από εσάς χρησιμοποιείτε Forefront, πρέπει να εκτελέσετε αυτά τα σημαντικά βήματα από τη γραμμή εντολών «command line» στο Forefront directory πριν και μετά τη διαδικασία της εγκατάστασης του rollup. Στην περίπτωση που δεν πραγματοποιηθούν αυτά τα βήματα, τα Exchange services για το Exchange Information Store και Transport δεν θα μπορέσουν να ξεκινήσουν. Θα χρειαστεί να απενεργοποιήσετε το Forefront μέσω «fscutility /disable» προτού εγκαταστήσετε το patch και στη συνέχεια ενεργοποιήστε το ξανά μετά την εγκατάσταση του patch με την εκτέλεση της εντολής «fscutility /enable» να ξεκινήσει και πάλι μετά την εγκατάσταση.

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

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

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

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

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

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

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

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

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

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

    • You can now use Kerberos authentication when you deploy an array using network load balancing (NLB).
    Για να διαβάσετε τα release notes, δείτε εδώ Forefront TMG Release Notes (SP2).
    Για να πραγματοποιήσετε λήψη του Microsoft Forefront Threat Management Gateway (TMG) 2010 Service Pack 2 πατήστε εδώ.
  25. Catastrophic Failure
    Μπορεί να μην πήγαμε στο TechEd Australia 2011 , αλλά φέραμε το TechEd Australia 2011 εδώ με μερικά Exchange Sessions. Αξίζει τον κόπο να τα παρακολουθήσετε…
    Upgrading to Exchange 2010: Notes from Field - In this session Sofiane and Colin will provide notes from the field as they take you on a journey to upgrading your legacy Exchange environment. They will highlight the best practices you should consider as you plan your upgrade from Exchange 2003, Exchange 2007, as well as touch on migrating from alternative messaging platforms. Sofiane and Colin will cover the gotchas and pitfalls you are likely to encounter, and follow through with tips and tricks that experienced ITPros leveraged on a regular basis. Additionally they will look at some of the recommended tools, such as the Exchange Deployment Assistant, that will ensure you have a smooth upgrade to the latest version of Exchange. Converged Exchange: A Blueprint for 2010 deployment - With the myriad of new capabilities in Exchange 2010, organisations are looking to their solutions providers to help them not only deploy the new platform but help them manage it. In this presentation, Tim Jones investigates the challenges faced with moving to 2010, migration options, configuration of Disk Access Groups and archiving solutions. He also discusses how Microsoft and Hitachi Data Systems joint reference architecture delivers Exchange 2010 as a “converged solution in a rack”. Exchange Virtualisation - Is it right for you? - Many production Exchange Server deployments are virtualized. This is to achieve better hardware utilisation, provide operational flexibility or align with data centre deployment standards. As a business critical server application, it’s important to understand the implications of virtualising Exchange Server and ensure that deployments are aligned to Microsoft’s best practices and meet the ever changing business demands of a modern messaging service. This breakout session will cover what has been learned about the best ways to deploy Exchange Server in a virtual environment, the various virtualisation technologies that can impact Exchange Server user experience, and scenarios where virtualisation may not be the best choice. Also the differences between Exchange Server native data protection and the high availability and failover features offered by virtualisation stacks will be examined to help you make informed design decisions. Load Balancing with Microsoft Exchange Server 2010 - Understand the Exchange 2010 requirements for load balancing. Review the pros and cons of current hardware-based load balancing solutions. Discuss the nuances of high-end/high-scale load balancing and the impact to Microsoft Exchange Server 2010. Exchange Server 2010: High Availability Deep Dive - Go beyond the basics of Exchange High Availability and learn what’s really going on under the hood in an Exchange 2010 database availability group (DAG). This session covers the inner workings of DAGs, including a deep dive discussion on how DAGs rely on quorum and how the DAG witness and witness server are used. You’ll also gain a solid understanding of the inner workings of Active Manager and its best copy selection process. Exchange Server 2010: High Availability Concepts - This session covers the basics of the new technologies, concepts, terms and methods used to plan, design, manage and troubleshoot Exchange high availability. Learn how settings like AutoDatabaseMountDial and Activation Preference work. Get an understanding of the basic functions of Active Manager, learn the difference between the Witness Server and the Alternate Witness Server, and more! Microsoft Office 365: From Simple Migration to a Hybrid Environment - Whether you’re looking to migrate all of your mailboxes to the cloud or planning to run a hybrid environment then this is the session for you. This presentation will cover how and when to take advantage of Simple Exchange Migration which supports migrating existing Exchange on-premise customers who want to move all of their mailboxes to the cloud with full data fidelity. You will also learn how rolling out an Exchange 2010 server in your current Exchange environment prepares you for seamless integration with Exchange Online. Whether you are piloting a few users or moving a large part of your workforce to the cloud, we give you the technical details on Exchange-to-cloud integration that you need to be successful.
×
×
  • Create New...