This document was written to provide step by step instructions for anyone wanting to configure multiple OWA and ECP directories in Exchange 2010. The document will go through a setup and configuration which can provide the baseline for any configuration variation required by an organization needing this type of solution. This document will NOT provide a one stop solution for all scenarios. The solution provided was based on the article by the Exchange Team which can be found here.
Note: The sample configurations shown were done primarily through Exchange Management Shell (EMS). Some of these tasks can be completed through Exchange Management Console (EMC); however, showing them through EMS allows an easily repeatable process through scripting or copy and paste.
To convert between the CPU ready summation value in vCenter’s performance charts and the CPU ready % value that you see in esxtop, you must use a formula.
The formula requires you to know the default update intervals for the performance charts. These are the default update intervals for each chart:
- Realtime: 20 seconds
- Past Day: 5 minutes (300 seconds)
- Past Week: 30 minutes (1800 seconds)
- Past Month: 2 hours (7200 seconds)
- Past Year: 1 day (86400 seconds)
- P2V of a Windows 2008 R2 machine fails at 96%
- You see the error:
Cannot find system volume
- After the P2V conversion fails, the virtual machine cannot be started
- The Windows 2008 R2 system has a default 100MB System Reserved partition
- During the conversion, the 100MB System Reserved partition is not detected on the source machine
- Running the bcedit command reports the error:
The boot configuration data store could not be opened.
The system cannot find the file specified.
When running an Exchange 2010 DAG over a WAN, you may run into some of the limitations of Microsoft FCS (Failover Cluster Service). This service defaults to fairly low timeouts for fast failover in LAN environments. In a WAN environment, where latency may be higher, and some packet loss may occur, you may need to tweak the timeouts for FCS. I advise to tweak most of the settings via the FCS admin tool. However, there are a few settings to tweak via the command line, and here are the maximum values you can configure to make it “less sensitive”
Регулярные выражения (“регэкспы”, от англ. Regular Expressions) – мощное средство составления шаблонов, с помощью которых в заданном тексте может проводиться поиск и сопоставление символов любой сложности.
Как составляется такой шаблон? Для этого используются специальные символы, метасимволы и классы (наборы) символов. Регулярное выражение – это простая строка и любые символы в этой строке, которые не являются специальными (зарезервированными), считаются обычными символами.
Applies To: Windows Server 2008, Windows Server 2008 R2, Windows Server 2012
Functional levels determine the available Active Directory Domain Services (AD DS) domain or forest capabilities. They also determine which Windows Server operating systems you can run on domain controllers in the domain or forest. However, functional levels do not affect which operating systems you can run on workstations and member servers that are joined to the domain or forest.
You can use regular expressions in Microsoft Exchange Server 2010 transport rule predicates to match text patterns in different parts of a message (such as message headers, sender, recipients, message subject, and body). Predicates are used by conditions and exceptions to determine whether a configured action should be applied to an e-mail message.
If you work with the Exchange Management Shell, you’re probably aware that some parameters on cmdlets can accept multiple values. These parameters are associated with “multivalued properties”. If you’ve worked with multivalued properties, you’re probably also aware that it’s very easy to accidentally overwrite these properties when you attempt to add a value to them. That’s because the behavior in the shell is generally to overwrite the existing value in a property, rather than add to it.
One thing that caught me by surprise in Exchange 2010 was the new ways it handled relaying to external domains. Well Microsoft is moving closer and closer to lockdown by default type of methodology for their systems; making you open the holes you want to open. Well what this did was made me troubleshooting why notifications from network applications were going to internal users instead of external users.
Here is how you fix it.
Consider the following scenario. You create certificate certificate by using either Exchange Management Console (EMC) or Exchange Management Shell (EMS) and save it to a file. When you attempt to submit certificate request to a Windows-based Certification Authority (CA) (also known as Microsoft Certificate Services), you may receive error message. If CA server runs on Windows Server 2003 (R2) or Windows Server 2008, you receive the following message : ASN1 bad tag value met. 0x8009310b (ASN: 267).