Exchange Server Resource; Blog ; Windows Server; Tutorials; Forum; Exchange Server Help
|
Exchange Server -
Exchange 2010
|
|
Written by Dominic Savio
|
|
Monday, 30 April 2012 19:42 |
|
Have you ever noticed that when you book a conference room in Exchange Server 2010, the subject line gets deleted. Why is it deleted in the first place ? I would assume that Microsoft wanted some privacy here, so that when another person tries to book, he only gets to know who booked it. Why he booked remains a secret
So subject missing in the meeting request of a room mailbox is the default behaviour.
This can be changed thru “Set-MailboxCalendarSettings” you do a Set-MailboxCalendarSettings | fl and you will see all the true and false. Enable what you want. Simple.
Now the question anyone want the subject line – because, there are many organisation, who publish the room mailbox calendar weekly, monthly. They need subject and do not completely agree with Microsoft on privacy of “why you have booked the room “
So in our case you can key out this command : Set-MailboxCalendarSettings RoomName -DeleteSubject $False -AddOrganizerToSubject $False
Hope it helps some one.,….
~Dom
|
|
|
Exchange Server -
Exchange 2010
|
|
Written by Dominic Savio
|
|
Friday, 14 October 2011 05:23 |
|
Microsoft Federation
Have ever been in a situation where you had two different forest and wanted to share your
The screen below gives you a overview of what you could share between forest/orgs

|
|
Read more...
|
|
Office 365 | BPOS -
Office 365
|
|
Written by Dominic Savio
|
|
Wednesday, 12 October 2011 23:24 |

|
|
Read more...
|
|
Office 365 | BPOS -
Office 365
|
|
Written by Dominic Savio
|
|
Tuesday, 27 September 2011 00:13 |
|
BPOS SINGLE SIGN ON TOOL REGISTRY SETTINGS
Please find the Autodiscover settings that are created by the SSO tool of Microsoft Online Services below:
The Sign In Application creates a local file named Autodiscover.xml and corresponding registry keys:
Registry subkeys are created under the following registry key:
|
|
Read more...
|
|
Office 365 | BPOS -
Office 365
|
|
Written by prasad
|
|
Friday, 23 September 2011 03:35 |
|
Before moving from on premise to Office 365, administrators must upgrade their current infrastructure for Office 365.
Following is the list of suppored OS/Software and Browser.
|
|
Read more...
|
|
General -
General
|
|
Written by Dominic Savio
|
|
Wednesday, 24 August 2011 23:33 |
|
1. MAPI connects to exchange server by TCP.
|
|
Read more...
|
|
Exchange Server -
Exchange 2007
|
|
Written by Dominic Savio
|
|
Wednesday, 24 August 2011 23:54 |
|
|
|
Read more...
|
|
Exchange Server -
Exchange Client
|
|
Written by Dominic Savio
|
|
Thursday, 25 August 2011 00:40 |
|
|
|
Read more...
|
|
Exchange Server -
Exchange 2007
|
|
Written by Dominic Savio
|
|
Thursday, 25 August 2011 00:35 |
|
EXCHANGE 2007 TRANSPORT TERMs
There are few transport features which were introduced in Exchange 2007 and carried over to the new Exchange 2010 product and few which were carried from previous version with different naming terms. I thought I would put them in one place. Here are few of them:
|
|
Read more...
|
|
Exchange Server -
Exchange 2007
|
|
Written by Dominic Savio
|
|
Thursday, 25 August 2011 03:45 |
|
APPLYING/REMOVING MANAGED FOLDER MAILBOX POLICY
To apply the defined policy to all the users:
Get-Mailbox -ResultSize unlimited | Set-Mailbox -ManagedFolderMailboxPolicy “Policy Name”
To apply the defined policy to a specific Database:
Get-mailbox -Database "MailboxDatabaseName" | Set-mailbox -ManagedFolderMailboxPolicy "Policy Name"
|
|
Read more...
|
|
Exchange Server -
Exchange 2007
|
|
Written by Nilesh Shetty
|
|
Wednesday, 18 May 2011 01:39 |
|
Have any of you wondered how would you find this information? If yes and you do not know the solution, please read further. In case you already know about it kindly ignore. There are more than a couple of ways to find this information, listed below are the ones I find most easy: 1. Using Powershell Cmdlet: Get-ExchangeServer | where {$_.ServerRole -eq "Mailbox"} | Get-Mailbox -ResultSize Unlimited | Get-LogonStatistics | select UserName, ServerName, StorageGroupName, DatabaseName, LastAccessTime, LogonTime, ClientIPAddress, ClientMode, ClientName, ClientVersion | Export-CSV -path C:\Output.csv –NoTypeInformation Note: For the above command to work, you need to ensure you have Powershell v2.0 installed. 2. Using SCCM or Group Policy or another script (VBScript or Powershell), we could query for the value of the following registry key on the client machines: HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles\UserNameHere\13dbb0c8aa05101a9bb000aa002fc45a\00036601 which contains information about cached or not cached
|
|
|
|
|
|
|
Page 1 of 5 |