Upgrading to Exchange 2007 SP2

Exchange 2007 SP2 Overview

Microsoft Exchange Server 2007 SP2 helps meet the challenges and business needs of any Organization with the stake in messaging system. Exchange 2007 SP2 is a mission-critical communications tool that enables employees to be more productive and access their information anytime from anywhere. For the Administrators, Exchange Server 2007 SP2 provides advanced protection options against email security threats, such as spam and antivirus as well as tools to help manage internal compliance and high availability needs.


Whats New in Exchange 2007 SP2

• Enhanced Backup Functionality
  Exchange 2007 SP2 includes VSS plug-in for Windows Server backup to support Exchange backups. Once Sp2 is installed, Windows Server backup can be used for backup and restore of Exchange Server 2007 SP2 databases. The new plugin is delivered in the form of a single executable called wsbexchange.exe.
  


• Deploying Exchange Server 2010
  Before deploying Exchange 2010 in the coexistence mode of Exchange 2007, all the CAS Server must be upgraded to Exchange 2007 SP2. In addition, all Exchange 2007 Server in Active Directory site, regardless to role must be upgraded to Exchange 2007 SP2.
  


• Enhanced Auditing
  New Exchange auditing events and audit log repository enable Exchange Administrators to more easily audit the activities occurring on Exchange Servers. It allows the right balance of granularity, performance and easy access to audited events via a dedicated audit log repository. This simplifies the auditing process and reviewing of audited events in a dedicated location.
  


• Dynamic AD Schema Validation
  The dynamic AD Schema update and validation feature allows for future Schema updates to be dynamically deployed as well as proactively preventing conflicts whenever a new property is added to the AD Schema. Once this capability is deployed it will enable easier management of schema updates and will support issues when adding properties that don't exist in the AD Schema
  


• Public Folder Quota Management
  Exchange 2007 SP2 provides more efficient way to manage Public Folder Quotas by improving the cmdlets and removing the dependency authoring and visioning Administration to perform management tasks.
  


• Centralized Organization Settings
  There are several new cmdlets parameters that have been added that enable centralized management of many of the Exchange Organization settings.

Step by step process for Upgrading Exchange 2007 SP1 to SP2

If you are upgrading Exchange 2007 Server in production, then make sure to have a restorable backup of Exchange Configuration and its databases. Although the upgradation is straight forward and come clean bu it is advisable to have the backups in place. During the upgradation process the Exchange services will be stopped and disabled. The downtime may vary from one server to another. You may plan for a downtime of 30 - 45 mins. See screenshots below









Once you are readyfor upgradation, download Exchange 2007 SP2 from the link. Extract SP2 and run setup.exe. You will get the screenshot as below








Click on install Exchange 2007 Service Pack 2

On the introduction screen click on next.

On the license page click on I accept and click on next.

Readiness check will be performed. Once completed Click on Upgrade to start the upgradation.

It will then start upgrading Exchange Server to SP2. During this process Exchange services will stopped.

On successful completion page click on Finish. Your Exchnage Server is now upgraded to Service Pack 2.

Please let me know if the above article was able to provide you with the information you needed.

Deploying Exchange 2007 SP1

Exchange 2007 Server Roles

• Mailbox Role: The Mailbox role provides email storage and advanced scheduling services for Microsoft Office Outlook users. The Mailbox Server role also includes public folders
  
• Client Access Role: The Client Access Role (CAS) enables clients to connect to their Exchange mailbox through Outlook Web Access, POP, IMAP or through mobile device using activesync. this role also provides free buy lookup and offline address books.


• HUB Transport Role: The HUB Transport role (HUB) provides routing within a AD Site. HUB Server can be used for applying messaging policies, security polices, antispam and antivirus policies to email messages in Transport.
  
• Unified Messaging role: The Unified Messaging role (UM) role provides connectivity between a corporate telephony system and Exchange Server. Clients can access their mailboxes from any telephony or mobile device using Outlook Mobile Access (OMA) and perform almost the same functionality as OWA.
  
• Edge Transport Role: The Edge Transport role performs antispam amd antivirus filterin and applies messaging and security policies to the inbound and outbound external messages in the transport. This role is deployed in the perimeter network.

Prerequisites for Deploying Exchange 2007

• Domain Name System (DNS)


• Windows 2003 based Active Directory.


• The Forest and Domain functional level should be Windows 2003


• The server on which Exchange needs to be deployed should be member of Active Directory Domain.


• AD DS and IIS roles is required to be installed from Server Manager


• .Net and Windows Powershell features is required to be installed.

By taking care of the above we are now ready for implementing Exchange 2007 SP1. Given below are the step by step process for implementing Exchange 2007 SP1. Pop in Exchange 2007 installable DVD and double click on Setup

You will be presented with the above screen. Step 1, 2 and 3 will be highlighted if the required prerequisites are missing. For installing Exchange 2007 SP1 click on Step4. You will be presented with the below screen.

This screen provides brief introduction about Exchange 2007 SP1. Click on next

The next screen is for license agreement. Accept on the license agreement and click on next.

The above screen is for how you want to report errors to Microsoft. For this deployment sake I have selected No. Click on next to get the below screen.

The above window gives you the option to choose the role that needs to be deployed on the Exchange Server. Click on Custom to select the roles that needs to be deployed.

I have selected all the roles that can be deployed on a single server. Edge server can only be deployed in the DMZ. Click next.

Type the name of the Exchange Organization. For this deployment I have put as NMAIL. Click on next.

On the above select Yes if any of your users are using clients older than Outlook 2003. For this deployment I have selected No. Click on Next.

On this screen the setup does a readiness check before starting the installation. Once done click on Install

The installation process starts for the roles selected. Click on Next.

The screen above gives you the status of the deployment. You get completed for all the roles selected for deployment that indicates you are done with the deployment.

Please let me know if the above article was able to provide you with the information you needed.

Configuring permissions with SCCM

Object	Rights to create	Rights to modify	Rights to delete	Rights to distribute
Boot Images	Create\Boot image package, Read\Boot image package	Modify\Boot image package, Read\Boot image package	Delete\Boot image package, Read\Boot image package	Read\Boot image package, Modify\Boot image package, Distribute\Boot image package, Read\Site
Computer Association	Create\Computer association, Read\Computer association, Read\Collection	Modify\Computer association, Read\Computer association	Delete\Computer association, Read\Computer association	Not applicable
Operating System Images	Create\OS image, Read\OS image	Modify\OS image, Read\OS image	Delete\OS image, Read\OS image	Modify\OS image, Read\OS image, Distribute\OS image, Read\Site
Operating System Install Pacakges	Create\OS install package, Read\OS install package	Modify\OS install package, Read\OS install package	Delete\OS install package, Read\OS install package	Modify\OS install package, Read\OS install package, Distribute\OS install package, Read\Site
Task Sequences	Create\Task sequence package, Read\Task sequence package, Modify\Task sequence package	Modify\Task sequence package, Read\Task sequence package	Delete\Task sequence package, Read\Task sequence package	Modify\Task sequence package, Read\Task sequence package, Distribute\Task sequence package, Read\Site
Advertisement (for task sequence)	Read\Task sequence package, Read\Collection, Advertise\Collection, Read\Package, Create\Advertisement	Modify\Advertisement, Read\Advertisement	Delete\Advertisement, Read\Advertisement	Not applicable
Task sequence bootable media	Read\Task sequence package, Create Task sequence media\Task sequence package, Read\Site, Manage OSD and ISV Proxy Certificates\Site, Read\Boot image	Modify\Task sequence package, Read\Task sequence package	Delete\Task sequence package, Read\Task sequence package	Not applicable
Drivers	Create\Device driver, Read\Device driver	Modify\Device driver, Read\Device driver	Delete\Device driver, Read\Device driver	Not applicable
Driver package	Create\Driver package, Read\Device driver	Modify\Driver package, Read\Driver package, Distribute\Driver packages	Delete\Driver package, Read\Driver package	Not applicable

Please let me know if the above article was able to provide you with the information you needed.

VMC to Hyper V

VMC to Hyper-V Import Tool

http://technet.microsoft.com/en-us/magazine/2009.03.utilityspotlight.aspx?pr=blog

Please let me know if the above article was able to provide you with the information you needed.

Exchange 2010 Overview

Exchange 2010 has some carried over features from Exchange 2007 as well as some improved and new features broadly falling under the below categories

• Protection and Collaboration
  
• Anywhere Access
  
• Flexibility and Reliability
  

Listed below are the features that have carried over from Exchange 2007 as well as improved and new features falling under each of these categories

Protection and Collaboration

The goal of protection and collaboration is to achieve increased IT governance compliance with advanced tools to protect communication and manage the Messaging infrastructure.

Some of the features that have been carried over from Exchange 2007 are:

• On premise and hosted protection from virus and spam
  
• Compliance to corporate and government regulation
  
• Mobile device security and management policies
  

While some of the features that have been enhanced and new with Exchange 2010 are

• Email archiving and more powerful retention policies
  
• Automated rights management and protection of email
  
• Powerful multi mailbox search UI for eDiscovery or Legal reasons
  

Anywhere Access

The goal of the Anywhere Access is to help and manage communication load by offering an easy to navigate, Universal inbox with advanced messaging feature.

Some of the features carried over from Exchange 2007 are

• Outlook experience on Web, Phone and mobile device
  
• Single inbox for voice mail, email and fax
  
• Increased productivity with improved calendar experience
  

While some of the features that have been enhanced and new with Exchange 2010 are

• Easier inbox navigation with updated conversation view
  
• Enhanced voice mail with text preview
  
• Share free busy calendar information with external partners
  

Flexibility and Reliability

The goal is to provide flexibility needed to operate a scalable high performing and easy to administer messaging infrastructure.

Some of the features carried over by Exchange 2007 are

• Improved installation and deployment scenarios
  
• High Availability through Continuous Replication
  
• Simplified management console and command line shell
  

While some of the features that have been enhanced and new with Exchange 2010 are

• Choice of solution delivery with addition of hosted service
  
• Single platform for High Availability and Disaster Recovery
  
• Role based Administration and User self service

Please let me know if the above article was able to provide you with the information you needed.

Terminal Services Overview

Terminal Services can provide access to Windows based applications from almost any location to almost any computing device. Terminal Services in Windows Server 2008 includes Terminal Services RemoteApp (TS RemoteApp). Please note that the Terminal Services role cannot be installed on Domain Controller.

Terminal Services Terminology

• TS Remote App: Allows users to run a program located on a remote server from desktop as if it is running from the desktop.
  TS Web Access: It provides Web interface for accessing applications published on the Terminal Server
• TS Gateway: It provides authorized users to access to the remote application published behind the Firewall without needing VPN connectivity.
• TS Licensing: It manages the Terminal Services Client access licenses (TS CALs) that are required to connect to a Terminal Server. You can use TS Licensing to install, issue and monitor the availability of TS CALs.
• TS Session Broker: It helps in load balancing the sessions between the Terminal Servers in the Farm.

What are RemoteApp programs?

RemoteApp programs are programs that are accessed remotely through Terminal Services and appear as if they are running on the end user's local computer. Instead of being presented to the user in the desktop of the remote terminal server, the RemoteApp program is integrated with the client's desktop, running in its own resizable window with its own entry in the taskbar. Users can run RemoteApp programs side-by-side with their local programs. If a user is running more than one RemoteApp program on the same terminal server, the RemoteApp programs will share the same Terminal Services session.

In Windows Server 2008, users can access RemoteApp programs in the following ways:

• Access a link to the program on a Web site by using TS Web Access.
• Double-click a Remote Desktop Protocol (.rdp) file that has been created and distributed by their administrator.
• Double-click a program icon on their desktop or Start menu that has been created and distributed by their administrator with a Windows Installer (.msi) package.
• Double-click a file where the file name extension is associated with a RemoteApp program. This can be configured by their administrator with a Windows Installer package.

The .rdp files and Windows Installer packages contain the settings that are needed to run RemoteApp programs. After opening a RemoteApp program on their local computer, the user can interact with the program that is running on the terminal server as if it were running locally. The applications to be published on TS RemoteApp must be installed only after the Terminal services role is installed.

Distributing RemoteApp programs

RemoteApp program can be distributed in the following deployment methods:

• You can make RemoteApp programs available on a Web site by distributing the RemoteApp programs through TS Web Access.
• You can distribute RemoteApp programs as .rdp files or Windows Installer packages as .msi through a file share, or through other distribution mechanisms such as Microsoft Systems Management Server or Active Directory software distribution.

Scenarios where TS RemoteApp can be used

TS RemoteApp is especially useful in scenarios such as the following:

• Remote users: Users often need to access programs from remote locations, such as while working from home or while traveling. If you want users to access RemoteApp programs over an Internet connection, you can allow access through a Virtual Private Network (VPN), or you can deploy TS RemoteApp together with Terminal Services Gateway (TS Gateway) to help secure remote access to the programs.
• Branch offices: In a branch office environment, there may be limited local IT support and limited network bandwidth. By using TS RemoteApp, you can centralize the management of your applications and improve remote program performance in limited bandwidth scenarios.
• Line-of-business (LOB) applications deployment: Companies often need to run consistent LOB applications on computers that are running different Windows versions and configurations. Instead of deploying the LOB applications to all the computers in the company, which can be expensive in terms of time and cost, you can install the LOB applications on a terminal server and make them available through TS RemoteApp.
• Application deployment: With TS RemoteApp you do not have to deploy and maintain different versions of the same program for individual computers. If employees need to use multiple versions of a program, you can install those versions on one or more terminal servers, and users can access them through TS RemoteApp.
• Roaming users: In a company with a flexible desk policy, users can work from different computers. In some cases, the computer where a user is working may not have the necessary programs installed locally. By using TS RemoteApp, you can install the programs on a terminal server and make them available to users as if those programs were installed locally.
  

Please let me know if the above article was able to provide you with the information you needed.

Basic Concepts of Citrix XenApp

Citrix Licensing: A Citrix License Server is a required component for all XenApp deployments. Install the license server on either a shared or standalone server, depending on your farm’s size. After you install the license server, download the appropriate license files and add these to the license server.

Data Store: The data store is the database where servers store farm static information, such as configuration information about published applications, users, printers, and servers. Each server farm has a single data store.

Data Collector: A data collector is a server that hosts an in-memory database that maintains dynamic information about the servers in the zone, such as server loads, session status, published applications, users connected, and license usage. Data collectors receive incremental data updates and queries from servers within the zone. Data collectors relay information to all other data collectors in the farm. By default, the first server in the farm functions as the data collector. By default, the data collector is configured on the first farm server during the Create Farm Setup and all other servers are configured so they have equal rights to become the data collector if the data collector fails. When the zone’s data collector fails, a data collector election occurs and another server takes over the data collector functionality. Farms determine the data collector based on the election preferences set for a server. The data collector is an infrastructure server and applications are not typically published on it.

Zone: A zone is a grouping of XenApp servers that communicate with a common data collector. In large farms with multiple zones, each zone has a server designated as its data collector. Data collectors in farms with more than one zone, function as communication gateways with the other zone data collectors. The data collector maintains all load and session information for the servers in its zone. All farms have at least one zone, even small ones. The fewest number of zones should be implemented, with one being optimal. Multiple zones are necessary only in large farms that span WANs.

Streaming File or Web Server: Applications can be delivered to users by either streaming or hosting the applications on the server. If you are streaming applications, either to client or server, you must install a streaming file server in your environment. When streaming applications, you create profiles of the application and then store the profile on a file or Web server. The profile consists of the manifest file (.profile), which is an XML file that defines the profile, as well as the target CAB files, a hash key file, the icons repository (Icondata.bin), and a scripts folder for pre-launch and post-exit scripts.

Web Interface: The Web Interface is a required component in any environment where users access their applications using either the XenApp plugin or a Web browser. Install the Web Interface on a stand-alone computer; however, where resources are limited, the Web Interface is sometimes collocated with other functions. For instructions, see the Web Interface Administrator’s Guide.

XenApp Web and XenApp Services Sites: XenApp Web and XenApp Services sites (formerly known as Access Platform and Program Neighborhood Agent Services sites, respectively) provide an interface to

the server farm from the client device. When a user authenticates to a XenApp Web or XenApp Services site, either directly or through the XenApp plugin or the Access Gateway, the site:

• Forwards the user’s credentials to the Citrix XML Service
• Receives the set of applications available to that user by means of the XML Service
• Displays the available applications to the user either through a Web page or by placing shortcuts directly on the user’s computer.

Citrix XML Service and the Citrix XML Broker: The Citrix XML Broker functions as an intermediary between the other servers in the farm and the Web Interface. When a user authenticates to the Web Interface, the XML Broker:

• Receives the user’s credentials from the Web Interface and queries the server farm for a list of published applications that the user has permission to access. The XML Broker retrieves this application set from the Independent Management Architecture (IMA) system and returns it to the Web Interface.
• Upon receiving the user’s request to launch an application, the broker locates the servers in the farm that host this application and identifies which of these is the optimal server to service this connection based on several factors. The XML Broker returns the address of this server to the Web Interface.

The XML Broker is a function of the Citrix XML Service. By default, the XML Service is installed on every server during XenApp Setup. However, only the XML Service on the server specified in the Web Interface functions as the broker. (The XML Service on other farm servers is still running but is not used for servicing end-user connections.) In a small farm, the XML Broker is typically designated on a server dedicated to several infrastructure functions. In a large farm, the XML Broker might be configured on one or more dedicated dedicated servers.

The XML Broker is sometimes referred to as a Citrix XML Server or the Citrix XML Service. For clarity, the term XML Broker is used to refer to when the XML Service functions as the intermediary between the Web Interface and the IMA service, regardless of whether it is hosted on a dedicated server or collocated with other infrastructure functions.

Please let me know if the above article was able to provide you with the information you needed.

Changed names with Citrix XenApp 5.0

With Citrix XenApp 5.0 some of the terminologies are changed as were in Citrix Presentation Server. Below is the list of the terminologies that are changed

- Citrix XenApp is the new name for Citrix Presentation Server

- Citrix XenApp Advanced Configuration is the new name for Presentation Server Console.

- Citrix XenApp Pugin for Hosted Application is the new name for plugin for server side virtualization formerly known as Citrix Presentation Client

- Citrix XenApp Agent is the new name for Citrix Program Agent

- Citrix XenApp Provider is the new name for WMI Provider.

- Citrix XenApp Management Pack is the new name for SCOM Management Packs.

- Citrix XenApp Web is the new name for Citrix Web Interface.

- Citrix XenApp Plugin for Streamed Application is the new name for Citrix Streaming Client.

- Branch Optimization is the new name for WAN Optimization.

- Secure Application Access is the new name for Smart Access.

- Easy Call Voice Services is the new name for Easy Call

- Load Testing Service is the new name for Load Testing

- Provisioning Services is the new name for Provisioning Server for Datacenter.

- Profile Management is the new name for Portable Profile Manager

- Workflow Studio Orchestration is the new name for Workflow Studio

Please let me know if the above article was able to provide you with the information you needed.

Introduction to Citrix Presentation Server

Introduction to Citrix Presentation Server

Citrix Presentation server provides application virtualization and application streaming to the users with any device working over any network. It allows delivery of windows application as a service to the users using any network device. Citrix server can be used to:

- Provide tailored secure access control in any access scenario.

- Deliver continuous access across devices, networks and locations.

- Provide scalability and continuous availability for any business scenario.

- Protect information through a multidimensional secure architecture.

- Observer, monitor and measure access infrastructure resources.

Citrix Presentation server enables multiple users to log on and run applications in separate, protected sessions on a single server or multiple servers across a Farm. Server Farm is a group of Citrix servers that you manage as a single entity. Server Farm provides you with a flexible and robust way of deploying applications and content to the users.

Citrix Web Interface

Citrix Web Interface provides the ability to the users to access the published applications using any Web interface.. The Web Interface dynamically creates an HTML page that shows the allowed published application to the users.

You can use Web Interface with Access Gateway or Secure Gateway to transport data securely over the Internet.

The Platinum edition provides Web Interface integration with the Password Manager self-service features (account unlock and self-service password reset). Users can use Password Manager Agent software and register with security questions. When the security questions are registered, the users can reset or unlock their domain password using Web Interface without the intervention of Account Administrator.

Secure Gateway

The Secure Gateway is a secure Internet Gateway device for ICA data travelling into and out of a server farm. You can secure all traffic travelling across the Internet among computers running Citrix Presentation Server and SSL enabled clients

Citrix EdgeSight for Presentation Server

Citrix EdgeSight can be deployed on Presentation Server Platinum edition. It is an end-to-end performance management solution for computers running Citrix Presentation Server. It monitors user sessions and server performance in real time, allowing you to quickly analyze, resolve and proactively prevent problems. You can use Citrix EdgeSight for endpoints for performance management of end user systems.

Resource Manager for Citrix Presentation Server

Resource Manager can be installed on Presentation Server Enterprise Edition. It enables you to collect, display and analyze data about system performance, application use and user activity.

Resource Manager can track and store information about a wide variety of system and network processes and events. If the value of these metrics falls outside normal limits, Resource Manager can warn you by email and pager alerts.

Installation Manager for Citrix Presentation Server

Installation Manager is installed automatically with Citrix Presentation Server Enterprise Edition. Installation Manager lets you install an application package, such as Microsoft Office 2000, from one server to all the servers in a domain or in a server farm. Use Installation Manager whenever you need to deploy applications, files, service packs, or software patches on the servers in your server farm.

You can automate the application installation process, enabling the replication of published applications to computers running Citrix Presentation Server across the enterprise. Automating the process enables you to save time and reduce errors when installing many applications or applications that are frequently updated.

Network Manager for Citrix Presentation Server

Network Manager allows you to remotely control and monitor the status of computers running Citrix Presentation Server Enterprise Edition, using a third party SNMP management console. Network Manager consists of the SNMP Agent for Citrix Presentation Server, installed automatically as part of Citrix Presentation Server Enterprise Edition, and plug-ins for supported SNMP management console applications. Using a third-party SNMP management console, you can terminate processes, send a message to, log off, or disconnect from an active ICA session on a computer running Citrix Presentation Server Enterprise Edition.

Network Manager also includes the Management Information Base (MIB) definition file for Citrix Presentation Server. You can use any SNMP management console application that supports MIB browsing to monitor and control computers running Citrix Presentation Server. The Network Manager plug-ins interact with the SNMP management consoles through API calls provided by the SNMP management consoles. The Network Manager plug-ins automatically:

- Explore and gather information from servers on which the SNMP Agent is enabled.

- Update the gathered data on the network map.

- Log server traps in the event database

Please let me know if the above article was able to provide you with the information you needed.

Citrix Concepts

Citrix Server is available in the three editions, they are
- Standard Edition: It is ideal for small Organization. This edition is used for single server deployment.
- Advanced Edition: It is ideal for small to medium Organization. This edition is used for deploying Citrix servers in a Farm for providing high availability. It adds Load Manager Component.
- Enterprise Edition: It is ideal for large to very large Organization. It provides all the functionality of Advance edition. In addition it adds Installation Manager, Resource Manager, Load Manager, WMI Manager and Network Manager.

Components of Citrix Server

- Installation Manager: It is a toll which helps in deploying packaged installation to Citrix Presentation Server
- Resource Manager: It is a tool to monitor the resources such as event logs and performance monitor logs of Citrix Presentation Server.
- Load Manager: It is a tool used for managing the load of Citrix Server in a Farm.
- Network Manager: It is a tool to connect presentation server to Operations management server.

Citrix Terminology

- Published Application: It is a component for publishing application on Citrix Server. The authenticated users can access the application as if it is being launched from their desktop.
- Published Desktop: it is a tool for publishing entire desktop to the set of users.
- Published Content: It is a tool for publishing the content of the file such a word or an excel file.

Citrix Client

Citrix resources can be accessed by using the below clients
- Program Neighborhood: It provides the flexibility to the end users to the way they connect to the Citrix Server.
- Program Neighborhood Agent: It provides a shortcut which the user can use to access the application published on the Citrix Server.
- Web Client: It provides the accessibility of published applications on the Citrix Server using Web Client
- Java Client: It provides the ability to access published applications on Citrix Server without installing any Citrix Client on user’s desktop.

Citrix Services

Below are the Citrix services that gets installed based on the edition and application you install
- ADF Installer Service
- Citrix CPU Utilization Management / Resource Management service
- Citrix CPU Utilization Management / user-session sync service
- Citrix Licensing Service
- Citrix Licensing WMI service
- Citrix Print Manager service
- Citrix SMA service
- Citrix WMI service
- Citrix XTE Service
- Citrix Virtual memory optimization service
- Client Network
- Diagnostic facility COM server
- Encryption service
- Independent Management Architecture service
- License Management console for Citrix Licensing service
- Metaframe COM server service
- Resource Manager Mail service
- Secure Gateway

Citrix ICA protocol features

- It provides screen updates and mouse / keyboard clicks
- It is optimized for WAN connections (~30-35 kb/sec connection)

Please let me know if the above article was able to provide you with the information you needed.

Exchange 2010 RC

Download Microsoft Exchange Server 2010 RC from the link below

http://technet.microsoft.com/en-us/evalcenter/dd185495.aspx

Operating Systems supported on Windows 2008 R2 Hyper-V

Supported Guest Operating Systems


The following guest operating systems are supported on Hyper-V:

Windows Server 2008 R2 (VM configured with 1, 2, or 4 virtual processors)

· Windows Server 2008 R2 Standard
· Windows Server 2008 R2 Enterprise
· Windows Server 2008 R2 Datacenter
· Windows Web Server R2 2008

Windows Server 2008 x64 Edition (VM configured with 1, 2, or 4 virtual processors)

· Windows Server 2008 Standard x64
· Windows Server 2008 Enterprise x64
· Windows Server 2008 Datacenter x64
· Windows Web Server 2008 x64
· Windows Server 2008 HPC Edition x64
· Windows Server 2008 Standard without Hyper-V x64
· Windows Server 2008 Enterprise without Hyper-V x64
· Windows Server 2008 Datacenter without Hyper-V x64

Windows Server 2008 x86 (VM configured with 1, 2, or 4 virtual processors)

· Windows Server 2008 Standard x86
· Windows Server 2008 Enterprise x86
· Windows Server 2008 Datacenter x86
· Windows Web Server 2008 x86
· Windows Server 2008 HPC Edition x86
· Windows Server 2008 Standard without Hyper-V x86
· Windows Server 2008 Enterprise without Hyper-V x86
· Windows Server 2008 Datacenter without Hyper-V x86

Windows Server 2003 x86 (VMs configured with 1 or 2 virtual processors)

· Windows Server 2003 Standard x86 Edition with Service Pack 2
· Windows Server 2003 Enterprise x86 Edition with Service Pack 2
· Windows Server 2003 Datacenter x86 Edition with Service Pack 2
· Windows Server 2003 Web x86 Edition with Service Pack 2

Windows Server 2003 R2 x86 (VMs configured with 1 or 2 virtual processors)

· Windows Server 2003 R2 Standard x86 Edition with Service Pack 2
· Windows Server 2003 R2 Enterprise x86 Edition with Service Pack 2
· Windows Server 2003 R2 Datacenter x86 Edition with Service Pack 2
· Windows Server 2003 R2 Web x86 Edition with Service Pack 2

Windows Server 2003 R2 x64 (VMs configured with 1 or 2 virtual processors)

· Windows Server 2003 R2 Standard x64 Edition with Service Pack 2
· Windows Server 2003 R2 Enterprise x64 Edition with Service Pack 2
· Windows Server 2003 R2 Datacenter x64 Edition with Service Pack 2

Windows Server 2003 x64 Edition (VMs configured with 1 or 2 virtual processors)

· Windows Server 2003 Standard x64 Edition with Service Pack 2
· Windows Server 2003 Enterprise x64 Edition with Service Pack 2
· Windows Server 2003 Datacenter x64 Edition with Service Pack 2

Windows Server 2000 (VMs configured with 1 virtual processor)

· Windows 2000 Server with Service Pack 4
· Windows 2000 Advanced Server with Service Pack 4

Linux Distributions (VMs configured with 1 virtual processor)

· SUSE Linux Enterprise Server 10 with Service Pack 2 (x86 Edition or x64 Edition)
· SUSE Linux Enterprise Server 10 with Service Pack 1 (x86 Edition or x64 Edition)
· SUSE Linux Enterprise Server 10 with Service Pack 2 (x86 Edition or x64 Edition)
· SUSE Linux Enterprise Server 11 (x86 Edition or x64 Edition)
· Red Hat Enterprise Linux (RHEL) 5.2 and 5.3 (x86 Edition or x64 Edition)




Supported Client Operating Systems

Windows 7 x86 Edition (VM configured with 1, 2, or 4 virtual processors)

· Windows 7 Business x86 Edition
· Windows 7 Enterprise x86 Edition
· Windows 7 Ultimate x86 Edition

Windows 7 x64 Edition (VM configured with 1, 2, or 4 virtual processors)

· Windows 7 Business x64 Edition
· Windows 7 Enterprise x64 Edition
· Windows 7 Ultimate x64 Edition

Windows Vista x86 (VMs configured with 1 or 2 virtual processors)

· Windows Vista Business x86 Edition with Service Pack 1
· Windows Vista Enterprise x86 Edition with Service Pack 1
· Windows Vista Ultimate x86 Edition with Service Pack 1

Windows Vista x64 Edition (VMs configured with 1 or 2 virtual processors)

· Windows Vista Business x64 Edition with Service Pack 1
· Windows Vista Enterprise x64 Edition with Service Pack 1
· Windows Vista Ultimate x64 Edition with Service Pack 1

Windows XP Professional x86

· Windows XP Professional x86 Edition with Service Pack 3 (VMs configured with 1 or 2 virtual processors)
· Windows XP Professional x86 Edition with Service Pack 2 (VMs configured with 1 virtual processor)

Windows XP Professional x64 Edition

Windows XP Professional x64 with Service Pack 2 (VMs configured with 1 or 2 virtual processors)




Please let me know if the above article was able to provide you with the information you needed.

Applications supported on Hyper-V Virtualisation

The following applications are supported on Hyper-V:

• Microsoft Application Virtualization (App-V) 4.5 and later versions such as Management Server, Publishing Server, Sequencer, RDS Client, and Desktop Client are supported.
• Microsoft Commerce Server Service Pack 2 and later
• Microsoft Dynamics CRM 4.0 and later
• Microsoft Exchange Server 2007 SP1 and later
• Microsoft Intelligent Application Gateway (IAG) 2007 SP2 and later
• Microsoft Forefront Client Security
• Microsoft Forefront Security for SharePoint (FSP) SP2 or later
• Microsoft Internet Security and Acceleration (ISA) Server
• Microsoft Office PerformancePoint Server 2007 SP2 or later
• Microsoft Office SharePoint Server 2007 SP1 or later
• Windows SharePoint Services 3.0 SP1 or later
• Microsoft Search Server
• Microsoft System Center Configuration Manager 2007 or later
• Microsoft System Center Essentials 2007 or later
• Microsoft System Center Virtual Machine Manager 2007 or later
• Microsoft Visual Studio Team System 2008 and later
• Windows Server 2003 Web Edition SP2
• Windows Web Server 2008
• Windows Web Server 2008 R2
• Microsoft BizTalk Server 2004, 2006, 2006 R2, 2009 and later
• Microsoft Dynamics AX 2009 and later
• Microsoft Dynamics NAV 2009 and later
• Microsoft Forefront Client Security
• Microsoft Forefront Security for Exchange (FSE) SP1 or later
• Microsoft Host Integration Server 2006 or later
• Microsoft Office Groove Server 2007 SP1 or later
• Microsoft Office Project Server SP1 or later
• Microsoft Operations Manager (MOM) 2005 SP1 (Agents Only)
• Microsoft SQL Server 2005 and 2008
• Microsoft System Center Data Protection Manager 2007 and later
• Microsoft System Center Operations Manager 2007 and later
• Microsoft Systems Management Server (SMS) 2003 SP3 (agents only)
• Microsoft Windows HPC Server 2008
• Microsoft Windows Server Update Services (WSUS) 3.1 and later
• Windows Essential Business Server 2008 and later
• Windows Small Business Server 2008 and later

Please let me know if the above article was able to provide you with the information you needed.

Telephony concepts

What is CENTREX?

CENTRAL Office Telephone Exchange (CENTREX) is a business phone service that provides switching functionality at a telephone company’s Central Office rather than at the client site. The communications infrastructure and required software are typically owned and managed by Telephone Company, which then sells the service to its customer. The Telephone Company manages the service from it’s own site to the client site either through individual copper pair lines or through multiplexed lines that use fiber optics or copper link. To deploy Exchange Unified messaging in a traditional CENTREX environment, you must have a VOIP Gateway.

IP CENTREX: It is an updated version of CENTREX which uses IP/PBX based telephony system. The client site is connected through a data network instead of telephone wires. IP CENTREX provides VOIP and other IP based services besides its connectivity to PSTN. A VOIP gateway may not be required to deploy Exchange Unified Messaging.

What is PBX?

PBX sometimes known as telephone switch or telephony switching device is a device that connects office telephones to the public telephone network. It routes incoming calls to the appropriate extension. PBX users share a certain number of external lines for making calls external to PBX. For PBX to be integrated with Exchange unified messaging you need a VIOP gateway. For IP/PBX which supports SIP over TCP and T.38 for FAX you don’t need VOIP Gateway.

Types of PBX

Analog PBX: It sends voice and signaling information such as touchtone of dialed phone number, as analog signals, technically known as Dual Tone Multi-Frequency (DTMF).

Digital PBX: It encodes analog signals to digital signal using audio codec G.711. after it is encoded, the digitized voice signal is sent on a channel by using circuit switching. It can also support analog Trunks.

Hybrid PBX: It can provide both digital and IP/PBX capabilities. Depending on VOIP protocol compatibility of Hybrid PBX with Exchange unified messaging, you may or may not require VOIP Gateway.

IP PBX: It carries voice over data network by using packet switching technology that allows a single network channel to handle multiple connections. The IP phone contains NIC which is connected to the data network. The phone converts the voice signal to the digital signal before being transmitted to the data network. These digital signals are transmitted using Real-time Transport Protocol (RTP) so that the delivery order and timing of data packets are maintained.

PBX concepts

Direct Inward Dialing (DID): In DID, a unique phone number is assigned to a user within the Organization, so the users can be directly called from the external number without the need to transfer the call. Exchange unified messaging requires DID number for configuring Auto Attendant.

Hunt Group: It is a set of extensions that are defined as a group, that have identical endpoint such as sales or support so that callers receive busy signal less often.

Pilot Number: It is a method by which PBX identifies the Hunt Group. When used with Exchange unified messaging, PBX uses pilot number to target a diverted ring no answer or busy call to Exchange unified messaging so that voice messages can be taken and diverted to the intended user’s mailbox.

Please let me know if the above article was able to provide you with the information you needed.

Benefits and features of Exchange Unified Messaging

Benefits of Exchange Unified Messaging

• Exchange Unified Messaging enables users to access their mailboxes from various devices such as telephones and mobiles using Outlook Voice Access (OVA).

• Voice mail, email, calendar data and fax messages are stored in user’s inbox.

• Unified Messaging helps in reducing the cost by integrating email, voice mail and fax, which otherwise would require separate infrastructure.

• Play voice message on PC or phone.

• Provides out of office voice mail greetings to the callers


Features of Exchange Unified Messaging

• Exchange ActiveSync: Exchange ActiveSync is a protocol to connect mobile devices such as smart phones or PDAs to the Exchange Server. It help in accessing mailbox, view email and fax messages, view and change calendar information and listen to voice message. It uses direct push technology to establish HTTPs connection between mobile device and Exchange. In Exchange 2007 and Administrator can issue remote wipe command through Exchange Management Console or Exchange Management Shell to wipe out the information from the mobile devices in case the device is lost or stolen. Users can also issue remote wipe command from Outlook Web Access.

• Outlook Voice Access (OVA): When a user dials Subscriber Access Number set on Exchange Unified Messaging to access their mailbox they are presented with a series of Telephone User Interface (TUI) or Voice User Interface (VUI) prompts. These are together called as Outlook Voice Access. OVA can be accessed from anywhere using telephony device.

• Auto Attendant (AA): It is a series of voice prompt that a caller hears instead of human operator. Callers can place a call to the Unified Messaging enabled users using either Dual Tone Multi Frequency (DTMF) inputs or voice activated inputs such as speech recognition.

• Voice Call: it is used when an internal or external user leave a voice message. Incoming voice messages are created as Multi Purpose Internet Extension (MIME) messages. Then they are submitted by using SMTP to the HUB Transport Server. HUB Transport server then delivers to the mailbox server using SMTP.

• FAX Call: It is used when an internal or external user calls from a Fax to unified messaging enabled phone number. Fax calls are handled in the similar way as voice calls.


Exchange Unified Messaging Call handling

Exchange Unified Messaging server delivers the call by using transport protocols such as SMTP, RPC, MAPI or LDAP. Exchange Unified Messaging uses Active Directory to resolve incoming calls to the users. For the incoming calls to function correctly, users extension must be listed in Active Directory as well as in the user’s Unified Messaging configuration.



Please let me know if the above article was able to provide you with the information you needed.

VOIP Telephony Concepts used with Exchange Unified Messaging

VOIP Telephony Concepts used with Exchange Unified Messaging

To successfully deploy Unified Messaging in an Organization, you need to know Voice mail and telephony concepts such as Circuit Switching, Packet Switching and VOIP.

Circuit Switched Network

It is a dedicated connection that connects two nodes so that the two nodes can communicate with each other. After a call is established only two nodes can use the connection until one of the two parties ends the call. Circuit Switched Network ensures a level of service by transferring large amount of data with guaranteed transmission capacity. There are two types of Circuit Switched network, they are:
· Analog Circuit Switched Network
· Digital Circuit Switched Network

Public Switched Telephony Network (PSTN)

PSTN is a technology using which multiple calls can be transmitted over the same physical medium. PSTN shares available bandwidth more efficiently over the same physical network connectivity.

Connectivity Concepts

T1 and E1 Lines: They work more or less in the similar war and can carry multiple digital voice channels. T1 is used mostly in North America and Japan while E1 is mostly used at UK, Australia and New Zealand. T1 can carry 24 channels per frame, out of which 23 are used for voice while one is used for data signaling. E1 can carry up to 32 channels per frame out of which 30 are used for voice and 2 are used for data signaling.

Trunk Lines: Trunk lines are used to connect Corporate PBX to the Phone Company’s Central Office Switch.

Tie Lines: Tie Lines are T1 or E1 lines that is used to connect 2 or more Corporate PBX systems using Inter-PBX Network signaling or Protocols.

Time Division Multiplexing (TDM): TDM is a technology for transmitting a number of separate voice signals separately over a single physical high Bandwidth phone line. Using this technique the line can be divided into smaller multiple fixed bandwidth channels, each carrying its own voice signal. This shares the transmission productivity of the high bandwidth line. This is how T1 and E1 lines are divided.

Analog PBX systems

Analog PBX systems use the following protocol

In-Band Dual Tone Multi Frequency (DTMF) signaling: It defines a Protocol where call signaling contains DTMF tones. These are within the voice frequency range and are carried in the same channel as voice. The Call Diversion information is supplemental signaling, but it is required to support voice mail.

Out of Band RS232 Signaling: It defines a supplementary protocol where the call signaling is carried on a separate channel from voice. This is done on a separate wire or serial connection using RS232. Out of Band RS 232 signaling is also known as Simplified Message Desk Interface (SMDI).
Exchange Unified Messaging uses VOIP Gateway to transfer analog circuit switching protocols to packet switching protocols. VOIP gateway interprets and translates the call diversion information from the PBX specific protocol to Unified Messaging supported SIP protocol.

Digital PBX systems

Digital PBX system uses the following protocols

Set Emulation: it is used when the signaling protocol is proprietary to the PBX vendor. In this case VOIP gateway must be able to interpret the protocol and translate to Unified Messaging understandable protocol.

QSIG: it is a signaling protocol that is based on ISDN Q.931 standard. QSIG is used between corporate PBX systems and it allows multiple PBX systems to operate together in feature transparent way. Therefore large and distributed Organizations can appear to have a single phone system, though they may have multiple PBX system. QSIG can also be used as Circuit Switch and signaling protocol translated by VOIP gateway.

Channel Associated Signaling (CAS): It is a signaling protocol associated with each channel of voice in a T1 environment. Within the channel, bits are robbed and replaced with basic call signaling information. However, basic CAS does not include the signaling requirements for voice mail. These are provided through In-Band DTMF or RS232 signaling.

Voice over IP (VOIP): It is a technology where voice data is sent in packets by using IP instead of traditional circuit transmission or circuit switched telephone lines of PSTN.

VOIP protocols used by Unified Messaging

SIP: It is a text based application layer signaling and a call control protocol. It is used for initiating, modifying and ending an interactive user session, which involves multimedia elements such as voice, video, instant messaging, online games and virtual reality. It supports both unicast and multicast communication. SIP is used only for setting up and tearing down voice or video calls. SIP uses RTP for transferring digitized audio data between parties participating in a call. Each RTP packet contains one or more media pay loads and other relevant information, such as time stamp and sequence numbers.

Real-time Transport Protocol (RTP): It is standard packet format for delivering audio and video over a given network. RTP uses dynamic ports that are negotiated between sender and receiver.

T.38: It is a protocol that allows you to send FAX messages over an IP based network. Then the IP based network uses SMTP and MIME to send the message to the recipient’s mailbox.

Call Diversion Information

While using Unified Messaging systems you need called party and call diversion information so that the system is aware of the recipients. When an outside caller dials a number of someone inside the business, the call is routed to the Central Office and then to the appropriate customer site’s PBX system. The PBX routes the call to the appropriate desk phone. If the recipient of the call is not at the desk, the call is directed to Ring No Answer. Then, the PBX uses it’s call coverage information to check where the unanswered call should be routed.

Please let me know if the above article was able to provide you with the information you needed.