High Availability with DAG (Database Availability Group)
Cross forest management through EMC
Certificate management with Exchange Management Console
Enabling Diagnostics Logging Management through EMC
Exchange Management Shell Command Log
Move mailbox took a new twist
Setting up OWA policies though EMC
In house Archiving
Federation and Sharing of PIM data across different exchange organization
Proactive Organizational Health check
RBAC
Sunday, November 8, 2009
Friday, November 6, 2009
Exchange 2010 Shadow Redundancy compared to transport dumpster
" Exchange 2007 introduced the Transport Dumpster feature for the Hub server role. An Exchange 2007 hub server maintains a queue of messages delivered recently to recipients whose mailboxes are on a clustered mailbox server. When a failover is experienced, the clustered mailbox server automatically requests every Hub server in the Active Directory site to resubmit mail from the transport dumpster queue. This prevents mail from being lost during the time taken for the cluster to fail over. While this does provide a basic level of transport redundancy, it is only available for message delivery in a Cluster Continuous Replication environment and does not address potential message loss when messages are in transit between hub and edge servers.
Exchange 2010 introduces the Shadow Redundancy feature to provide redundancy for messages for the entire time they are in transit. The solution involves a technique similar to the Transport Dumpster. With Shadow Redundancy, the deletion of a message from the transport databases is delayed until the transport server verifies that all of the next hops for that message have completed delivery. If any of the next hops fail before reporting back successful delivery, the message is resubmitted for delivery to that next hop. "
Exchange 2010 introduces the Shadow Redundancy feature to provide redundancy for messages for the entire time they are in transit. The solution involves a technique similar to the Transport Dumpster. With Shadow Redundancy, the deletion of a message from the transport databases is delayed until the transport server verifies that all of the next hops for that message have completed delivery. If any of the next hops fail before reporting back successful delivery, the message is resubmitted for delivery to that next hop. "
Wednesday, November 4, 2009
Exchange 2010 Control Panel
It is now possible to perform some basic Exchange management tasks using the options page in Outlook Web Access; not only on the user’s own properties, but also at an organizational level. With this method, it is possible to create users, mailboxes, distribution groups, mailenabled contact, management e-mail addresses etc.
Features of Outlook Web App in Exchange Server 2010
The most visible improvement for end-users is Outlook Web App (previously known as Outlook Web Access). One of the design goals for the Outlook Web App was a seamless cross-browser experience, so users running a browser like Safari, even on an Apple MacBook, should have exactly the same user experience as users running Internet Explorer.
Outlook Web App off ers a very rich client experience and narrows the gap between a fullyfl edged Outlook client and Outlook Web Access. To reinforce that experience, a lot of new features have been introduced. To name a few: Favorites, Search Folders, attaching messages to messages, integration with Offi ce Communicator, a new Conversation View (which works very well!), integration with SMS (text) messages and the possibility to create Outlook Web Access policies, which give the Exchange organization administrator the ability to fi ne tune
the user experience.
Outlook Web App off ers a very rich client experience and narrows the gap between a fullyfl edged Outlook client and Outlook Web Access. To reinforce that experience, a lot of new features have been introduced. To name a few: Favorites, Search Folders, attaching messages to messages, integration with Offi ce Communicator, a new Conversation View (which works very well!), integration with SMS (text) messages and the possibility to create Outlook Web Access policies, which give the Exchange organization administrator the ability to fi ne tune
the user experience.
Top 10 reasons to upgrade to Windows Server 2008 R2
1. Powerful hardware and scaling features Windows Server 2008 R2 supports
up to 256 logical processors. R2 also supports SLAT, which enables R2 to take advantage of the Enhanced Page Tables feature found in the latest AMD CPUs as well as the similar Nested Page Tables feature found in Intel’s latest processors. The combination enables R2 servers to run with much improved memory management.
2. Improved Hyper-V Hyper-V in Windows Server 2008 R2 can now access up to 64 logical CPUs on host computers—twice Hyper-V’s initial number of supported CPUs.Live migration enables a highly fault-tolerant virtualization infrastructure, and dynamic addition and removal of disks simplifies backup scenarios and overall management of virtualized resources.
3. Reduced power consumption Windows Server 2008 R2 supports Core Parking, which dynamically turns off unused processor cores when they aren’t needed, reducing power consumption.
4. Reduced desktop costs Windows Server 2008 R2 enables VDI technology, which extends the functionality of RDS to provide full desktop virtualization or application virtualization of key applications.
5. Improved server management Windows Server 2008 R2 includes a new version
of Windows PowerShell, which is now available on Server Core as well. Server Manager can now also be used remotely.
6. Improved branch office performance and security Windows Server 2008 R2
includes BranchCache and read-only DFS-R, which extends the branch office scenarios introduced in Windows Server 2008.
7. Improved Web server Windows Server 2008 R2 includes IIS 7.5 as well as a new FTP server. IIS 7.5 includes a new Windows PowerShell provider for IIS management.
8. Windows PowerShell v2 Windows Server 2008 R2 includes an improved and
more powerful version of Windows PowerShell that has cmdlet support for remote management. Windows PowerShell is now available on Server Core in Windows Server 2008 R2.
9. Improved Remote Desktop Services The new RDS features provide an improved and more seamless user experience, especially when the client is running Windows 7.
10. Improved mobile user experience Mobile users running Windows 7 have seamless and continuous access to corporate resources through DirectAccess. And RD Web Access, provides users running at least Windows XP SP3 with full access to published applications or desktops.
up to 256 logical processors. R2 also supports SLAT, which enables R2 to take advantage of the Enhanced Page Tables feature found in the latest AMD CPUs as well as the similar Nested Page Tables feature found in Intel’s latest processors. The combination enables R2 servers to run with much improved memory management.
2. Improved Hyper-V Hyper-V in Windows Server 2008 R2 can now access up to 64 logical CPUs on host computers—twice Hyper-V’s initial number of supported CPUs.Live migration enables a highly fault-tolerant virtualization infrastructure, and dynamic addition and removal of disks simplifies backup scenarios and overall management of virtualized resources.
3. Reduced power consumption Windows Server 2008 R2 supports Core Parking, which dynamically turns off unused processor cores when they aren’t needed, reducing power consumption.
4. Reduced desktop costs Windows Server 2008 R2 enables VDI technology, which extends the functionality of RDS to provide full desktop virtualization or application virtualization of key applications.
5. Improved server management Windows Server 2008 R2 includes a new version
of Windows PowerShell, which is now available on Server Core as well. Server Manager can now also be used remotely.
6. Improved branch office performance and security Windows Server 2008 R2
includes BranchCache and read-only DFS-R, which extends the branch office scenarios introduced in Windows Server 2008.
7. Improved Web server Windows Server 2008 R2 includes IIS 7.5 as well as a new FTP server. IIS 7.5 includes a new Windows PowerShell provider for IIS management.
8. Windows PowerShell v2 Windows Server 2008 R2 includes an improved and
more powerful version of Windows PowerShell that has cmdlet support for remote management. Windows PowerShell is now available on Server Core in Windows Server 2008 R2.
9. Improved Remote Desktop Services The new RDS features provide an improved and more seamless user experience, especially when the client is running Windows 7.
10. Improved mobile user experience Mobile users running Windows 7 have seamless and continuous access to corporate resources through DirectAccess. And RD Web Access, provides users running at least Windows XP SP3 with full access to published applications or desktops.
Removal from Exchange Server 2010 compared to Exchange 2007
1. In Exchange Server 2007 we had LCR, CCR and SCR - three diff erent versions of replication, all with
their own management interfaces. All three are no longer available in Exchange Server 2010.
2. Windows Server Fail-over Clustering has been removed in Exchange Server 2010. Although seriously improved in Windows Server 2008, a lot of Exchange Administrators still found the fail-over clustering complex and diffi cult to manage. As a result, it was still prone to error and a potential source of all kinds of problems.
3. Storage Groups are no longer available in Exchange Server 2010. The concepts of a database,log files and a checkpoint file are still there, but now it is just called a database. It’s like CCR in Exchange Server 2007, where you could only have one database per Storage Group.
4. The Single Instance Storage (SIS) is no longer available. This means that when you send a 1 MB message to 100 recipients, the database will potentially grow by 100 MB. This will surely have an impact on the storage requirements in terms of space, but the performance improvements on the Database are really great.
their own management interfaces. All three are no longer available in Exchange Server 2010.
2. Windows Server Fail-over Clustering has been removed in Exchange Server 2010. Although seriously improved in Windows Server 2008, a lot of Exchange Administrators still found the fail-over clustering complex and diffi cult to manage. As a result, it was still prone to error and a potential source of all kinds of problems.
3. Storage Groups are no longer available in Exchange Server 2010. The concepts of a database,log files and a checkpoint file are still there, but now it is just called a database. It’s like CCR in Exchange Server 2007, where you could only have one database per Storage Group.
4. The Single Instance Storage (SIS) is no longer available. This means that when you send a 1 MB message to 100 recipients, the database will potentially grow by 100 MB. This will surely have an impact on the storage requirements in terms of space, but the performance improvements on the Database are really great.
Tuesday, November 3, 2009
MFCMapi to remove all rules in Outlook 2007
a. Open the folder C:\_localdata, double click mfcmapi.exe and then click OK.
b. On the Session menu, click Logon and Display Store Table.
c. If you are prompted to select a profile, click the client’s mail profile in the Profile Name list, and then click OK.
d. Double-click the mailbox that contains the inbox rules that you want to delete.
e. Expand Root Container, and then expand Top of information Store.
f. Right-click Inbox and then click Open Associated Contents Table.
g. Use the Horizontal Scroll Bar to bring the Message Class column in view.
h. IMPORTANT! Highlight and delete ONLY items named IPM.Rule.Message and IPM.ExtendedRule.Message.
i. Once you hit the delete key you will be prompted to choose the type of deletion. Using the drop down box select, Permanent delete passing DELETE_HARD_DELETE (unrecoverable).
j. Close all MFCmapi windows and restart Outlook. Double check that all client rules have been removed by going into Toolsà Rules and Alerts.
b. On the Session menu, click Logon and Display Store Table.
c. If you are prompted to select a profile, click the client’s mail profile in the Profile Name list, and then click OK.
d. Double-click the mailbox that contains the inbox rules that you want to delete.
e. Expand Root Container, and then expand Top of information Store.
f. Right-click Inbox and then click Open Associated Contents Table.
g. Use the Horizontal Scroll Bar to bring the Message Class column in view.
h. IMPORTANT! Highlight and delete ONLY items named IPM.Rule.Message and IPM.ExtendedRule.Message.
i. Once you hit the delete key you will be prompted to choose the type of deletion. Using the drop down box select, Permanent delete passing DELETE_HARD_DELETE (unrecoverable).
j. Close all MFCmapi windows and restart Outlook. Double check that all client rules have been removed by going into Toolsà Rules and Alerts.
Monday, November 2, 2009
Function of /3GB switch
The /3GB switch changes the way the 4GB virtual address space is split up. Instead of splitting it as 2GB of user mode virtual address space and 2GB of kernel mode virtual address space, the split is 3GB of user mode virtual address space and 1GB of kernel mode virtual address space.
Sunday, November 1, 2009
The System Attendant mailbox has been removed from Exchange 2010
In previous versions of Exchange, the System Attendant (SA) Mailbox was used by the link monitoring service and for publishing Free / Busy information. However, this functionality is no longer needed in Exchange 2010. As such the mailbox has been removed.
One catalyst to this change was the new High Availability (HA) features in Exchange 2010. Having the System Attendant mailbox on servers presents a problem when the server needs to failover to the passive mailboxdatabase copy. Since only one SA mailbox can exist per server which SA mailbox do you use? The mailbox database's passive copy or the one from the mailbox that just failed over?
There are two components to the System Attendant mailbox, the directory object and the mailbox object. The key here is that the directory object has _not_ been removed, only the mailbox object. Therefore, you will still be allowed to connect to Exchange using the System Attendant however you will not be able to logon (effectively open the mailbox object).
So what are your workarounds?
1. You can still use the per mailboxdatabase System mailbox.
2. You can change your application to rely on a user created account and mailbox.
One catalyst to this change was the new High Availability (HA) features in Exchange 2010. Having the System Attendant mailbox on servers presents a problem when the server needs to failover to the passive mailboxdatabase copy. Since only one SA mailbox can exist per server which SA mailbox do you use? The mailbox database's passive copy or the one from the mailbox that just failed over?
There are two components to the System Attendant mailbox, the directory object and the mailbox object. The key here is that the directory object has _not_ been removed, only the mailbox object. Therefore, you will still be allowed to connect to Exchange using the System Attendant however you will not be able to logon (effectively open the mailbox object).
So what are your workarounds?
1. You can still use the per mailboxdatabase System mailbox.
2. You can change your application to rely on a user created account and mailbox.
History of M: Drive came out in Exchange 2003
There are two reasons: first, “M” for “Mail”, and second, because it was in the middle of the alphabet and least likely to collide either with actual storage drives -which start at A and move up - or mapped network drives - which start at Z and move down), and get a list of mailboxes, navigate to mail folders via cmd or windows explorer and look at actual messages.
Exchange System Management (ESM) tool does not use DSAccess to discover the DC it will talk to. Instead it discovers the DC it will use on its own, using ADSI to do a server-less binding to the directory. The reason behind this is because of ESM's extensive use of and queries to the AD.
Exchange System Management (ESM) tool does not use DSAccess to discover the DC it will talk to. Instead it discovers the DC it will use on its own, using ADSI to do a server-less binding to the directory. The reason behind this is because of ESM's extensive use of and queries to the AD.
Subscribe to:
Posts (Atom)