Jump to content

Catastrophic Failure

Members
 View Profile  See their activity

  • Posts

    562

  • Joined

  • Last visited

 Content Type 

Blog Entries posted by Catastrophic Failure

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

  2. 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
  3. Catastrophic Failure
    As we mention in Part1, Exchange Server 2013 has 2 server roles, Mailbox Server role and Client Access Server role. We have the option to install either single server role or both the roles on the same computer.
    In any case of installation role, CAS Role or both servers roles (CAS and Mailbox), Exchange Management Tools will be
    installed together.
    After you extract the Exchange-x64.exe file, start the exchange 2013 installation by click on the setup file available on the installation file. Below window appears up, check the option “Connect to the Internet and check for Updates” and click next to
    continue.

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

    Accept on the License Agreement page and click Next to continue

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

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

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

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

    Type the Exchange Organization name and click Next

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

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

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

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

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

    Enjoy..
  4. Catastrophic Failure
    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...
  6. 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
  7. 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
  8. 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
  9. 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
  10. 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…..
×
×
  • Create New...