Scott Schnoll discusses Exchange Server 2010 topology changes including consolidating client access paths through the new Client Access service and introducing shadow redundancy for improved transport resiliency. The document also provides guidance on scaling out Exchange 2010 servers rather than scaling up single servers and recommends processor core limits for different server roles in the beta/RC versions.
SIA311 Better Together: Microsoft Exchange Server 2010 and Microsoft Forefron...Louis Göhl
Â
Come learn how Forefront and Exchange Server 2010 work better together! This session covers how Forefront Protection 2010 for Exchange Server (FPE) and Forefront Online Protection for Exchange (FOPE) will facilitate protection of Microsoft Exchange Server 2010 from malware and unsolicited mail.
UNC309 - Getting the Most out of Microsoft Exchange Server 2010: Performance ...Louis Göhl
Â
Selecting the right server hardware for an Exchange 2010 deployment becomes much easier when you know the product team's scalability and performance guidelines. This session provides a look at the product team's guidance for the processor and memory requirements of each server role in Exchange 2010. A number of key performance enhancements from this release are discussed, and you also learn about how to use related tools like the Exchange Storage Calculator, Exchange Profile Analyzer, Loadgen, and Jetstress to take the guesswork out of server sizing.
This document provides an overview and agenda for migrating from Exchange Server 2003 and Active Directory 2008 to Exchange Server 2010 and Active Directory 2008 R2. The key steps include installing prerequisites, installing Exchange 2010, configuring Exchange 2010, migrating mailboxes and public folders from Exchange 2003, updating DNS, and removing the legacy Exchange 2003 servers once the migration is complete. PowerShell commands are provided as alternatives to the graphical user interface for many configuration tasks.
Microsoft Exchange Server 2010 provides benefits and improvements over previous versions such as enhanced protection, compliance, flexibility and reliability, continuous availability, simplified administration, and deployment flexibility. It allows for anywhere access through Outlook on the web, phone, and mobile devices. Exchange 2010 also aims to help users manage inbox overload through improved conversation view and filtering, integrate archiving and retention capabilities, and provide advanced security and protection of communications.
Exchange 2010 introduces several new high availability features:
- It allows up to 16 replicated copies of each database across multiple mailbox servers for improved redundancy.
- Failover can occur at the database level within 30 seconds for higher availability.
- Storage has been optimized to support larger mailboxes and allow storage on inexpensive JBOD disks without RAID.
- Simplified administration and incremental deployment make high availability easier and cheaper to manage.
SIA311 Better Together: Microsoft Exchange Server 2010 and Microsoft Forefron...Louis Göhl
Â
Come learn how Forefront and Exchange Server 2010 work better together! This session covers how Forefront Protection 2010 for Exchange Server (FPE) and Forefront Online Protection for Exchange (FOPE) will facilitate protection of Microsoft Exchange Server 2010 from malware and unsolicited mail.
UNC309 - Getting the Most out of Microsoft Exchange Server 2010: Performance ...Louis Göhl
Â
Selecting the right server hardware for an Exchange 2010 deployment becomes much easier when you know the product team's scalability and performance guidelines. This session provides a look at the product team's guidance for the processor and memory requirements of each server role in Exchange 2010. A number of key performance enhancements from this release are discussed, and you also learn about how to use related tools like the Exchange Storage Calculator, Exchange Profile Analyzer, Loadgen, and Jetstress to take the guesswork out of server sizing.
This document provides an overview and agenda for migrating from Exchange Server 2003 and Active Directory 2008 to Exchange Server 2010 and Active Directory 2008 R2. The key steps include installing prerequisites, installing Exchange 2010, configuring Exchange 2010, migrating mailboxes and public folders from Exchange 2003, updating DNS, and removing the legacy Exchange 2003 servers once the migration is complete. PowerShell commands are provided as alternatives to the graphical user interface for many configuration tasks.
Microsoft Exchange Server 2010 provides benefits and improvements over previous versions such as enhanced protection, compliance, flexibility and reliability, continuous availability, simplified administration, and deployment flexibility. It allows for anywhere access through Outlook on the web, phone, and mobile devices. Exchange 2010 also aims to help users manage inbox overload through improved conversation view and filtering, integrate archiving and retention capabilities, and provide advanced security and protection of communications.
Exchange 2010 introduces several new high availability features:
- It allows up to 16 replicated copies of each database across multiple mailbox servers for improved redundancy.
- Failover can occur at the database level within 30 seconds for higher availability.
- Storage has been optimized to support larger mailboxes and allow storage on inexpensive JBOD disks without RAID.
- Simplified administration and incremental deployment make high availability easier and cheaper to manage.
The document discusses the architecture of Microsoft Exchange 2013. Exchange 2013 uses a building block approach to facilitate deployments at any scale. It utilizes server role evolution, network layer improvements, and versioning/interoperability principles. The architecture features load balancing at the network and client access layers. Exchange 2013 also includes a new managed store that reduces database IOPS and supports larger mailboxes and modern public folders with improved search capabilities.
Exchange Server 2013 introduced new server roles that simplified the architecture. The Client Access server role became a thin, stateless proxy server that routes client protocol requests. The Mailbox server role consolidated functionality into a single server that processes, renders, and stores Exchange data. This evolution improved hardware efficiency, simplified deployments, and enabled cross-version interoperability. The Front End Transport service acts as a load-balanced ingress/egress point that determines the optimal Mailbox server for delivering messages to avoid unnecessary hops.
Paul's presentation at SOA Workshop,Colombo,Sri Lanka identifies how ESBs fit into a Service Oriented Architecture, discusses when to use an ESB and when not to, looks at ESB patterns and anti-patterns, covers some simple ESB approaches and investigates how ESBs can fit into EDA.
Here are the key steps to migrate from Exchange 2010 to Exchange 2013:
1. Prepare - Install Exchange 2010 SP3 across the organization, prepare Active Directory with Exchange schema extensions, validate Exchange 2010 Client Access connectivity
2. Deploy Exchange 2013 servers - Install new Exchange 2013 Mailbox and Client Access servers
3. Obtain and deploy certificates - Obtain and deploy SSL certificates on the Exchange 2013 Client Access servers
4. Cutover mailboxes - Use cutover or staged migration to move mailboxes from Exchange 2010 to Exchange 2013 servers
5. Redirect clients to Exchange 2013 - Update autodiscover and DNS records to redirect clients to the new Exchange 2013 Client Access servers
- The main difference between OBIEE 10g and 11g architectures is that 11g wraps components in the WebLogic Server (WLS) platform and uses Enterprise Manager (EM) for management.
- Key components like the BI server, presentation server, and BI publisher are unchanged, but some reworking in 11g includes unified logging and managing configuration files through EM.
- New features in the RPD include support for ragged/skipped hierarchies, parent-child hierarchies, lookup tables, and the action framework.
- New analytics features include hierarchical columns, KPIs, scorecards, chart viewer with sliders, and BI published reporting.
An Enterprise Service Bus (ESB) provides a common integration infrastructure across enterprise applications and systems. It acts as a lightweight backbone through which software services and components interact. The ESB handles messaging, routing, protocol conversion, and provides capabilities like quality of service, policy enforcement, transaction management, and security. It evolved from point-to-point integration and message-oriented middleware as a more flexible, scalable and standards-based integration approach.
ViestinnÀn seminaari 8.11.2012 / ExchangeSalcom Group
Â
The document announces a Microsoft Exchange Server preview workshop on October 2012 that will be led by a senior trainer/consultant and will cover Exchange from all versions, certification services, and server infrastructure. The workshop will discuss how Exchange enables remaining in control of communications both online and on-premises, helping users be more productive across devices, and keeping the organization safe by protecting information and meeting compliance requirements.
WSO2Con2011: Using WSO2 ESB with SAP ERP (Retail)WSO2
Â
The document discusses using WSO2 ESB to integrate SAP ERP with KeellsSuper, a leading supermarket chain in Sri Lanka. It provides background on John Keells Group, which implemented SAP across its subsidiaries, and on KeellsSuper's business requirements to migrate to SAP's retail industry solution. The solutions evaluated for integration included SAP PI, direct RFC/BAPI calls, and file uploads. The recommended and implemented solution was to use WSO2 ESB for its lightweight integration capabilities to streamline the SAP and POS integration and eliminate performance issues.
Introduction to the Azure Service Bus EAI & EDI featuresiedi featuresSandro Pereira
Â
In this session weâll see EAI (Enterprise Application Integration) and EDI (Electronic Data Interchange) functionalities like: how to manage EDI message exchanges and trading partners with the Azure ... (Bouvet BizTalk Innovation Event)
Managing Enterprise Services through Service Versioning & Governance - Impact...Prolifics
Â
Speakers: Brian Bubonic, Huntington National Bank; Emil Thomas, Prolifics
Description: Huntington National Bank is a Midwestern bank headquartered in Columbus, Ohio. Over the past one year, Huntington has been trying to enforce service governance by using IBM SOA products and also by adopting more stricter policies and standards around design, development and usage of the services. With an estimated 500 plus enterprise services to be in Production by the end of 2012 and with challenging requirements to evolve services continually for the various consuming applications, this is no mean feat. In this presentation, we will showcase the challenges faced in the journey, the approaches taken and the benefits achieved with enterprise service versioning and enforcing service governance to achieve enterprise service agility.
The document discusses service oriented architecture (SOA) and enterprise service buses (ESBs). It defines SOA as using well-defined interactions between loosely coupled systems. ESBs are defined as providing "any to any" connectivity and transformation of data, including web services, using a proven middleware infrastructure. The document discusses how ESBs can help simplify SOA deployment by providing features like virtualization, transport matching, message transformation and an integrated registry. It also covers ESB patterns, such as the concentrator and federated patterns, and anti-patterns to avoid when using an ESB.
This document provides a summary of 39 questions that are commonly asked during interviews for Oracle SOA Suite 11g positions. The questions cover topics like the differences between SOA Suite 10g and 11g, definitions of core SOA concepts like SOA, SCA, mediators and ESBs, how to implement various integration patterns in Oracle Service Bus, and details about developing and deploying BPEL processes.
This document provides an overview of Oracle Service Bus. It discusses key SOA concepts like service enablement, mediation, and orchestration that can be addressed using a service bus. It describes the target audience for learning about OSB and provides a roadmap for the course content, which will cover the OSB architecture, proxy service development, and service management and monitoring capabilities. It also gives examples of how a service bus can provide location transparency, backwards compatibility, message enrichment, and service orchestration.
The document discusses Enterprise Service Bus (ESB) and Java Business Integration (JBI). It defines ESB as middleware that acts as a mediator between different protocols and products. JBI is a specification that defines a standard architecture and container for pluggable integration components. OpenESB is an open source implementation of an ESB runtime based on JBI. It provides tools for developing, deploying, and managing composite applications. The document presents examples of how OpenESB and GlassFish can be used to implement a loan processing application using components like BPEL, JavaEE, and XSLT within a JBI architecture.
This document provides an overview of Apache Camel, an open source integration framework. It discusses integration patterns, why Camel is named Camel, Camel's parents (Apache ServiceMix), messaging concepts like queues and topics, common message brokers like ActiveMQ, characteristics of an ESB including routing and transformation, OSGi and JBI specifications, and what components and DSLs are included in Camel.
Introduction to Service Oriented ArchitectureDATA Inc.
Â
The document introduces SOA and discusses its key concepts. It describes why organizations adopt SOA, defines what SOA is, and outlines some of its benefits including reuse, flexibility and cost savings. It also discusses components of a SOA system like services, service contracts and an enterprise service bus.
Exchange 2013 introduces a new server role architecture with two main building blocks - the Database Availability Group (DAG) and the Client Access server role. The DAG allows for multiple Mailbox servers to host copies of mailbox databases and provide failover capabilities. The Client Access role is a load balanced front end that routes clients to the appropriate Mailbox server based on the active database copy. This new architecture aims to simplify deployment and administration while improving hardware efficiency and cross-version interoperability compared to previous versions of Exchange.
WSO2 Carbon and WSO2 Stratos Summer Release Roundup WSO2
Â
- The webinar covered the upcoming releases of WSO2 Carbon and Stratos in summer 2012, including new products, features, and capabilities.
- Carbon 4.0 includes improvements to deployment synchronization, performance, and multi-tenancy, as well as new products like API Manager and Storage Server.
- Stratos 2.0 features a new cartridge model for multiple languages/frameworks, support for additional IaaS providers, and an enhanced management console.
- Both releases focus on improved scalability, manageability, and a modular approach to building and deploying middleware components.
Driving Business Innovation: Latest Generative AI Advancements & Success StorySafe Software
Â
Are you ready to revolutionize how you handle data? Join us for a webinar where weâll bring you up to speed with the latest advancements in Generative AI technology and discover how leveraging FME with tools from giants like Google Gemini, Amazon, and Microsoft OpenAI can supercharge your workflow efficiency.
During the hour, weâll take you through:
Guest Speaker Segment with Hannah Barrington: Dive into the world of dynamic real estate marketing with Hannah, the Marketing Manager at Workspace Group. Hear firsthand how their team generates engaging descriptions for thousands of office units by integrating diverse data sourcesâfrom PDF floorplans to web pagesâusing FME transformers, like OpenAIVisionConnector and AnthropicVisionConnector. This use case will show you how GenAI can streamline content creation for marketing across the board.
Ollama Use Case: Learn how Scenario Specialist Dmitri Bagh has utilized Ollama within FME to input data, create custom models, and enhance security protocols. This segment will include demos to illustrate the full capabilities of FME in AI-driven processes.
Custom AI Models: Discover how to leverage FME to build personalized AI models using your data. Whether itâs populating a model with local data for added security or integrating public AI tools, find out how FME facilitates a versatile and secure approach to AI.
Weâll wrap up with a live Q&A session where you can engage with our experts on your specific use cases, and learn more about optimizing your data workflows with AI.
This webinar is ideal for professionals seeking to harness the power of AI within their data management systems while ensuring high levels of customization and security. Whether you're a novice or an expert, gain actionable insights and strategies to elevate your data processes. Join us to see how FME and AI can revolutionize how you work with data!
Dive into the realm of operating systems (OS) with Pravash Chandra Das, a seasoned Digital Forensic Analyst, as your guide. đ This comprehensive presentation illuminates the core concepts, types, and evolution of OS, essential for understanding modern computing landscapes.
Beginning with the foundational definition, Das clarifies the pivotal role of OS as system software orchestrating hardware resources, software applications, and user interactions. Through succinct descriptions, he delineates the diverse types of OS, from single-user, single-task environments like early MS-DOS iterations, to multi-user, multi-tasking systems exemplified by modern Linux distributions.
Crucial components like the kernel and shell are dissected, highlighting their indispensable functions in resource management and user interface interaction. Das elucidates how the kernel acts as the central nervous system, orchestrating process scheduling, memory allocation, and device management. Meanwhile, the shell serves as the gateway for user commands, bridging the gap between human input and machine execution. đ»
The narrative then shifts to a captivating exploration of prominent desktop OSs, Windows, macOS, and Linux. Windows, with its globally ubiquitous presence and user-friendly interface, emerges as a cornerstone in personal computing history. macOS, lauded for its sleek design and seamless integration with Apple's ecosystem, stands as a beacon of stability and creativity. Linux, an open-source marvel, offers unparalleled flexibility and security, revolutionizing the computing landscape. đ„ïž
Moving to the realm of mobile devices, Das unravels the dominance of Android and iOS. Android's open-source ethos fosters a vibrant ecosystem of customization and innovation, while iOS boasts a seamless user experience and robust security infrastructure. Meanwhile, discontinued platforms like Symbian and Palm OS evoke nostalgia for their pioneering roles in the smartphone revolution.
The journey concludes with a reflection on the ever-evolving landscape of OS, underscored by the emergence of real-time operating systems (RTOS) and the persistent quest for innovation and efficiency. As technology continues to shape our world, understanding the foundations and evolution of operating systems remains paramount. Join Pravash Chandra Das on this illuminating journey through the heart of computing. đ
The document discusses the architecture of Microsoft Exchange 2013. Exchange 2013 uses a building block approach to facilitate deployments at any scale. It utilizes server role evolution, network layer improvements, and versioning/interoperability principles. The architecture features load balancing at the network and client access layers. Exchange 2013 also includes a new managed store that reduces database IOPS and supports larger mailboxes and modern public folders with improved search capabilities.
Exchange Server 2013 introduced new server roles that simplified the architecture. The Client Access server role became a thin, stateless proxy server that routes client protocol requests. The Mailbox server role consolidated functionality into a single server that processes, renders, and stores Exchange data. This evolution improved hardware efficiency, simplified deployments, and enabled cross-version interoperability. The Front End Transport service acts as a load-balanced ingress/egress point that determines the optimal Mailbox server for delivering messages to avoid unnecessary hops.
Paul's presentation at SOA Workshop,Colombo,Sri Lanka identifies how ESBs fit into a Service Oriented Architecture, discusses when to use an ESB and when not to, looks at ESB patterns and anti-patterns, covers some simple ESB approaches and investigates how ESBs can fit into EDA.
Here are the key steps to migrate from Exchange 2010 to Exchange 2013:
1. Prepare - Install Exchange 2010 SP3 across the organization, prepare Active Directory with Exchange schema extensions, validate Exchange 2010 Client Access connectivity
2. Deploy Exchange 2013 servers - Install new Exchange 2013 Mailbox and Client Access servers
3. Obtain and deploy certificates - Obtain and deploy SSL certificates on the Exchange 2013 Client Access servers
4. Cutover mailboxes - Use cutover or staged migration to move mailboxes from Exchange 2010 to Exchange 2013 servers
5. Redirect clients to Exchange 2013 - Update autodiscover and DNS records to redirect clients to the new Exchange 2013 Client Access servers
- The main difference between OBIEE 10g and 11g architectures is that 11g wraps components in the WebLogic Server (WLS) platform and uses Enterprise Manager (EM) for management.
- Key components like the BI server, presentation server, and BI publisher are unchanged, but some reworking in 11g includes unified logging and managing configuration files through EM.
- New features in the RPD include support for ragged/skipped hierarchies, parent-child hierarchies, lookup tables, and the action framework.
- New analytics features include hierarchical columns, KPIs, scorecards, chart viewer with sliders, and BI published reporting.
An Enterprise Service Bus (ESB) provides a common integration infrastructure across enterprise applications and systems. It acts as a lightweight backbone through which software services and components interact. The ESB handles messaging, routing, protocol conversion, and provides capabilities like quality of service, policy enforcement, transaction management, and security. It evolved from point-to-point integration and message-oriented middleware as a more flexible, scalable and standards-based integration approach.
ViestinnÀn seminaari 8.11.2012 / ExchangeSalcom Group
Â
The document announces a Microsoft Exchange Server preview workshop on October 2012 that will be led by a senior trainer/consultant and will cover Exchange from all versions, certification services, and server infrastructure. The workshop will discuss how Exchange enables remaining in control of communications both online and on-premises, helping users be more productive across devices, and keeping the organization safe by protecting information and meeting compliance requirements.
WSO2Con2011: Using WSO2 ESB with SAP ERP (Retail)WSO2
Â
The document discusses using WSO2 ESB to integrate SAP ERP with KeellsSuper, a leading supermarket chain in Sri Lanka. It provides background on John Keells Group, which implemented SAP across its subsidiaries, and on KeellsSuper's business requirements to migrate to SAP's retail industry solution. The solutions evaluated for integration included SAP PI, direct RFC/BAPI calls, and file uploads. The recommended and implemented solution was to use WSO2 ESB for its lightweight integration capabilities to streamline the SAP and POS integration and eliminate performance issues.
Introduction to the Azure Service Bus EAI & EDI featuresiedi featuresSandro Pereira
Â
In this session weâll see EAI (Enterprise Application Integration) and EDI (Electronic Data Interchange) functionalities like: how to manage EDI message exchanges and trading partners with the Azure ... (Bouvet BizTalk Innovation Event)
Managing Enterprise Services through Service Versioning & Governance - Impact...Prolifics
Â
Speakers: Brian Bubonic, Huntington National Bank; Emil Thomas, Prolifics
Description: Huntington National Bank is a Midwestern bank headquartered in Columbus, Ohio. Over the past one year, Huntington has been trying to enforce service governance by using IBM SOA products and also by adopting more stricter policies and standards around design, development and usage of the services. With an estimated 500 plus enterprise services to be in Production by the end of 2012 and with challenging requirements to evolve services continually for the various consuming applications, this is no mean feat. In this presentation, we will showcase the challenges faced in the journey, the approaches taken and the benefits achieved with enterprise service versioning and enforcing service governance to achieve enterprise service agility.
The document discusses service oriented architecture (SOA) and enterprise service buses (ESBs). It defines SOA as using well-defined interactions between loosely coupled systems. ESBs are defined as providing "any to any" connectivity and transformation of data, including web services, using a proven middleware infrastructure. The document discusses how ESBs can help simplify SOA deployment by providing features like virtualization, transport matching, message transformation and an integrated registry. It also covers ESB patterns, such as the concentrator and federated patterns, and anti-patterns to avoid when using an ESB.
This document provides a summary of 39 questions that are commonly asked during interviews for Oracle SOA Suite 11g positions. The questions cover topics like the differences between SOA Suite 10g and 11g, definitions of core SOA concepts like SOA, SCA, mediators and ESBs, how to implement various integration patterns in Oracle Service Bus, and details about developing and deploying BPEL processes.
This document provides an overview of Oracle Service Bus. It discusses key SOA concepts like service enablement, mediation, and orchestration that can be addressed using a service bus. It describes the target audience for learning about OSB and provides a roadmap for the course content, which will cover the OSB architecture, proxy service development, and service management and monitoring capabilities. It also gives examples of how a service bus can provide location transparency, backwards compatibility, message enrichment, and service orchestration.
The document discusses Enterprise Service Bus (ESB) and Java Business Integration (JBI). It defines ESB as middleware that acts as a mediator between different protocols and products. JBI is a specification that defines a standard architecture and container for pluggable integration components. OpenESB is an open source implementation of an ESB runtime based on JBI. It provides tools for developing, deploying, and managing composite applications. The document presents examples of how OpenESB and GlassFish can be used to implement a loan processing application using components like BPEL, JavaEE, and XSLT within a JBI architecture.
This document provides an overview of Apache Camel, an open source integration framework. It discusses integration patterns, why Camel is named Camel, Camel's parents (Apache ServiceMix), messaging concepts like queues and topics, common message brokers like ActiveMQ, characteristics of an ESB including routing and transformation, OSGi and JBI specifications, and what components and DSLs are included in Camel.
Introduction to Service Oriented ArchitectureDATA Inc.
Â
The document introduces SOA and discusses its key concepts. It describes why organizations adopt SOA, defines what SOA is, and outlines some of its benefits including reuse, flexibility and cost savings. It also discusses components of a SOA system like services, service contracts and an enterprise service bus.
Exchange 2013 introduces a new server role architecture with two main building blocks - the Database Availability Group (DAG) and the Client Access server role. The DAG allows for multiple Mailbox servers to host copies of mailbox databases and provide failover capabilities. The Client Access role is a load balanced front end that routes clients to the appropriate Mailbox server based on the active database copy. This new architecture aims to simplify deployment and administration while improving hardware efficiency and cross-version interoperability compared to previous versions of Exchange.
WSO2 Carbon and WSO2 Stratos Summer Release Roundup WSO2
Â
- The webinar covered the upcoming releases of WSO2 Carbon and Stratos in summer 2012, including new products, features, and capabilities.
- Carbon 4.0 includes improvements to deployment synchronization, performance, and multi-tenancy, as well as new products like API Manager and Storage Server.
- Stratos 2.0 features a new cartridge model for multiple languages/frameworks, support for additional IaaS providers, and an enhanced management console.
- Both releases focus on improved scalability, manageability, and a modular approach to building and deploying middleware components.
Driving Business Innovation: Latest Generative AI Advancements & Success StorySafe Software
Â
Are you ready to revolutionize how you handle data? Join us for a webinar where weâll bring you up to speed with the latest advancements in Generative AI technology and discover how leveraging FME with tools from giants like Google Gemini, Amazon, and Microsoft OpenAI can supercharge your workflow efficiency.
During the hour, weâll take you through:
Guest Speaker Segment with Hannah Barrington: Dive into the world of dynamic real estate marketing with Hannah, the Marketing Manager at Workspace Group. Hear firsthand how their team generates engaging descriptions for thousands of office units by integrating diverse data sourcesâfrom PDF floorplans to web pagesâusing FME transformers, like OpenAIVisionConnector and AnthropicVisionConnector. This use case will show you how GenAI can streamline content creation for marketing across the board.
Ollama Use Case: Learn how Scenario Specialist Dmitri Bagh has utilized Ollama within FME to input data, create custom models, and enhance security protocols. This segment will include demos to illustrate the full capabilities of FME in AI-driven processes.
Custom AI Models: Discover how to leverage FME to build personalized AI models using your data. Whether itâs populating a model with local data for added security or integrating public AI tools, find out how FME facilitates a versatile and secure approach to AI.
Weâll wrap up with a live Q&A session where you can engage with our experts on your specific use cases, and learn more about optimizing your data workflows with AI.
This webinar is ideal for professionals seeking to harness the power of AI within their data management systems while ensuring high levels of customization and security. Whether you're a novice or an expert, gain actionable insights and strategies to elevate your data processes. Join us to see how FME and AI can revolutionize how you work with data!
Dive into the realm of operating systems (OS) with Pravash Chandra Das, a seasoned Digital Forensic Analyst, as your guide. đ This comprehensive presentation illuminates the core concepts, types, and evolution of OS, essential for understanding modern computing landscapes.
Beginning with the foundational definition, Das clarifies the pivotal role of OS as system software orchestrating hardware resources, software applications, and user interactions. Through succinct descriptions, he delineates the diverse types of OS, from single-user, single-task environments like early MS-DOS iterations, to multi-user, multi-tasking systems exemplified by modern Linux distributions.
Crucial components like the kernel and shell are dissected, highlighting their indispensable functions in resource management and user interface interaction. Das elucidates how the kernel acts as the central nervous system, orchestrating process scheduling, memory allocation, and device management. Meanwhile, the shell serves as the gateway for user commands, bridging the gap between human input and machine execution. đ»
The narrative then shifts to a captivating exploration of prominent desktop OSs, Windows, macOS, and Linux. Windows, with its globally ubiquitous presence and user-friendly interface, emerges as a cornerstone in personal computing history. macOS, lauded for its sleek design and seamless integration with Apple's ecosystem, stands as a beacon of stability and creativity. Linux, an open-source marvel, offers unparalleled flexibility and security, revolutionizing the computing landscape. đ„ïž
Moving to the realm of mobile devices, Das unravels the dominance of Android and iOS. Android's open-source ethos fosters a vibrant ecosystem of customization and innovation, while iOS boasts a seamless user experience and robust security infrastructure. Meanwhile, discontinued platforms like Symbian and Palm OS evoke nostalgia for their pioneering roles in the smartphone revolution.
The journey concludes with a reflection on the ever-evolving landscape of OS, underscored by the emergence of real-time operating systems (RTOS) and the persistent quest for innovation and efficiency. As technology continues to shape our world, understanding the foundations and evolution of operating systems remains paramount. Join Pravash Chandra Das on this illuminating journey through the heart of computing. đ
Ocean lotus Threat actors project by John Sitima 2024 (1).pptxSitimaJohn
Â
Ocean Lotus cyber threat actors represent a sophisticated, persistent, and politically motivated group that poses a significant risk to organizations and individuals in the Southeast Asian region. Their continuous evolution and adaptability underscore the need for robust cybersecurity measures and international cooperation to identify and mitigate the threats posed by such advanced persistent threat groups.
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
Trusted Execution Environment for Decentralized Process MiningLucaBarbaro3
Â
Presentation of the paper "Trusted Execution Environment for Decentralized Process Mining" given during the CAiSE 2024 Conference in Cyprus on June 7, 2024.
TrustArc Webinar - 2024 Global Privacy SurveyTrustArc
Â
How does your privacy program stack up against your peers? What challenges are privacy teams tackling and prioritizing in 2024?
In the fifth annual Global Privacy Benchmarks Survey, we asked over 1,800 global privacy professionals and business executives to share their perspectives on the current state of privacy inside and outside of their organizations. This yearâs report focused on emerging areas of importance for privacy and compliance professionals, including considerations and implications of Artificial Intelligence (AI) technologies, building brand trust, and different approaches for achieving higher privacy competence scores.
See how organizational priorities and strategic approaches to data security and privacy are evolving around the globe.
This webinar will review:
- The top 10 privacy insights from the fifth annual Global Privacy Benchmarks Survey
- The top challenges for privacy leaders, practitioners, and organizations in 2024
- Key themes to consider in developing and maintaining your privacy program
Fueling AI with Great Data with Airbyte WebinarZilliz
Â
This talk will focus on how to collect data from a variety of sources, leveraging this data for RAG and other GenAI use cases, and finally charting your course to productionalization.
Nunit vs XUnit vs MSTest Differences Between These Unit Testing Frameworks.pdfflufftailshop
Â
When it comes to unit testing in the .NET ecosystem, developers have a wide range of options available. Among the most popular choices are NUnit, XUnit, and MSTest. These unit testing frameworks provide essential tools and features to help ensure the quality and reliability of code. However, understanding the differences between these frameworks is crucial for selecting the most suitable one for your projects.
leewayhertz.com-AI in predictive maintenance Use cases technologies benefits ...alexjohnson7307
Â
Predictive maintenance is a proactive approach that anticipates equipment failures before they happen. At the forefront of this innovative strategy is Artificial Intelligence (AI), which brings unprecedented precision and efficiency. AI in predictive maintenance is transforming industries by reducing downtime, minimizing costs, and enhancing productivity.
Letter and Document Automation for Bonterra Impact Management (fka Social Sol...Jeffrey Haguewood
Â
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on automated letter generation for Bonterra Impact Management using Google Workspace or Microsoft 365.
Interested in deploying letter generation automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
Your One-Stop Shop for Python Success: Top 10 US Python Development Providersakankshawande
Â
Simplify your search for a reliable Python development partner! This list presents the top 10 trusted US providers offering comprehensive Python development services, ensuring your project's success from conception to completion.
Taking AI to the Next Level in Manufacturing.pdfssuserfac0301
Â
Read Taking AI to the Next Level in Manufacturing to gain insights on AI adoption in the manufacturing industry, such as:
1. How quickly AI is being implemented in manufacturing.
2. Which barriers stand in the way of AI adoption.
3. How data quality and governance form the backbone of AI.
4. Organizational processes and structures that may inhibit effective AI adoption.
6. Ideas and approaches to help build your organization's AI strategy.
Programming Foundation Models with DSPy - Meetup SlidesZilliz
Â
Prompting language models is hard, while programming language models is easy. In this talk, I will discuss the state-of-the-art framework DSPy for programming foundation models with its powerful optimizers and runtime constraint system.
Generating privacy-protected synthetic data using Secludy and MilvusZilliz
Â
During this demo, the founders of Secludy will demonstrate how their system utilizes Milvus to store and manipulate embeddings for generating privacy-protected synthetic data. Their approach not only maintains the confidentiality of the original data but also enhances the utility and scalability of LLMs under privacy constraints. Attendees, including machine learning engineers, data scientists, and data managers, will witness first-hand how Secludy's integration with Milvus empowers organizations to harness the power of LLMs securely and efficiently.
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdfChart Kalyan
Â
A Mix Chart displays historical data of numbers in a graphical or tabular form. The Kalyan Rajdhani Mix Chart specifically shows the results of a sequence of numbers over different periods.
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAUpanagenda
Â
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind fĂŒr viele in der HCL-Community seit letztem Jahr ein heiĂes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und LizenzgebĂŒhren zu kĂ€mpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklĂ€ren Ihnen, wie Sie hĂ€ufige Konfigurationsprobleme lösen können, die dazu fĂŒhren können, dass mehr Benutzer gezĂ€hlt werden als nötig, und wie Sie ĂŒberflĂŒssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige AnsĂ€tze, die zu unnötigen Ausgaben fĂŒhren können, z. B. wenn ein Personendokument anstelle eines Mail-Ins fĂŒr geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche FĂ€lle und deren Lösungen. Und natĂŒrlich erklĂ€ren wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt nĂ€herbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Ăberblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und ĂŒberflĂŒssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps fĂŒr hĂ€ufige Problembereiche, wie z. B. Team-PostfĂ€cher, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
3. Agenda
Discuss the topology changes introduced in
Exchange Server 2010
Client Access
Transport
Mailbox
Understand our guidance on server sizing
4. Exchange 2010 Enterprise Topology
Enterprise Network Phone system
(PBX or VOIP)
Edge Transport Hub Transport
Routing & AV/AS Routing & Policy
External
SMTP
servers
Mailbox Unified Messaging
Storage of mailbox Voice mail &
and public folder
voice access
Mobile phone items
Client Access
Web browser Client connectivity
Web services
Outlook
(remote user) Line of business application
Outlook (local user)
5. Consolidation of Store Access Paths
Entourage
Exchange Components Exchange Components
Transport
WS
Transport WS Agents
OWA Agents
Mailbox
OWA
Mailbox
Agents UM Agents UM
Sync Outlook / Sync
MAPI clients
MAPI,
Middle
Exchange Outlook /
Exchange
Middle
MAPI clients RFR &
Tier
Biz Logic Biz Logic
Tier
NSPI RPC
Entourage
Exchange Core Biz Logic
MAPI RPC DAV
Mailbox
Mailbox
MAPI RPC
Store
Store
7. Client Access
The middle tier Outlook Clients
CAS is true middle tier with new
services and functionality designed to
restrict all Outlook data access to a
single common path by migrating
Mailbox and Directory endpoints to CAS
Exchange CAS Array
Outlook data connections go to RPC
Client Access service on CAS instead of
connecting directly to mailbox servers
Address Book service on CAS replaces
the DSProxy interface
MBX GC
Public folder connections connect
directly to the Mailbox server, but
through RPC Client Access service on
backend
8. Client Access
How RPC Client Access service improves experience
Provides a better client experience during switchovers/failovers
When a MBX server fails over, Outlook client will only see ~30 sec
disconnection, as compared to 1-TTL min before
Uses the same business logic for Outlook and other CAS clients
Calendar logging + fix up
Content/body conversion
Greatly simplifies AD topology requirements for Outlook
Supports more concurrent connections/mailboxes per
Mailbox server
Reduces code and client logic in Exchange Store process for
increased reliability
9. Client Access
How directory referral connections work
1. Outlook calls get Address Book
server API
2. CAS queries Active Directory 4
1 3
a. Mailbox location (AD site)
b. Mailbox version
AD Site 2
AD Site 1
c. RpcClientAccessServer property of
mailbox database
3. CAS tells Outlook which CAS or CAS CAS CAS
2010 2 2010
array should be used for directory
requests
4. Outlook connects to the
appropriate CAS MBX 2010 GC MBX 2010 GC
If mailbox is moved back to 2003/2007, CAS will redirect the client to the
mailbox server so that it can provide a referral to a global catalog server
Otherwise, all legacy mailboxes will get directory referrals from mailbox server
10. Client Access Outlook connecting
Outlook anywhere improvements with Outlook
Anywhere
Outlook Anywhere clients use HTTPS HTTPS
the Address Book service on RPC_IN_DATA RPC_OUT_DATA
Windows 2008+
CAS for directory-related RPC/HTTP Proxy
requests
This architecture resolves the RPC_IN_DATA RPC_OUT_DATA
issue regarding DSProxy and CAS
split HTTP connections that are RPC Client Access and
Address Book services
due to using SSL-ID load
balancing solutions LDAP RPC
AD Mailbox
11. Client Access
Writing to the directory
New behavior ensure that Outlook can write changes to Active
Directory for the following scenarios
Distribution group membership
Delegate management
Certificate management
When the Address Book service detects one of these
modifications, it will utilize the appropriate cmdlet to commit
the change to Active Directory based on the property tag
(assuming user is scoped and authorized to make those
changes)
Add/Remove-DistributionGroupMember
Set-Mailbox -PublicDelegates
Set-Mailbox -UserCertificate -UserSMIMECertificate
12. Client Access
Scaling mailbox connections 60K outbound 60K outbound
connections / connections /
CAS IP (W2K8) MBX server
Outlook Anywhere Clients CAS MBX GC
Exchange Server 2007
60K connections / MBX server
Outlook Clients MBX
Exchange Server 2007
13. Client Access
Scaling mailbox connections
# of CAS servers
x 100 connections / CAS RPCCA
service/process
MBX
Outlook Clients Exchange CAS NLB
LDAP
GC
Exchange Server 2010
14. Client Access
Firewall/proxy guidelines
Internet Security and Acceleration (ISA) Server 2006
Kernel memory limitations imposed by the 32-bit architecture
ISA:CAS ratio 3:1 (worst case â heavy Outlook Anywhere usage)
Important when you have a large percentage of your users connected via Outlook
Anywhere, as the ratio of Transmission Control Protocol (TCP) connections to users is
much higher than you would see for Outlook Web Access (OWA), ActiveSync, POP, or
IMAP traffic
Beyond ISA 2006 ⊠pre-release product information
Forefront Unified Access Gateway (UAG)
Next-generation secure remote access product and the future version of Microsoft
Intelligent Application Gatewayânative 64-bit architecture
Will be tested with Exchange Server 2010
Forefront Threat Management Gateway (TMG)
Next-generation network security product and the future version of Microsoft ISA
Serverânative 64-bit architecture
Will be tested with Exchange Server 2010
15. Client Access
Architectural considerations
Versioning
Exchange 2010 CAS required in every AD site where
Exchange 2010 MBX is deployed
Exchange 2007 MBX requires Exchange 2007 CAS
Load balancing
If planning on deploying more than 8 CAS servers in a load
balanced array, consider deploying hardware load balancing
solution
If CAS is co-located with highly available Mailbox server,
then non-Windows NLB solution is needed (e.g., hardware
load balancer, ISA load balancing, or third-party software-
based load balancing)
17. Transport Roles
Resiliency issues in Exchange 2007
Transport database is stateful
Loss of service results in loss of mail
Transport dumpster impacts the environment
In extreme cases, up to 200% increase in
IOPS/message due to many SGs and inefficient
cache usage when compared to similar scenarios
without dumpster
Redelivery submission results in entire quota being
redelivered and store removing duplicates
18. Transport Roles
Exchange 2010 resiliency improvements
Shadow redundancy is a new feature of transport
Provides redundancy for messages for the entire time they
are in transit
Transport becomes stateless
Eliminates need for RAID, which reduces 50% write I/O
Transport Dumpster Changes
Database replication feedback is now used to control which
messages remain in transport dumpster
When message has been replicated to all database copies,
message is truncated from transport dumpster
Transport dumpster size is now based on log replication
latency and frequency of feedback
19. Transport Roles
How does shadow redundancy work?
1. Hub (shadow) delivers message to
Hub Edge1 (primary)
Detects that Edge1 supports Transport
1
redundancy through XSHADOW verb
Hub moves message to shadow queue and
stamps Edge1 as current, primary owner
Edge1 Edge2 2. Edge1 (primary) receives message
2
(becomes âprimary ownerâ)
Edge1 delivers message to next hop
Edge1 updates discard status of the
Foreign message indicating delivery complete
MTA
to foreign MTA
20. Transport Roles
How does shadow redundancy work?
3. Success: Hub (shadow) queries Edge1
(primary) for expiry status
Hub Hub issues XQDISCARD command (next SMTP
Session),Edge1 checks local discard status and
4
1 3 responds with list of messages considered
delivered
ï Hub deletes messages from its shadow queue
4. Failure: Hub (shadow) queries Edge1 (primary)
Edge1 Edge2 discard status and resubmits
2 Hub opens SMTP session, issued XQDISCARD
command (heartbeat)âif Hub canât contact Edge1
within timeout, resubmits messages in shadow
Foreign queueâresubmitted messages are delivered to
MTA Edge2 (go to #1)
21. Transport Roles
Shadow redundancy: other scenarios
For systems that do not support shadow redundancy, Exchange
2010 utilizes a delayed acknowledgement process
SMTP submission from Exchange 2003/2007, 3rd party Message
Transfer Agent( MTA ) and Mail User Agent (MUA - UM, POP and
IMAP clients)
250 response delayed up to 30 sec (default)
If transport server fails before ack, client resubmits
Mailbox Submission redundancy relies on copy of message in
senderâs âSent Itemsâ folder
Mail Submission Service resubmits copy when hub doesnât acknowledge
successful delivery of message
System generated (Journal Report, NDR) are considered âside
effectsâ of original message submission, tracked as part of
original delivery status
22. Transport Roles
Exchange 2010 performance enhancements
ESE changes:
ESE page size is 32KB
ESE database page compression
Intrinsic long value record storage
ESE version store maintenance
DB cache size increased to 1GB
Checkpoint depth increased to 512MB
Results:
With transport dumpster changes and ESE improvements, transport
IOPS requirements are targeted to be reduced by more than 50%
Larger message sizes are supported without causing backpressure
23. Transport Roles
Edge transport improvements
Better Performance for EdgeSync via Deltasync Mode
Under this mode, each time EdgeSync service only reads the
delta change since last sync and updates the
target accordingly
Support for safe senders and blocked senders
Configurable Safe List quotas
Administrator defined blocked senders
Automatic update of Safe Sender list propagation into
Active Directory
24. Transport Roles
Resilient routing for co-located HA Mailbox/Transport
Hub Transport attempts to re-route a message for a
local Mailbox server to another Hub Transport server in
same site if the Hub Transport server is also a DAG
member and it has a copy of the mailbox database
mounted locally
Mail Submission service was modified so that it would
prefer to not submit messages to a local Hub Transport
role when Mailbox/Hub server is a member of a DAG.
The behavior is to load balance across other Hub
Transport servers in same AD site, and fall back to local
Hub Transport server if there are no other available
Hub Transport servers in the same site
25. Transport Roles
Architectural considerations
Shadow redundancy enables RAID-less solutions for mail.que
database
Routing version boundary change:
Exchange 2010 Mailbox servers can only submit to Exchange 2010
Hub Transport servers and Exchange 2010 Hub Transport servers
can only deliver to Exchange 2010 Mailbox servers
Exchange 2007 Mailbox servers can only submit to Exchange 2007
Hub Transport servers and Exchange 2007 Hub Transport servers
can only deliver to Exchange 2007 Mailbox servers
Exchange 2010 Hub Transport servers can communicate with
Exchange 2007 Hub Transport servers via SMTP (and vice versa)
For Edge, Exchange 2010 Hub Transport will become authoritative for
Edgesync in the coexistence scenario
27. Mailbox
Store/ESE changes
Exchange 2007 Issues Exchange Server 2010
Exchange does many small, random Exchange store schema and ESE optimized for fewer large,
smoother, sequential I/Os
input/outputs (I/Os) which inhibit the types of âąStore schema changes
disks that can be used âąDB I/O size improvements
âąDatabase cache effectiveness improvements
âąESE optimized for new store schema
Result: Exchange 2010 reduces I/O by an additional 70%
when compared to Exchange Server 2007 and is optimized for
SATA class disks
Large item count per folder is an issue due to Schema changes of the table structure and deferred index
updates greatly improves restricted view performance
restricted views (affects large mailbox
deployments) Result: Supports 100,000 items per folder
Outlook Personal Folder Files (PSTs) are a New Messaging Records Management features
âąItem level policy settings
litigation, security, and management nightmare âąArchive mailbox feature for importing and storing PST
data
âąCompliance Officer search capabilities
Result: PSTs can be removed by placing data into Exchange
repository and can be searched easily
Attend UNC304 â Storage in Exchange Server 2010 â Today @ 5:00 PM, Arena 2
28. Mailbox
High availability changes
Single-copy cluster Cluster Continuous Exchange Server 2010
Replication High Availability
*Over granularity Server-level Server-level Database-level
Copies of data 1 2 2 to 16
*Over time ~2 min ~2 min ~30 sec (POR)
*Over management Windows Cluster Windows Cluster Exchange Server
Data replication SCR or 3rd party replication Continuous replication Continuous replication
Management tools Separate Separate Unified
Host other roles? No No Yes
Other advantages
Step up to automatic failover without rebuilding the mailbox server
Incrementally add replicated copies to meet business needs
No subnet or special DNS requirements
Attend UNC303 â High Availability in Exchange Server 2010 â Today @ 3:30 PM, Arena 1B
29. Mailbox
Architectural considerations
Streaming backup support has been removed
Utilize direct-attached storage (DAS) solutions to reduce costs
with large mailboxes and continuous replication
Leverage the Storage Cost Calculator
Deploy Database Availability Groups (DAGs) and use replication
to achieve high availability
If deploying 3 or more database copies, consider RAID-less storage
design and combining logs and database on same spindles
Ensure unique database names across the organization
30. Mailbox
Architectural considerations
Large mailbox support (10 GB+) enables different scenarios
Deploy Office 2007 Service Pack 2 (SP2) or later
Leverage records management functionality
Scenario 1:
Deploy a single mailbox to contain all data
Scenario 2:
Deploy primary mailbox to support 1-2 years worth of data
Deploy archive mailboxes to allow end users to retain long-term
needed data
31. Mailbox
Public Folders
Co-existence support between Mailbox server 2010 and Mailbox
server 2003/2007
Outlook can access public folder data from Exchange 2010,
2007, or 2003
OWA 2010 only gives access to public folders with replicas
located on Exchange 2010
This is different from OWA 2007, which had a redirection behavior,
opening up OWA 2000/2003 for public folders on older mailbox servers
in separate browser windows
Get-PublicFolderStatistics now captures last user access
Unlike Exchange 2007, public folder stores can no longer be
enabled for continuous replication, but you can create a public
folder store on a mailbox server that resides in a DAG
Public Folder replication is your data resiliency solution
32. Agenda
Discuss the topology changes introduced in
Exchange Server 2010
Understand our guidance on server sizing
33. Scale Out vs. Scale Up
Scale out is a strategic choice made
by Microsoft
Focus is on supporting large mailboxes at low
cost, goal to further decrease input/output (I/O)
to reduce Total Cost of Ownership (TCO)
Scaling up increases risk that an outage or
failure affects more users
Scaling out provides an opportunity for high
availability at low cost
34. Processor Core Scalability
Single role servers
Beta/RC: 12 cores maximum
No benefit moving to 16 cores from a performance
perspective
High scale all-in-one serverâcurrently under
investigation
Beta/RC: 16 cores max
35. Client Access
RC sizing guidance
Since CAS role is now a true middle-tier solution, CAS
servers require beefier hardware
CAS to Mailbox processor core ratio changes drastically
as a result of RPC Client Access service (3:4)
Processor/Memory requirements:
8 cores recommended
2 GB RAM/core recommended (8 GB min)
36. Transport
RC sizing guidance
Memory and processor requirements are
staying inline with Exchange 2007 requirements
Processor/Memory requirements:
4 cores recommended
1 GB RAM/core recommended
Transport rule attachment scanning and content
encryption technologies may impact these
guidelines
37. Mailbox
RC sizing guidance
Use 4 â 8 total cores for mailbox
16 cores shows decline in throughput on single
role machines
RAM
4GB base RAM for content indexing and mailbox assistants
2-8MB per mailbox recommended for database cache and
will be based on message profile and mailbox size
Example: Light Message Profile with 10+GB mailbox â 8MB memory
Size and prepare disks correctly
Use storage calculator
38. Unified Messaging
RC sizing guidance
Use 4 cores
4-8 GB of RAM recommended
More than 8 GB is not shown to improve TCO
or scale
Not recommended combining with other roles
Audio quality can be affected
Place close to the mailbox servers that host UM-
enabled mailboxes
Voice mail preview may impact these guidelines
39. Exchange 2010 Ratio Guidelines
Processor core ratios
Client Access Server (CAS) : Mailbox = 3 : 4
Hub Transport server : Mailbox
= 1 : 7 (no A/V on Hub)
= 1 : 5 (with A/V Hub)
Edge guidance expected to be very similar to
Exchange Server 2007
GC: Mailbox
= 1 : 4 (32âbit GC)
= 1 : 8 (64-bit GC)
41. Key Takeaways
Exchange Server 2010 introduces several
paradigm shifts
Client connections are performed through Client Access
Server role
Shadow redundancy introduces message resiliency within
transport pipeline
High Availability, store, and new compliance scenarios
improve data retention, resiliency, and availability
There are changes to server sizing and scalability, most
notably with CAS
42.
43. Resources
www.microsoft.com/teched www.microsoft.com/learning
Sessions On-Demand & Community Microsoft Certification & Training Resources
http://microsoft.com/technet http://microsoft.com/msdn
Resources for IT Professionals Resources for Developers
44. Related Content
Breakout Sessions
UNC302 Exchange 2010 Architecture
UNC304 Storage in Exchange 2010
UNC305 Exchange 2010 Voicemail
UNC306 Migrating to Exchange 2010: Deployment Best Practices
UNC308 Migration and Co-existence with Exchange/Non-Exchange and Exchange Online
Hands-on Labs
UNC11-HOL Microsoft Exchange Server 2010 Governance and Archiving
UNC13-HOL Microsoft Exchange Server 2010 Server Management Tools
UNC14-HOL Microsoft Exchange Server 2010 Setup and Deployment
UNC15-HOL Microsoft Exchange Server 2010 Transport Routing
UNC17-HOL Microsoft Exchange Server 2010 Unified Messaging Configuration and
Interoperability with Microsoft Office Communications Server 2007 R2
Instructor Led Labs
UNC14-ILL Microsoft Exchange Server 2010 Setup and Deployment
45. Track Resources
Exchange Server 2010 Release Candidate Download (English)
http://www.microsoft.com/exchange/2010/en/us/try-it.aspx
Exchange Server 2010 Documentation
http://technet.microsoft.com/library/bb124558(EXCHG.140).aspx
Read Exchange Team Blog Posts
http://msexchangeteam.com/archive/category/11164.aspx
Participate in Exchange Server 2010 Forums
http://social.technet.microsoft.com/Forums/en-US/exchange2010/threads
Read Communications Server Team Blog Posts
http://communicationsserverteam.com/
46. Evaluation Prize
Complete an evaluation on
CommNet and enter to win
an award winning JABRA
premium DECT headset
5 to win per day
RRP $599