Integrating your application with Active Directory (or another LDAP based directory) is a common requirement in many business applications. Almost every language has a way to query LDAP but little known is the approach of integrating SQL Server with your LDAP controller. This quick article will guide you through setting up and using LDAP queries through SQL Server with Active Directory as the LDAP controller.

- In SQL server Management Studio, go to Server Objects, Linked Servers, and right click ADSI, go to Properties.
- Go to Security, Add mapping, Local Login - “Whatever you want” in my case schoolpostadmin, Then put the remote user that you want to run the login + password.

Now run this on the server you want use:

Code:

Now just write your query. Eg:

Code:

1) Make sure that the task is set to “configure for Windows Vista or Windows 2008″ on the first page of the task properties (under the “general” tab)
2) Make sure that the task is set to “start in” the folder that contains the batch file: open the task properties, click on the “actions” tab, click on the action and then the “edit” button at the bottom. In the “Edit Action” Window there is a field for “start in (optional)” that you set to the path to the batch file.
3) Make sure that the task is running as an account that has explicit “Full access” permissions to all these things: The .bat file itself, the folder containing the .bat file, and the target files/folders that are affected by the .bat script. Inherited permissions didn’t seem to work for me.
4) Make sure that the account running the task is a member of the local “administrators” group for this machine
5) Make sure that the task is set to “run whether logged on or not”
6) The Task should run successfully with expected output when you right-click on the task and select “run” If it does that then it will run successfully when you are logged off.

Mailbox Role Failed

Error:
Object is read only because it was created by a future version of Exchange: 0.10 (14.0.100.0). Current supported version is 0.1 (8.0.535.0).

A closer look at the ExchangeSetup.txt tells me something about the Offline Address book and Public Folder store:

[28/10/2009 21:37:05] [2] Checking whether the public folder database “MB\Public Folder Storage Group\Public Folder Database” has local replicas.
[28/10/2009 21:37:06] [2] Searching objects of type “OfflineAddressBook” with filter “(PublicFolderDatabase Equal MB\Public Folder Storage Group\Public Folder Database)", scope “SubTree” under the root “Delimon Organization".
[28/10/2009 21:37:06] [2] Previous operation run on domain controller ‘x.delimon.be’.
[28/10/2009 21:37:06] [2] [ERROR] Object is read only because it was created by a future version of Exchange: 0.10 (14.0.100.0). Current supported version is 0.1 (8.0.535.0).

Opening the Offline Addressbook settings with Exchange 2007 Management Console also spawns the same error and makes the configuration Read Only.

So lets remove the Exchange 2007 CAS Server from the AOB Distribution and disable Public Folder Distribution with the Exchange 2010 Management Console…
That did not change anything

So lets remove the Public Folder Database with ADSIEDIT.MSC
(Connect to the Configuration Container)

IMPORTANT : You must have moved all PF data to another server, this will destroy your PF Database.
(In my case all information was already moved)

Now that replication has finished you can see that the Public Folder DB is no longer available

So now let’s retry the uninstall…

That worked out great
You can see below that the Exchange 2007 Mailbox Server has been removed from the Exchange Configuration

Conclusion:

If you have a public folder on your mailbox server then the Uninstallation of Exchange 2007 Mailbox Server may fail if Exchange 2010 is already deployed.
My guess is that Microsoft will release an update installer/uninstaller that does not fail on the Offline Address book/Public Folder info that was upgraded to Exchange 2010 version information in AD

Using ADSIEDIT.MSC should not be considered a supported solution, this is only a workaround!

Thanks to Johan for this one - : http://www.proexchange.be/blogs/exchange2010/archive/2009/10/28/remove-exchange-2007-mailbox-role-fails-with-error-object-is-read-only-because-it-was-created-by-a-future-version-of-exchange-0-10-14-0-100-0-current-supported-version-is-0-1-8-0-535-0.aspx

SYMPTOMS
You start to uninstall Microsoft Exchange Server 2007 by using the Add or Remove Programs item in Control Panel. When you do this, the following tasks are completed successfully:
All server roles are removed.
The Exchange organization is removed.
However, the uninstall operation stops responding when it runs the task to remove Exchange files. Although the progress bar indicates that 100 percent of the task is completed, the operation does not continue to the next step.

Additionally, when you open Task Manager, the Powershell.exe process constantly displays 25 percent CPU usage.

CAUSE
This problem occurs because a custom action invokes the Powershell.exe process but never executes the action.

RESOLUTION
To resolve this problem, open Task Manager, and then end the Powershell.exe process. The Powershell.exe process will restart immediately and then complete the uninstall operation.

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section.

MORE INFORMATION
For more information about how to completely remove Exchange Server 2007, visit the following Microsoft Web site:
http://technet.microsoft.com/en-us/library/bb123893.aspx (http://technet.microsoft.com/en-us/library/bb123893.aspx)
Back to the top

We had done an upgrade from exchange 2007 to 2010 but that didn’t seem to matter as it was not a server problem - some could use them and some could not.

The solution to this was found in the OWA help feature!

The reason the “Previous Item” & “Next Item” buttons are grayed out is because you have the Conversation option selected for the items in that folder (Note: Conversation is selected, by default, for all folders, when your mailbox is upgraded to R4).

If you turn it off (i.e. uncheck the check box next to “Conversation” or found within the “Sort” area - I.e: sort by date, from, to, etc..), then the arrows will work again.
The way you turn it off is by clicking the dropdown next to where it says “Arrange by” and unchecking the check box next to the word “Conversation".

Specify the alias, username, or e-mail address of the user for which you want to open the Inbox.

When clicking “OK”, you will now have access to the Inbox of the specified user via the navigation pane.

The interesting thing about this method is that this will be remembered until you right-click the other user’s Inbox and select “Remove from view”. Even next time you open your mailbox using OWA 2010.

If you want to open the complete mailbox of another user, you should instead click on the drop-down button in the upper right corner and specify the username, alias or e-mail address.

When clicking “Open”, the mailbox of the specified mailbox user will open in the current OWA 2010 browser window.

Two very nice features indeed! But what if you want to authenticate directly against another user’s mailbox on the OWA 2010 FBA page?

Well, you simply enter the following URL:

https://mail.domain.com/owa/e-mail_address_of_mailbox_user

And there we go.

{Thanks to Henrik Walther for the above blog post. You can read his original post on http://blogs.msexchange.org/walther/2010/01/19/opening-other-users-inboxesmailboxes-using-owa-2010/ }

In Exchange 2010, circular logging is disabled by default. By enabling it, you reduce drive storage space requirements. However, without a complete set of transaction log files, you can’t recover any data more recent than the last full backup. Therefore, in a normal production environment, circular logging isn’t recommended.

In the standard transaction logging used by Exchange 2010, each database transaction is written to a log file and then to the database. When a log file reaches one megabyte in size, it’s renamed and a new log file is created. Over time, this results in a set of log files. If Exchange stops unexpectedly, you can recover the transactions by replaying the data from these log files into the database. Circular logging overwrites and reuses the first log file after the data it contains has been written to the database.

Use the EMC to configure mailbox database properties
You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the “Mailbox database” entry in the Mailbox Permissions topic.

1.In the console tree, navigate to Organization Configuration > Mailbox.

2.In the result pane, on the Database Management tab, select the database you want to configure.

3.In the work pane, click Properties.

4.Use the Maintenance tab to configure mailbox database settings, including specifying a journal recipient, setting a maintenance schedule, and mounting the database at startup:

Journal recipient Select this check box to enable transport journaling of e-mail.

Maintenance schedule Use this list to select one of the preset maintenance schedules. You can also configure a custom schedule. To configure a custom schedule, in the Maintenance schedule list, select Use Custom Schedule, and then click Customize.

Don’t mount this database at startup Select this check box to prevent Exchange from mounting this mailbox database when it starts.

This database can be overwritten by a restore Select this check box to allow the mailbox database to be overwritten during a restore process.

Enable circular logging Select this check box to enable circular logging. For more information about circular logging see Understanding the Exchange 2010 Store.

You then need to dismount and remount the database. You can just right click to get to this menu.

1. Open the cmd prompt. (Start -> Run or press win key + R, then type cmd and press OK)

2. Type telnet server.com 25 (where “server.com” is the name of the smtp (outgoing) server of your email provider, such as smtp-server.austin.rr.com). This can be found by checking your account info in the program you normally use for email.

3. Type HELO mail-01. (Or “EHLO server.com")
4. Type MAIL FROM:you@server.com.
5. You may get a message saying “250 ok”
6. Type RCPT TO:joe@me.com, matt@bobsmith.org,
7. again, You may get a message saying “250 ok”
8. To write the message, type DATA and press Enter.
a. On the first line type SUBJECT:your subject and press Enter twice.
b. Continue typing your message.
c. Put a single period (.) on a line by itself and press Enter to send your message.
The server should say ‘Message accepted for delivery’. (Or it says 250 OK id=`a long id`)
9. Type QUIT to exit Telnet.