Recently I came across a great article on publishing Exchange 2010 with TMG, I use this article in the production environment and it worked perfectly and I thought its worth having the these links at my blog.
http://rdpfiles.com/2011/08/15/publishing-exchange-2010-with-tmg/
http://rdpfiles.com/2011/08/15/publishing-exchange-2010-with-tmg-2/
http://rdpfiles.com/2011/08/15/publishing-exchange-2010-with-tmg-3/
regards,
Krishna 🙂
Exchange 2013 has brought major architecture changes and now there are just two roles – Client Access Server (CAS) role and Mailbox Server role, whereas the previous version of Exchange had five server roles.
Mailbox Server role: It includes traditional features like Mailbox Database, transaction logs, but now it also hosts Client Access protocol, Transport service and Unified messaging server.
Client Access Server role: It is an office client access protocol like HTTP, POP and IMAP and SMTP. Outlook no longer uses RPC to connect to the Client Access Server, it uses RPC over HTTPS (also known as Outlook Anywhere) and Outlook client doesn’t connect using fully qualified domain name (FQDN) or CAS Array as it was done in all previous versions of Exchange. It uses user’s mailbox GUID + @ + the domain portion of the user’s primary SMTP address to connect to the mailbox. This is a huge benefit to overcome limitations and complexity of Exchange 2010 RPC Client Access service on the Client Access Server.
To read about more on this topic, please use the below link at blog.netwrix.com
Exchange 2013 has simplified the Client Access Server (CAS) design architecture using global/single namespace. This is because of the way CAS works in Exchange 2013. Outlook no longer uses RPC protocol to access the email, but instead it connects to the CAS server and accesses the mailbox through https protocol. The CAS server makes a direct connection with the mailbox server, if the mailbox exists on the same AD site. If not, then it decides, whether to proxy the request or to redirect the request to another CAS/Mailbox infrastructure. It queries the Active Manager to determine the mailbox server hosting the active copy and it will proxy the request to mailbox server. This occurs irrespectively of a mailbox location. One CAS server redirects its request to another CAS server only if there is a telephony related request or an OWA request.
To read about more on this topic, please use the below link at blog.netwrix.com
Exchange 2013 Multi site CAS URL configuration with global name space for site resilience
As part of upgrading to Exchange 2013 from Exchange 2007/2010, we need to make sure that Exchange 2013 is the point of communication for sending and receiving email from the Internet.In addition to installing, configuring, and testing Exchange 2013 Server, migration also consists of configuring and testing mail flow between Exchange 2013 and Exchange 2007/2010. In this article we will understand on how to configure for both sending and receiving emails from internet
Configure Exchange 2013 Internet mail flow during migration
Hope this articles helps you 
An Active Directory site is stretched if it is spread across multiple physical sites. Exchange setup may vary from organization to organization. Some Exchange organization are single site , some are multi site and some times single sites is spread across multiple AD site. In this series of two posts, I will show you how to recover an Exchange 2013 Data Availability Group in a stretched AD site.
Exchange 2013 DAG recovery in a stretched AD site – Part 1
Exchange 2013 DAG recovery in a stretched AD site – Part 2
I hope this article gives you a clear picture of understanding and recovering the DAG in the stretched AD site scenario 
Microsoft has released the latest cumulative update 2 (CU2) of Exchange Server 2013. I believe it is the right time for an organization to start planning to migrate Exchange 2010 to Exchange 2013.
Below article should give you the quick idea on how to migrate from Exchange 2010 to Exchange 2013 environment in the production environment.
How to migrate Exchange 2010 to 2013 – Part 1
How to migrate Exchange 2010 to 2013 – Part 2
Hope you like this article 😉
I would say Exchange 2013 HA and site resiliency got into a matured state from the previous version of Exchange. Exchange 2013 provides multiple options for HA and site resilience. Microsoft has tried to keep human intervention to a minimum and allow Exchange to recover itself from any kind of failures so that the administrator can focus on recovering the failed hardware or server rather than recovering the service.
Below are the two articles by me on Exchange 2013 HA and Site resiliency
Exchange 2013 High Availability(HA)
I hope you got some quick understanding on Exchange 2013 HA and Site Resiliency options 🙂
Media Contact:
Shawn Gundotra
(951) 268-7015
Email: info@enowinc.com
Website: www.enowsoftware.com
Corona, CA- August 13, 2013 – ENow, a Silver Microsoft Independent Software Vendor, specializing in the development of applications to simplify Microsoft system management, announced the release of EMS 6.0.
The EMS 6.0 release includes many benefits that will make the jobs of Microsoft Exchange and Lync administrators easier while at the same time increasing service availability. Microsoft Exchange 2013 has many improvements and is now being deployed. The EMS 6.0 release now enables Exchange 2013 administrators to proactively monitor and have visibility into their messaging infrastructure. EMS 6.0’s Mailscape module has received over 12 awards in the last 3 years including recently being named best Exchange Administration Tool by MSExchange.org. Mailscape proactively tests all the core messaging components including DAG configuration, external and internal mail flow, OWA, and ActiveSync. The reporting module has over 210 reports including detailed insight on mobile device usage.
Also included in this release is a new module, named UniScope, which provides visibility into Microsoft Lync deployments. Microsoft Lync is an outstanding Unified Communications platform that seamlessly integrates instant messaging, video conferencing, telecommunications and presence information. It enables consumers and company employees to communicate more efficiently and also increase productivity. Lync is being widely adopted and the need to proactively monitor this technology is critical as outages can cost a company thousands of dollars. UniScope proactively tests the core components of a Lync deployment including Front End, Web Conferencing, Mediation servers, end user connectivity, PSTN access and address book downloads.
“Due to our global customer base, we have a broad perspective on what technologies are being adopted.” states Jay Gundotra, CEO of ENow. “Microsoft has done a great job of continually adding useful features to both the Exchange and Lync platforms. As companies roll these technologies out, the dependency upon them grows and so does the need to ensure service availability. Our new additions to the EMS platform enable administrators to proactively manage both Exchange and Lync from a single dashboard.”
The ENow Management System is a monitoring and reporting platform which is currently used in over 50 countries by enterprise companies, including Facebook, NYSE, DirecTV, Blue Cross Blue Shield, Wendy’s and Advanced Auto Parts. The EMS platform features a dashboard with red, yellow, and green lights indicating the health of each monitored server. The solution enables IT support staff to proactively monitor servers in real time and avoid costly outages. It also provides administrators with deep reporting capabilities for Exchange, Office 365, BlackBerry, Active Directory, Lync and SharePoint servers.
About ENow
ENow is a Microsoft Silver Independent Software Vendor focused on helping companies implement the latest Microsoft technologies and developing software tools to simplify the job of an IT administrator. The ENow Management System (EMS) is an award winning platform that provides a dashboard view of Exchange, BlackBerry, SharePoint and Active Directory servers. For more information, call 1-877-TRY-ENOW, email us at info@enowsoftware.com, or visit us at www.enowsoftware.com.
Last week I wrote an article on Jetstress 2013 using PowerShell. It’s a very good script to automate Jetstress on exchange mailbox servers before the server build. It really helps on the large scale deployment. Please find the below link with the details of the same with the live example. This script is inspired by Neil Johnson’s – Automating Jetstress and it’s an updated version of the script.
Hope you like the article and let me know if you have any questions. 🙂
Please register for the Bangalore User Group Event using the below link,i will be taking a session on Exchange 2013 Role requirements Calculator.
http://bitprojuly2013.eventbrite.com/
This is a Bangalore IT Pro and PowerShell Bangalore User Group combined UG meet.
Agenda for this meet is as follows:
10.00AM – 10.15AM – Registrations and Welcome note.
10.15AM – 10.45AM – PowerShell for Beginners – Deepak Dhami
10.45AM – 11.15AM – Introduction to Exchange Calculator – Krishna Kumar
11.15AM – 11.30AM – Break
11.30AM – 12.00Noon – PowerShell 4.0 – First Look – Ravikath Chaganti
12.00Noon – 12.30PM – Building GUI for PowerShell Scripts – Vinith Menon
Regards,
Krishna
Shameless Null Neutrality