A new client side feature which Microsoft has released in Exchange 2010 SP1 is the ability of Outlook 2010 to automatically map all mailboxes to which the logged in user has full access.
There by, on each mailbox that you have been granted Full Access, you will see it on your own personal mailbox.

In Order to disable automatic mapping:

1. Go to this user mailbox, right click on it and choose manage full mailbox access, then just remove your user from the full mailbox access page
2. You can use ADSIEDIT, and go this user properties, and under msExchDelegateListLink attribute, just remove the link to your user
3. You can use the following script for future mailbox permissions – this will add full mailbox access with no AutoMapping.
4. You can remove msExchDelegateListLink values from multiple users properties using ADModify.net

In order to find all users that have Full Mailbox Access on other users’ mailbox, run the following powershell:

Get-Mailbox -ResultSize Unlimited | Get-MailboxPermission | ? {($_.AccessRights -match "FullAccess") -and -not ($_.User -like "NT AUTHORITYSELF")} | ft Identity, User

While performing maintenance to Exchange 2010 DAG server you should first remove the DAG member from DAG group.Other wise you may have unwanted DB failovers and many other unexpected issue that may affect company mail services availability

Shutting Down DAG Members

The Exchange 2010 high availability solution is integrated with the Windows shutdown process. If an administrator or application initiates a shutdown of a Windows server in a DAG that has a mounted database that’s replicated to one or more DAG members, the system attempts to activate another copy of the mounted database prior to allowing the shutdown process to complete.

However, this new behavior doesn’t guarantee that all of the databases on the server being shut down will experience a lossless activation. As a result, it’s a best practice to perform a server switchover prior to shutting down a server that’s a member of a DAG.

The correct way to perform any maintenance is to run first  StartDagServerMaintenance.ps1 script that is located under “C:Program FilesMicrosoftExchange ServerV14scripts”
This script moves all the active databases to next preferred DAG server and prevents active databases from moving to that server during the maintenance.
In addition the script ensures that all critical DAG support functionality that may be on this server has been moved to next proffered server

To run the script open EMC
Type:
cd $exscripts
StartDagServerMaintenance.ps1 -server YourServername

The script performs the following tasks on the background:

• Runs the Suspend-MailboxDatabaseCopy cmdlet for each database copy hosted on the DAG member.
• Pauses the node in the cluster, which prevents the node from being and becoming the PAM.
• Sets the value of the DatabaseCopyAutoActivationPolicy parameter on the DAG member to blocked
• Moves all active databases currently hosted on the DAG member to other DAG members.
• If the DAG member currently owns the default cluster group, the script moves the default cluster group (and therefore the PAM role) to another DAG member.

If any of the preceding tasks fails, all operations, except for successful database moves, are undone.

After the maintenance is complete and the DAG member is ready to return to serve clients you need to run the following script:

cd $exscripts
StopDagServerMaintenance.ps1 -server YourServername

The script performs the following tasks on the background:

• Runs the Resume-MailboxDatabaseCopy cmdlet for each database copy hosted on the DAG member.
• Resumes the node in the cluster, which enables full cluster functionality for the DAG member.
• Sets the value of the DatabaseCopyAutoActivationPolicy parameter on the DAG member to Unrestricted

I highly recommend using  Start/StopDagServerMaintenanceInstalling maintainance scripts before any action that requiers server Reboot/ShutDown or Update Rollups instalation.

Most of the material has been taken from Managing Database Availability Groups MS article

When you try to upgrade to new version of VMware tools , Installation wizard asks you to uninstall older version .
If you can’t do it , or uninstall feature failed to complete, you will need to uninstall them manually.

You may receive the following errors
A previous version of VMware Tools is already installed

To remove old VMware tools follow the steps bellow:

1. Open registry editor
2. Navigate to the following key
   HKEY_LOCAL_MACHINESoftwareMicrosoftWindowsCurrentVersionuninstall search for VMware Tools related branch and delete the key Please note:Do not delete the entire uninstall branch.
3. Navigate to
   HKEY_LOCAL_MACHINESoftwareClassesInstallerProducts search for VMware Tools related branch and delete the key
   Please note:Do not delete the entire Products  key
4. Navigate to
   HKEY_CLASSES_ROOTInstallerProducts search for VMware Tools related branch and delete the key
   Please note:Do not delete the entire Products  key
5. Navigate to
   HKEY_LOCAL_MACHINESoftwareVMware Delete the branch called VMware Tools.
6. Delete the "VMware Tools" directory within in the Vmware directory under Program Files
7. Restart the server
8. Install updated version of VMware Tools through Vsphere Client or VMware client

Some times we need to use PS script to send email, script can be used in Task Scheduler or any other program

BatchFile to run script: Create *.bat file

C:WindowsSystem32WindowsPowerShellv1.0powershell.exe -PSConsoleFile "C:Program FilesMicrosoftExchange Serverbinexshell.psc1" -noexit -command ". C:scriptslocationscriptname.ps1"

PS Script to send mail: Create  .ps1 file

$filename = “c:filelocationHtmlFIleyouwant torecieve.html”
$smtpServer = “SMTP Servername”

$msg = new-object Net.Mail.MailMessage
$att = new-object Net.Mail.Attachment($filename)
$smtp = new-object Net.Mail.SmtpClient($smtpServer)

$msg.From = “sendername@domainanme”
$msg.To.Add(“recipient_address@domainanme”)
$msg.Subject = “Subject”
$msg.Body = “Body ”
$msg.Attachments.Add($att)
$smtp.Send($msg)

ODF is the default format of OpenOffice.org

Most common OpenOffice file extensions are

odt : Word Processor
ods: Spreadsheet ( Excel)
odp: Presentation (PowerPoint)

By default MS Office doesn’t support those formats’.

For Office 2003
To open one of the following formats you need to install Sun ODF Plugin You can download the Sun ODF Plugin from here 

For office 2007 users
Install Sun ODF Plugin for Microsoft Office.

You must have Office 2007 SP 1 installed to make it work

Terminal Server Office 2003/2007/2010 Installation issue

If you installed office in the same way you install it on your desktop.
Your user information will be replicated to all other users.

You may receive complaints that some excel or word files are been hold by your username or username you used to install Office.

You can fix it the following way.

Search for the user in registry
One of the keys under HKLMSOFTWAREMicrosoftWindowsCurentVersionInstallerUserData will have office instalation details.

Delete user RegOwner key Information.

Continue searching the registry right-click and delete the Username and UserInitials with problematic username

Additional information can be found here:http://support.microsoft.com/kb/2001595

You may see this error when you try to accept recurrence meeting ,which time was been updated.

To resolve this issue:

1. On the BES Server, click Start > Run and type regedit.
2. Navigate to the following registry HKEY_CURRENT_USERSoftwareMicrosoftOffice11.0OutlookOptionsCalendar.
3. Right-click the Calendar folder and click New > DWORD Value.
4. Type DisableMeetingRegeneration and press ENTER.
5. Double-click the new key and type 1 in the Value data field of the Edit String screen.
6. Click OK and close the Registry Editor.

Go to your device and delete BIS CICAL service book

To delete CICAL on BB device go to Settings–>Advanced Options –> Service Books
Locate BIS CICAL and delete it.

Than go to your BlackBerry Enterprise server , right click on user and pres “Resend Service Book”

Restart your device and meeting accepts should start working.

Scenario:

User is not been reconnected to same Terminal Server session.

The consequences can be duplicated sessions, profile location lose, locked files on storage and more.
After few hours I found that Microsoft have A HotFix that addresses the issue

KB article is: KB977541

I got this after installing some update, can’t say exactly which.
The problem symptom is that when you type anything in search bar it looks like that

To solve it.

Go to Run> type regedit.exe

Navigate to :HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurre ntVersionExplorerFolderTypes{EF87B4CB-F2CE-4785-8658-4CA6C63E38C6}TopViews

You will see a key named {00000000-0000-0000-0000-000000000000}
Just rename it to anything else like {00000000-0000-0000-0000-000000000000}.Orig

After you rename the key , start Task manager and kill the explorer.exe process

Run the process again from file>New Task (Run..)

Type in bar explorer.exe

And Walla!

It works!

Microsoft published a hotfix that addresses the issue in Windows 7 and 2008R2

http://support.microsoft.com/kb/977380

During migration from Exchange 2003 to 2007 we had the problem with Outlook 2007 client free busy response was slow , about 10 seconds to load .

To fix it .
Open registry editor on your Desktop(where outlook is installed)

Navigate to the following path : HKEY_CURRENT_USERSoftwareMicrosoftOffice12.0OutlookOptionsCalendar
Create new DWORD value named UseLegacyFB and set value to 1

Note:
0 or not set will use default outlook settings
1 will use Public Folder based Free/Busy information

Read KB958934 to get more information.