To use OWA, browser settings must allow scripts to run

Situation: When trying to access the OWA from A windows 2003 server, you may receive this message: “To use Microsoft Outlook Web access, browser settings must allow scripts to run. For information about how to allow scripts, consult the Help for your browser. If your browser does not support scripts, you can download Microsoft Internet Explorer for access to Outlook Web Access”


1.You can enable Allow Scriptlets under ActiveX Control in the Internet option/Security
2. You can simple add the OWA server to the Trust site.


Microsoft Released New Virtualization Policy for Exchange 2010

Microsoft has announced new support policy for running Exchange on virtualization software. 

Basically the Exchange is now completly supported to be run in a virtualized environment. This includes also support for features that were not supported earlier like:

  • The Unified Messaging server role and,
    ·  Combining Exchange 2010 Database Availability Groups with hypervisor-based clustering, high availability, or migration solutions that will move or automatically failover mailbox servers that are members of a DAG between virtualization hosts.

    This applies to all virtualization vendors participating in the Windows Server Virtualization Validation Program  (SVVP).

In addition, the Best Practices for Virtualizing Exchange Server 2010 with Windows Server 2008 R2 Hyper-V  whitepaper has been released. This whitepaper is designed to provide technical guidance on Exchange server roles, capacity planning, sizing and performance, as well as high availability best practices.
Complete system requirements for Exchange Server 2010 running under hardware virtualization software can be found in Exchange 2010 System Requirements . Also, the support policy for Microsoft software running in non-Microsoft hardware virtualization software can be found here .

New Features in Exchange Server 2013

Exchange Server 2013 comes with a number of new features as well as improvements on existing features that are already familiar to those who have worked with Exchange Server 2010.

Here are a few of the highlights:

  • Reduction in server roles to just two; Client Access server and Mailbox server
  • New streamlined Outlook 2013 and Outlook Web App user interfaces, and offline access for OWA
  • No more Exchange Management Console, all administration is now performed using the new web-basedExchange Administration Center and the Exchange Management Shell (using PowerShell 3.0)
  • Improvements to high availability features and manageability
  • Public folders are now stored in mailbox databases and can take advantage of Database Availability Groups for replication and high availability
  • Data loss prevention capabilities that can be integrated into Transport Rules

Exchange 2010’s five server roles

Exchange 2010’s five server roles
Exchange Server 2010 is divided into five separate but related server roles; the mailbox server, client access server (CAS), hub transport server, edge transport server and unified messaging server. It’s important for administrators to understand what they do and how they can be combined for an effective Exchange 2010 deployment.

  • Mailbox server role — The mailbox server is Exchange 2010’s back-end repository and contains content items like mailboxes, public folders, address lists, resource schedules and meeting items. Database availability groups support the mailbox server; this support allows admins to deploy highly available mailboxes within the organization.
  • Client access server role — The CAS role handles all connections between all external clients that need email access. All the protocols necessary for client access are handled in the CAS, including POP3, Internet Message Access Protocol 4 (IMAP4), Messaging Application Programming Interface (MAPI) and HTTPS. The CAS also supports Microsoft Outlook, Outlook AnywhereOutlook Web App (OWA) and Exchange ActiveSync (EAS).
  • Hub transport server role — This server role processes, routes and delivers all mail sent through Exchange 2010. The hub transport server oversees message filtering and formatting and checks the validity of attachments. This provides the oversight that an Exchange organization needs to control internal and external email.

    A hub transport server also record and journals email messages, adds company disclaimers and other actions that support regulatory requirements. This role can work in conjunction with an edge transport server.

  • When installed, the optional Edge transport server role provides an added layer of security between the Exchange Server 2010 organization and the outside network. The edge transport server checks that messages sent from outside an organization are free from spam and viruses before routing them to the hub transport server. Outgoing mail from the hub transport server is routed to the edge transport (if deployed) before leaving the Exchange organization.
  • Unified messaging server role — the UM server, which is also optional, integrates an organization’s PBX system with Exchange Server 2010. This stores business data like voicemail and faxes with email, calendars and contacts in users’ mailboxes. Users also get features like call answering, automated greetings, message recording and fax support.

The benefits of Exchange 2010 server roles 
Having so many roles might seem to complicate Exchange, but experts note there are several advantages to a role-based architecture. First, adopting individual roles can improve security over previous versions.

“There was a larger potential attack footprint on the machine; 20 or 30 ports might be open on an Exchange box in the old days,” said Sean Evans, senior consultant at Blue Chip Consulting Group in Independence, Ohio. “By separating roles, you only need to worry about the client access server having port 443  open.”

Evans also noted that older server hardware is more likely to provide the resource requirements needed for one or more individual roles. This means organizations can avoid the capital expense of buying powerful new servers to host the entire Exchange Server system.

It’s difficult to say which server role is most important for Exchange 2010. It depends on the organization and its needs. Some experts suggest that the mailbox server role is most important since it’s at the core of any deployment.

Other experts suggest that the CAS is most important because it handles the majority of mail processing in Exchange Server 2010. This removes much of the functionality that existed in the mailbox server under previous versions of Exchange. Still, every organization is different and other admins have focused on other roles. “Unified messaging is extremely important for us,” said Joe Chiarchiaro, senior messaging engineer with Grant Thornton LLP. “We’re moving our voicemail platform to Microsoft unified messaging on [Exchange] 2010.”

Distributing Exchange 2010 server roles
Exchange Server architects have the flexibility to distribute roles across hardware platforms. A basic Exchange Server 2010 deployment involves a mailbox, client access and hub transport server on the same physical box. This is the minimum set of roles needed to store, route and deliver messages inside and outside an organization.

It is also possible to add the UM server to the same physical system; the edge transport server cannot coexist on the same computer as other server roles. The physical server must have enough resources to support all roles. This setup is often the most cost-effective approach for smaller, cost-conscious businesses. Blue Chip’s Evans also points out that licensing costs can be mitigated when configuring combined (multi-role) servers.

Distributing roles across multiple servers enables an Exchange organization to scale them according to specific needs. When performance demands increase, segregate affected role(s) on separate servers to make the most of the available computing power. You can also group servers to boost performance and resilience; migrating roles to larger and more capable boxes according to traffic loads can also help.

When selecting servers to host Exchange Server 2010 roles, experts say there are few concrete rules because system requirements aren’t spelled out. However, experts recommend referring to Microsoft best practices for hardware sizing.

Windows PowerShell ISE v3.0

Here you can see the whole application, and you will notice the command bar off to the right. This command bar has some nice features that will let you access commands from the various modules that are available on your machine very easily.


Here is a close-up of the command bar showing some of the modules that are available by default.

There are some buttons across the bottom Run, Insert, Copy and Hide. When you select a command from the list above and click Run the command is run and the output is displayed in the output pane. If you have a command selected and click Insert, that command is inserted into either the script pane or the command pane. Finally a selected command can be copied to the clipboard, or you can hide this bar altogether.
Once a command is selected an additional button appears [?] with the command selected clicking this displays the help in a separate window that is not modal, but sits on top of everything. The screenshot below shows you the command bar with all the buttons clicked.

Auto-complete for many things in PowerShell have been around for a while, but if you miss the Intellisense features from like Visual Studio, it’s now available within ISE, both in the script pane and the command pane. I know this can be really helpful as I’m used to using get-member to get a lot of this information as I’m working on a script.


Outlines! I really missed this feature when I moved from Notepad++ to PowerShell ISE. But in the following screenshot you can see that you now have collapsible outlines in PowerShell ISE, as well as something like code highlighting. You can see I have one of my functions collapsed, and have left the Process section of the code expanded. In the function below you can see that the help section of the function is highlighted. You can’t see my mouse from this screenshot but it’s hanging out in the border near line 66 where the help section begins.