Exchange Experts

Setup & Deployment of Lync Server 2010 Edge Server

2011-11-18T00:46:00.001+05:30

Setup & Deployment of Lync Server 2010: Edge Server

Hardware System Requirements for Edge Servers

Hardware component Minimum requirement

CPU One of the following:

• 64-bit dual processor, quad-core, 2.0 GHz or higher
• 64-bit 4-way processor, dual-core, 2.0 GHz or higher

Memory 12 GB recommended

Disk Local storage with at least 30 GB free disk space

Network Two interfaces required, either one 2-port 1 Gbps NIC or two 1-port 1 Gbps NICs.

Software System Requirements for Edge Servers

Lync Server 2010 is available only in a 64-bit edition, so each Edge Server requires one of the following operating systems.

• The 64-bit edition of Windows Server 2008 Enterprise Edition with SP2 operating system, or the 64-bit edition of Windows Server 2008 Standard Edition with SP2 operating system.

• The 64-bit edition of Windows Server 2008 R2 Enterprise operating system, or the 64-bit edition of Windows Server 2008 R2 Standard operating system.

Lync Server 2010 also requires installation of the following programs and updates:

• Microsoft .NET Framework 3.5 SP1

• Windows PowerShell command-line interface version 2.0

• Windows Server 2008 R2 update available from Microsoft Knowledge Base article 2028827, "The applications that use the TDI driver for network traffic may stop responding in Windows Server 2008 R2 or in Windows 7," at http://go.microsoft.com/fwlink/?LinkId=205459.

• Windows 2008 SP2 update is required to avoid increasing memory usage on Web Conferencing Edge Server. For details, see Microsoft Knowledge Base article 979231,"Memory usage keeps increasing if Schannel authentication is used after the update 968389 is installed in Windows Vista or in Windows Server 2008," at http://go.microsoft.com/fwlink/?LinkId=200747. After you apply this update, the increasing memory usage should go away.

• Windows Server 2008 update available from Microsoft Knowledge Base article 2029048, "Applications that use the TDI driver for network traffic may stop responding in Windows Server 2008 or in Windows Vista," at http://go.microsoft.com/fwlink/?LinkId=205458.
A
dditionally, Lync Server requires the Microsoft Visual C++ 2008C redistributable, but it is automatically installed as part of the Edge Server installation.

Steps to Install Edge Server

Actions to be performed on the server with topology builder installed

1. In topology builder, go to edge server pools and click on “New Edge Pool”.

2. An installation wizard will come up listing all the necessary things for a new edge pool.

3. Provide the FQDN of the edge server. Also, choose the “Single Computer Pool” option.

4. Select the features of the edge pool.

5. On the next screen, as the “Use a Single FQDN & IP Address” was selected, only one FQDN will have to be provided.

6. Provide the Internal and External IP addresses.

7. Select the next hop pool and the Associated Front end pool.

8. Proceed to complete the configuration of an edge server on topology builder.

9. From topology builder, publish the topology.

10. On the Lync Server Management Shell, run the following script to export the configuration details as a compressed file: export-csconfiguration -Filename "c:\confignew.zip"

11. Copy the exported file onto the Edge server machine.

Actions to be performed on the Edge Server Machine

1. Change the FQDN of the machine to what has been defined in topology builder.

2. Make sure that there are two NICs on this machine and configure their IPs as defined in the topology builder.

3. Run the script to install all the prerequisites required for the Edge Server role.

Import-Module ServerManager
Add-WindowsFeature Desktop-Experience,NET-Framework,RSAT-ADDS,Telnet-Client,Web-Server,Web-Static-Content,Web-Default-Doc,Web-Http-Errors,Web-Http-Redirect,Web-Asp-Net,Web-Net-Ext,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-Http-Logging,Web-Log-Libraries,Web-Http-Tracing,Web-Windows-Auth,Web-Client-Auth,Web-Filtering,Web-Stat-Compression,Web-Mgmt-Console,Web-Scripting-Tools,Web-Mgmt-Compat –Restart

4. Install the following KB: 982021

5. In the Deployment Wizard of Lync Server, click on “Install or Update Lync Server System”.

6. Run “Install Local Configuration Store”. Give the path of the configuration file.

7. Run the Setup or Remove Lync Server Components

8. Now request for certificates. The Certificates Wizard looks as follows.

9. Request for an offline certificate and provide a friendly name for the certificate. Also mark the private key as exportable and provide organizational details and the geographical details. Proceed to complete the request.

10. Follow the same steps for requesting the External certificate.

11. Copy the request files to the DC and through the Certification Authority, submit a new request and generate the certificates.

12. Copy the certificates back to the Edge Server and import them using the Certificate Wizard.

13. Once the import is complete, assign the certificates to their respective networks.

14. Start the services.

Step-by-Step installation of Lync Server 2010

2011-09-20T00:22:00.000+05:30

Lync 2010 Front End Server System Requirement:

Hardware Recommendations for Servers Running Lync Server 2010

Hardware component Recommended

CPU One of the following:
• 64-bit dual processor, quad-core, 2.0 GHz or higher
• 64-bit 4-way processor, dual-core, 2.0 GHz or higher
Intel Itanium processors are not supported for Lync Server 2010 server roles.
Memory 16 GB
Disk Local storage with at least 72 GB free disk space on a 10,000 RPM disk drive
Network 1 network adapter required (2 recommended), each 1 Gbps or higher
The number of users is less and you are not using voice functionality so you can reduce the RAM upto 8 GB.
Operating Systems
Windows Server 2008 R2 Standard operating system as we are not using clustering.
Additional Software Requirements
http://technet.microsoft.com/hi-in/library/gg398686(en-us).aspx
Network requirement:
In Standard Edition topologies, servers should be in a network that supports 1 Gbps Ethernet or equivalent.
Active Directory requirement:
Domain Controller should be Windows Server 2003 operating system and above.
Forest and Domain Functional Level
Raise all forest and domains Functional Level to at least Windows Server 2003 native mode

Steps to Install Lync 2010 Front End Server:

Go to control panel, check if any speech update is installed, if yes then uninstall it.

1. Login as domain admin

2. Make sure AD certificate services with web enrollment

3. Run windows update.

4. Install the Hotfix that is described in KB 975858 for Windows Server 2008 R2.
975858 An application or service that calls the InitializeSecurityContext function together with the ISC_REQ_EXTENDED_ERROR flag may encounter a TLS/SSL negotiation failure on a computer that is running Windows Server 2008 R2 or Windows 7 operating system

5. Install Fix KB 974571

6. If you want to change the NTLM setting, follow these steps:
1. Start secpol.msc on a Windows Server 2008 R2 operating system server.
2. Click to select Local Policies and then click Security Options node.
3. Make sure that the following values of the policies are set to "No Minimum."
• Network Security: Minimum session security for NTLM SSP based (including secure RPC)
• Network Security: Minimum session security for NTLM SSP based (including secure RPC) servers

The default security setting on Windows Server 2008 R2 operating system for NTLM SSP requires 128-bit encryption. Depending on the client operating system mix in the enterprise, you may have to reduce this setting on a Windows Server 2008 R2 operating system that is running Office Communications Server 2007 R2 as a down level operating system. The key is set to "No requirement."
1. For any down level operating system, such as Windows XP or for Windows Vista, the default value is set to "No Minimum."
2. For a Windows 7 operating system, the default value is set to "Requires 128-bit encryption."

Start secpol.msc on a Windows Server 2008 R2 operating system server.
Click to select Local Policies and then click Security Options node.
Make sure that the following values of the policies are set to "No Minimum."
• Network Security: Minimum session security for NTLM SSP based (including secure RPC)
• Network Security: Minimum session security for NTLM SSP based (including secure RPC) servers

10. Windows Power shell
PS C:> Import-Module ServerManager
PS C:> Add-WindowsFeature NET-Framework,RSAT-ADDS,Telnet-Client,Web-Server,Web-Static-Content,Web-Default-Doc,Web-Http-Errors,Web-Http-Redirect,Web-Asp-Net,Web-Net-Ext,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-Http-Logging,Web-Log-Libraries,Web-Http-Tracing,Web-Windows-Auth,Web-Client-Auth,Web-Filtering,Web-Stat-Compression,Web-Mgmt-Console,Web-Scripting-Tools -Restart

11. Install Lync server iso or cd

12. Click yes to visuall c++ 2008

13. Accept license agreement

14. Prepare Active directory

15. Select prepare schema run tab and let it complete

16. Select prepare current forest run tab and let it complete

17. Select prepare current domain run tab and let it complete

18. Select "prepare first standard edition" top right hand side

19. Install topology builder

20. Now go to start->program file ->Lync server 2010 -> topology builder

21. Topology builder pop up will come select new topology

22. In create new topology select sip domain ( local domain)

23. Next screen alternate domain add (exchange email address domain eg:contoso.com)

24. Define first site: add site name (Any name to identify the site)

25. Specify site detail: city, state, country

26. Make sure "Open the New Front End Wizard" is checked Click on finish

26. Click next on define new front end pool

27. Now, define new front end pool fqdn screen, type FQDN on Lync server, select standard server edition option.
29. Select features screen, select the conferencing, enterprise voice depending on requirement.

30. If enterprise voice is selected then in select collocated server role option select option for Collocated mediation server.

31. Next wizard screen associate server roles with front end pool
1. If you want archiving option go for archiving but it requires separate server with sql database.
2. You can enable monitoring only if enterprise voice is selected earlier
3. Egde pool option should be only checked if you have complete information on Edge server setup.

32. Next wizard screen, define SQl store click Next.

33. Next wizard screen, define file share. Keep the default option and create a share folder on Lync front end server.
Share folder should be shared with domain admins with full access and everyone read.

34. Next wizard screen, specify the web services the external URL by default is fqdn. We can make changes to it afterwards. Select "Finish"

35. Right click on the lync server 2010 in topology builder, properties ->central management server

36.
37. In administrative access url type "https://admin.domainname.com'

38. Now we have to Publish topology, lync server right click 'publish"

39.

40. Publish topolgy " select next'

41. Select central management store "make sure fqdn on lync FE is there"

42. In Publish wizard "select finish"

43. Go to setup wizard i.e Lync ISO ->setup-amd64->setup.exe ->Install or update Lync Server System
=> Install local configuration store ( Run, simple next)
=>Setup or remove Lync Server Components ( may require restart)
=> Request, Install or Assign Certificates
44. Now certificate information is simple. Before this make sure you have Certificate authority installed in domain In Name and Security setting page of wizard mention the internal name of certificate, basic information of organization. If there are multiple sip domain then select multiple domain at sip domain setting on subject alternative names.

45. Now start services.

46. Now certificate information is simple. Before this make sure you have Certificate authority installed in domain

47. If there is multiple domains then only changes are require apart from that select next :)

48. Now start services.

49. Now go to active directory users and computers in domain controller.

50. Add domain admin account to CS administrator group and RTC universal server admin.

51. Go back to Lync front end server start -> program > Lync server 2010-> Lync server control panel. Keep it open

52. Go back to Lync front end server start -> program > Lync server 2010-> Lync server management shell ->
eg
Enable-CsUser -Identity "Pilar Ackerman" -RegistrarPool "atl-cs-001.litwareinc.com" -SipAddress sip:pilar@litwareinc.com

53. Create internal DNS record, A record for sip.domainname.com pointing to Front end server
Create SRV record, right click on zone => other new record, SRV record, Service :_sipinternaltls, protocol :_tcp, port number :5061

To updated photos in Lync Client:
exchange management sheel:\

Import RecipientDataProperty –Identity bobby –Picture –FileData ([Byte[]]$(Get Content –Path “d:\labfiles\images\bobbymoore.jpg” –Encoding Byte –ReadCount 0))

Blocking Active Sync Devices on Exchange 2010

2010-11-17T13:45:00.005+05:30

What is the Allow/Block/Quarantine list?
In Exchange 2010 we added a feature called the Allow/Block/Quarantine list (or ABQ for short). This feature was designed to help IT organizations control which of the growing number of Exchange ActiveSync-enabled devices are allowed to connect to their Exchange Servers. With this feature, organizations can choose which devices (or families of devices) can connect using Exchange ActiveSync (and conversely, which are blocked or quarantined).

Some of you may remember my previous post on this topic dealing with organizations that do not have Exchange 2010 and thus I wanted to show you the far better way you can do this in Exchange 2010 (which is also what you will see in Office 365 and Exchange Online if you are looking at our cloud-based offerings).
It is important to understand that the ABQ list is not meant to displace policy controls implemented using Exchange ActiveSync policies. Policy controls allow you to control and manage device features (such as remote wipe, PIN passwords, encryption, camera blocking, etc.) whereas the ABQ list is about controlling which devices are allowed to connect (for example, there may be a lot of devices that support EAS PIN policies, but some IT departments only want allow certain devices to connect to limit support or testing costs). The easy takeaway is that Exchange ActiveSync policies allow you to limit device access by capabilities while the Allow/Block/Quarantine list allows you to control device access by device type. If you're curious as to what devices OS support which policies, the Wikipedia article we blogged about is a good place to look.

Different device access models for different folks
When we designed the ABQ list, we talked to a lot of organizations to find out how all of you use (or wanted to use) this kind of technology. What we realized is that there is a continuum of organizations; from permissive organizations that let employees connect whatever device they have to their Exchange Server, all the way to restrictive organizations that only support specific devices. Since we always want to make our software as flexible for IT as possible (as we know there are a lot of you folks that are using our software in a lot of different ways) we created this feature so that no matter which type of organization you are (or even if you are one that is in between these two extremes) we could help meet your needs. Below are some descriptions and "how-to"s for using the ABQ list in these different ways.
The restrictive organization
Restrictive organizations follow a more traditional design where only a set of supported devices is allowed to connect to the Exchange server. In this case, the IT department will only choose to allow the particularly devices they support and all other devices are blocked.

It's important to note that a restrictive organization is created by specifying a set of allowed devices and blocking the unknown.
Below is a flow chart of the logic.

Figure 1: Restrictive organizations specify a set of allowed devices and block unknown devices

The permissive organization:
Permissive organizations allow all (or most devices) to connect to their Exchange Server. In these cases, the ABQ list can help organizations block a particular device (or set of devices) from connecting (useful if there is a security vulnerability or if the device is putting a particularly heavy load on the Exchange server). In these cases, The IT department can identify the misbehaving device and block that device until a fix/update for that device brings it into compliance. For all other devices (including the unknown) the devices are given access. Below is a flowchart of that logic.

Figure 2: Permissive organizations allow all devices and block specified misbehaving devices
The one off case:
Of course, if you are limiting the devices that connect to your organization, there is almost always a need for an exception. Whether it's testing a new device before rolling it out to the organization as a supported device, or an exception made for an executive, we wanted to give you the ability to make an exception without allowing all users with that device to access your organization's email, and PIM data. Below is a flowchart of that logic.

Figure 3: You can allow specific devices to connect without having to create rules to allow or block all devices of that type
When to quarantine:
Quarantining devices is useful when an IT department wants to monitor new devices to their organization. Both permissive and restrictive organizations may choose to employ this mechanism. In a permissive organization, quarantine can be used so that IT administrators know what devices, and which users, are making new connections. In restrictive organizations, this can be used to see who is trying to work around policy and also gauge demand from "Bring Your Own Device" (BYOD) users. Below is a flowchart of that logic. Note that you could also choose to quarantine at the device/device family level if you wanted (although not shown here, you could also quarantine at the device/family decision).

Figure 4: Quarantine devices to monitor new devices connecting to your Exchange organization
Now that we've gone through the theory, let's talk about how we would do this in practice.
Accessing the ABQ settings:
1. Log in to the Exchange Control Panel (ECP)
(you can also access the ECP from Outlook Web App (OWA) by selecting Options > See all options)
2. In the ECP, make sure you are managing My Organization (#1 in the screenshot below). Be aware that most users won't see the "My Organization" option — it's only visible to users with Exchange Administrator access.
3. Select Phone & Voice (#2 in the screenshot below) > ActiveSync Access tab (#3 in the screenshot below). This is the Allow/Block/Quarantine configuration screen.
Note for all you Exchange Management Shell (EMS) gurus, you can also configure device access using PowerShell cmdlets if you prefer.

Figure 5: Accessing ABQ settings from the Exchange Control Panel
Creating a device (or a family of devices) rule:
To create a new rule, select New from the Device Access Rules section of the ABQ page (#5 in the screenshot above).
When setting up a rule for a device, it is important to understand the difference between the "family" of the device and the specific device. This information is communicated as part of the EAS protocol and is reported by the device itself. In general, you can think of the deivce rule as applying only to the particular device type (like an HTC-ST7377 as shown in the image below) whereas a device family might be something more broad like "Pocket PC". This distinction between the specific (device type) and the general (device family) is important since many device manufacturers actually release the same device with different names on different carriers. To make it so that you don't have to make a separate rule for each device. For instance, the HTC Touch Pro was available on all four majour US carriers as well as some of the regional ones, and that's just the USA, not to mention the other versions around the world. As you can see, making a rule for each of those different devices (which are all in the same family and effectively the same device) could mean a lot of extra work for IT, so we added the family grouping to help you make good decisions about devices in bulk. It's important to note that when making a new rule you select the device family or the model but not both. Once you've selected the device or a device family, you can then choose what Exchange will do with that device (in this example, I'm just going to do a specific device).
This brings you to the New Device Access Rule page. The easiest way to set the rule is to select Browse, which will show you a list of all the devices or device families that have recently connected to your Exchange Server. Once you've selected the device or family, you can choose the action to take. This is where you can choose to block the device if you are a permissive organization looking to limit a specific device for a specific reason or where you can set access rules if you are a restrictive organization (in such a case you would just create an allow rule for each supported device and then set the state for all unknown devices to block (we'll talk about how to set the action for unknown devices in the next section). Once you select the action (Allow access, Block access, or Quarantine), click Save and you're done! You can repeat this process for each rule you want to create. You can also have both block and allow rules simultaniously.

Figure 6: Creating a device access rule
Setting up a rule for unknown devices:
To access the rule for unknown devices, select Edit (#4 in Figure 5 above). On the Exchange ActiveSync Settings page, you can configure the action to take when Exchange sees a user try to connect with a device that it does not recognize. By default, Exchange allows connections from all devices for users that are enabled for EAS. This example configures the Exchange organization to quarantine all unknown devices. This means that if there's no rule for the device (or device family) or if there's no exception for the particular user, then an unknown device will follow this behavior.

Figure 7: You can create a default rule for unknown devices and select administrators to be notified about quarantined devices
We have the ability to specify who gets an email alert when a device is placed in quarantine. You can add one or more administrators (or users) or even a distribution group to this list of notified individuals. Anyone on that list will receive an email like the one shown in the screenshot below. The notification provides you information about who tried to connect the device, the device details and when the attempt was made.

Figure 8: Quarantined device notifications inform you about connection attempts from unknown devices
You can also set a custom message that will be delivered to the user in their Inbox and on their device. Although the device is in quarantine, we send this one message to the device so the user doesn't automatically call help desk because their device isn't syncing. The custom message is added to the notification email to the user that their device is in quarantine (see example image below).

Figure 9: Quarantined devices receive a notification
The user and device will also now appear on the Quarantined Devices list on the ABQ configuration page (circled in red in the image below).

Figure 10: Quarantined devices in ECP
The device will stay in quarantine until an administrator decides to allow or block the device in quarantine. This can be done by selecting the device and then clicking on the Allow or Block buttons in Quarantined Devices (circled in red below). This creates a personal exemption (the "one off case" mentioned earlier). If you wish to create an access rule that is to apply to all devices of the same family or model, you can select Create a rule for similar devices. (#2 in the image below) to open a new, prepopulated, rule.

Figure 11: You can allow or block a quarantined device or create a device access rule for the device model or family
Making changes:
Of course we realize that many organizations are dynamic and have changing requirements and policies. Any of the rules that have been set up can be changed dynamically by accessing the ABQ page in the ECP and editing, deleting, or adding the desired rule.

This Article is taken from MSEXCHANGE.ORG at "http://msexchangeteam.com/archive/2010/11/15/456931.aspx"

Cross Forest Domain and Exchange Migration

2010-09-19T10:15:00.001+05:30

Hi Guys,

Soon i will be sharing an article on Cross Forest Domain migration, which will include user account, groups, computer account, mailbox etc. I am working on preparation of document and will publish it shortly..... Stay Tuned :)

Changing the IP address of a RSA Authentication Manager server

2010-09-19T10:13:00.001+05:30

Below are the steps-by-step procedure which needs to be carried out to change the IP address of RSA Authentication Manager Server

Stop Services

1) Select Start
2) All Programs
3) RSA Authentication Manager Control Panel
4) Select Start & Stop RSA Auth Mgr Services
5) Click Stop All
6) Click OK
7) Click Edit
8) Uncheck Automatically start services on system startup
9) Click OK

Update Replica

1) Select Start
2) All Programs
3) RSA Security
4) RSA Authentication Manager
5) RSA Authentication Manager Configuration Tools
6) RSA Authentication Manager Replica Management
7) Highlight the Primary Server
8) Click Details
9) Change the Name and/or the IP addresses of the Primary ACE/Server configuration
10) Click OK to the notice that you have changed the Name and now must change the system name

Update Server

1) Change the name or IP address on the Primary Server Operating system, and reboot the machine
2) Select Start
3) All Programs
4) RSA Security
5) RSA Authentication Manager
6) RSA Authentication Manager Configuration Tools
7) RSA Authentication Manager Replica Management
8) Click OK to the “The name and/or IP address of this Primary RSA ACE/Server has changed successfully”
Start Services

1) Select Start
2) All Programs
3) RSA Authentication Manager Control Panel
4) Select Start & Stop RSA Auth Mgr Services
5) Click Start All
6) Click OK
7) Click Edit
8) Check Automatically start services on system startup
9) Click OK

Unable to Start DHCP Client Service Access is Denied

2010-09-19T10:01:00.002+05:30

If you get an error 5 : Access is Denied while starting the DHCP client service.

This is because of permissions issue on this service to Network Service account.

to resolve this problem kindly give access to network service at this location
"HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\dhcp\Parameters" and you are done!!!

Exchange 2007 reinstall error 3221684226

2010-08-15T12:55:00.011+05:30

An error occurred. The error code was 3221684226. The message was The system cannot find the file specified..
Background: Installing Exchange 2007 Server SP3 on a Windows Server 2008 R2 may produce the following error during setup: An error occurred. The error code was 3221684226. The message was The system cannot find the file specified..

Cause: Remote Server Administration Tools (RSAT) and Active Directory Domain Services Tools are not installed.

Solution: Install the required features. (Open a command prompt and: ServerManagerCmd -i RSAT-ADDS)

The following table lists the class modifications that Exchange 2007 SP2 makes to the Active Directory schema.

2010-07-22T18:13:00.001+05:30

The following table lists the class modifications that Exchange 2007 SP2 makes to the Active Directory schema.
Class Change Attribute/Class
Address-Book-Container add:mayContain msExchSystemAddressList
Group add:mayContain msExchArbitrationMailbox
Group add:mayContain msExchCoManagedByLink
Group add:mayContain msExchGroupDepartRestriction
Group add:mayContain msExchGroupJoinRestriction
Mail-Recipient add:mayContain msExchAggregationSubscriptionCredential
Mail-Recipient add:mayContain msExchArbitrationMailbox
Mail-Recipient add:mayContain msExchBlockedSendersHash
Mail-Recipient add:mayContain msExchBypassModerationBL
Mail-Recipient add:mayContain msExchBypassModerationFromDLMembersBL
Mail-Recipient add:mayContain msExchBypassModerationFromDLMembersLink
Mail-Recipient add:mayContain msExchBypassModerationLink
Mail-Recipient add:mayContain msExchCalendarRepairDisabled
Mail-Recipient add:mayContain msExchCoManagedObjectsBL
Mail-Recipient add:mayContain msExchDirsyncID
Mail-Recipient add:mayContain msExchEdgeSyncRetryCount
Mail-Recipient add:mayContain msExchEnableModeration
Mail-Recipient add:mayContain msExchExternalSyncState
Mail-Recipient add:mayContain msExchForeignGroupSID
Mail-Recipient add:mayContain msExchImmutableId
Mail-Recipient add:mayContain msExchIntendedMailboxPlanLink
Mail-Recipient add:mayContain msExchMailboxMoveBatchName
Mail-Recipient add:mayContain msExchMailboxMoveFlags
Mail-Recipient add:mayContain msExchMailboxMoveRemoteHostName
Mail-Recipient add:mayContain msExchMailboxMoveSourceMDBLink
Mail-Recipient add:mayContain msExchMailboxMoveStatus
Mail-Recipient add:mayContain msExchMailboxMoveTargetMDBLink
Mail-Recipient add:mayContain msExchMailboxPlanType
Mail-Recipient add:mayContain msExchModeratedByLink
Mail-Recipient add:mayContain msExchModeratedObjectsBL
Mail-Recipient add:mayContain msExchModerationFlags
Mail-Recipient add:mayContain msExchOWAPolicy
Mail-Recipient add:mayContain msExchParentPlanLink
Mail-Recipient add:mayContain msExchProvisioningFlags
Mail-Recipient add:mayContain msExchRBACPolicyLink
Mail-Recipient add:mayContain msExchRetentionComment
Mail-Recipient add:mayContain msExchRetentionURL
Mail-Recipient add:mayContain msExchRMSComputerAccountsLink
Mail-Recipient add:mayContain msExchSendAsAddresses
Mail-Recipient add:mayContain msExchSenderHintTranslations
Mail-Recipient add:mayContain msExchSharingPartnerIdentities
Mail-Recipient add:mayContain msExchSharingPolicyLink
Mail-Recipient add:mayContain msExchSignupAddresses
Mail-Recipient add:mayContain msExchSupervisionDLLink
Mail-Recipient add:mayContain msExchSupervisionOneOffLink
Mail-Recipient add:mayContain msExchSupervisionUserLink
Mail-Recipient add:mayContain msExchSyncAccountsPolicyDN
Mail-Recipient add:mayContain msExchTextMessagingState
Mail-Recipient add:mayContain msExchThrottlingPolicyDN
Mail-Recipient add:mayContain msExchTransportRecipientSettingsFlags
Mail-Recipient add:mayContain msExchUMAddresses
Mail-Recipient add:mayContain msExchUMCallingLineIDs
Mail-Recipient add:mayContain msExchWindowsLiveID
ms-Exch-Accepted-Domain add:mayContain msExchFedAcceptedDomainLink
ms-Exch-Active-Sync-Device add:mayContain msExchDeviceAccessControlRuleLink
ms-Exch-Active-Sync-Device add:mayContain msExchDeviceAccessState
ms-Exch-Active-Sync-Device add:mayContain msExchDeviceAccessStateReason
ms-Exch-Active-Sync-Device add:mayContain msExchDeviceEASVersion
ms-Exch-Active-Sync-Device add:mayContain msExchDeviceModel
ms-Exch-Address-Rewrite-Configuration add:auxiliaryClass msExchBaseClass
ms-Exch-Auto-Discover-Virtual-Directory add:auxiliaryClass msExchBaseClass
ms-Exch-Availability-Config add:auxiliaryClass msExchBaseClass
ms-Exch-Availability-Foreign-Connector-Virtual-Directory add:auxiliaryClass msExchBaseClass
ms-Exch-Base-Class add:mayContain msExchConfigurationUnitBL
ms-Exch-Base-Class add:mayContain msExchCU
ms-Exch-Base-Class add:mayContain msExchDirsyncID
ms-Exch-Base-Class add:mayContain msExchEdgeSyncCookies
ms-Exch-Base-Class add:mayContain msExchEdgeSyncSourceGuid
ms-Exch-Base-Class add:mayContain msExchOURoot
ms-Exch-Base-Class add:mayContain msExchProvisioningFlags
ms-Exch-Base-Class add:mayContain msExchRecipientValidatorCookies
ms-Exch-Base-Class add:mayContain msExchServerAssociationBL
ms-Exch-Base-Class add:mayContain msExchServerAssociationLink
ms-Exch-Base-Class add:mayContain msExchSetupStatus
ms-Exch-Base-Class add:mayContain msExchContentConversionSettings
ms-Exch-Base-Class add:mayContain msExchIMAP4Settings
ms-Exch-Base-Class add:mayContain msExchManagementSettings
ms-Exch-Base-Class add:mayContain msExchMobileSettings
ms-Exch-Base-Class add:mayContain msExchOWASettings
ms-Exch-Base-Class add:mayContain msExchPOP3Settings
ms-Exch-Base-Class add:mayContain msExchTransportInboundSettings
ms-Exch-Base-Class add:mayContain msExchTransportOutboundSettings
ms-Exch-Certificate-Information add:auxiliaryClass msExchBaseClass
ms-Exch-Client-Access-Array add:defaultSecurityDescriptor D:(A;;RP;;;AU)
ms-Exch-Client-Access-Array add:lDAPDisplayName msExchClientAccessArrayLegacy
ms-Exch-Configuration-Container add:mayContain msExchOrganizationsAddressBookRootsLink
ms-Exch-Configuration-Container add:mayContain msExchOrganizationsGlobalAddressListsLink
ms-Exch-Configuration-Container add:mayContain msExchOrganizationsTemplateRootsLink
ms-Exch-Configuration-Unit-Container add:mayContain msExchDirsyncIdSourceAttribute
ms-Exch-Configuration-Unit-Container add:mayContain msExchGalsyncDisableLiveIdOnRemove
ms-Exch-Configuration-Unit-Container add:mayContain msExchGalsyncFederatedTenantSourceAttribute
ms-Exch-Configuration-Unit-Container add:mayContain msExchGalsyncLastSyncRun
ms-Exch-Configuration-Unit-Container add:mayContain msExchGalsyncPasswordFilePath
ms-Exch-Configuration-Unit-Container add:mayContain msExchGalsyncProvisioningDomain
ms-Exch-Configuration-Unit-Container add:mayContain msExchGalsyncResetPasswordOnNextLogon
ms-Exch-Configuration-Unit-Container add:mayContain msExchGalsyncSchedule
ms-Exch-Configuration-Unit-Container add:mayContain msExchGalsyncSourceActiveDirectorySchemaVersion
ms-Exch-Configuration-Unit-Container add:mayContain msExchGalsyncWlidUseSmtpPrimary
ms-Exch-Configuration-Unit-Container add:mayContain msExchManagementSiteLink
ms-Exch-Configuration-Unit-Container add:mayContain msExchObjectCountQuota
ms-Exch-Configuration-Unit-Container add:mayContain msExchReseller
ms-Exch-Configuration-Unit-Container add:mayContain msExchServicePlan
ms-Exch-Department add:auxiliaryClass msExchBaseClass
ms-Exch-Department add:possSuperiors msExchDepartment
ms-Exch-DSN-Message add:mayContain msExchSystemMessageCustomizations
ms-Exch-ECP-Virtual-Directory add:auxiliaryClass msExchBaseClass
ms-Exch-Edge-Sync-Service-Config add:mayContain msExchEdgeSyncAdvancedConfiguration
ms-Exch-ELC-Folder add:mayContain msExchPolicyTagLink
ms-Exch-ELC-Folder add:mayContain msExchPolicyTagLinkBL
ms-Exch-Exchange-Assistance add:mayContain msExchOWALightFeedbackEnabled
ms-Exch-Exchange-Assistance add:mayContain msExchOWALightFeedbackURL
ms-Exch-Exchange-Assistance add:mayContain msExchOWALightHelpURL
ms-Exch-Exchange-Server add:mayContain msExchActivationConfig
ms-Exch-Exchange-Server add:mayContain msExchAssistantsMaintenanceSchedule
ms-Exch-Exchange-Server add:mayContain msExchCalendarRepairFlags
ms-Exch-Exchange-Server add:mayContain msExchCalendarRepairIntervalEndWindow
ms-Exch-Exchange-Server add:mayContain msExchCalendarRepairIntervalStartWindow
ms-Exch-Exchange-Server add:mayContain msExchCalendarRepairLogFileAgeLimit
ms-Exch-Exchange-Server add:mayContain msExchCalendarRepairLogFileSizeLimit
ms-Exch-Exchange-Server add:mayContain msExchCalendarRepairLogPath
ms-Exch-Exchange-Server add:mayContain msExchCalendarRepairMaxThreads
ms-Exch-Exchange-Server add:mayContain msExchCIMDBExclusionList
ms-Exch-Exchange-Server add:mayContain msExchContentAggregationFlags
ms-Exch-Exchange-Server add:mayContain msExchContentAggregationMaxAcceptedJobsPerProcessor
ms-Exch-Exchange-Server add:mayContain msExchContentAggregationMaxActiveJobsPerProcessor
ms-Exch-Exchange-Server add:mayContain msExchContentAggregationMaxDispatchers
ms-Exch-Exchange-Server add:mayContain msExchContentAggregationMaxDownloadItemsPerConnection
ms-Exch-Exchange-Server add:mayContain msExchContentAggregationMaxDownloadSizePerConnection
ms-Exch-Exchange-Server add:mayContain msExchContentAggregationMaxDownloadSizePerItem
ms-Exch-Exchange-Server add:mayContain msExchContentAggregationMaxNumberOfAttempts
ms-Exch-Exchange-Server add:mayContain msExchContentAggregationProxyServerURL
ms-Exch-Exchange-Server add:mayContain msExchContentAggregationRemoteConnectionTimeout
ms-Exch-Exchange-Server add:mayContain msExchContinuousReplicationMaxMemoryPerMDB
ms-Exch-Exchange-Server add:mayContain msExchCustomerFeedbackEnabled
ms-Exch-Exchange-Server add:mayContain msExchDeltaSyncClientCertificateThumbprint
ms-Exch-Exchange-Server add:mayContain msExchExchangeRPCServiceArrayBL
ms-Exch-Exchange-Server add:mayContain msExchHostServerBL
ms-Exch-Exchange-Server add:mayContain msExchHttpProtocolLogAgeQuotaInHours
ms-Exch-Exchange-Server add:mayContain msExchHTTPProtocolLogDirectorySizeQuota
ms-Exch-Exchange-Server add:mayContain msExchHTTPProtocolLogFilePath
ms-Exch-Exchange-Server add:mayContain msExchHTTPProtocolLogLoggingLevel
ms-Exch-Exchange-Server add:mayContain msExchHTTPProtocolLogPerFileSizeQuota
ms-Exch-Exchange-Server add:mayContain msExchInternetWebProxy
ms-Exch-Exchange-Server add:mayContain msExchMailTipsSettings
ms-Exch-Exchange-Server add:mayContain msExchMaxActiveMailboxDatabases
ms-Exch-Exchange-Server add:mayContain msExchMDBAvailabilityGroupLink
ms-Exch-Exchange-Server add:mayContain msExchSmtpMaxMessagesPerConnection
ms-Exch-Exchange-Server add:mayContain msExchSyncAccountsPoisonAccountThreshold
ms-Exch-Exchange-Server add:mayContain msExchSyncAccountsPoisonItemThreshold
ms-Exch-Exchange-Server add:mayContain msExchSyncAccountsSuccessivePoisonItemsThreshold
ms-Exch-Exchange-Server add:mayContain msExchSyncHubHealthLogAgeQuotaInHours
ms-Exch-Exchange-Server add:mayContain msExchSyncHubHealthLogDirectorySizeQuota
ms-Exch-Exchange-Server add:mayContain msExchSyncHubHealthLogFilePath
ms-Exch-Exchange-Server add:mayContain msExchSyncHubHealthLogPerFileSizeQuota
ms-Exch-Exchange-Server add:mayContain msExchSyncLogAgeQuotaInHours
ms-Exch-Exchange-Server add:mayContain msExchSyncLogDirectorySizeQuota
ms-Exch-Exchange-Server add:mayContain msExchSyncLogFilePath
ms-Exch-Exchange-Server add:mayContain msExchSyncLogLoggingLevel
ms-Exch-Exchange-Server add:mayContain msExchSyncLogPerFileSizeQuota
ms-Exch-Exchange-Server add:mayContain msExchSyncMailboxHealthLogAgeQuotaInHours
ms-Exch-Exchange-Server add:mayContain msExchSyncMailboxHealthLogDirectorySizeQuota
ms-Exch-Exchange-Server add:mayContain msExchSyncMailboxHealthLogFilePath
ms-Exch-Exchange-Server add:mayContain msExchSyncMailboxHealthLogPerFileSizeQuota
ms-Exch-Exchange-Server add:mayContain msExchSyncMailboxLogAgeQuotaInHours
ms-Exch-Exchange-Server add:mayContain msExchSyncMailboxLogDirectorySizeQuota
ms-Exch-Exchange-Server add:mayContain msExchSyncMailboxLogFilePath
ms-Exch-Exchange-Server add:mayContain msExchSyncMailboxLogLoggingLevel
ms-Exch-Exchange-Server add:mayContain msExchSyncMailboxLogPerFileSizeQuota
ms-Exch-Exchange-Server add:mayContain msExchTransportMaxRecipientStatisticsLogAge
ms-Exch-Exchange-Server add:mayContain msExchTransportMaxServerStatisticsLogAge
ms-Exch-Exchange-Server add:mayContain msExchTransportRecipientStatisticsDirectorySize
ms-Exch-Exchange-Server add:mayContain msExchTransportRecipientStatisticsFileSize
ms-Exch-Exchange-Server add:mayContain msExchTransportRecipientStatisticsPath
ms-Exch-Exchange-Server add:mayContain msExchTransportServerStatisticsDirectorySize
ms-Exch-Exchange-Server add:mayContain msExchTransportServerStatisticsFileSize
ms-Exch-Exchange-Server add:mayContain msExchTransportServerStatisticsPath
ms-Exch-Exchange-Server add:mayContain msExchUMCertificateThumbprint
ms-Exch-Exchange-Server add:mayContain msExchUMForwardingAddressTemplate
ms-Exch-Exchange-Server add:mayContain msExchUMLoadBalancerFQDN
ms-Exch-Exchange-Server add:mayContain msExchUMRedirectTarget
ms-Exch-Exchange-Server add:mayContain msExchUMSiteRedirectTarget
ms-Exch-Exchange-Server add:mayContain msExchUMStartupMode
ms-Exch-Exchange-Server add:mayContain msExchUMTcpListeningPort
ms-Exch-Exchange-Server add:mayContain msExchUMTlsListeningPort
ms-Exch-Fed-OrgId add:mayContain msExchImmutableId
ms-Exch-Fed-OrgId add:mayContain msExchSharingDefaultPolicyLink
ms-Exch-Fed-Sharing-Relationship add:mayContain msExchFedLocalRecipientAddress
ms-Exch-Fed-Sharing-Relationship add:mayContain msExchFedRemoteTargetAddress
ms-Exch-Fed-Trust add:mayContain msExchFedAdminKey
ms-Exch-Fed-Trust add:mayContain msExchFedOrgNextCertificate
ms-Exch-Fed-Trust add:mayContain msExchFedOrgNextPrivCertificate
ms-Exch-Fed-Trust add:mayContain msExchFedProvisioningProvider
ms-Exch-Generic-Policy-Container add:possSuperiors msExchOrganizationContainer
ms-Exch-IM-Recipient add:auxiliaryClass msExchBaseClass
ms-Exch-Mailbox-Recipient-Template add:auxiliaryClass msExchBaseClass
ms-Exch-Mail-Storage add:mayContain msExchAlternateMailboxes
ms-Exch-Mail-Storage add:mayContain msExchApprovalApplicationLink
ms-Exch-Mail-Storage add:mayContain msExchArchiveDatabaseLink
ms-Exch-Mail-Storage add:mayContain msExchArchiveGUID
ms-Exch-Mail-Storage add:mayContain msExchArchiveName
ms-Exch-Mail-Storage add:mayContain msExchArchiveQuota
ms-Exch-Mail-Storage add:mayContain msExchArchiveWarnQuota
ms-Exch-Mail-Storage add:mayContain msExchDelegateListLink
ms-Exch-Mail-Storage add:mayContain msExchDumpsterQuota
ms-Exch-Mail-Storage add:mayContain msExchDumpsterWarningQuota
ms-Exch-Mail-Storage add:mayContain msExchMailboxMoveFlags
ms-Exch-Mail-Storage add:mayContain msExchMailboxMoveRemoteHostName
ms-Exch-Mail-Storage add:mayContain msExchMailboxMoveStatus
ms-Exch-Mail-Storage add:mayContain msExchMailboxMoveTargetMDBLink
ms-Exch-Mail-Storage add:mayContain msExchMobileBlockedDeviceIDs
ms-Exch-Mail-Storage add:mayContain msExchPreviousHomeMDB
ms-Exch-Mail-Storage add:mayContain msExchUMAddresses
ms-Exch-Mail-Storage add:mayContain msExchUMAudioCodec2
ms-Exch-Mail-Storage add:mayContain msExchUMEnabledFlags2
ms-Exch-Mail-Storage add:mayContain msExchUMMailboxOVALanguage
ms-Exch-Mail-Storage add:mayContain msExchUMPhoneProvider
ms-Exch-MDB add:mayContain msExchDataMoveReplicationConstraint
ms-Exch-MDB add:mayContain msExchDumpsterQuota
ms-Exch-MDB add:mayContain msExchDumpsterWarningQuota
ms-Exch-MDB add:mayContain msExchESEParamBackgroundDatabaseMaintenance
ms-Exch-MDB add:mayContain msExchESEParamBaseName
ms-Exch-MDB add:mayContain msExchESEParamCachedClosedTables
ms-Exch-MDB add:mayContain msExchESEParamCachePriority
ms-Exch-MDB add:mayContain msExchESEParamCheckpointDepthMax
ms-Exch-MDB add:mayContain msExchESEParamCircularLog
ms-Exch-MDB add:mayContain msExchESEParamCopyLogFilePath
ms-Exch-MDB add:mayContain msExchESEParamCopySystemPath
ms-Exch-MDB add:mayContain msExchESEParamDbExtensionSize
ms-Exch-MDB add:mayContain msExchESEParamEventSource
ms-Exch-MDB add:mayContain msExchESEParamLogBuffers
ms-Exch-MDB add:mayContain msExchESEParamLogFilePath
ms-Exch-MDB add:mayContain msExchESEParamLogFileSize
ms-Exch-MDB add:mayContain msExchESEParamMaxCursors
ms-Exch-MDB add:mayContain msExchESEParamMaxOpenTables
ms-Exch-MDB add:mayContain msExchESEParamMaxSessions
ms-Exch-MDB add:mayContain msExchESEParamMaxTemporaryTables
ms-Exch-MDB add:mayContain msExchESEParamMaxVerPages
ms-Exch-MDB add:mayContain msExchESEParamPreferredVerPages
ms-Exch-MDB add:mayContain msExchESEParamReplayBackgroundDatabaseMaintenance
ms-Exch-MDB add:mayContain msExchESEParamReplayCachePriority
ms-Exch-MDB add:mayContain msExchESEParamReplayCheckpointDepthMax
ms-Exch-MDB add:mayContain msExchESEParamSystemPath
ms-Exch-MDB add:mayContain msExchESEParamTempPath
ms-Exch-MDB add:mayContain msExchESEParamZeroDatabaseDuringBackup
ms-Exch-MDB add:mayContain msExchMasterServerOrAvailabilityGroup
ms-Exch-MDB add:possSuperiors msExchMDBContainer
ms-Exch-MDB add:mayContain msExchRecovery
ms-Exch-MDB add:mayContain msExchRestore
ms-Exch-MDB-Availability-Group add:mayContain msExchAllowCrossSiteRPCClientAccess
ms-Exch-MDB-Availability-Group add:mayContain msExchAlternateFileShareWitness
ms-Exch-MDB-Availability-Group add:mayContain msExchAlternateFileShareWitnessDirectory
ms-Exch-MDB-Availability-Group add:mayContain msExchDatacenterActivationMode
ms-Exch-MDB-Availability-Group add:mayContain msExchFileShareWitness
ms-Exch-MDB-Availability-Group add:mayContain msExchFileShareWitnessDirectory
ms-Exch-MDB-Availability-Group add:mayContain msExchMDBAvailabilityGroupIPv4Addresses
ms-Exch-MDB-Availability-Group add:mayContain msExchMDBAvailabilityGroupName
ms-Exch-MDB-Availability-Group add:mayContain msExchMDBAvailabilityGroupNetworkSettings
ms-Exch-MDB-Availability-Group add:mayContain msExchStartedMailboxServers
ms-Exch-MDB-Availability-Group add:mayContain msExchStoppedMailboxServers
ms-Exch-MDB-Availability-Group add:mayContain msExchThirdPartySynchronousReplication
ms-Exch-MDB-Copy add:mayContain msExchHostServerName
ms-Exch-MDB-Copy add:mayContain msExchMDBCopyParentClass
ms-Exch-MDB-Copy add:mayContain msExchMDBName
ms-Exch-Message-Hygiene-Content-Filter-Config add:auxiliaryClass msExchBaseClass
ms-Exch-Message-Hygiene-IP-Allow-List-Config add:auxiliaryClass msExchBaseClass
ms-Exch-Message-Hygiene-IP-Allow-List-Provider-Config add:auxiliaryClass msExchBaseClass
ms-Exch-Message-Hygiene-IP-Block-List-Config add:auxiliaryClass msExchBaseClass
ms-Exch-Message-Hygiene-IP-Block-List-Provider-Config add:auxiliaryClass msExchBaseClass
ms-Exch-Message-Hygiene-Recipient-Filter-Config add:auxiliaryClass msExchBaseClass
ms-Exch-Message-Hygiene-Sender-Filter-Config add:auxiliaryClass msExchBaseClass
ms-Exch-Message-Hygiene-Sender-Filter-Config add:mayContain msExchMessageHygieneRecipientBlockedSenderAction
ms-Exch-Message-Hygiene-Sender-ID-Config add:auxiliaryClass msExchBaseClass
ms-Exch-Mobile-Mailbox-Policy add:auxiliaryClass msExchBaseClass
ms-Exch-Mobile-Mailbox-Policy add:mayContain msExchMobileOTAUpdateMode
ms-Exch-Mobile-Virtual-Directory add:auxiliaryClass msExchBaseClass
ms-Exch-Multi-Media-User add:auxiliaryClass msExchBaseClass
ms-Exch-OAB add:mayContain msExchOABANRProperties
ms-Exch-OAB add:mayContain msExchOABDetailsProperties
ms-Exch-OAB add:mayContain msExchOABLastNumberOfRecords
ms-Exch-OAB add:mayContain msExchOABLastTouchedTime
ms-Exch-OAB add:mayContain msExchOABMaxBinarySize
ms-Exch-OAB add:mayContain msExchOABMaxMVBinarySize
ms-Exch-OAB add:mayContain msExchOABMaxMVStringSize
ms-Exch-OAB add:mayContain msExchOABMaxStringSize
ms-Exch-OAB add:mayContain msExchOABPreferredSite
ms-Exch-OAB add:mayContain msExchOABTruncatedProperties
ms-Exch-OAB-Virtual-Directory add:auxiliaryClass msExchBaseClass
ms-Exch-Oma-Carrier add:auxiliaryClass msExchBaseClass
ms-Exch-Oma-Configuration-Container add:auxiliaryClass msExchBaseClass
ms-Exch-Oma-Connector add:auxiliaryClass msExchBaseClass
ms-Exch-Oma-Container add:auxiliaryClass msExchBaseClass
ms-Exch-Oma-Data-Source add:auxiliaryClass msExchBaseClass
ms-Exch-Oma-Delivery-Provider add:auxiliaryClass msExchBaseClass
ms-Exch-Oma-Device-Capability add:auxiliaryClass msExchBaseClass
ms-Exch-Oma-Device-Type add:auxiliaryClass msExchBaseClass
ms-Exch-Oma-User add:auxiliaryClass msExchBaseClass
ms-Exch-Organization-Container add:mayContain msExchAddressListPagingEnabled
ms-Exch-Organization-Container add:mayContain msExchCustomerFeedbackEnabled
ms-Exch-Organization-Container add:mayContain msExchCustomerFeedbackURL
ms-Exch-Organization-Container add:mayContain msExchIndustry
ms-Exch-Organization-Container add:mayContain msExchMailTipsLargeAudienceThreshold
ms-Exch-Organization-Container add:mayContain msExchMailTipsSettings
ms-Exch-Organization-Container add:mayContain msExchMaxSignupAddressesPerUser
ms-Exch-Organization-Container add:mayContain msExchOrganizationFlags
ms-Exch-Organization-Container add:mayContain msExchOrganizationSummary
ms-Exch-Organization-Container add:mayContain msExchSetupStatus
ms-Exch-Organization-Container add:mayContain msExchSetupTime
ms-Exch-Organization-Container add:mayContain msExchSignupAddressesEnabled
ms-Exch-OWA-Mailbox-Policy add:mayContain msExchOWAFileAccessControlOnPrivateComputers
ms-Exch-OWA-Mailbox-Policy add:mayContain msExchOWAIMProviderType
ms-Exch-OWA-Virtual-Directory add:auxiliaryClass msExchBaseClass
ms-Exch-OWA-Virtual-Directory add:mayContain msExchOWAIMProviderType
ms-Exch-Private-MDB add:mayContain msExchRecoveryPointObjectiveInterADSite
ms-Exch-Private-MDB add:mayContain msExchRecoveryPointObjectiveIntraADSite
ms-Exch-Protocol-Cfg-IMAP-Server add:mayContain msExchPOPIMAPExternalConnectionSettings
ms-Exch-Protocol-Cfg-IMAP-Server add:mayContain msExchPOPIMAPInternalConnectionSettings
ms-Exch-Protocol-Cfg-IMAP-Server add:mayContain msExchPopImapProtocolFlags
ms-Exch-Protocol-Cfg-POP-Server add:mayContain msExchPOPIMAPExternalConnectionSettings
ms-Exch-Protocol-Cfg-POP-Server add:mayContain msExchPOPIMAPInternalConnectionSettings
ms-Exch-Protocol-Cfg-POP-Server add:mayContain msExchPopImapProtocolFlags
ms-Exch-Pseudo-PF add:possSuperiors Container
ms-Exch-Pseudo-PF-Admin add:possSuperiors Container
ms-Exch-Role add:mayContain msExchMailboxPlanType
ms-Exch-Role add:possSuperiors msExchRole
ms-Exch-Role add:mayContain msExchRoleBL
ms-Exch-Role add:mayContain msExchRoleEntriesExt
ms-Exch-Role add:mayContain msExchRoleType
ms-Exch-Role add:mayContain msExchUserLink
ms-Exch-Routing-SMTP-Connector add:mayContain msExchSmtpMaxMessagesPerConnection
ms-Exch-Rpc-Http-Virtual-Directory add:auxiliaryClass msExchBaseClass
ms-Exch-Scope add:mayContain msExchConfigRestrictionBL
ms-Exch-Scope add:mayContain msExchDomainRestrictionBL
ms-Exch-Sender-Reputation add:auxiliaryClass msExchBaseClass
ms-Exch-Smtp-Connection-Turf-List-Rule add:auxiliaryClass msExchBaseClass
ms-Exch-Smtp-Receive-Connector add:mayContain msExchSmtpReceiveMaxAcknowledgementDelay
ms-Exch-Smtp-Receive-Connector add:mayContain msExchSMTPReceiveMessageRateSource
ms-Exch-Throttling-Policy add:mayContain msExchRCAThrottlingPolicyState
ms-Exch-Transport-Settings add:mayContain msExchOrgFederatedMailbox
ms-Exch-Transport-Settings add:mayContain msExchRelationTags
ms-Exch-Transport-Settings add:mayContain msExchSharingRelationshipForExternalOrganizationEmail
ms-Exch-Transport-Settings add:mayContain msExchSupervisionListMaxLength
ms-Exch-Transport-Settings add:mayContain msExchTransportExternalDefaultLanguage
ms-Exch-Transport-Settings add:mayContain msExchTransportExternalDSNReportingAuthority
ms-Exch-Transport-Settings add:mayContain msExchTransportExternalMaxDSNMessageAttachmentSize
ms-Exch-Transport-Settings add:mayContain msExchTransportExternalPostmasterAddress
ms-Exch-Transport-Settings add:mayContain msExchTransportInternalDefaultLanguage
ms-Exch-Transport-Settings add:mayContain msExchTransportInternalDSNReportingAuthority
ms-Exch-Transport-Settings add:mayContain msExchTransportInternalMaxDSNMessageAttachmentSize
ms-Exch-Transport-Settings add:mayContain msExchTransportSettingsAVFlags
ms-Exch-Transport-Settings add:mayContain msExchTransportShadowHeartbeatRetryCount
ms-Exch-Transport-Settings add:mayContain msExchTransportShadowHeartbeatTimeoutInterval
ms-Exch-Transport-Settings add:mayContain msExchTransportShadowMessageAutoDiscardInterval
ms-Exch-UM-Auto-Attendant add:mayContain msExchUMAutoAttendantPromptChangeKey
ms-Exch-UM-Auto-Attendant add:mayContain msExchUMBusinessLocation
ms-Exch-UM-Auto-Attendant add:mayContain msExchUMBusinessName
ms-Exch-UM-Auto-Attendant add:mayContain msExchUMDefaultMailbox
ms-Exch-UM-Auto-Attendant add:mayContain msExchUMWeekStartDay
ms-Exch-UM-Dial-Plan add:mayContain msExchAllowHeuristicADCallingLineIdResolution
ms-Exch-UM-Dial-Plan add:mayContain msExchUMAudioCodec2
ms-Exch-UM-Dial-Plan add:mayContain msExchUMCallingLineIDFormats
ms-Exch-UM-Dial-Plan add:mayContain msExchUMDefaultOutboundCallingLineID
ms-Exch-UM-Dial-Plan add:mayContain msExchUMDialPlanDialedNumbers
ms-Exch-UM-Dial-Plan add:mayContain msExchUMDialPlanFlags2
ms-Exch-UM-Dial-Plan add:mayContain msExchUMDialPlanPromptChangeKey
ms-Exch-UM-Dial-Plan add:mayContain msExchUMDialPlanSubscriberType
ms-Exch-UM-Dial-Plan add:mayContain msExchUMEquivalentDialPlanPhoneContexts
ms-Exch-UM-Dial-Plan add:mayContain msExchUMGlobalCallRoutingScheme
ms-Exch-UM-IP-Gateway add:mayContain msExchUMGlobalCallRoutingScheme
ms-Exch-UM-IP-Gateway add:mayContain msExchUMIPGatewayFlags2
ms-Exch-UM-Recipient-Template add:auxiliaryClass msExchBaseClass
ms-Exch-UM-Recipient-Template add:mayContain msExchUMEnabledFlags2
ms-Exch-UM-Recipient-Template add:mayContain msExchUMFaxServerURI
ms-Exch-UM-Recipient-Template add:mayContain msExchUMMissedCallText
ms-Exch-UM-Recipient-Template add:mayContain msExchUMProtectAuthenticatedVoiceMail
ms-Exch-UM-Recipient-Template add:mayContain msExchUMProtectedVoiceMailText
ms-Exch-UM-Recipient-Template add:mayContain msExchUMProtectUnauthenticatedVoiceMail
ms-Exch-UM-Recipient-Template add:mayContain msExchUMRequireProtectedPlayOnPhone
ms-Exch-UM-Recipient-Template add:mayContain msExchVoiceMailPreviewPartnerAddress
ms-Exch-UM-Recipient-Template add:mayContain msExchVoiceMailPreviewPartnerAssignedID
ms-Exch-UM-Recipient-Template add:mayContain msExchVoiceMailPreviewPartnerMaxDeliveryDelay
ms-Exch-UM-Recipient-Template add:mayContain msExchVoiceMailPreviewPartnerMaxMessageDuration
ms-Exch-UM-Virtual-Directory add:auxiliaryClass msExchBaseClass
ms-Exch-Web-Services-Virtual-Directory add:auxiliaryClass msExchBaseClass
Site add:mayContain msExchPartnerId
Top add:mayContain msExchArchiveDatabaseBL
Top add:mayContain msExchAvailabilityOrgWideAccountBL
Top add:mayContain msExchAvailabilityPerUserAccountBL
Top add:mayContain msExchDelegateListBL
Top add:mayContain msExchDeviceAccessControlRuleBL
Top add:mayContain msExchIntendedMailboxPlanBL
Top add:mayContain msExchMailboxMoveSourceMDBBL
Top add:mayContain msExchMailboxMoveTargetMDBBL
Top add:mayContain msExchMobileRemoteDocumentsAllowedServersBL
Top add:mayContain msExchMobileRemoteDocumentsBlockedServersBL
Top add:mayContain msExchMobileRemoteDocumentsInternalDomainSuffixListBL
Top add:mayContain msExchOrganizationsAddressBookRootsBL
Top add:mayContain msExchOrganizationsGlobalAddressListsBL
Top add:mayContain msExchOrganizationsTemplateRootsBL
Top add:mayContain msExchOWAAllowedFileTypesBL
Top add:mayContain msExchOWAAllowedMimeTypesBL
Top add:mayContain msExchOWABlockedFileTypesBL
Top add:mayContain msExchOWABlockedMIMETypesBL
Top add:mayContain msExchOWAForceSaveFileTypesBL
Top add:mayContain msExchOWAForceSaveMIMETypesBL
Top add:mayContain msExchOWARemoteDocumentsAllowedServersBL
Top add:mayContain msExchOWARemoteDocumentsBlockedServersBL
Top add:mayContain msExchOWARemoteDocumentsInternalDomainSuffixListBL
Top add:mayContain msExchOWATranscodingFileTypesBL
Top add:mayContain msExchOWATranscodingMimeTypesBL
Top add:mayContain msExchParentPlanBL
Top add:mayContain msExchRBACPolicyBL
Top add:mayContain msExchRMSComputerAccountsBL
Top add:mayContain msExchServerAssociationBL
Top add:mayContain msExchServerSiteBL
Top add:mayContain msExchSMTPReceiveDefaultAcceptedDomainBL
Top add:mayContain msExchSupervisionDLBL
Top add:mayContain msExchSupervisionOneOffBL
Top add:mayContain msExchSupervisionUserBL
Top add:mayContain msExchUserBL
Attributes Modified by Exchange 2007 SP2
The following table lists the attribute modifications that Exchange 2007 SP2 makes to the Active Directory schema.
Attribute Change Value
ms-Exch-Approval-Application-Link attributeSecurityGuid iYopH5jeuEe1zVcq1T0mfg==
ms-Exch-Auth-Orig mAPIID 36056
ms-Exch-Client-Access-Array defaultSecurityDescriptor D:(A;;RP;;;AU)
ms-Exch-Client-Access-Array lDAPDisplayName msExchClientAccessArrayLegacy
ms-Exch-Co-Managed-Objects-BL attributeSecurityGuid iYopH5jeuEe1zVcq1T0mfg==
ms-Exch-Config-Restriction-Link searchFlags 0
ms-Exch-Device-Model isMemberOfPartialAttributeSet TRUE
ms-Exch-DL-Mem-Reject-Perms mAPIID 36059
ms-Exch-DL-Mem-Submit-Perms mAPIID 36058
ms-Exch-Mailbox-Plan-Type attributeSecurityGuid iYopH5jeuEe1zVcq1T0mfg==
ms-Exch-Moderated-Objects-BL attributeSecurityGuid iYopH5jeuEe1zVcq1T0mfg==
ms-Exch-OU-Root searchFlags 9
ms-Exch-Parent-Plan-Link attributeSecurityGuid iYopH5jeuEe1zVcq1T0mfg==
ms-Exch-Provisioning-Flags attributeSecurityGuid iYopH5jeuEe1zVcq1T0mfg==
ms-Exch-Safe-Recipients-Hash rangeUpper 12000
ms-Exch-Safe-Senders-Hash rangeUpper 32000
ms-Exch-Schema-Version-Pt rangeUpper 14622
ms-Exch-Sender-Hint-Translations attributeSecurityGuid iYopH5jeuEe1zVcq1T0mfg==
ms-Exch-Server-Association-BL attributeSecurityGuid F6SzsVXskUGzJ7cuM+OK8g==
ms-Exch-Server-Association-Link attributeSecurityGuid F6SzsVXskUGzJ7cuM+OK8g==
ms-Exch-Setup-Time delete rangeUpper
ms-Exch-Sharing-Admin-Key lDAPDisplayName msExchFedAdminKey
ms-Exch-Sharing-Org-Next-Certificate lDAPDisplayName msExchFedOrgNextCertificate
ms-Exch-Sharing-Org-Next-Priv-Certificate lDAPDisplayName msExchFedOrgNextPrivCertificate
ms-Exch-Sharing-Policy-Link attributeSecurityGuid F6SzsVXskUGzJ7cuM+OK8g==
ms-Exch-Sharing-Policy-Link isMemberOfPartialAttributeSet TRUE
ms-Exch-Sharing-Provisioning-Provider lDAPDisplayName msExchFedProvisioningProvider
ms-Exch-Sharing-Provisioning-Provider rangeUpper 2048
ms-Exch-Sync-Accounts-Policy-DN attributeSecurityGuid iYopH5jeuEe1zVcq1T0mfg==
ms-Exch-Throttling-Policy-DN attributeSecurityGuid iYopH5jeuEe1zVcq1T0mfg==
ms-Exch-Throttling-Policy-DN searchFlags 1
ms-Exch-Transport-Recipient-Settings-Flags attributeSecurityGuid F6SzsVXskUGzJ7cuM+OK8g==
ms-Exch-UM-Auto-Attendant-Dialed-Numbers searchFlags 1
ms-Exch-UM-Enabled-Text rangeUpper 1024
ms-Exch-UM-Fax-Message-Text rangeUpper 1024
ms-Exch-UM-IP-Gateway-Address rangeUpper 2048
ms-Exch-UM-IP-Gateway-Address searchFlags 1
ms-Exch-UM-Load-Balancer-FQDN attributeSecurityGuid iYopH5jeuEe1zVcq1T0mfg==
ms-Exch-UM-Max-Recording-Duration rangeLower 1
ms-Exch-UM-Phone-Provider attributeSecurityGuid F6SzsVXskUGzJ7cuM+OK8g==
ms-Exch-UM-Phone-Provider isMemberOfPartialAttributeSet TRUE
ms-Exch-UM-Reset-PIN-Text rangeUpper 1024
ms-Exch-UM-Spoken-Name mapiId 36034
ms-Exch-UM-Voice-Mail-Text rangeUpper 1024
ms-Exch-Unauth-Orig mAPIID 36057
ms-Exch-User-BL attributeSecurityGuid iYopH5jeuEe1zVcq1T0mfg==
ms-Exch-User-Link searchFlags 0
ms-Exch-Version searchFlags 8
ms-Exch-Windows-Live-ID attributeSecurityGuid iYopH5jeuEe1zVcq1T0mfg==
ms-Exch-Windows-Live-ID searchFlags 9

Exchange Server 2010 Faq's

2010-01-03T03:37:00.002+05:30

In Exchange Server 2010, The service called "Microsoft Exchange RPC Client" is responsible to establish a RPC connection between outlook and Client Access Server. If this service is down or stopped, users will not be able to connect Exchange Server using RPC connection.

Exchange Server 2003 database size limits

2010-01-03T03:27:00.000+05:30

Please follow below steps,

1.On the computer that is running Exchange Server, open a registry editor such as Regedit.exe or RegEdt32.exe.

2.Navigate to: HKLM\System\CurrentControlSet\Services\MSExchangeIS\\Private-

3.Right-click MailboxStoreGUID, point to New, and then click DWORD Value.

4.For the new value name, type Database Size Limit in Gb.

5.Double-click Database Size Limit in Gb. In Value data, type an appropriate value for maximum database size in GB. Click OK.

6.Right-click MailboxStoreGUID, point to New, and then click DWORD Value.

7.For the new value name, type Database Size Buffer in Percentage.

8.Double-click Database Size Buffer in Percentage. In Value data, type a value between 1 and 100 to specify when you want events to be logged to warn you that you are nearing the maximum size for a database. Click OK.

Note:
The default value of 10 will cause warning events to be logged when you have 10 percent capacity left before you reach the maximum size for that database.
9.Right-click MailboxStoreGUID, point to New, and then click DWORD Value.

10.For the new name, type Database Size Check Start Time in Hours From Midnight.

11.Double-click Database Size Check Start Time in Hours From Midnight. In Value data, type a value between 0 and 23 to specify when you want Exchange to look at the database size. Click OK.

Note:
The default value of 5 causes Exchange Server to look at the database size at 5 hours after midnight (05:00).
12.Close the registry editor.

Mastering Powershell

2009-12-22T23:10:00.001+05:30

Mastering PowerShell, a Free eBook from a PowerShell MVP

This is taken From muc-ug.org.in.

http://muc-ug.org.in/index.php/news/91-mastering-powershell-a-free-ebook-from-a-powershell-mvp.html

Thanks to Amit Tank.

2009-11-22T14:21:00.001+05:30

Microsoft have introduced new feature called Email-Moderation with exchange server 2010 immigration additionally delivery restriction came with exchange 2007.
Using Moderated Transport feature in Exchange 2010 administrator have capability to push emails for moderated approval process if the destination moderated user. You would be able to configure email moderation for any type of recipient type.
Components of Moderated Transport
• Categorizer – Categorizer is responsible to initiate approval process.
• Store Driver – The store driver process the email messages that categorizer marks for approval process.
• Information Assistant – The information Assistant monitors the Arbitration mailbox and its resubmit if any messages approved or delete any rejected messages.
• Arbitration Mailbox – The Arbitration Mailbox store all email messages for approval process.
Configure a Moderated Recipient
Using Exchange Management Console
Required permission to configuration Moderated Recipient.
• Organization Management
• Recipient Management
• My Distribution Groups
Scenario
Administrator wants to enable Moderation for “Company Users” distribution group and nominate Mike and Vonod as Moderators, then notify only internal senders if users messages were rejected, not for the external recipients.
1. In the EMC console tree, click Recipient Configuration then click distribution group. See figure 1

Figure 1
2. Click the Company Users distribution group in the result pane and select properties .Then select Mail Flow Settings tab. See figure 2

Figure 2
3. Select Message Moderation and click properties. See figure 3

Figure 3
4. Select the Messages sent to this group have to be approved by a moderator check box.then click add to add Moderated Recipients and select Mike and Vinod.then click ok. See figure 4

Figure 4
5.Click the Notify senders in your organization only when their message is not approved option.Then click OK twice. See figure 5.

Figure 5
Test E-mail moderation.
OK E-mail moderation configuration part is done. Now we want to test email Moderation is working or not.
Send email to Company Users distribution group. Immediately appeared mail tip and it was mentioned Company Users distribution group is Moderated and it might reject or delayed. See figure 6.

Figure 6
Check Mikes mailbox to see whether email has come for approval. See figure 7

Exchange Management Shell Quick Reference for Exchange 2010

2009-11-22T13:44:00.003+05:30

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=6a516cc0-c337-40c5-adda-3e8f023870e1#tm

Exchange Management Shell Quick Reference for Exchange 2010

2009-11-22T13:44:00.001+05:30

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=6a516cc0-c337-40c5-adda-3e8f023870e1#tm

Exchange 2010 Professional Plus Available for Download

2009-11-19T22:59:00.001+05:30

Below is the link for download both x86 and x64 bit verions.

http://www.microsoft.com/office/2010/en/download-office-professional-plus/default.aspx

Set a Dedicated Domain controller for Exchange Server

2009-11-17T08:43:00.000+05:30

Our goal is simple we will dedicate GC for exchange server in enterprise environment. Pointing DS access to the DC's is not good enough. Those of you experts know already the meaning of Multi Master Replication model with AD 2000 and 2003 and how it works.
Follow the simple steps below to get to work done.
Step by Step
Prepare a DC/GC to be used by Exchange servers only
• Open local GPO
• Local computer Policy
• Administrative templates
• System
• Net logon
• DC Located DSN records
• Priority Set in the DC locator DNs SRV Records
• Double click on it
• Enabled
• Set priority anything greater than "0" ( I set all DC's to 200 in this example)
• Save the GPO and give a data and some logical name.
Go to Event log and you will see this DC is no longer authenticating users, and being used by DSAccess only
SRV resource records
Specifies the Priority field in the SRV resource records registered by domain controllers (DC) to which this setting is applied. These DNS records are dynamically registered by the Net Logon service and are used to locate the DC.
The Priority field in the SRV record sets the preference for target hosts (specified in the SRV record's Target field). DNS clients that query for SRV resource records attempt to contact the first reachable host with the lowest priority number listed.
To specify the Priority in the DC Locator DNS SRV resource records, click Enabled, and then enter a value. The range of values is 0 to 65535. If this setting is not configured, it is not applied to any DCs, and DCs use their local configuration.

Move-HubTransport Database

2009-11-17T08:39:00.003+05:30

Use Move-TransportDatabase.ps1 Script located in %exchangeserver%\scripts folder

Database:
Move-TransportDatabase.ps1 -QueueDatabasePath:

Example:
Move-TransportDatabase.ps1 -QueueDatabasePath: D:\Exchange\Transport Queue\Data

Log:
Move-TransportDatabase.ps1 -QueueDatabaseLoggingPath:

Example:
Move-TransportDatabase.ps1 -QueueDatabaseLoggingPath: "D:\Exchange\Transport Queue\Log"

Exchange mailbox client version scan from EMS

2009-11-07T00:21:00.003+05:30

To check outlook client version of a particular mailbox user from EMS is easy now. we can run a EMS command to get the required details. such as

Mailbox User Client IP address, Machine Name, version of outlook used by the mailbox owner etc. Below is the command

Get-LogonStatistics fl

Important and Easiest steps to Recover Exchange in case of failure because of Drive Space issue

2009-07-28T00:55:00.001+05:30

When our Exchange Transaction Logs drive run out of space then first thing we think about movement of committed log files to another drive where server has space so here is the way…!!

Note: If we move committed logs then we cannot perform incremental backup and need to take full backup.

To perform this operation we need Microsoft Exchange Troubleshooting Assistance tool.

Download: http://www.microsoft.com/downloads/details.aspx?familyid=4bdc1d6b-de34-4f1c-aeba-fed1256caf9a&displaylang=en

It is inbuilt tools in Exchange 2007 and available in Toolbox “Database Recovery Management”.

We need to install it manually in Exchange 2003.

After installation we can find it under Programs -> Microsoft Exchange -> Troubleshooting Assistant

Select Check for updates on startup (recommended) and click on Check for update now.

If no updates are available then Select Go to Welcome Screen.

Click on Select a Task.

Select Database Recovery Management.

Note: As discussed earlier, in Exchange 2007 we can directly select Database Recovery Management in Toolbox.

Give identifying label for this activity & Server name.

Click on Show Advance logon options if we want to give alternate credential.

Click Next.

It retrieves Exchange Server Information from Active Directory.

Click on Analyze log drive space.

It gives us Transaction log Drive Statistics.

We can see some important fact about our server…

Available log disk space.
Logs (GB).
Average daily log generation rate.
Estimated days to run before exhausting current log drive space.

Click on Select a storage group for log move.

Select the storage group(s) to move log files.

Click on Confirm the log move options.

We can see below things…

Log File Name for Current Checkpoint
Number of Removable Logs
Recoverable Space (GB)

Select a Path where we want to move log files.

Click Perform Move Log Action.

It starts copying and removing logs operation.

Once it is finished, we can see the message, Successfully Copied the log files to new location and removed the logs.

Click on Go back to task center & Close Microsoft Exchange Troubleshooting Assistant.

Note : Make sure that we take backup after completion of this.

Hope this helps us…!!! Put our comments…!!!

This Post Originally Belongs to Amit Tank... Thanks Amit.

Important questions on windows server and exchange - Part 3

2009-07-24T11:40:00.001+05:30

Q11.Which two operations master roles should be available when new security principals are being created and named?

Domain naming master and the relative ID master

Q12. What are different types of groups?

■ Security groups Security groups are used to group domain users into a single administrative unit. Security groups can be assigned permissions and can also be used as e-mail distribution lists. Users placed into a group inherit the permissions assigned to the group for as long as they remain members of that group. Windows itself uses only security groups.

■ Distribution groups these are used for nonsecurity purposes by applications other than Windows. One of the primary uses is within an e-mail

As with user accounts, there are both local and domain-level groups. Local groups are stored in a local computer’s security database and are intended to control resource access on that computer. Domain groups are stored in Active Directory and let you gather users and control resource access in a domain and on domain controllers.

Q13. What is a group scope and what are the different types of group scopes?

Group scopes determine where in the Active Directory forest a group is accessible and what objects can be placed into the group. Windows Server 2003 includes three group scopes: global, domain local, and universal.

■ Global groups are used to gather users that have similar permissions requirements. Global groups have the following characteristics:

1. Global groups can contain user and computer accounts only from the domain in which the global group is created.

2. When the domain functional level is set to Windows 2000 native or Windows Server 2003 (i.e., the domain contains only Windows 2000 or 2003 servers), global groups can also contain other global groups from the local domain.

3. Global groups can be assigned permissions or be added to local groups in any domain in a forest.

■ Domain local groups exist on domain controllers and are used to control access to resources located on domain controllers in the local domain (for member servers and workstations, you use local groups on those systems instead). Domain local groups share the following characteristics:

1. Domain local groups can contain users and global groups from any domain in a forest no matter what functional level is enabled.

2. When the domain functional level is set to Windows 2000 native or Windows Server 2003, domain local groups can also contain other domain local groups and universal groups.

■ Universal groups are normally used to assign permissions to related resources in multiple domains. Universal groups share the following characteristics:

1. Universal groups are available only when the forest functional level is set to Windows 2000 native or Windows Server 2003.

2. Universal groups exist outside the boundaries of any particular domain and are managed by Global Catalog servers.

3. Universal groups are used to assign permissions to related resources in multiple domains.

4. Universal groups can contain users, global groups, and other universal groups from any domain in a forest.

5. You can grant permissions for a universal group to any resource in any domain.

Q14. What are the items that groups of different scopes can contain in mixed and native mode domains?

Q15. What is group nesting?

Placing of one group in another is called as group nesting

For example, suppose you had junior level administrators in four different geographic locations, as shown in Figure 4-10. You could create a separate group for each location (named something like Dallas Junior

Admins). Then, you could create a single group named Junior Admins and make each of the location-based groups a member of the main group. This approach would allow you to set permissions on a single group and have those permissions flow down to the members, yet still be able to subdivide the junior administrators by location.

Q16. How many characters does a group name contain?

Q17. Is site part of the Active Directory namespace?

NO: - When a user browses the logical namespace, computers and users are grouped into domains and OUs without reference to sites. However, site names are used in the Domain Name System (DNS) records, so sites must be given valid DNS names.

Q18. What is DFS?

The Distributed File System is used to build a hierarchical view of multiple file servers and shares on the network. Instead of having to think of a specific machine name for each set of files, the user will only have to remember one name; which will be the 'key' to a list of shares found on multiple servers on the network. Think of it as the home of all file shares with links that point to one or more servers that actually host those shares.

DFS has the capability of routing a client to the closest available file server by using Active Directory site metrics. It can also be installed on a cluster for even better performance and reliability.

Understanding the DFS Terminology
it is important to understand the new concepts that are part of DFS. Below is a definition of each of them.

Dfs root: You can think of this as a share that is visible on the network, and in this share you can have additional files and folders.

Dfs link: A link is another share somewhere on the network that goes under the root. When a user opens this link they will be redirected to a shared folder.

Dfs target (or replica): This can be referred to as either a root or a link. If you have two identical shares, normally stored on different servers, you can group them together as Dfs Targets under the same link.

The image below shows the actual folder structure of what the user sees when using DFS and load balancing.

Figure 1: The actual folder structure of DFS and load balancing

Windows 2003 offers a revamped version of the Distributed File System found in Windows 2000, which has been improved to better performance and add additional fault tolerance, load balancing and reduced use of network bandwidth. It also comes with a powerful set of command-line scripting tools which can be used to make administrative backup and restoration tasks of the DFS namespaces easier. The client windows operating system consists of a DFS client who provides additional features as well as caching.

Q19. What are the types of replication in DFS?

There are two types of replication:

* Automatic - which is only available for Domain DFS
* Manual - which is available for stand alone, DFS and requires all files to be replicated manually.

Q20. Which service is responsible for replicating files in SYSVOL folder?

File Replication Service (FRS)

Important questions on Windows server and exchange

2009-07-24T11:39:00.001+05:30

Q1. What does the physical structure of active directory contain?

Physical structures include domain controllers and sites.

Q2.What is nesting?

The creation of an OU inside another OU.

IMP: - once you go beyond about 12 OUs deep in a nesting structure, you start running into significant performance issues.

Q3. What is trust relationship and how many types of trust relationship is there in exchange 2003?

Since domains represent security boundaries, special mechanisms called trust relationships allow objects in one domain (called the trusted domain) to access resources in another domain (called the trusting domain).

Windows Server 2003 supports six types of trust relationships:

■ Parent and child trusts

■ Tree-root trusts

■ External trusts

■ Shortcut trusts

■ Realm trusts

■ Forest trusts

Q4. What is a site?

A Windows Server 2003 site is a group of domain controllers that exist on one or more IP subnets (see Lesson 3 for more on this) and are connected by a fast, reliable network connection. Fast means connections of at least 1Mbps. In other words, a site usually follows the boundaries of a local area network (LAN). If different LANs on the network are connected by a wide area network (WAN), you’ll likely create one site for each LAN.

Q5. What is the use of site?

Sites are primarily used to control replication traffic. Domain controllers within a site are pretty much free to replicate changes to the Active Directory database whenever changes are made. Domain controllers in different sites compress the replication traffic and operate based on a defined schedule, both of which are intended to cut down on network traffic.

More specifically, sites are used to control the following:

■ Workstation logon traffic

■ Replication traffic

■ Distributed File System (DFS)

Distributed File System (DFS) is a server component that provides a unified naming convention for folders and files stored on different servers on a network. DFS lets you create a single logical hierarchy for folders and files that is consistent on a network, regardless of where on the network those items are actually stored. Files represented in the DFS might be stored in multiple locations on the network, so it makes sense that Active Directory should be able to direct users to the closest physical location of the data they need. To this end, DFS uses site information to direct a client to the server that is hosting the requested data within the site. If DFS does not find a copy of the data within the same site as the client, DFS uses the site information in Active Directory to determine which file server that has DFS shared data is closest to the client.

■ File Replication Service (FRS)

Every domain controller has a built-in collection of folders named SYSVOL (for System Volume). The SYSVOL folders provide a default Active Directory location for files that must be replicated throughout a domain. You can use SYSVOL to replicate Group Policy Objects, startup and shutdown scripts, and logon and logoff scripts. A Windows Server 2003 service named File Replication Service (FRS) is responsible for replicating files in the SYSVOL folders between domain controllers. FRS uses site boundaries to govern the replication of items in the SYSVOL folders.

Q6. What are the objects a site contains?

Sites contain only two types of objects. The first type is the domain controllers contained in the site. The second type of object is the site links configured to connect the site to other sites.

Q7.What is a Site link?

Within a site, replication happens automatically. For replication to occur between sites, you must establish a link between the sites. There are two components to this link: the actual physical connection between the sites (usually a WAN link) and a site link object. The site link object is created within Active Directory and determines the protocol used for transferring replication traffic (Internet Protocol [IP] or Simple Mail Transfer Protocol [SMTP]). The site link object also governs when replication is scheduled to occur.

Q8. Explain Replication in Active directory?

Windows Server 2003 uses a replication model called multimaster replication, in which all replicas of the Active Directory database are considered equal masters. You can make changes to the database on any domain controller and the changes will be replicated to other domain controllers in the domain.

Domain controllers in the same site replicate on the basis of notification. When changes are made on a domain controller, it notifies its replication partners (the other domain controllers in the site); the partners then request the changes and replication occurs. Because of the high-speed, low-cost connections assumed within a site, replication occurs as needed rather than according to a schedule.

You should create additional sites when you need to control how replication traffic occurs over slower WAN links. For example, suppose you have a number of domain controllers on your main LAN and a few domain controllers on a LAN at a branch location. Those two LANs are connected to one another with a slow (256K) WAN link. You would want replication traffic to occur as needed between the domain controllers on each LAN, but you would want to control traffic across the WAN link to prevent it from affecting higher priority network traffic. To address this situation, you would set up two sites— one site that contained all the domain controllers on the main LAN and one site that contained all the domain controllers on the remote LAN.

Q9. What is LDAP?

LDAP, Lightweight Directory Access Protocol, is an Internet protocol that email and other programs use to look up information from a server.

An LDAP-aware directory service (such as Active Directory) indexes all the attributes of all the objects stored in the directory and publishes them. LDAP-aware clients can query the server in a wide variety of ways.

Q10. What is multimaster replication?

Active Directory follows the multimaster replication which every replica of the Active Directory partition held on every domain is considered an equal master. Updates can be made to objects on any domain controller, and those updates are then replicated to other domain controllers.

Important questions and answers on Windows Server and Exchange

2009-07-24T11:33:00.002+05:30

Q21. What all can a site topology owner do?

The site topology owner is the name given to the administrator (or administrators) that oversee the site

Topology. The owner is responsible for making any necessary changes to the site as the physical network grows and changes. The site topology owner’s responsibilities include:

■ making changes to the site topology based on changes to the physical network topology.

■ tracking subnetting information for the network. This includes IP addresses, subnet masks, and the locations of the subnets.

■ monitoring network connectivity and setting the costs for links between sites.

Exchange 2007 SP1 replication behaviour with Windows server 2008 Clusters

2009-07-16T12:49:00.004+05:30

If you are reading this blog post I also suggest you read the the following white paper: "White Paper: Continuous Replication Deep Dive" which can be found at http://technet.microsoft.com/en-us/library/cc535020.aspx. This white paper does a fantastic job of covering the operations of the replication service.

Windows 2008 and Windows 2008 clustering introduce changes to the operating system which effect the operation of the Exchange Replication Service. Specifically there are two items of interest. The first is the ability to programmatically create a share to a specific host and the integration of file sharing operations with the cluster service when shared storage is used. (These same concepts also effect Exchange Offline Address List Generation, see Dave Goldman's blog for more info on these topics - http://blogs.msdn.com/dgoldman/archive/2008/12/11/fix-for-oab-generation-failing-on-ccr-and-scc-clusters.aspx.).

Lets take a look at how this effects Exchange 2007 SP1 Cluster Continuous Replication (CCR) clusters.

With Exchange 2007 SP1 CCR clusters there are no shared storage devices. File shares that are created, which are necessary for the replication service to replicate log files, are created on the host.

In Windows 2003 clustering, when a file share was created on a local node it was accessible by any name the resolved to that node. (If the name did not exist as either the node name, or a virtual network name in cluster, it would be necessary to disable strict name checking in order for the host to accept the request - http://support.microsoft.com/kb/281308 - this could possibly happen when using a host file to map a different name or using a CNAME DNS record to map to a host). For example, if I create a share on the host named Files, I could access the share at file://nodename/Files or file://cmsname/Files if the CMS (clustered mailbox server) was active on that node. In addition, if I used enable-continuousreplicationhostnames to create replication networks to replicate logs on an alternate network interface, I could also access the share at file://continuousreplicationhostname/Files

In the below example on Windows 2003, on the root of C, I created a share called Files and placed two text files in the share. There is a cluster network name that runs on the node where I created the share. From another machine in the environment, you can see that the share can be accessed at both file://nodename/ and file://cmsname/.

In Windows 2008, if I created the same share on the local node, it would only be accessible by file://nodename/Files. If attempting to access the share at file://cmsname/Files an error is displayed. (In this example node name is 2008-Node1 and CMSName is 2008-MBX3).

On Windows 2008, in server manager-> roles -> file services -> share and storage management, the Files share appears in the list of available shares.

If you get the properties of the share, you can see that it's specifically scoped to the Node Name (review the share path).

In a default configuration for CCR, scoped shares do not have any impact how the replication service replicates log files. The main impact comes when using continuous replication host names. In order for this to function, the replication service has to specifically create the share and have it scoped at both the NodeName and CMSName.

When using continuous replication hostnames, if you review the Share and Storage Management console, you will see two (or more depending on how many continuous replication host names exist) instances of the shares for each storage group.

Each instance of the share uses the same share name and the same physical path on storage. The difference is in the properties of each of these shares. When reviewing the properties, you will see one share specifically scoped to the node name, the other share specifically scoped to the continuous replication host name. (In this example 2008-MBX3-ReplC is the continuous replication host name.)

*Example of share scoped to continuous replication host name.

*Example of share scoped to node name.

By creating scoped shares at both endpoints, the replication service is able to access logs using both the NodeName and ContinuousReplicationHostName.

Lets take a look at how this effects Exchange 2007 SP1 Single Copy Clusters (SCC).

With Exchange 2007 SP1 SCC all databases and log files reside on a shared storage device. This requires that the shares necessary for creation be created against folders that exist on shared volumes. In this instance, there is no local replication activity or replication between nodes of the cluster. The replication service is only used against a single copy cluster when the SCC cluster is acting as a standby continuous replication source.

With Windows 2003 the replication service would create the shares necessary for SCR replication to occur. These shares, by default, were available at both file://nodename/ and file://cmsname/. There was no tight integration between the sharing functions of the operating system and cluster where shared storage was concerned. (Remember that an SCR target replicates log files from an SCC SCR source at file://cmsname/StorageGroupGuid$).

In Windows 2008 cluster is more aware of shares created on shared storage. By default, when a share is created on a shared disk, the cluster service will automatically intercept that share and scope it only to the virtual name associated with the client access point that owns the disk. This happens when manually creating a share through the operating system or programmatically creating a share (regardless of the endpoint passed into the sharing function). Let's take a look at an example.

In this example I created a empty service or application. In the empty service or application, I created a new client access point. I created a new shared disk on my SAN, added the disk to available storage, and then moved it to the client access point. In my case the disk is the H volume (Cluster Disk 9).

On the node that owns the Empty-Group with the the client access point and disk, through the operating system, I created a folder on the H drive and shared it. After completing the sharing wizard, you can see the share is immediately scoped to the name used in the client access point. In this example my client access point name is EMPTY-GROUP, so the share is available at file://empty-group/Files.

When reviewing share and storage management, you will see the share. It's properties also reference the share created to the client access point name.

In additional to the above information, in the cluster administrator, in the service or application that I created, a new FileServer resource is created. The file server resource is dependant on the physical disk that the share resides on, and the client access point name. The share that was created is also viewable in cluster administrator.

How is this handled programmatically?

A common method to create shares was the Share_Info_502 Structure. (http://msdn.microsoft.com/en-us/library/bb525410(VS.85).aspx) When this structure is used on Windows 2008 cluster, the share is automatically created against the node name (as long as the shared folder does not reside on a shared disk). If the folder that is being shared resides on shared disk, cluster automatically intercepts this sharing requests and scopes the share to the client access point that owns the shared disk resource.

A new sharing method was introduced with Windows 2008. This is the Share_Info_503 structure. (http://msdn.microsoft.com/en-us/library/cc462916(VS.85).aspx) This structure allows the programmer to specify the server name as part of the sharing call. Here is an excerpt from the MSDN page.
shi503_servername
A pointer to a string that specifies the DNS or NetBIOS name of the remote server on which the shared resource resides. A value of "*" indicates no configured server name.
When using this sharing structure, the programmer can specify to create the share against the node name, the cms name (in the Exchange case), or both. The only exception is when the folder to be shared resides on a shared disk. Cluster will intercept this sharing call and allow the share to only be scoped to the client access point that owns the physical disk resource.

*Note: When creating shares on a shared storage device in Windows 2008 you should install KB 955733.

Improve CCR with SCR cluster log shipping perfomance

2009-07-16T12:45:00.002+05:30

Many customers have requested instructions on how to enable standby continuous replication to use an alternate network interface. By design standby continuous replication always uses the “public” interface to ship logs and seed the database.
Over the past few weeks we have been working with the Exchange product group on a “supported” method to allow standby continuous replication to use an alternate network interface. This blog will detail how to implement these steps and what effects it has on the overall solution.
First if you are reading this post you should review the replication service deep dive whitepaper located at http://technet.microsoft.com/en-us/library/cc535020.aspx (“White Paper: Continuous Replication Deep Dive"). When reviewing this whitepaper it is important to pay attention to what sources are involved in replication when using standby continuous replication. For example:
When the source is a standalone mailbox server, logs are replicated by connecting to shares mapped to the server name.
When the source is a cluster continuous replication server, logs are replicated by connecting to shares mapped to the ACTIVE node server name.
When the source is a single copy cluster, logs are replicated by connecting to shares mapped to the clustered mailbox server name.
Keeping these parameters in mind will help you understand how the following changes will allow for standby continuous replication to use an alternate network interface.
The steps to implement this vary little by operating system. Windows 2008 though does introduce some changes to the way file shares are handled. Please review this blog for information on how share scoping in Windows 2008 effects the operations of the replication service. (http://blogs.technet.com/timmcmic/archive/2008/12/23/exchange-replication-service-exchange-2007-sp1-and-windows-2008-clusters.aspx)
The following instructions are based on Exchange 2007 SP1 with RU7. All customers implementing these instructions are encouraged to do so on Exchange 2007 SP1 RU7.

Replication behavior when using standby continuous replication over an alternate network interface.
When the instructions are implemented as documented, all network traffic from the SCR target to the SCR source is first routed through the private interface. This can be verified with netmon by reviewing SMB (Windows 2003) or SMBv2 (Windows 2008) traffic.
It is important to note that these instructions only effect the LOG SHIPPING functionality of SCR. Other functions such as update-storagegroupcopy will only occur using the public interface. This requires that both the source and target have the ability to communicate over both the public and private interfaces. Planning for network sizing should take into account that re-seeding operations using update-storagegroupcopy must occur over the public interface.
Unlike continuous replication host names in CCR there is no automatic failover between interfaces. Should the private interface serving log shipping be unavailable for any reason, log shipping will fail. With this in mind appropriate monitoring of log copy operations is necessary to ensure replication is functioning. In the event that the network link serving replication is not available, the host file should be removed and replication resumed over the public interface. As mentioned earlier your network design considerations should take into account the need to communicate over both the public and private interfaces as well as the potential need to perform log shipping operations over the public interface.
For the solution to be fully supported network connectivity must be available between the source and target on both the private and public interfaces. All replication operations must be able to function on both interfaces.
When engaging product support services for assistance with replication when these steps are used you may be requested to remove the host file and verify that log shipping works as originally designed with no modifications.
Behavior of commandlets used for implementing / managing standby continuous replication when replication is enabled to use an alternate interface.
Get-storagegroupcopystatus: No issues noted.
Enable-storagegroupcopy: No issues noted.
Disable-storagegroupcopy: No issues noted.
Restore-storagegroupcopy: No issues noted when machines involved are running Exchange 2007 SP1 RU7. Prior to RU7 it may be necessary to use restore-storagegroupcopy –force for the command to complete successfully.
Update-storagegroupcopy: Because update-storagegroupcopy uses online streaming functionality to seed the database to the target the network traffic associated with this occurs over the public interface.
Suspend-storagegroupcopy: No issues noted.
Resume-storagegroupcopy: No issues noted.

Changes to the SCR activation process when replication is enabled to use an alternate interface.
Whether using the database portability method or the single node cluster method after running restore-storagegroupcopy the entries in the host file should be removed or commented out. Once the removal is complete, dns resolver cache should be flushed (ipconfig /flushdns) and a ping from the target machine to it’s own name performed to ensure DNS resolves the correct IP address on the public interface.
When name resolution occurs successfully your move-mailbox –configurationonly or setup.com /recoverCMS can be run to complete the activation process.

**********************
Windows 2008
**********************
Configuring networks and network interfaces to support standby continuous replication using an alternate network interface on Windows 2008.
The first step is to configure the network settings for the network interface that will be used for standby continuous replication. These instructions are performed on both the source and target machines. To configure these settings:
Select Start –> Control Panels –> Network and Sharing Center
In the tasks pane, select “Manage Network Connections”
Right click on the interface for SCR private replication, select rename.
Change the name of the interface to something meaningful indicating it’s purpose.
Right click on the interface for SCR private replication, select properties.
Ensure that Client for Microsoft Networks is enabled.
Ensure the File and Print Sharing for Microsoft Networks is enabled.

In the network properties, select “Internet Protocol Version 4 (TCP/IPv4)”, press properties button.
On the general tab:
Under “Use the following IP address”, provide a valid IP address and subnet mask.
Do not provide a default gateway. (If the source and target reside on different subnets it will be necessary to utilize persistent static routes in order to ensure network communications follow the appropriate path. Do not use two default gateways on a single host).
Do not provide any DNS servers under “Use the following DNS server addresses” .

Selecting the advanced button, on the DNS tab:
Uncheck “Register this connection’s addresses in DNS”.

Complete the changes by pressing OK three times.
The network configuration process is then completed by updating the network binding orders. To update the network binding orders:
Select Start –> Control Panels –> Network and Sharing Center
In the tasks pane, select “Manage Network Connections”
Ensure that the toolbar is displayed:
Select Organize –> Layout –> Menu Bar
From the advanced menu select advanced settings.
On the “Adapters and Bindings” tab, using the arrow keys, adjust the binding order so that the public facing interface is first on the list. All other interfaces may be set in any order.

This completes the base networking configuration for standalone machines and clustered nodes.

Additional configuration steps for SCR source servers on Windows 2008.
Exchange 2007 SP1 / Windows 2008 Standalone Mailbox Server Source
No additional configuration changes are necessary.
Exchange 2007 SP1 / Windows 2008 Cluster Continuous Replication (CCR) Source
Windows 2008 enumerates all networks in a cluster for cluster use. To ensure full supportability of the cluster, the cluster should be re-validated using the validation wizard in Failover Cluster Management.
No additional configuration changes are necessary.
Exchange 2007 SP1 / Windows 2008 Single Copy Cluster (SCC) Source
Windows 2008 enumerates all networks in a cluster for cluster use. To ensure full supportability of the cluster, the cluster should be re-validated using the validation wizard in Failover Cluster Management.
Enable the network for SCR replication for client connectivity.
Launch Failover Cluster Management
In the left hand pane, expand networks.
Identify the network that contains the interfaces used for standby continuous replication.
Right click on the network, select properties.
Select the checkbox next to “Allow clients to connect through this network”.
Press the OK button.
When prompted that the network is now available for client use, press the OK button.

Enable an IP address resource in the Exchange Clustered Mailbox Server (CMS) group.
In the left hand pane, under services and applications, find the CMS group.
Right click on the group, select Add a Resource –> More Resources –> Add IP Address
This will create a not configured IP Address resource in the CMS group.

Right click on the not configured IP Address resource and select properties.
In the "Resource Name” field, enter and appropriate name.
In the “Network” drop down, select the SCR replication network.
In the “Static IP Address” fields input a static IP address valid on the SCR replication network.

Press the OK button.
Right click on the new IP address resource, select “Bring this resource online”.
DO NOT UPDATE ANY DEPENDENCIES ON THIS RESOURCE OR MAKE THIS RESOURCE DEPENDANT ON ANY OTHER RESOURCE(S).

Additional configuration steps for SCR Targets on Windows 2008.
These instructions apply to both standalone and single node SCR targets based on Windows 2008.
Using notepad, open the hosts files located at c:\Windows\System32\Drivers\Etc
Depending on the source make the following changes:
Exchange 2007 SP1 / Windows 2008 Standalone Mailbox Server Source
Add entries in the host file for both the NetBIOS and fully qualified domain name (FQDN). Associate these names to the IP address assigned to the SCR network on the source server.
Exchange 2007 SP1 / Windows 2008 Cluster Continuous Replication (CCR) Source
Add entries in the host file for both the NetBIOS names and fully qualified domain names (FQDN) of the source NODES. Associate these names to the IP address assigned to the SCR network on the source nodes.
Exchange 2007 SP1 / Windows 2008 Single Copy Cluster (SCC) Source
Add entries in the host file for both the NetBIOS name and fully qualified domain name (FQDN) of the source CMS. Associate these names to the IP address created in the CMS group assigned to the SCR network.
Here is the output of a sample host file.
# Copyright (c) 1993-2006 Microsoft Corp. # # This is a sample HOSTS file used by Microsoft TCP/IP for Windows. # # This file contains the mappings of IP addresses to host names. Each # entry should be kept on an individual line. The IP address should # be placed in the first column followed by the corresponding host name. # The IP address and the host name should be separated by at least one # space. # # Additionally, comments (such as these) may be inserted on individual # lines or following the machine name denoted by a '#' symbol. # # For example: # # 102.54.94.97 rhino.acme.com # source server # 38.25.63.10 x.acme.com # x client host
127.0.0.1 localhost ::1 localhost
#Exchange 2007 SP1 / Windows 2008 / Standalone Mailbox Server
10.1.1.1 2008-MBX1 10.1.1.1 2008-MBX1.exchange.msft
#Exchange 2007 SP1 / Windows 2008 / Cluster Continuous Replication (CCR)
10.1.1.3 2008-Node1 10.1.1.3 2008-Node1.exchange.msft 10.1.1.4 2008-Node2 10.1.1.4 2008-Node2.exchange.msft 10.1.1.8 2008-Node5 10.1.1.8 2008-Node5.exchange.msft 10.1.1.9 2008-Node6 10.1.1.9 2008-Node6.exchange.msft
#Exchange 2007 SP1 / Windows 2008 / Single Copy Cluster (SCC)
10.1.1.7 2008-MBX4 10.1.1.7 2008-MBX4.exchange.msft
This completes the configuration steps for Windows 2008.

**********************
Windows 2003
**********************
Configuring networks and network interfaces to support standby continuous replication using an alternate network interface on Windows 2003.
The first step is to configure the network settings for the network interface that will be used for standby continuous replication. These instructions are performed on both the source and target machines. To configure these settings:
Select Start –> Control Panels –> Network Connections
Right click on the interface for SCR private replication, select rename
Change the name of the interface to something meaningful indicating it’s purpose.
Right click on the interface for SCR private replication, select properties.
Ensure that Client for Microsoft Networks is enabled.
Ensure the File and Print Sharing for Microsoft Networks is enabled.

In the network properties, select “Internet Protocol (TCP/IP)”, press properties button.
On the general tab:
Under “Use the following IP address”, provide a valid IP address and subnet mask.
Do not provide a default gateway. (If the source and target reside on different subnets it will be necessary to utilize persistent static routes in order to ensure network communications follow the appropriate path. Do not use two default gateways on a single host).
Do not provide any DNS servers under “Use the following DNS server addresses” .

Selecting the advanced button, on the DNS tab:
Uncheck “Register this connection’s addresses in DNS”.

Complete the changes by pressing OK three times.
The network configuration process is then completed by updating the network binding orders. To update the network binding orders:
Select Start –> Control Panels –> Network Connections
From the advanced menu select advanced settings.
On the “Adapters and Bindings” tab, using the arrow keys, adjust the binding order so that the public facing interface is first on the list. All other interfaces may be set in any order.

This completes the base networking configuration for standalone machines and clustered nodes.

Additional configuration steps for SCR source servers on Windows 2003.
Exchange 2007 SP1 / Windows 2003 Standalone Mailbox Server Source
No additional configuration changes are necessary.
Exchange 2007 SP1 / Windows 2003 Cluster Continuous Replication (CCR) Source
No additional configuration changes are necessary.
Exchange 2007 SP1 / Windows 2003 Single Copy Cluster (SCC) Source
Enable the network for SCR replication for client connectivity.
Launch Cluster Administrator
In the left hand pane, expand “Cluster Configuration” –> “Networks”.
Identify the network that contains the interfaces used for standby continuous replication.
Right click on the network, select properties.
Select “Enable this network for cluster use” and “All Communications (mixed network)”. Press the OK button.

Enable an IP address resource in the Exchange Clustered Mailbox Server (CMS) group.
In the left hand pane, expand groups, find the CMS group.
Right click on the group, select New –> Resource.
Provide an appropriate name in the Name field.
Provide an appropriate description in the Description field.
For Resource Type, change the drop down to “IP Address”

Press the next button.
Verify that the possible owners of the CMS group are correct. Press the next button.

DO NOT UPDATE ANY DEPENDENCIES ON THIS RESOURCE OR MAKE THIS RESOURCE DEPENDANT ON ANY OTHER RESOURCE(S).

In the address field type an appropriate static IP address for the SCR replication network.
In the subnet mask field type the appropriate subnet mask.
In the network drop down ensure that the SCR replication network is selected.
Keep “Enable NetBIOS for this address” selected.

Press the finish button.
Right click on the new IP address resource, select “Bring this resource online”.

Additional configuration steps for SCR Targets on Windows 2003.
These instructions apply to both standalone and single node SCR targets based on Windows 2003.
Using notepad, open the hosts files located at c:\Windows\System32\Drivers\Etc
Depending on the source make the following changes:
Exchange 2007 SP1 / Windows 2003 Standalone Mailbox Server Source
Add entries in the host file for both the NetBIOS and fully qualified domain name (FQDN). Associate these names to the IP address assigned to the SCR network on the source server.
Exchange 2007 SP1 / Windows 2003 Cluster Continuous Replication (CCR) Source
Add entries in the host file for both the NetBIOS names and fully qualified domain names (FQDN) of the source NODES. Associate these names to the IP address assigned to the SCR network on the source nodes.
Exchange 2007 SP1 / Windows 2003 Single Copy Cluster (SCC) Source
Add entries in the host file for both the NetBIOS name and fully qualified domain name (FQDN) of the source CMS. Associate these names to the IP address created in the CMS group assigned to the SCR network.
Here is the output of a sample host file.
# Copyright (c) 1993-2006 Microsoft Corp. # # This is a sample HOSTS file used by Microsoft TCP/IP for Windows. # # This file contains the mappings of IP addresses to host names. Each # entry should be kept on an individual line. The IP address should # be placed in the first column followed by the corresponding host name. # The IP address and the host name should be separated by at least one # space. # # Additionally, comments (such as these) may be inserted on individual # lines or following the machine name denoted by a '#' symbol. # # For example: # # 102.54.94.97 rhino.acme.com # source server # 38.25.63.10 x.acme.com # x client host
127.0.0.1 localhost
#Exchange 2007 SP1 / Windows 2003 / Standalone Mailbox Server
10.1.1.1 2003-MBX1 10.1.1.1 2003-MBX1.exchange.msft
#Exchange 2007 SP1 / Windows 2003 / Cluster Continuous Replication (CCR)
10.1.1.3 2003-Node1 10.1.1.3 2003-Node1.exchange.msft 10.1.1.4 2003-Node2 10.1.1.4 2003-Node2.exchange.msft
#Exchange 2007 SP1 / Windows 2003 / Single Copy Cluster (SCC)
10.1.1.7 2003-MBX4 10.1.1.7 2003-MBX4.exchange.msft
This completes the configuration steps for Windows 2003.

Add or Remove Programs in clustered installations of SQL Server 2005

2009-07-16T11:44:00.002+05:30

For a clustered installation of SQL Server 2005, the Add or Remove Programs item only lets you add or remove the nodes in a cluster or remove the whole installation.You cannot use the Add or Remove Programs item on a cluster to add or remove cluster-aware SQL Server components. For example, you cannot use the Add or Remove Programs item on a cluster to add or remove SQL Server 2005 Database Engine or SQL Server 2005 Analysis Services. You can only run the Setup program at a command prompt to add or remove SQL Server components.Notice that if you try to install a new SQL Server component from an active cluster node by using Add or Remove Programs, the installation wizard will not report an error. However, the installation wizard will fail in the end during the installation. You must only use the Setup program at a command prompt to add or remove SQL Server components on a cluster.

How to use the Add or Remove Programs item in Control Panel to add or remove components for stand-alone installations and clustered installations-SQL

2009-07-16T11:43:00.002+05:30

Add or Remove Programs in stand-alone installations of SQL Server 2005
For a stand-alone installation of SQL Server 2005, you can use the Add or Remove Programs item to perform the following actions.
Add a new component to an existing SQL Server 2005 installation
You may want to add a new component, such as SQL Server 2005 Analysis Services or SQL Server 2005 Reporting Services. To do this, follow these steps:
1. In Control Panel, open Add or Remove Programs.
2. In the Currently installed programs list, click Microsoft SQL Server 2005, and then click Change. The SQL Server 2005 Maintenance Wizard starts.
3. On the Component Selection page, click To install a new component, click here.
4. When you are prompted to provide the location of the Setup.exe file in the SQL Server 2005 installation media, specify the correct path.
5. Click OK. The regular SQL Server 2005 Setup program starts.
6. Click Next on subsequent screens and provide the required information.
7. On the Component to Install page, select the component that you want to install.
8. Click Next, and then complete the wizard.
Remove a component from an existing SQL Server 2005 installation
You may want to remove a component, such as the Workstation components or SQL Server 2005 Reporting Services. To do this, follow these steps:
1. In Control Panel, open Add or Remove Programs.
2. In the Currently installed programs list, click Microsoft SQL Server 2005, and then click Change. The SQL Server 2005 Maintenance Wizard starts.
3. On the Component Selection page, under the SQL Server 2005 instances node, select the instance that includes the instance of the component that you want to remove. For example, if you want to remove SQL Server 2005 Analysis Services from an instance, click the instance name. Note You may want to remove Full-Text Search. Full-Text Search is a part of the Database Engine. To do this, click the item that has Database Engine listed. If you want to remove common components such as SQL Server 2005 Integration Services, SQL Server 2005 Notification Services, or Workstation components, click the component under the SQL Server 2005 common components node.
4. Click Next. The SQL Server 2005 Maintenance Wizard starts the SQL Server 2005 Installation Wizard.
5. Click Next several times until the Change or Remove Instance page appears.
6. On the Change or Remove Instance page, click Change Installed Components.
7. Click Next.
8. On the Feature Selection page, notice the component that you selected earlier. Click the component that you want to remove, and then click Entire feature will be unavailable.
9. Click Next, and then complete the wizard.
Completely remove an existing SQL Server 2005 installation
To completely remove SQL Server 2005 installation from the computer, follow these steps:
1. In Control Panel, open Add or Remove Programs.
2. In the Currently installed programs list, click Microsoft SQL Server 2005, and then click Remove. The SQL Server 2005 Maintenance Wizard starts.
3. On the Component Selection page, under the SQL Server 2005 instances node, select the instance of SQL Server 2005 that you want to remove from the computer. Note The Remove SQL Server 2005 common components list includes the common components that are used by all instances of SQL Server 2005 on the computer. Only select to remove these common components if you are sure that no other instances on the computer need the components. Remember that common components such as SQL Server 2005 Integration Services, SQL Server 2005 Notification Services, and Client Tools are only installed one time on the same computer, regardless of the number of instances of SQL Server 2005.
4. Click Next, and then complete the wizard.

Reason for the Outlook retrieving data…pop-up:

2009-07-16T11:42:00.002+05:30

The popup dialog for the Outlook retrieving data is displayed when Outlook 2003/2007 has to wait longer than 5 seconds for a response from an Exchange server or global catalog server. You can tell from the dialog box what server might be causing the delay. From : “Tip: If the server name shown in the Requesting data … dialog box is in the FQDN format, Outlook is waiting for a response from the directory service. If you see a short server name, Outlook is waiting for either the mailbox server or public folder server to respond.”
A little info... When using Outlook in MAPI mode, user actions in Outlook translate to remote procedure calls (RPCs) between the clients and the server. If the user is running in online mode, these RPC calls occur synchronously. Any delay by the server in fulfilling these synchronous requests directly affects user experience and the responsiveness of Outlook. Conversely, running in cached mode results in the majority of these requests being handled asynchronously. Asynchronous processing means that the speed at which most user actions are initiated should not translate into the responsiveness or overall experience of Outlook.

How do Exchange Server rules work?

2009-07-16T11:41:00.002+05:30

You've been using Outlook for years now and you've probably established some delivery rules for yourself. Maybe mail from your manager is automatically routed to a subfolder of your inbox. If you're using Outlook 2003 or later, you've got an automatically maintained rule to handle junk mail. If you've ever set your Out Of Office, that's handled by a rule too.
But how do rules actually work? What's the implementation like? Obviously, I won't get into the grimy details (trade secrets and all), but I can pass along the basics.
First, the rules infrastructure is fully documented on MSDN. Those among you brave enough to explore this documentation may be inspired to write a little app which will enumerate your inbox rules and print them out on the console for detailed inspection of just what Outlook creates. I wrote such an app for internal diagnostic purposes (which means I most likely can't share it with you, sorry). Oh wait! Someone else has already published something here!
A rule consists of two fundamental properties, and a bunch of other support properties which mostly won't matter for this discussion. The important ones are the rule's conditions, and the rule's actions. Simplistically, if the incoming mail passes the restriction, the rule engine subsequently carries out the actions. The rule engine itself is completely agnostic to the intentions of the rule creator. In other words, the rule engine doesn't care what the title of the rule type in Outlook's wizard is – it only applies the restriction and then if that passes, it carries out the actions.
The conditions are expressed as a MAPI Restriction. As each mail is delivered, the restriction on each rule is applied to the incoming message. The restriction describes a complex property value comparison tree, such as (the received time > somedatetime AND the sender's display name starts with "Bob" AND the body contains "Loser") OR (the message size is greater than 2k). Such restrictions are also used for searching for messages, filtering views, and so on. In this case, the restriction is applied to the incoming message. This means that rules cannot check against dynamic values, such as the current system time or how big the mailbox is. It's constrained to checking properties of the message against constant values. One exception to this is how the Junk Mail rule works, which I'll describe later.
Outlook has a variety of pre-canned restrictions that it uses and I won't go into the exact nature of each one (yes, I know, you're just burning to know what the precise nature of each of these is, but you can use the sample app I linked to above to study the precise nature of each of the rule types). I will point out an important design point though: rules which are of the form "FROM some DISTRIBUTION GROUP" actually means "if the sender is a direct or indirect member of that DL". This often confuses people because they create a rule like "mail from , move to the folder". What ends up happening is all mail from anyone on the "my team DL" starts having their mail moved to that folder. If you think about it, it makes complete sense. However, more often than not, folks really wanted the rule "mail SENT TO , move it".
If the message meets the restriction criteria, the actions are then carried out. While Outlook rarely creates rules with multiple actions within, it's possible to have a list of actions on one rule. The possible actions are:
Move the message to another folder*
Copy the message to another folder*
Reply to the message (with a given template message)
Send an "Out Of Office" reply (with a given template message)
Fail delivery with a specific error code
Forward the message to another address
Delegate the message to another address (a lot like forward, but it preserves original sender info)
Tag the message with a specific property value
Permanently delete the message (Outlook doesn't use this when you create a rule with a delete action. Instead, it creates a MOVE action with the Deleted Items as the destination folder)
Mark the message as read
And finally, the big one: defer to the client to carry out client-defined actions.
The asterisk on Move and Copy refers to what to do if the server can't reach the destination database. In this case, the server turns it into a "defer to client" action where it specifies to the client a) the move or copy action and b) the destination that should be used. As you can see, the server itself is pretty constrained on the kinds of things it can do, yet Outlook offers all these wonderful actions that can be carried out. This is accomplished via the "deferred" action. The client stores in the action any relevant data it needs and the server will later notify the client that it needs to carry out a deferred action on a message, and includes whatever the client stored in the rule (such as, perhaps, the WAV data for the sound to play, for example).
Because a single rule could have conflicting actions, or even because multiple rules that may apply to the message could have conflicting actions, the server pulls off trickery to make sure everything happens correctly. For example, you may have two MOVE rules which apply to a message. You can't move a message to two different folders at once, yet that's the end result (the server treats subsequent MOVEs as if they were COPYs instead).
Exchange Server rules are only executed during delivery. Outlook provides a "Run Rules Now" feature, but that's implemented entirely by Outlook. The server is not involved. Also, realize that server rules are not ever executed after delivery is complete. If you witness spontaneous changes happening to your inbox, this is either Outlook carrying out deferred actions, or someone else logged into your mailbox is changing things under your feet.
What about the Junk Mail Rule? How does it adjust itself based on the administrator's configuration of the move action threshold? The administrator's configuration lives in Active Directory, so how could the rule dynamically retrieve this value for comparison against the Spam Confidence Level value stamped on all incoming messages? Well, there's a one-off cheat just for this. The rule itself is crafted to compare the Spam Confidence Level against the constant value -1. The rule execution engine pre-scans the restriction, looking for this specific comparison. If it finds it, it replaces the constant -1 with the current value in Active Directory, and then the restriction is applied to the incoming mail.
You may be thinking: "but what about two mailboxes, each with a reply rule that replies to the other mailbox? Won't that cause a mail storm?" Well, ordinarily, yes. However, our rules engine is smarter than that. As a rule is triggered on a message, the rule's ID is stamped into an ever-growing property of "I've already run this rule" history. Therefore, if a message "comes back", the rules engine can check to see if any particular rule is in this rule history and avoid running it again. So, if mbx1 sends mail to mbx2, which autoreplies back to mbx1, which autoreplies back to mbx2, the rules engine will detect the loop and not execute the rule that would otherwise cause another autoreply back to mbx1.

Troubleshooting Exchange 2007 Store Log/Database growth issues

2009-07-16T11:34:00.002+05:30

One of the common issues we see in support is excessive Database and/or Transaction log growth problems. If you have ever run in to one of these issues, you will find that they are not always easy to troubleshoot as there are many tools that are needed to help understand where the problem might be coming from. Customers have asked why does the Server allow these type of operations to occur in the first place and why is the Exchange Server not resilient to this? That is not always an easy question to answer as there as so many variables as to why this may occur in the first place ranging from faulty Outlook Add-ins, Custom or 3rd party applications, corrupted rules, corrupted messages, online maintenance not running long enough to properly maintain your database, and the list goes on and on.
Once an Outlook client has created a profile to the Exchange server, they pretty much have full reign to do whatever actions they want within that MAPI profile. This of course, will be controlled mostly by your Organizations mailbox and message size limits and some of the Client throttling or backoff features that are new to Exchange 2007.
Since I have dealt with these type problems in great detail, I thought it would be helpful to share some troubleshooting steps with you that may help you collect, detect and mitigate these problems when and if you should see them.
General Troubleshooting
Use Exchange User Monitor (Exmon) server side to determine if a specific user is causing the log growth problems.
Sort on CPU (%) and look at the top 5 users that are consuming the most amount of CPU inside the Store process. Check the Log Bytes column to verify for this log growth for a potential user.
If that does not show a possible user, sort on the Log Bytes column to look for any possible users that could be attributing to the log growth
If it appears that the user in Exmon is a ?, then this is representative of a HUB/Transport related problem generating the logs. Query the message tracking logs using the Message Tracking Log tool in the Exchange Management Consoles Toolbox to check for any large messages that might be running through the system. See step 5.9 for a Powershell script to accomplish the same task.
If suspected user is found via Exmon, then do one of the following:
Disable the users AD account temporarily
Kill their TCP connection with TCPView
Call the client to have them close Outlook in the condition state for immediate relief.
If closing the client down seems to stop the log growth issue, then we need to do the following to see if this is OST or Outlook profile related:
Have the user launch Outlook while holding down the control key which will prompt if you would like to run Outlook in safe mode. If launching Outlook in safe mode resolves the log growth issue, then concentrate on what add-ins could be attributing to this problem.
If you can gain access to the users machine, then do one of the following:
Launch Outlook to confirm the log file growth issue on the server.
If log growth is confirmed, do one of the following
Check users Outbox for any messages.
If user is running in Cached mode, set the Outlook client to Work Offline. Doing this will help stop the message being sent in the outbox and sometimes causes the message to NDR.
If user is running in Online Mode, then try moving the message to another folder to prevent Outlook or the HUB server from processing the message.
After each one of the steps above, check the Exchange server to see if log growth has ceased
Call Microsoft Product Support to enable debug logging of the Outlook client to determine possible root cause.
Follow the Running Process Explorer instructions in the below article to dump out dlls that are running within the Outlook Process. Name the file username.txt. This helps check for any 3rd party Outlook Add-ins that may be causing the excessive log growth. 970920 Using Process Explorer to List dlls Running Under the Outlook.exe Process http://support.microsoft.com/kb/970920
Check the Sync Issues folder for any errors that might be occurring
Let’s attempt to narrow this down further to see if the problem is truly in the OST or something possibly Outlook Profile related:
Run ScanPST against the users OST file to check for possible corruption.
With the Outlook client shut down, rename the users OST file to something else and then launch Outlook to recreate a new OST file. If the problem does not occur, we know the problem is within the OST itself.
If renaming the OST causes the problem to recur again, then recreate the users profile to see if this might be profile related.
Ask Questions:
Is the user using any type of mobile device?
Question the end user if at all possible to understand what they might have been doing at the time the problem started occurring. It’s possible that a user imported a lot of data from a PST file which could cause log growth server side or there was some other erratic behavior that they were seeing based on a user action.
If Exmon does not provide the data that is necessary to get root cause, then do the following:
Check current queues against all HUB Transport Servers for stuck or queued messages get-exchangeserver where {$_.IsHubTransportServer -eq "true"} Get-Queue where {$_.Deliverytype –eq “MapiDelivery”} Select-Object Identity, NextHopDomain, Status, MessageCount export-csv HubQueues.csv Review queues for any that are in retry or have a lot of messages queued. Export out message sizes in MB in all Hub Transport queues to see if any large messages are being sent through the queues. get-exchangeserver where {$_.ishubtransportserver -eq "true"} get-message –resultsize unlimited Select-Object Identity,Subject,status,LastError,RetryCount,queue,@{Name="Message Size MB";expression={$_.size.toMB()}} sort-object -property size –descending export-csv HubMessages.csv Export out message sizes in Bytes in all Hub Transport queues. get-exchangeserver where {$_.ishubtransportserver -eq "true"} get-message –resultsize unlimited Select-Object Identity,Subject,status,LastError,RetryCount,queue,size sort-object -property size –descending export-csv HubMessages.csv
Check Users Outbox for any large, looping, or stranded messages that might be affecting overall Log Growth.
get-mailbox -ResultSize Unlimited Get-MailboxFolderStatistics -folderscope Outbox Sort-Object Foldersize -Descending select-object identity,name,foldertype,itemsinfolder,@{Name="FolderSize MB";expression={$_.folderSize.toMB()}} export-csv OutboxItems.csv Note: This does not get information for users that are running in cached mode.
Utilize the MSExchangeIS Client\Jet Log Record Bytes/sec and MSExchangeIS Client\RPC Operations/sec Perfmon counters to see if there is a particular client protocol that may be generating excessive logs. If a particular protocol mechanism if found to be higher than other protocols for a sustained period of time, then possibly shut down the service hosting the protocol. For example, if Exchange Outlook Web Access is the protocol generating potential log growth, then stopping the World Wide Web Service (W3SVC) to confirm that log growth stops. If log growth stops, then collecting IIS logs from the CAS/MBX Exchange servers involved will help provide insight in to what action the user was performing that was causing this occur.
Run the following command from the Management shell to export out current user operation rates: To export to CSV File: get-logonstatistics select-object username,Windows2000account,identity,messagingoperationcount,otheroperationcount,progressoperationcount,streamoperationcount,tableoperationcount,totaloperationcount where {$_.totaloperationcount -gt 1000} sort-object totaloperationcount -descending export-csv LogonStats.csv To view realtime data: get-logonstatistics select-object username,Windows2000account,identity,messagingoperationcount,otheroperationcount,progressoperationcount,streamoperationcount,tableoperationcount,totaloperationcount where {$_.totaloperationcount -gt 1000} sort-object totaloperationcount -descending ft Key things to look for: In the below example, the Administrator account was storming the testuser account with email. You will notice that there are 2 users that are active here, one is the Administrator submitting all of the messages and then you will notice that the Windows2000Account references a HUB server referencing an Identity of testuser. The HUB server also has *no* UserName either, so that is a giveaway right there. This can give you a better understanding of what parties are involved in these high rates of operations UserName : Administrator Windows2000Account : DOMAIN\Administrator Identity : /o=First Organization/ou=First Administrative Group/cn=Recipients/cn=Administrator MessagingOperationCount : 1724 OtherOperationCount : 384 ProgressOperationCount : 0 StreamOperationCount : 0 TableOperationCount : 576 TotalOperationCount : 2684 UserName : Windows2000Account : DOMAIN\E12-HUB$ Identity : /o= First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=testuser MessagingOperationCount : 630 OtherOperationCount : 361 ProgressOperationCount : 0 StreamOperationCount : 0 TableOperationCount : 0 TotalOperationCount : 1091
Enable Perfmon/Perfwiz logging on the server. Collect data through the problem times and then review for any irregular activities. You can grab some pre-canned Perfmon import files at http://blogs.technet.com/mikelag/archive/2008/05/02/perfwiz-replacement-for-exchange-2007.aspx to make collecting this data easier.
Run ExTRA (Exchange Troubleshooting Assistant) via the Toolbox in the Exchange Management Console to look for any possible Functions (via FCL Logging) that may be consuming Excessive times within the store process. This needs to be launched during the problem period. http://blogs.technet.com/mikelag/archive/2008/08/21/using-extra-to-find-long-running-transactions-inside-store.aspx shows how to use FCL logging only, but it would be best to include Perfmon, Exmon, and FCL logging via this tool to capture the most amount of data.
Dump the store process during the time of the log growth. (Use this as a last measure once all prior activities have been exhausted and prior to calling Microsoft for assistance. These issues are sometimes intermittent, and the quicker you can obtain any data from the server, the better as this will help provide Microsoft with information on what the underlying cause might be.)
Download the Current Release version of the Windows debuggers from http://www.microsoft.com/whdc/devtools/debugging/install64bit.mspx and select a custom installation and change the directory to install the debuggers to c:\debuggers and finish the installation.
Open the command prompt and change in to the c:\Debuggers directory
Type cscript adplus.vbs –hang –pn store –quiet –o d:\DebugData. Note: -o switch signifies the location in which you want to store the debug data that has sufficient drive space. Important: Once this has launched, a minimized CDB window will open. Please wait for this to complete and do not close this window as this will disappear once the dump has completed.
Wait 2 minutes and perform the same dump operation again.
Open a case with Microsoft Product Support Services to get this data looked at.
Collect a portion of Store transaction log files (100 would be good) during the problem period and parse them following the directions in http://blogs.msdn.com/scottos/archive/2007/11/07/remix-using-powershell-to-parse-ese-transaction-logs.aspx to look for possible patterns such as high pattern counts for IPM.Appointment. This will give you a high level overview if something is looping or a high rate of messages being sent. Note: This tool may or may not provide any benefit depending on the data that is stored in the log files, but sometimes will show data that is MIME encoded that will help with your investigation

Export out Message tracking log data from affected MBX server Method 1 Download the attached ExLogGrowthCollector.zip file to this post and extract to the MBX server that experienced the issue. Run ExLogGrowthCollector.ps1 from the Exchange Management Shell. Enter in the MBX server name that you would like to trace, the Start and End times and click on the Collect Logs button. Note: What this script does is to export out all mail traffic to/from the specified mailbox server across all HUB servers between the times specified. This helps provide insight in to any large or looping messages that might have been sent that could have caused the log growth issue. Method 2 Copy/Paste the following data in to notepad, save as msgtrackexport.ps1 and then run this on the affected Mailbox Server. Open in Excel for review. This is similar to the GUI version, but requires manual editing to get it to work.
#Export Tracking Log data from affected server specifying Start/End Times Write-host "Script to export out Mailbox Tracking Log Information" Write-Host "#####################################################" Write-Host $server = Read-Host "Enter Mailbox server Name" $start = Read-host "Enter start date and time in the format of MM/DD/YYYY hh:mmAM" $end = Read-host "Enter send date and time in the format of MM/DD/YYYY hh:mmPM" $fqdn = $(get-exchangeserver $server).fqdn Write-Host "Writing data out to csv file..... " Get-ExchangeServer where {$_.IsHubTransportServer -eq "True" -or $_.name -eq "$server"} Get-MessageTrackingLog -ResultSize Unlimited -Start $start -End $end where {$_.ServerHostname -eq $server -or $_.clienthostname -eq $server -or $_.clienthostname -eq $fqdn} sort-object totalbytes -Descending export-csv MsgTrack.csv -NoType Write-Host "Completed!! You can now open the MsgTrack.csv file in Excel for review"
Method 3 You can also use the Process Tracking Log Tool at http://msexchangeteam.com/archive/2008/02/07/448082.aspx to provide some very useful reports.
Save off a copy of the application/system logs from the affected server and review them for any events that could attribute to this problem
Enable IIS extended logging for CAS and MB server roles to add the sc-bytes and cs-bytes fields to track large messages being sent via IIS protocols and to also track usage patterns.
Proactive monitoring and mitigation efforts
Increase Diagnostics Logging for the following objects depending on what stores are being affected:
MSExchangeIS\Mailbox\Rules
MSExchangeIS\PublicFolders\Rules
Enable Client Side monitoring per http://technet.microsoft.com/en-us/library/cc540465.aspx
Create a monitoring plan using MOM/SCOM to alert when the amount of Log Bytes being written hit a specific threshold and then alert the messaging team for further action. There are thresholds that are a part of the Exchange 2007 Management Pack that could help alert to these type situations before the problem gets to a point of taking a database offline. Here are 2 examples of this. ESE Log Byte Write/sec MOM threshold Warning Event http://technet.microsoft.com/en-us/library/bb218522.aspx Error Event http://technet.microsoft.com/en-us/library/bb218733.aspx If an alert is raised, then perform an operation to start collecting data.
Ensure http://support.microsoft.com/kb/958701 is installed at a minimum for each Outlook 2003 client to address known log/database growth issues for users streaming data to the information store that have exceeded message size limits. This fix also addresses a problem where clients could copy a message to their inbox from a PST that during the sync process could exceed mailbox limits, thus causing excessive log growth problems on the server. These hotfixes make use of the PR_PROHIBIT_SEND_QUOTA and PR_MAX_SUBMIT_MESSAGE_SIZE which is referenced in http://support.microsoft.com/kb/894795
Additional Outlook Log Growth fixes: http://support.microsoft.com/kb/957142 http://support.microsoft.com/kb/936184
Implement minimum Outlook Client versions that can connect to the Exchange server via the Disable MAPI clients registry key server side. See http://technet.microsoft.com/en-us/library/bb266970.aspx for more information. To disable clients less than Outlook 2003 SP2, use the following entries on an Exchange 2007 server "-5.9.9;7.0.0-11.6568.6567"
Setting this to exclude Outlook client versions less than Outlook 2003 SP2 will help protect against stream issues to the store. Reason being is that Outlook 2003 SP2 and later understand the new quota properties that were introduced in to the store in http://support.microsoft.com/kb/894795. Older clients have no idea what these new properties are, so if a user sent a 600MB attachment on a message, it would stream the entire message to the store generating excessive log files and then get NDR’ed once the message size limits were checked. With SP2 installed, the Outlook client will first check to see if the attachment size is over the set quota for the organization and immediately stop the send with a warning message on the client and prevent the stream from being sent to the server.
Allowing any clients older than SP2 to connect to the store is leaving the Exchange servers open for a growth issue.
If Entourage clients are being utilized, then implement the MaxRequestEntityAllowed property in http://support.microsoft.com/kb/935848 to address a known issue where sending a message over the size limit could potentially create log growth for a database.
Check to ensure File Level Antivirus exclusions are set correctly for both files and processes per http://technet.microsoft.com/en-us/library/bb332342.aspx
Enable Content Conversion tracing on all HUB servers per http://technet.microsoft.com/en-us/library/bb397226.aspx . This will help log any failed conversion attempts that may be causing the log growth problem to occur.
If POP3 or IMAP4 clients are connecting to specific servers, then implementing Protocol Logging for each on the servers that may be making use of these protocols will help log data to a log file where these protocols are causing excessive log growth spurts. See http://technet.microsoft.com/en-us/library/aa997690.aspx on how to enable this logging.
Ensure Online maintenance is completing a pass for each database within the past week or two. Query Application event logs for the ESE events series 700 through 704 to clarify. If log growth issues occur during online maintenance periods, this could be normal as Exchange shuffles data around in the database. We just need to ensure that we keep this part in mind during these log growth problems.
Check for any excessive ExCDO warning events related to appointments in the application log on the server. (Examples are 8230 or 8264 events). http://support.microsoft.com/kb/947014 is just one example of this issue. If recurrence meeting events are found, then try to regenerate calendar data server side via a process called POOF. See http://blogs.msdn.com/stephen_griffin/archive/2007/02/21/poof-your-calender-really.aspx for more information on what this is. Event Type: Warning Event Source: EXCDO Event Category: General Event ID: 8230 Description: An inconsistency was detected in username@domain.com: /Calendar/ .EML. The calendar is being repaired. If other errors occur with this calendar, please view the calendar using Microsoft Outlook Web Access. If a problem persists, please recreate the calendar or the containing mailbox.
Event Type: Warning Event ID : 8264 Category : General Source : EXCDO Type : Warning Message : The recurring appointment expansion in mailbox has taken too long. The free/busy information for this calendar may be inaccurate. This may be the result of many very old recurring appointments. To correct this, please remove them or change their start date to a more recent date. Important: If 8230 events are consistently seen on an Exchange server, have the user delete/recreate that appointment to remove any corruption
Add additional store logging per http://support.microsoft.com/kb/254606 to add more performance counter data to be collected with Perfmon. This will allow us to utilize counters such as ImportDeleteOpRate and SaveChangesMessageOpRates which allows us to see what these common log growth rates are.
Recommend forcing end dates on recurring meetings. This can be done through the usage of the registry key DisableRecurNoEnd (DWORD). For Outlook 2003: http://support.microsoft.com/kb/952144 HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Outlook\Preferences For Outlook 2007: http://support.microsoft.com/kb/955449 HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\Preferences Value: 1 to Enable, 0 to Disable
Implement LimitEmbeddingDepth on the Exchange servers as outlined in KB 833607 to prevent log growth due to recursion looping. Note: This article states this if for Exchange 2000-2003, but the key is also still valid in Exchange 2007 per source code
Known Issues
Exchange Server
The Store.exe process uses almost 100 percent of CPU resources, and the size of the public folder store increases quickly in Exchange Server 2007 http://support.microsoft.com/kb/925252/
Check the event log for warnings similar to the following Event ID : 107 Category : None Source : MSExchange Search Indexer Type : Warning Message : Exchange Search Indexer has temporarily disabled indexing of the Mailbox Database (GUID = xxxx) due to an error (Microsoft.Mapi.MapiExceptionNotFound: MapiExceptionNotFound: Unable to read events. (hr=0x8004010f, ec=-2147221233) Diagnostic context: Lid: 33865 Lid: 1494 ---- Remote Context Beg ---- Lid: 10804 StoreEc: 0xFFFFF9BF Lid: 9308 StoreEc: 0x8004010F Lid: 2970 StoreEc: 0x8004010F Lid: 2986 StoreEc: 0x8004010F Lid: 18438 Lid: 3798 StoreEc: 0x8004010F Lid: 23330 StoreEc: 0x8004010F Lid: 12624 StoreEc: 0x8004010F Lid: 2031 StoreEc: 0x8004010F Lid: 20057 StoreEc: 0x8004010F Lid: 1750 ---- Remote Context End ---- Lid: 28777 StoreEc: 0x8004010F Lid: 20098 Lid: 20585 StoreEc: 0x8004010F at Microsoft.Mapi.MapiExceptionHelper.ThrowIfError(String message, Int32 hresult, Object objLastErrorInfo) at Microsoft.Mapi.MapiEventManager.ReadEvents(Int64 startCounter, Int32 eventCountWanted, Int32 eventCountToCheck, Restriction filter, ReadEventsFlags flags, Int64& endCounter) at Microsoft.Mapi.MapiEventManager.ReadEvents(Int64 startCounter, Int32 eventCountWanted) at Microsoft.Exchange.Search.RetriableOperations.ReadEvents(ThreadLocalCrawlData unused1, Guid unused2, MapiEventManager eventManager, Int64 watermark, Int32 eventCount) at Microsoft.Exchange.Search.RetriableOperations.DoRetriableMapiOperation[SourceType,ReturnType,Parameter1Type,Parameter2Type](ThreadLocalCrawlData crawlData, Guid mailboxGuid, SourceType source, Parameter1Type parameter1, Parameter2Type parameter2, MapiOperationDelegate`4 operationDelegate) at Microsoft.Exchange.Search.NotificationWatcher.GetMapiEvents(Int32 maxEvents, NotificationQueue notificationQueue) at Microsoft.Exchange.Search.NotificationWatcher.NotificationWatcherThread()). If you are seeing these events, you may be running in to a problem where messages sit in a Users Outbox and transport is trying to redeliver this message over and over. This problem will be corrected in Release Update 9 for Exchange 2007 Server Service Pack 1
947014 - An Exchange Server 2007 mailbox server randomly generates many transaction logs in an Exchange Server 2007 Service Pack 1 environment
957124 - You do not receive an NDR message even though your meeting request cannot be sent successfully to a recipient
960775 - You receive a "Message too large for this recipient" NDR that has the original message attached after you restrict the Maximum Message Send Size value in Exchange Server 2007
Outlook 2007
970944 – Installing this hotfix package addresses and issue where log files are generated unexpectedly when a user is running Outlook 2007 in the cached Exchange mode and sends an e-mail message to the recipients who have a corrupted e-mail address and/or e-mail address
Outlook 2003
958701 - Description of the Outlook 2003 Post-Service Pack 3 hotfix package (Engmui.msp, Olkintl.msp, Outlook.msp): October 28, 2008
936184 - Description of the Outlook 2003 post-Service Pack 3 hotfix package: December 14, 2007
897247 - Description of the Microsoft Office Outlook 2003 post-Service Pack 1 hotfix package: May 2, 2005
Entourage
935848 - Various performance issues occur when you use Entourage for Mac to send large e-mail messages to an Exchange 2007 server

Want to Test Exchange connectivity ?

2009-07-16T11:25:00.002+05:30

Want to Test Exchange connectivity ?

Click on below link for Exchange Activesync, Mapi, Outlook and OWA connectivity

https://www.testexchangeconnectivity.com/