If you read the Microsoft article “XADM: How Circular Logging Affects the Use of Transaction Logs” (http://support.microsoft.com/?kbid=147524) carefully, you’ll see that circular logging is working just fine. When it’s enabled, Exchange can reuse log files instead of creating new ones. Under typical circumstances, Exchange will create no more than five logs when you enable circular logging; however, Exchange will create additional log files, if needed, during surge conditions of high activity–such as when you run LoadSim to create a bunch of sessions and messages. After Exchange creates those log files, Exchange won’t delete them until you purge the files by doing a full backup with an Exchange-aware backup utility. Exchange will reuse the first log files, but they’ll stay in place across reboots until you purge them.
The main difference is that using Tools, Options and setting permissions on the Delegates tab also grants the delegate Send On Behalf Of permission on the mailbox in Active Directory (AD). The user can then send messages as if he or she were the mailbox owner, and the From line on such messages will read From <sender> on behalf of <mailbox owner>. If you want to allow only folder access, without letting the user send on behalf of the mailbox owner, right-click the folder, choose Properties, and set access on the Permissions tab. You also need to use the Properties dialog box when you want to allow access to any folders other than Inbox, Contacts, Calendar, Tasks, Journal, or Notes.
No. You can’t introduce Exchange 2007 into an existing Exchange organization while an Exchange 5.5 server still exists in the organization. If you run Exchange 5.5, you must first upgrade to Exchange 2000 Server or Exchange Server 2003, effectively Exchange native mode. After you move the mailboxes to an Exchange 2000 or Exchange 2003 organization, you can move the mailboxes to Exchange 2007 via the Exchange 2007 GUI if Exchange 2007 and the Exchange 2003/2000 installation are in the same organization or by using the Power Shell Move-Mailbox command for cross-organization migrations.
You can copy Exchange server 2003’s ESEUTIL to another machine, along with the database to run. First, create a temporary folder on the computer that you want to run the defrag on. Then, copy the eseutil.exe, ese.dll, jcb.dll, exosal.dll, and exchmem.dll files from the Exchange 2003 computer’s ExchsrvrBin folder to the temporary folder, along with the database and streaming files. At a command prompt, change the directory to the temporary directory folder you created and copied the files to. Finally, run the Eseutil command from this folder against any databases that you copied from the Exchange 2003 computer.
Exchange 2003 SP2 raises the maximum database size for the standard edition from 16GB to 75GB. By default, the size is increased to 18GB when you install the service pack, however you can raise this limit by modifying the registry, as follows:
1. Start the registry editor (regedit.exe) on the Exchange server.
2. Navigate to the HKLMSYSTEMCurrentControlSetServicesMSExchangeISSAVDALDC01Private- subkey.
3. From the Edit menu, select New – DWORD value.
4. Enter a name of Database Size Limit in GB and press enter.
5. Double-click the new value and set it to a value between 1 and 75. Click OK.
6. Close the registry editor.
You can also set a warning level that writes a warning to the event log when the database size reaches a certain percent of remaining space. To do so, you navigate to the same registry subkey as the earlier instructions show, create a DWORD value named Database Size Buffer in Percentage, and set it to a value between 1 and 100 (the default value is 10).
This check of the database size occurs once a day at 5:00 A.M. You can change this time by creating a DWORD value named Database Size Check Start Time in Hours From Midnight in the same registry key as above and setting it to the number of hours past midnight at which to perform the check (e.g., a setting of 12 means the check would occur at noon). You need to dismount and mount the Store for the changes to take effect.
By default, Exchange writes 5MB transaction logs that are kept until you perform a full backup. If the database becomes corrupted, Exchange restores the last full backup then applies all the transaction logs. However, you can turn on circular logging, which instead reuses transaction logs when the 5MB is full, but this means in the event of a database loss, data could be restored only to the point of the last backup. To enable circular logging:
1. Start Exchange System Manager (ESM–Start, Programs, Microsoft Exchange, System Manager).
2. Expand Administrative Groups, Servers, then expand the server.
3. Right-click the storage group for which you want to enable circular logging and select Properties (remember transaction logs are per storage group and not per database).
4. Select the “Enable circular logging” check box and click OK, as the figure shows.
5. Click Yes to the warning.
6. Restart the Information Store by using the following command: net stop msexchangeis net start msexchangeis
When run on your BlackBerry Enterprise Server the following command line will export your installed licence keys to a text file. Replace c:beskeys.txt with the path and filename of your choice.
bcp besmgmt..licensekeys out c:beskeys.txt -c -T
Microsoft has released several demonstrations about Exchange 2007 that will give you a good idea of what you can expect from the new messaging release. You can download the demos here
Yes I have some MSN Messenger Live invites to give out.
Its easy, just leave a comment and explain why you prefer Windows over Unix.
I will pick the best replies and mail the invites out.
Good luck !
No competitions, no quizzes, no waiting !…