This document provides an overview of upgrading Exchange Server organizations from Exchange Server 2003 or Exchange Server 2007 to Exchange Server 2010. It discusses the different upgrade options and supported scenarios. It also outlines the processes for installing Exchange Server 2010, implementing coexistence between the server versions, and removing the legacy servers from the organization. Considerations are provided for client access, message transport, and administration during the upgrade and coexistence phases.
24 Hours Of Exchange Server 2007 ( Part 6 Of 24)guestef2a2b
Configuring Exchange Server 2007 Part 1
[There may be some inconsistencies as I have not had a chance to go through and clean up. This usually involves terminology].
24 Hours Of Exchange Server 2007 ( Part 5 Of 24)guestef2a2b
Transitioning and Migrating to Exchange Server 2007
[There may be some inconsistencies as I have not had a chance to go through and clean up. This usually involves terminology].
24 Hours Of Exchange Server 2007 ( Part 4 Of 24)guestef2a2b
Installing Exchange Server 2007
[There may be some inconsistencies as I have not had a chance to go through and clean up. This usually involves terminology].
Attention Session en Anglais, animée par Scott Schnoll, Senior Content Developer à Microsoft Corp. Cette session vous expliquera comment architecturer une migration vers Exchange 2013 depuis d'ancienne versions d'Exchange avec comme speaker Scott Schnoll, Gourou Exchange en provenance directe de Redmond. La coexistence de serveurs de versions différentes sera aussi abordée.
Speaker : Scott Schnoll (Microsoft)
24 Hours Of Exchange Server 2007 ( Part 6 Of 24)guestef2a2b
Configuring Exchange Server 2007 Part 1
[There may be some inconsistencies as I have not had a chance to go through and clean up. This usually involves terminology].
24 Hours Of Exchange Server 2007 ( Part 5 Of 24)guestef2a2b
Transitioning and Migrating to Exchange Server 2007
[There may be some inconsistencies as I have not had a chance to go through and clean up. This usually involves terminology].
24 Hours Of Exchange Server 2007 ( Part 4 Of 24)guestef2a2b
Installing Exchange Server 2007
[There may be some inconsistencies as I have not had a chance to go through and clean up. This usually involves terminology].
Attention Session en Anglais, animée par Scott Schnoll, Senior Content Developer à Microsoft Corp. Cette session vous expliquera comment architecturer une migration vers Exchange 2013 depuis d'ancienne versions d'Exchange avec comme speaker Scott Schnoll, Gourou Exchange en provenance directe de Redmond. La coexistence de serveurs de versions différentes sera aussi abordée.
Speaker : Scott Schnoll (Microsoft)
Exchange Server 2013 : upgrade migration et co-existence avec les anciennes v...Microsoft Technet France
Vous souhaitez tester / installer la toute nouvelle version d'Exchange 2013... mais quelles sont les implications à connaitre pour effectuer un upgrade depuis les anciennes versions d'Exchange ou encore pour mettre en place une infrastructure mixte avec coexistence d'anciennes versions des serveurs ? Cette session est animée par Scott Schnoll, Principal Technical Writer dans l'équipe Exchange à Microsoft Corp. Vous aurez en direct les conseils et les meilleures pratiques prodigués par l'expert mondial sur Exchange. Attention session technique en anglais.
24 Hours Of Exchange Server 2007 ( Part 2 Of 24)guestef2a2b
Exchange Server 2007 Transport and Routing Architecture
[There may be some inconsistencies as I have not had a chance to go through and clean up. This usually involves terminology].
24 Hours Of Exchange Server 2007 (Part 2 Of 24)Harold Wong
Exchange Server 2007 Transport and Routing Architecture
[There may be some inconsistencies with the slide deck as I have not had a chance to do any cleanup. This is usually around terminology].
MailRetriever for DPM: Quick Start GuideMailRetriever
Learn how to quickly and easily start restoring damaged and deleted emails and other items from Outlook PST files with MailRetriever for DPM, reliable email restoring solution. Targeted for Microsoft Exchange Network Administrators, Exchange Engineers, Messaging and Infrastructure Consultants MailRetriever provides the ability to restore individual e-mails, mailboxes, tasks, calendar items, contacts, and public folders from offline Exchange Data Store (.edb file).
MailRetriever for Exchange: Quick Start GuideMailRetriever
Learn how to quickly and easily start restoring damaged and deleted emails and other items from Outlook PST files with MailRetriever for Exchange, reliable email restoring solution. Targeted for Microsoft Exchange Network Administrators, Exchange Engineers, Messaging and Infrastructure Consultants MailRetriever provides the ability to restore individual e-mails, mailboxes, tasks, calendar items, contacts, and public folders from offline Exchange Data Store (.edb file).
Mule complete training for all level of mule experts. Gives you the basic idea where to use mule and how to use mule along with example for the connectors.
Exchange Server 2013 : upgrade migration et co-existence avec les anciennes v...Microsoft Technet France
Vous souhaitez tester / installer la toute nouvelle version d'Exchange 2013... mais quelles sont les implications à connaitre pour effectuer un upgrade depuis les anciennes versions d'Exchange ou encore pour mettre en place une infrastructure mixte avec coexistence d'anciennes versions des serveurs ? Cette session est animée par Scott Schnoll, Principal Technical Writer dans l'équipe Exchange à Microsoft Corp. Vous aurez en direct les conseils et les meilleures pratiques prodigués par l'expert mondial sur Exchange. Attention session technique en anglais.
24 Hours Of Exchange Server 2007 ( Part 2 Of 24)guestef2a2b
Exchange Server 2007 Transport and Routing Architecture
[There may be some inconsistencies as I have not had a chance to go through and clean up. This usually involves terminology].
24 Hours Of Exchange Server 2007 (Part 2 Of 24)Harold Wong
Exchange Server 2007 Transport and Routing Architecture
[There may be some inconsistencies with the slide deck as I have not had a chance to do any cleanup. This is usually around terminology].
MailRetriever for DPM: Quick Start GuideMailRetriever
Learn how to quickly and easily start restoring damaged and deleted emails and other items from Outlook PST files with MailRetriever for DPM, reliable email restoring solution. Targeted for Microsoft Exchange Network Administrators, Exchange Engineers, Messaging and Infrastructure Consultants MailRetriever provides the ability to restore individual e-mails, mailboxes, tasks, calendar items, contacts, and public folders from offline Exchange Data Store (.edb file).
MailRetriever for Exchange: Quick Start GuideMailRetriever
Learn how to quickly and easily start restoring damaged and deleted emails and other items from Outlook PST files with MailRetriever for Exchange, reliable email restoring solution. Targeted for Microsoft Exchange Network Administrators, Exchange Engineers, Messaging and Infrastructure Consultants MailRetriever provides the ability to restore individual e-mails, mailboxes, tasks, calendar items, contacts, and public folders from offline Exchange Data Store (.edb file).
Mule complete training for all level of mule experts. Gives you the basic idea where to use mule and how to use mule along with example for the connectors.
This seminar will give you tips to improve your website's promotional strategy through blogging, social marketing, and Web 2.0 results. Learn to utilize the social web to connect with your client base, improve customer service, and generate sales leads. Streamline your blogging and social media marketing methods with the latest tools, techniques, and innovation. You will leave the seminar with actionable tactics you can use to make money NOW.
Desde el comienzo, aun antes de la creación del hombre, el propósito de Dios fue compartir con el hombre todo lo que tiene y todo lo que él es. Y justamente, el verdadero plan, el verdadero enfoque para el evangelismo personal ¡es compartir lo que tenemos!
24 Hours Of Exchange Server 2007 ( Part 3 Of 24)guestef2a2b
Planning Exchange Server Installation
[There may be some inconsistencies as I have not had a chance to go through and clean up. This usually involves terminology].
24 Hours Of Exchange Server 2007 (Part 1 Of 24)Harold Wong
Integration of Exchange Server 2007 and Active Directory
[There may be some inconsistencies with the deck as I have not had a chance to do any cleanup. Most of that is usually related to terminology.]
24 Hours Of Exchange Server 2007 ( Part 7 Of 24)guestef2a2b
Configuring Exchange Server 2007 Part 2
[There may be some inconsistencies as I have not had a chance to go through and clean up. This usually involves terminology].
This is a presentation held as part of a one day workshop covering the topics:
What's new in Exchange Server 2016
Planning an upgrade to Exchange Server 2016
Implementing an upgrade to Exchange Server 2016
A tale of scale & speed: How the US Navy is enabling software delivery from l...sonjaschweigert1
Rapid and secure feature delivery is a goal across every application team and every branch of the DoD. The Navy’s DevSecOps platform, Party Barge, has achieved:
- Reduction in onboarding time from 5 weeks to 1 day
- Improved developer experience and productivity through actionable findings and reduction of false positives
- Maintenance of superior security standards and inherent policy enforcement with Authorization to Operate (ATO)
Development teams can ship efficiently and ensure applications are cyber ready for Navy Authorizing Officials (AOs). In this webinar, Sigma Defense and Anchore will give attendees a look behind the scenes and demo secure pipeline automation and security artifacts that speed up application ATO and time to production.
We will cover:
- How to remove silos in DevSecOps
- How to build efficient development pipeline roles and component templates
- How to deliver security artifacts that matter for ATO’s (SBOMs, vulnerability reports, and policy evidence)
- How to streamline operations with automated policy checks on container images
Essentials of Automations: The Art of Triggers and Actions in FMESafe Software
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
Climate Impact of Software Testing at Nordic Testing DaysKari Kakkonen
My slides at Nordic Testing Days 6.6.2024
Climate impact / sustainability of software testing discussed on the talk. ICT and testing must carry their part of global responsibility to help with the climat warming. We can minimize the carbon footprint but we can also have a carbon handprint, a positive impact on the climate. Quality characteristics can be added with sustainability, and then measured continuously. Test environments can be used less, and in smaller scale and on demand. Test techniques can be used in optimizing or minimizing number of tests. Test automation can be used to speed up testing.
Elevating Tactical DDD Patterns Through Object CalisthenicsDorra BARTAGUIZ
After immersing yourself in the blue book and its red counterpart, attending DDD-focused conferences, and applying tactical patterns, you're left with a crucial question: How do I ensure my design is effective? Tactical patterns within Domain-Driven Design (DDD) serve as guiding principles for creating clear and manageable domain models. However, achieving success with these patterns requires additional guidance. Interestingly, we've observed that a set of constraints initially designed for training purposes remarkably aligns with effective pattern implementation, offering a more ‘mechanical’ approach. Let's explore together how Object Calisthenics can elevate the design of your tactical DDD patterns, offering concrete help for those venturing into DDD for the first time!
State of ICS and IoT Cyber Threat Landscape Report 2024 previewPrayukth K V
The IoT and OT threat landscape report has been prepared by the Threat Research Team at Sectrio using data from Sectrio, cyber threat intelligence farming facilities spread across over 85 cities around the world. In addition, Sectrio also runs AI-based advanced threat and payload engagement facilities that serve as sinks to attract and engage sophisticated threat actors, and newer malware including new variants and latent threats that are at an earlier stage of development.
The latest edition of the OT/ICS and IoT security Threat Landscape Report 2024 also covers:
State of global ICS asset and network exposure
Sectoral targets and attacks as well as the cost of ransom
Global APT activity, AI usage, actor and tactic profiles, and implications
Rise in volumes of AI-powered cyberattacks
Major cyber events in 2024
Malware and malicious payload trends
Cyberattack types and targets
Vulnerability exploit attempts on CVEs
Attacks on counties – USA
Expansion of bot farms – how, where, and why
In-depth analysis of the cyber threat landscape across North America, South America, Europe, APAC, and the Middle East
Why are attacks on smart factories rising?
Cyber risk predictions
Axis of attacks – Europe
Systemic attacks in the Middle East
Download the full report from here:
https://sectrio.com/resources/ot-threat-landscape-reports/sectrio-releases-ot-ics-and-iot-security-threat-landscape-report-2024/
LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...DanBrown980551
Do you want to learn how to model and simulate an electrical network from scratch in under an hour?
Then welcome to this PowSyBl workshop, hosted by Rte, the French Transmission System Operator (TSO)!
During the webinar, you will discover the PowSyBl ecosystem as well as handle and study an electrical network through an interactive Python notebook.
PowSyBl is an open source project hosted by LF Energy, which offers a comprehensive set of features for electrical grid modelling and simulation. Among other advanced features, PowSyBl provides:
- A fully editable and extendable library for grid component modelling;
- Visualization tools to display your network;
- Grid simulation tools, such as power flows, security analyses (with or without remedial actions) and sensitivity analyses;
The framework is mostly written in Java, with a Python binding so that Python developers can access PowSyBl functionalities as well.
What you will learn during the webinar:
- For beginners: discover PowSyBl's functionalities through a quick general presentation and the notebook, without needing any expert coding skills;
- For advanced developers: master the skills to efficiently apply PowSyBl functionalities to your real-world scenarios.
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
Threats to mobile devices are more prevalent and increasing in scope and complexity. Users of mobile devices desire to take full advantage of the features
available on those devices, but many of the features provide convenience and capability but sacrifice security. This best practices guide outlines steps the users can take to better protect personal devices and information.
Transcript: Selling digital books in 2024: Insights from industry leaders - T...BookNet Canada
The publishing industry has been selling digital audiobooks and ebooks for over a decade and has found its groove. What’s changed? What has stayed the same? Where do we go from here? Join a group of leading sales peers from across the industry for a conversation about the lessons learned since the popularization of digital books, best practices, digital book supply chain management, and more.
Link to video recording: https://bnctechforum.ca/sessions/selling-digital-books-in-2024-insights-from-industry-leaders/
Presented by BookNet Canada on May 28, 2024, with support from the Department of Canadian Heritage.
Alt. GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using ...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdfPaige Cruz
Monitoring and observability aren’t traditionally found in software curriculums and many of us cobble this knowledge together from whatever vendor or ecosystem we were first introduced to and whatever is a part of your current company’s observability stack.
While the dev and ops silo continues to crumble….many organizations still relegate monitoring & observability as the purview of ops, infra and SRE teams. This is a mistake - achieving a highly observable system requires collaboration up and down the stack.
I, a former op, would like to extend an invitation to all application developers to join the observability party will share these foundational concepts to build on:
Sudheer Mechineni, Head of Application Frameworks, Standard Chartered Bank
Discover how Standard Chartered Bank harnessed the power of Neo4j to transform complex data access challenges into a dynamic, scalable graph database solution. This keynote will cover their journey from initial adoption to deploying a fully automated, enterprise-grade causal cluster, highlighting key strategies for modelling organisational changes and ensuring robust disaster recovery. Learn how these innovations have not only enhanced Standard Chartered Bank’s data infrastructure but also positioned them as pioneers in the banking sector’s adoption of graph technology.
Pushing the limits of ePRTC: 100ns holdover for 100 daysAdtran
At WSTS 2024, Alon Stern explored the topic of parametric holdover and explained how recent research findings can be implemented in real-world PNT networks to achieve 100 nanoseconds of accuracy for up to 100 days.
By Design, not by Accident - Agile Venture Bolzano 2024
10135 a 12
1. Module 12 Upgrading from Exchange Server 2003 or Exchange Server 2007 to Exchange Server 2010
2.
3.
4. Upgrade Options for Exchange Server Upgrade is recommended whenever possible Upgrade An upgrade of an existing Exchange organization to Exchange Server 2010 in which you move data and functionality from the existing Exchange servers to new Exchange Server 2010 servers Migration Replacing a non-Exchange messaging system with Exchange Server 2010 or replacing an existing Exchange organization with a new Exchange organization, without retaining any of the configuration data In-Place Upgrade An upgrade of a computer running a previous Exchange Server version to a newer version of Exchange software on a single computer (not supported in Exchange Server 2010)
5.
6.
7.
8.
9.
10. How Client Access Works During Coexistence https://legacy.contoso.com External URL: https://mail.contoso.com Outlook Anywhere client Exchange 2003 front-end server Outlook Web Access client Exchange Server 2010 Exchange Server 2003 HTTP Outlook RPC Exchange ActiveSync client Exchange Server 2010 RPC HTTP
11. Implementing Client Access Coexistence To implement client access coexistence: Obtain the required server certificates 1 Install and configure the Exchange 2010 Client Access server Configure DNS Remove the Exchange 2003 from the RPC over HTTP configuration Test all client access scenarios 2 3 4 5
12.
13.
14. Considerations for Administration Coexistence Exchange 2003 Administration Exchange Server 2010 Equivalent Assign Exchange Server Full Administrator role at the organization level Add users or groups to the Exchange Organization Administrators role group Assign Exchange Server Administrator role at the organization level No Exchange Administrator role group equivalent, so create a management role group with restricted permissions Assign Exchange Server View Administrator role at the organization level Add users or groups to the Exchange View-Only Administrators role group Assign Exchange Server Full Administrator at the administrative group level Create a management role group with a limited scope
15.
16.
17.
18. How Client Access Works During Coexistence External URL: $null https://legacy.contoso.com HTTPS https://mail.contoso.com HTTPS Outlook Anywhere client Exchange Server 2007 RPC Exchange 2007 SP2 Exchange Server 2010 Exchange Server 2010 Exchange ActiveSync client Outlook Web Access client RPC Exchange 2007 SP2 Exchange Server 2007 RPC Exchange ActiveSync /WS Proxy Outlook Web Access /Exchange ActiveSync /WS Proxy Outlook RPC Outlook RPC
19.
20.
21.
22. Process for Removing Exchange Server 2007 from the Organization Remove Exchange Server 2007 servers in the following order: Mailbox servers Hub Transport servers Unified Messaging servers Remove all mailboxes and connectors from the Exchange Server 2007 servers before decommissioning the servers Client Access servers 4 3 1 2
Module 12: Upgrading from Exchange Server 2003 or Exchange Server 2007 to Exchange Server 2010 Course 10135A Presentation: 60 minutes After completing this module, students will be able to: Describe the general Microsoft® Exchange Server 2010 upgrade scenarios and strategies Upgrade from Microsoft Exchange Server 2003 to Exchange Server 2010 Upgrade from Microsoft Exchange Server 2007 to Exchange Server 2010 Required materials To teach this module, you need the Microsoft Office PowerPoint® file 10135A_12.ppt. Important: We recommend that you use PowerPoint 2002 or a later version to display the slides for this course. If you use PowerPoint Viewer or an earlier version of PowerPoint, all the features of the slides might not be displayed correctly. Preparation tasks To prepare for this module: Read all of the materials for this module. Work through the Module Review and Takeaways section, and determine how you will use this section to reinforce student learning and promote knowledge transfer to on-the-job performance. Make sure that students are aware that the Course Companion CD has additional information and resources for the module.
Module 12: Upgrading from Exchange Server 2003 or Exchange Server 2007 to Exchange Server 2010 Course 10135A
Module 12: Upgrading from Exchange Server 2003 or Exchange Server 2007 to Exchange Server 2010 Course 10135A
This topic is intended to be an overview slide for lesson one. The second lesson describes how to perform a upgrade from Microsoft Exchange Server 2003 with Service Pack 2 (SP2) to Exchange Server 2010, and the third lesson focuses on how to perform a upgrade from Microsoft Exchange Server 2007 with Service Pack 2 (SP2) . Discuss the differences between a upgrade and a migration. In a upgrade, you install Exchange Server 2010 into an existing Exchange Server 2003 or Exchange Server 2007 organization. In a migration, you install Exchange Server 2010 into a new organization, and then migrate mailboxes and other objects from the current messaging system to Exchange Server 2010. Upgrades are usually easier to perform than migrations, but upgrades are limited to only Exchange Server 2003 or Exchange Server 2007 organizations. Mention that because this module covers the upgrading scenarios, it does not include a lab. Module 12: Upgrading from Exchange Server 2003 or Exchange Server 2007 to Exchange Server 2010 Course 10135A
Highlight the Active Directory ® Domain Services (AD DS) and Active Directory directory services requirements for performing a upgrade. All global catalog servers must be running the Windows Server ® 2003 SP2 or newer operating system, and the domain and forest functional levels must be running the Windows Server 2003 operating system or higher. Also stress that Service Pack 2 or newer is required for both Exchange Server 2003 and Exchange Server 2007 upgrades. Exchange Server 2010 setup will fail if the computers are not upgraded to SP2. Module 12: Upgrading from Exchange Server 2003 or Exchange Server 2007 to Exchange Server 2010 Course 10135A
As part of the overview for this module, this topic describes some of the upgrade strategies. Stress that in all but the smallest organizations, a single phase upgrade is not feasible. This means that in most upgrades, there is a short or extended period of coexistence between the Exchange Server versions. Module 12: Upgrading from Exchange Server 2003 or Exchange Server 2007 to Exchange Server 2010 Course 10135A
Module 12: Upgrading from Exchange Server 2003 or Exchange Server 2007 to Exchange Server 2010 Course 10135A
Mention that in order for Exchange Server 2010 to coexist with Exchange Server 2003, the Active Directory permissions assigned to Exchange servers must be modified. Running Exchange Server 2010 setup with the PrepareLegacyExchangePermissions command makes this change. Mention that students do not have to run setup with the /PrepareLegacyExchangePermissions parameter if they run setup with the /PrepareAD parameter. If /PrepareLegacyExchangePermissions has not been run, /PrepareAD applies the same changes. Module 12: Upgrading from Exchange Server 2003 or Exchange Server 2007 to Exchange Server 2010 Course 10135A
Stress that Client Access servers must be deployed first and that all client connections must be configured to connect to the Client Access server. Mention that although Exchange Server 2003 does not use Active Directory sites for message routing, Exchange Server 2010’s dependency on Active Directory sites for options such as message routing and client access mean that you have to consider Active Directory sites during the upgrade. Module 12: Upgrading from Exchange Server 2003 or Exchange Server 2007 to Exchange Server 2010 Course 10135A
Use the diagram describe the different scenarios that occur when the different messaging clients connect to the Exchange environment during coexistence. Emphasize the process used by Outlook Web Access, pointing out the requirement for two different URLs so that the client request can be referred to the Exchange Server 2003 front-end server if the mailbox is located on an Exchange 2003 server. Module 12: Upgrading from Exchange Server 2003 or Exchange Server 2007 to Exchange Server 2010 Course 10135A
For clients other than Outlook to connect to the user mailboxes and use the single sign-on feature, the clients must be configured to use the Exchange Server 2010 Client Access server as the first point of connection. The Client Access server may then redirect the client to an Exchange Server 2003 front-end server, or it may proxy the client request to an Exchange Server 2003 front-end server. Because you can redirect client requests from the Exchange Server 2010 Client Access server to an Exchange Server 2003 server, you will need to enable Internet access for multiple URLs. Stress the importance of using server certificates that support all of the URLs. Because all clients are connecting to an Exchange Server 2010 Client Access server when the user mailboxes are moved to Exchange Server 2010, you must plan for Client Access server capacity. In previous versions of Exchange Server, the recommended deployment ratio was one Client Access server processor core for every four Mailbox server processor cores. In Exchange Server 2010, the recommended ratio is 3 to 4. Module 12: Upgrading from Exchange Server 2003 or Exchange Server 2007 to Exchange Server 2010 Course 10135A
Consider discussing the differences between how Exchange Server 2003 and Office Outlook versions prior to Outlook 2007 access free/busy information and the offline address book. Because the Exchange Server and client version architectures differ significantly, you must retain both the Exchange Server 2003 and the Exchange Server 2010 options for accessing this information. Also mention that you can replicate public folders from Exchange Server 2003 servers to Exchange Server 2010 servers. As Exchange Server 2003 servers are removed from the organization, the Exchange Server 2010 servers can host all the public folders. Module 12: Upgrading from Exchange Server 2003 or Exchange Server 2007 to Exchange Server 2010 Course 10135A
Use a whiteboard diagram to show how a routing group connector is created when the first Exchange Server 2010 Hub Transport server is deployed in an Exchange Server 2003 organization. Consider extending the diagram to describe what happens as Hub Transport servers replace bridgehead servers across multiple Active Directory sites and routing groups. Because Exchange Server 2010 uses Active Directory sites rather than routing groups to manage routing, replacing bridgehead servers can change the routing topology significantly. Module 12: Upgrading from Exchange Server 2003 or Exchange Server 2007 to Exchange Server 2010 Course 10135A
Use the table to describe the options for configuring administrative permissions in Exchange Server 2003, and how those same permissions can be assigned in Exchange Server 2010. Stress that because using role-based access control (RBAC) to assign permissions is so flexible, you can duplicate any Exchange Server 2003 administrative permission configuration. Ask students if Exchange Server 2003 limited their ability to assign permissions. For example, did their organization have requirements for delegating administrative permissions that were not possible in Exchange Server 2003? Discuss whether the same limitations will apply in Exchange Server 2010. Stress the importance of managing each Exchange Server version with the correct version of management tools. Once Exchange Server 2010 is introduced into the organization, all organization-level settings should be configured using the Exchange Server 2010 tools, but all server-level administration settings should be performed using the management tools that come with each version. Module 12: Upgrading from Exchange Server 2003 or Exchange Server 2007 to Exchange Server 2010 Course 10135A
Stress the importance of removing the mailbox servers in the correct order when upgrading from Exchange Server 2003. Because of the changes to the Client Access architecture in Exchange Server 2010, an Exchange Server 2003 server that supports non-MAPI client connections must be retained until the last mailbox has been moved to an Exchange Server 2010 server. Review some of the functionality that was available in Exchange Server 2003 that is not available in Exchange Server 2010. Examples include the Novell GroupWise connector and the Inter-Organization Replication tool. Mention that some organizations may need to retain one or more Exchange Server 2003 servers to retain this functionality. Module 12: Upgrading from Exchange Server 2003 or Exchange Server 2007 to Exchange Server 2010 Course 10135A
Module 12: Upgrading from Exchange Server 2003 or Exchange Server 2007 to Exchange Server 2010 Course 10135A
Mention that the Exchange Server 2010 setup program checks the status of the current Exchange Server deployment. If SP2 is not installed on the Exchange 2007 servers, the installation will not complete. Emphasize that Exchange Server 2010 SP2 includes several schema updates. This means that the Service Pack deployment may be more complicated than most because of the requirement for testing schema updates in most organizations. Stress that Client Access servers must be deployed first and that all client connections must be configured to connect to the Client Access server. For most client connections, the Exchange Server 2010 Client Access Server will proxy the client request to the Exchange Server 2007 Client Access server. Module 12: Upgrading from Exchange Server 2003 or Exchange Server 2007 to Exchange Server 2010 Course 10135A
Use the diagram to describe the different scenarios that occur when the different messaging clients connect to the Exchange environment during coexistence. Emphasize the following differences from how the client access works with Exchange Server 2003: Exchange ActiveSync clients can connect to either the Exchange 2010 Client Access server or the Exchange 2007 Client Access server The Client Access servers can proxy Exchange ActiveSync and Web Services requests between versions. The Exchange 2010 Client Access server can proxy client requests to Exchange 2007 Client Access servers in sites that are not accessible from the Internet. Module 12: Upgrading from Exchange Server 2003 or Exchange Server 2007 to Exchange Server 2010 Course 10135A
Stress that because Exchange Server 2007 Mailbox servers require Exchange Server 2007 Client Access servers, the last Client Access servers cannot be removed until all of the mailboxes have been moved to Exchange Server 2010 Mailbox servers. Module 12: Upgrading from Exchange Server 2003 or Exchange Server 2007 to Exchange Server 2010 Course 10135A
Emphasize that Exchange Server 2007 Mailbox servers require Exchange Server 2007 Hub Transport servers in addition to Exchange Server 2007 Client Access servers. However, once all the mailboxes are moved to Exchange Server 2010 servers, you can remove the Exchange Server 2007 Hub Transport servers. You can do this on a per-site basis. For example, after moving all of the mailboxes to Exchange Server 2010, you can remove the Exchange Server 2007 Hub Transport server. The Exchange Server 2010 Hub Transport server in one site can send and receive e-mails with Exchange Server 2007 Hub Transport servers in the same or other sites. Module 12: Upgrading from Exchange Server 2003 or Exchange Server 2007 to Exchange Server 2010 Course 10135A
Review the list in the student manual of tasks that can be performed in each version of Exchange Management Console. Point out that the Exchange Management Console enforce the rules about what tasks can be performed on each version of Exchange server so there is no danger in inadvertently modifying a setting using the wrong version of Exchange Management Console. As you discuss the options for replicating the delegation of Administrative permissions in Exchange 2010, ask students how they have configured permissions in Exchange 2007 (if they are running Exchange 2007). You can then describe how they can replicate the permissions in Exchange 2010 using role groups. Module 12: Upgrading from Exchange Server 2003 or Exchange Server 2007 to Exchange Server 2010 Course 10135A
Stress the importance of removing the servers in the correct order when upgrading from Exchange Server 2007. Mention that once you have removed the last mailbox from the Exchange Server 2007 mailbox servers and moved all connectors to Exchange Server 2010, you can remove all other Exchange Server 2007 server roles because they are no longer used. Module 12: Upgrading from Exchange Server 2003 or Exchange Server 2007 to Exchange Server 2010 Course 10135A
Review Questions Your organization is deploying Exchange Server 2010 in an Exchange 2003 organization. You have made the changes to Active Directory. What is the first Exchange 2010 server role that you should deploy? How will this deployment change the user experience? Answer: You should deploy the Client Access server role first. However, this deployment will not change the user experience until you configure the non-MAPI clients to use the Client Access server for a mailbox access. Why do you need to configure a new external URL on Exchange Server 2007 Client Access servers when you deploy Exchange Server 2010 Client Access servers? Answer: The external URL redirects Outlook Web Access requests for users whose mailboxes are on Exchange 2007 Mailbox servers. The Autodiscover service on the Exchange 2010 Client Access server uses this URL to redirect the clients. Your organization includes two locations and Active Directory sites. You have deployed Exchange Server 2007 servers in both sites. You now are deploying Exchange Server 2010 servers in one of the sites and removing the Exchange Server 2007 servers. When can you remove the last Exchange 2007 Hub Transport server in the site? Answer: You can remove the last Hub Transport server when you move all of the mailboxes, public folders, and connectors from the Exchange Server 2007 servers in the site. As long as there is an Exchange 2007 Mailbox server in the site, you must maintain an Exchange 2007 Hub Transport server. . Common Issues Related to Desktop Application Support Identify the causes for the common issues related to upgrading to Exchange Server 2010 and fill in the troubleshooting tips. For answers, refer to relevant lessons in the module. Module 12: Upgrading from Exchange Server 2003 or Exchange Server 2007 to Exchange Server 2010 Course 10135A
Real-World Issues and Scenarios A. Datum has three office locations and three Active Directory sites. They have deployed Exchange Server 2003 servers in all offices, but have enabled Internet access to the servers only in the main office. What high-level process should A. Datum use to upgrade to Exchange Server 2010? Answer: They should upgrade the main office first, as this is the only site that is accessible from the Internet. After the upgrade in the main office is complete, they can upgrade the other offices. Your organization has deployed Forefront Threat Management Gateway (TMG) to secure access to the Client Access server deployment. You have completed all of the steps required to enable access to both the Exchange 2010 Client Access server and the Exchange 2007 Client Access server. What changes do you need to make on the TMG server? Answer: You need to configure TMG to forward all requests using the main Client Access server URL to the Exchange Server 2010 Client Access server. Then you need to configure Forefront TMG to forward requests sent to the alternate or legacy URL to the Exchange Server 2007 Client Access server. Your organization is deploying Exchange Server 2010 in an Exchange Server 2003 organization. Your organization does not provide Internet access to messaging clients, and all users are located in a single office. You deploy an Exchange Server 2010 server using a standard installation. What else do you need to do before you start moving mailboxes to the Exchange Server 2010 server? Users need to be able to access their mailboxes by using Outlook Web App and Outlook 2003. Answer: You do not need to do anything else before you start moving mailboxes. During the installation of the Hub Transport server role, you will be prompted for the Exchange Server 2003 server’s name that will be the routing group bridgehead server, to enable message flow. However, with this configuration, Exchange Server 2003 users need to use an Exchange Server 2003 front-end server to access their mailbox through Outlook Web Access, and they need to switch to the Exchange Server 2010 Client Access server when their mailbox moves. To enable the users to use the Exchange 2010 Client Access server while their mailbox is on the Exchange Server 2003 server, you need to add the Exchange 2003 URL to the Exchange 2010 Client Access server. Best Practices for Supporting Users Running Applications on Windows XP Help the students understand the best practices presented in this section. Ask students to consider these best practices in the context of their own business situations. Module 12: Upgrading from Exchange Server 2003 or Exchange Server 2007 to Exchange Server 2010 Course 10135A
Module 12: Upgrading from Exchange Server 2003 or Exchange Server 2007 to Exchange Server 2010 Course 10135A Remind students to complete the course evaluation.