Page 323 of 1,002« First...102030...321322323324325...330340350...Last »

MS11-023: Description of the security update for Office 2008 for Mac 12.2.9 Update: April 12, 2011

Microsoft has released security bulletins MS11-021, MS11-022, and MS11-023. These security bulletins contain all the relevant information about the security update for Microsoft Office 2008 for Mac. To view the complete security bulletins, visit the following Microsoft websites:
The Office 2008 for Mac 12.2.9 Update contains several changes that improve security, stability, reliability, and performance. In addition, this update includes fixes for vulnerabilities that an attacker can use to overwrite the contents of a computer’s memory by using malicious code.

Improvements that are included in the update

The Office 2008 for Mac 12.2.9 Update includes the following improvements.

Improvements for all Microsoft Office 2008 for Mac applications

  • Security is improved
    This update fixes vulnerabilities in Office 2008 that an attacker can use to overwrite the contents of your computer’s memory with malicious code. For more information, see the security bulletin that is listed earlier in this document.
  • Stability is improved
    This update fixes an issue that causes Office 2008 applications to exit unexpectedly when you open or use Office 2008 applications.
  • Additional support for OneDrive (formerly SkyDrive) and Microsoft SharePoint
    This update adds support for OneDrive (formerly SkyDrive) and Forms Based Authentication, a service that SharePoint requires. 

Improvements for Microsoft PowerPoint 2008 for Mac

  • Compatibility with Windows versions Microsoft PowerPoint is improved
    This update fixes an issue that causes numbered lists to display incorrect numbering when you open a file that you created in a Windows version of PowerPoint.

Improvements for Microsoft Entourage 2008 for Mac

  • Conversation headers are displayed correctly
    This update fixes an issue that causes Entourage to display an incorrect number of unread email messages when you view messages by conversation. 

Previously released improvements included in this update

This update includes all the improvements that were released in all previous Office 2008 updates. For more information about the improvements in a previous update, click the following article number to view the article in the Microsoft Knowledge Base:

953822

(http://support.microsoft.com/kb/953822/
)

Description of the Microsoft Office 2008 for Mac 12.1.1 Update

956344

(http://support.microsoft.com/kb/956344/
)

Description of the Microsoft Office 2008 for Mac 12.1.2 Update

958267

(http://support.microsoft.com/kb/958267/
)

Description of the Microsoft Office 2008 for Mac 12.1.3 Update

960401

(http://support.microsoft.com/kb/960401/
)

Description of the Microsoft Office 2008 for Mac 12.1.5 Update

968694

(http://support.microsoft.com/kb/968694/
)

Description of the Microsoft Office 2008 for Mac 12.1.7 Update

971822

(http://support.microsoft.com/kb/971822/
)

Description of the Microsoft Office 2008 for Mac 12.1.9 Update

973254

(http://support.microsoft.com/kb/973254/
)

Description of the Microsoft Office 2008 for Mac 12.2.0 Update

974170

(http://support.microsoft.com/kb/974170/
)

Description of the Microsoft Office 2008 for Mac 12.2.1 Update

976828

(http://support.microsoft.com/kb/976828/
)

Description of the Microsoft Office 2008 for Mac 12.2.3 Update

980839

(http://support.microsoft.com/kb/980839/
)

Description of the Microsoft Office 2008 for Mac 12.2.4 Update

2028864

(http://support.microsoft.com/kb/2028864/
)

Description of the Microsoft Office 2008 for Mac 12.2.5 Update

2284162

(http://support.microsoft.com/kb/2284162/
)

Description of the Microsoft Office 2008 for Mac 12.2.6 Update

2422352

(http://support.microsoft.com/kb/2422352/
)

Description of the Microsoft Office 2008 for Mac 12.2.7 Update

2476512

(http://support.microsoft.com/kb/2476512/
)

Description of the Microsoft Office 2008 for Mac 12.2.8 Update

Before you install the Office 2008 12.2.9 Update, make sure that the computer is running Mac OS X 10.4.9 (Tiger) or a later version of the Mac OS X operating system.

To verify that the computer meets this prerequisite, click About This Mac on the Apple menu.

How to obtain the update

The following file is available for download from the Microsoft Download Center:

Collapse this imageExpand this image

Download the Download the Microsoft Office 2008 for Mac 12.2.9 package now.

(http://www.microsoft.com/downloads/details.aspx?FamilyID=84dfe3f4-a2a1-47b9-8da1-29ae67230918)

Release Date: April 12, 2011

For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:

119591

(http://support.microsoft.com/kb/119591/
)

How to obtain Microsoft support files from online services

Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

Updated Files

For a complete list of the files that this update adds or changes, double-click the update installer, and then on the File menu, click Show Files.

Notes

  • The Office 2008 12.2.9 Update is also available from Microsoft AutoUpdate. AutoUpdate is a program that automatically keeps Microsoft software up-to-date.

    To use AutoUpdate, start a Microsoft Office program. Then, on the Help menu, click Check for Updates.

    For more information about resources for Office 2008 for Mac, visit the following Microsoft website:

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

Article ID: 2505927 – Last Review: February 19, 2014 – Revision: 2.0


Applies to
  • Microsoft Office 2008 for Mac
  • Microsoft Office 2008 for Mac Business Edition
  • Microsoft Office 2008 for Mac Home and Student Edition
  • Microsoft Office 2008 for Mac Special Media Edition
  • Microsoft Entourage 2008 for Mac
  • Microsoft Excel 2008 for Mac
  • Microsoft PowerPoint 2008 for Mac
  • Microsoft Word 2008 for Mac
kbqfe kbfix kbbug kbsecurity kbsecbulletin kbsecvulnerability kbsurveynew kbexpertiseinter KB2505927

Original post:
MS11-023: Description of the security update for Office 2008 for Mac 12.2.9 Update: April 12, 2011

Description of the Office update: February 12, 2013

Product Update Access

2760350

(http://support.microsoft.com/kb/2760350/
)

Description of the Access 2013 update: February 12, 2013

Excel
2760339

(http://support.microsoft.com/kb/2760339/
)

Description of the Excel 2013 update: February 12, 2013

Lync
2767852

(http://support.microsoft.com/kb/2767852/
)

Description of the Lync 2013 update: February 2013

Lync
2760512

(http://support.microsoft.com/kb/2760512/
)

Description of the Lync 2013 update: February 2013

Office
2767916

(http://support.microsoft.com/kb/2767916/
)

Description of the 2007 Office system update: February 12, 2013

Office
2596620

(http://support.microsoft.com/kb/2596620/
)

Description of the 2007 Office system update: February 12, 2013

Office
2760631

(http://support.microsoft.com/kb/2760631/
)

Description of the Office 2010 update: February 12, 2013

Office
2553378

(http://support.microsoft.com/kb/2553378/
)

Description of the Office 2010 update: February 12, 2013

Office
2767864

(http://support.microsoft.com/kb/2767864/
)

Description of the Office 2013 update: February 12, 2013

Office
2767861

(http://support.microsoft.com/kb/2767861/
)

Description of the Office 2013 update: February 12, 2013

Office
2767856

(http://support.microsoft.com/kb/2767856/
)

Description of the Office 2013 update: February 12, 2013

Office
2767845

(http://support.microsoft.com/kb/2767845/
)

Description of the Office 2013 update: February 12, 2013

Office
2760318

(http://support.microsoft.com/kb/2760318/
)

Description of the Office 2013 update: February 12, 2013

Office
2760224

(http://support.microsoft.com/kb/2760224/
)

Description of the Office 2013 update: February 12, 2013

Office
2752025

(http://support.microsoft.com/kb/2752025/
)

Description of the Office 2013 update: February 12, 2013

Office
2737954

(http://support.microsoft.com/kb/2737954/
)

Description of the Office 2013 update: February 12, 2013

Office
2726996

(http://support.microsoft.com/kb/2726996/
)

Description of the Office 2013 update: February 12, 2013

Office
2726954

(http://support.microsoft.com/kb/2726954/
)

Description of the Office 2013 update: February 12, 2013

OneNote
2737968

(http://support.microsoft.com/kb/2737968/
)

Description of the OneNote 2013 update: February 12, 2013

Outlook
2767887

(http://support.microsoft.com/kb/2767887/
)

Description of the Outlook 2003 Junk Email Filter update: February 12, 2013

Outlook
2767848

(http://support.microsoft.com/kb/2767848/
)

Description of the Outlook 2007 Junk Email Filter update: February 12, 2013

Outlook
2596802

(http://support.microsoft.com/kb/2596802/
)

Description of the Outlook 2007 update: February 12, 2013

Outlook
982726

(http://support.microsoft.com/kb/982726/
)

Description of the Outlook 2010 Junk Email Filter update: February 12, 2013

Outlook
2597090

(http://support.microsoft.com/kb/2597090/
)

Description of the Outlook 2010 update: February 12, 2013

Outlook
2760587

(http://support.microsoft.com/kb/2760587/
)

Description of the Outlook 2013 Junk Email Filter update: February 12, 2013

PowerPoint
2598240

(http://support.microsoft.com/kb/2598240/
)

Description of the PowerPoint 2010 update: February 12, 2013

SharePoint Designer
2767858

(http://support.microsoft.com/kb/2767858/
)

Description of the SharePoint Designer 2013 update: February 12, 2013

OneDrive for Business (formerly SkyDrive Pro)
2760214

(http://support.microsoft.com/kb/2760214/
)

Description of the OneDrive for Business 2013 update: February 12, 2013

Visio
2760568

(http://support.microsoft.com/kb/2760568/
)

Description of the Visio 2013 update: February 12, 2013

Word
2767854

(http://support.microsoft.com/kb/2767854/
)

Description of the Word 2013 update: February 12, 2013

Word
2760244

(http://support.microsoft.com/kb/2760244/
)

Description of the Word 2013 update: February 12, 2013

Read the article:
Description of the Office update: February 12, 2013

The TechNet "Events and Errors Message Center" offers detailed explanations, recommendations, and additional resources that apply to event IDs

This article contains a link to the TechNet “Events and Errors Message Center.” You can use the “Events and Errors Message Center” to find detailed explanations of event IDs that are logged on the computer. You can also find recommendations for specific user actions to perform in response to these events.

When you search for an event or for an error at the TechNet “Events and Errors Message Center,” the search results provide detailed explanations of the event or of the error. The results also recommend particular resolutions for the event or for the error.

Additionally, the “Events and Errors Message Center” contains links to Microsoft Knowledge Base articles and to other resources that are related to the event or to the error.

For more information about “Events and Errors Message Center,” visit the following Microsoft Web site:

To perform an advanced search, type one or more of the following parameters in the appropriate box, and then press ENTER:

  • Event ID
  • Event source
  • Message text
  • File name

Note You can find these values in the Event Viewer logs.

Article ID: 939422 – Last Review: February 18, 2014 – Revision: 2.0


Applies to
  • Microsoft .NET Framework 1.0
  • Microsoft .NET Framework 2.0
  • Microsoft BizTalk Server 2004 Standard Edition
  • Microsoft BizTalk Server 2004 Enterprise Edition
  • Microsoft Exchange Server 2007 Enterprise Edition
  • Microsoft Exchange Server 2007 Standard Edition
  • Microsoft Exchange Server 2003 Enterprise Edition
  • Microsoft Exchange Server 2003 Standard Edition
  • Microsoft Exchange 2000 Server Standard Edition
  • Microsoft Host Integration Server 2004 Standard Edition
  • Microsoft Internet Security and Acceleration Server 2000 Standard Edition
  • Microsoft Internet Security and Acceleration Server 2006 Enterprise Edition
  • Microsoft Internet Security and Acceleration Server 2004 Standard Edition
  • Microsoft Money 2007 Premium
  • Microsoft Money 2007 Deluxe
  • Microsoft Money 2007 Home & Business
  • Microsoft Money 2006 Premium
  • Microsoft Money 2006 Small Business
  • Microsoft Money 2006 Standard
  • Microsoft Money 2005 Premium Edition
  • Microsoft Money 2005 Deluxe Edition
  • Microsoft Money 2005 Small Business Edition
  • Microsoft Money 2005 Standard Edition
  • Microsoft Money 2004 Standard Edition
  • Microsoft SQL Server 2000 Standard Edition
  • Microsoft SQL Server 2005 Enterprise Edition
  • Microsoft SQL Server 2005 Standard Edition
  • Microsoft SQL Server 2005 Express Edition
  • Microsoft SQL Server 2000 Reporting Services
  • Microsoft Windows Server 2003, Standard Edition (32-bit x86)
  • Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
  • Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
  • Microsoft Windows Server 2003, Web Edition
  • Microsoft Windows 2000 Server
  • Microsoft Windows 2000 Professional Edition
  • Microsoft Windows XP Professional
  • Microsoft Windows XP Home Edition
kbtshoot kbexpertiseinter kbinfo KB939422

Taken from:
The TechNet "Events and Errors Message Center" offers detailed explanations, recommendations, and additional resources that apply to event IDs

How to restore In-Place Hold and Litigation Hold settings in an Exchange 2013 hybrid deployment

This article describes how to restore In-Place Hold and Litigation Hold settings in an Exchange 2013 hybrid deployment.

In an Exchange Server 2013 hybrid deployment with or without on-premises Lync Server 2013

Restore In-Place Hold settings

To restore In-Place Hold settings, follow these steps:

  1. On the Exchange 2013 server, open the Exchange Admin Center by using on-premises admin credentials. 
  2. If your organization is enabled for a hybrid deployment with Exchange Online in Office 365, click the Enterprise tab in the navigation bar.

    Collapse this imageExpand this image

  3. Click compliance management, and then click in-place eDiscovery & hold.

    Collapse this imageExpand this image

  4. Select the In-Place Hold entry for which you want to restore In-Place Hold settings. Double-click it, or click Edit (

    Collapse this imageExpand this image

    ), to open the properties page.

    Collapse this imageExpand this image

  5. On the properties page, click In-Place Hold. The In-Place Hold settings for the user are displayed.

    Collapse this imageExpand this image

  6. Click to clear the Place content matching the search query in selected mailboxes on hold check box, and then click save.
  7. Reopen the same properties page, and then click In-Place Hold. Notice that the Place content matching the search query in selected mailboxes on hold check box is cleared.

    Collapse this imageExpand this image

  8. Click to select the Place content matching the search query in selected mailboxes on hold check box.

    Additionally, if you were using a time-based In-Place Hold, select Specify number of days to hold items relative to their received date, enter the duration, and then click save. Doing this restores any In-Place Hold settings that existed before the issue occurred.

  9. Repeat step 4 to step 8 for any other In-Place Hold entries that you have.

Restore Litigation Hold settings

To restore Litigation Hold settings, follow these steps:

  1. Open Exchange Management Shell, and connect to your on-premises Exchange Server 2013 deployment.
  2. To restore a user’s Litigation Hold duration setting, run the following command:
    Set-Mailbox  -LitigationHoldDuration 

    For example, to set NinaT’s Litigation Hold duration to 90 days, run the following command:

    Set-Mailbox NinaT -LitigationHoldDuration 90
  3. Repeat step 2 for each user whose Litigation Hold duration setting you want to restore.

In an Exchange Online deployment with on-premises Lync Server 2013, and is running the Windows Azure Active Directory Sync tool with hybrid enabled

To restore the Litigation Hold duration setting, follow these steps:

  1. Connect to Exchange Online by using remote PowerShell. For more info, go to Connect to Exchange Online Using Remote PowerShell

    (http://technet.microsoft.com/en-us/library/jj984289(v=exchg.150).aspx)

    .

  2. To restore a user’s Litigation Hold duration setting, run the following command:
    Set-Mailbox  -LitigationHoldDuration 

    For example, to set NinaT’s Litigation Hold duration to 90 days, run the following command:

    Set-Mailbox NinaT -LitigationHoldDuration 90
  3. Repeat step 2 for each user whose Litigation Hold duration setting you want to restore. 

After the next time that directory synchronization runs, the Lync 2013 server will pick up the restored Litigation Hold duration settings.

Still need help? Go to the Office 365 Community

(http://community.office365.com/)

 website or the Exchange TechNet Forums

(http://social.technet.microsoft.com/Forums/exchange/en-us/home?category=exchange2010%2Cexchangeserver)

.

Article ID: 2934398 – Last Review: February 15, 2014 – Revision: 1.0


Applies to
  • Microsoft Exchange Online
  • Microsoft Exchange Server 2013 Enterprise
  • Microsoft Exchange Server 2013 Standard
  • Microsoft Lync Server 2013
o365e o365m o365022013 after upgrade o365 o365a hybrid kbgraphic kbgraphxlink KB2934398

Continue Reading:
How to restore In-Place Hold and Litigation Hold settings in an Exchange 2013 hybrid deployment

Users who are dialed in to a Lync Online meeting can’t hear users who are joined through Lync

Microsoft Lync Online organizations that have audio conferencing enabled by partnering with an audio conferencing provider (ACP) provider such as Intercall, PGI, and BT may experience the following issues:
  • Some public switched telephone network (PSTN) dialed-in users can only hear other users who are dialed in, and Lync users can only hear Microsoft Lync users.
  • Dialed-in users may be intermittently dropped from the conference.
This is an intermittent failure and there is no workaround at this point.
Microsoft is investigating this issue and will post more information in this article when the information becomes available. If you experience this symptom, contact Lync Online technical support to report the outage.

Third-party information disclaimer

Collapse this imageExpand this image

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

Collapse this imageExpand this image

Article ID: 2934410 – Last Review: February 14, 2014 – Revision: 1.0

o365 o365e o365p o365a o365m o365022013 after upgrade kb3rdparty KB2934410

More:
Users who are dialed in to a Lync Online meeting can’t hear users who are joined through Lync

"MigrationPermanentException" error when you move a mailbox from Exchange Online to an on-premises Exchange 2010 server in a hybrid deployment

Assume that you have an Exchange hybrid deployment that includes on-premises Exchange 2010 servers. When you try to offboard or move a mailbox from Exchange Online to an Exchange 2010 server in your on-premises environment, you receive the following error message:
Error: MigrationPermanentException:

You shouldn’t migrate mailbox ‘‘ to Exchange 2010 or an earlier version while the user’s Instant Messaging contact list is stored in Exchange. If you do, the user could permanently lose access to their Instant Messaging contact list, which will cause serious data loss. The Exchange copy might be the only copy of this user’s contact list. To continue, please contact your Instant Messaging administrator and make sure that the user’s contact list is moved back to the Instant Messaging server. After this has been done, you should be able to complete this migration. If you must migrate the mailbox despite the potential data loss, you can do so by running ‎’Set-UMMailbox mailboxID -ImListMigrationCompleted $false‎’.

However, when you run the ‎Set-UMMailbox mailboxID -ImListMigrationCompleted $false‎ command as stated in the error message, you receive the following error message:

The Mailbox ‘@contoso.com’ isn’t enabled for unified messaging.

This problem occurs if the Lync 2013 contacts of the user who is associated with the mailbox are stored in the unified contact store in Exchange. By default, if the user signed in to Lync 2013, the unified contact store is enabled for that user. Additionally, the user’s Lync contacts are migrated from the Lync server to Exchange. 
Use the Set-Mailbox cmdlet together with the ImListMigrationCompleted parameter instead of the ‎Set-UMMailbox cmdlet. For example, run the following command:
Set-Mailbox @contoso.com -ImListMigrationCompleted $false

After you run the command, perform the mailbox move request. 

Note The $false setting in the ImListMigrationCompletedparameter indicates that the user’s contacts haven’t been migrated to Lync to preserve the contact list. Be aware that the solution in this section may result in data loss. Exchange 2010 doesn’t support the unified contact store feature in Lync 2013. Therefore, if you move a mailbox back to Exchange 2010 while the user’s Lync contacts are stored in the unified contact store, the user could lose access to his or her Lync contacts. You should first make sure that the user’s Lync contacts are moved back to Lync server before you move the mailbox to Exchange 2010.  

For more info about the Set-Mailbox cmdlet and the ImListMigrationCompleted parameter, see Set-Mailbox

(http://technet.microsoft.com/en-us/library/bb123981(v=exchg.141).aspx)

.

Still need help? Go to the Office 365 Community

(http://community.office365.com/)

 website or the Exchange TechNet Forums

(http://social.technet.microsoft.com/Forums/exchange/en-us/home?category=exchange2010%2Cexchangeserver)

.

Article ID: 2932443 – Last Review: February 14, 2014 – Revision: 2.0


Applies to
  • Microsoft Exchange Online
  • Microsoft Exchange Server 2010 Enterprise
  • Microsoft Exchange Server 2010 Standard
o365e o365m o365022013 after upgrade o365 o365a hybrid KB2932443

More:
"MigrationPermanentException" error when you move a mailbox from Exchange Online to an on-premises Exchange 2010 server in a hybrid deployment

"The task couldn’t sign in with user <domainename>extest_<id>" error message when test cmdlets fail

Symptom 1

The Test-OwaConnectivity and Test-ECPConnectivity cmdlets fail randomly in Microsoft Exchange Server 2010, and you receive the following error message:

The task couldn’t sign in with user extest_. Run Scriptsnew-TestCasConnectivityUser.ps1 to verify that the user exists on the Mailbox server  

Note The Microsoft Exchange management pack runs these test cmdlets regularly. Therefore, you will also experience this issue when you monitor your Exchange servers through SCOM.

Symptom 2

After many incorrect passwords are entered, the extest account becomes locked, and all test cmdlets fail.

This issue occurs because the date format that is set in the regional settings is not the same for all Exchange Server 2010-based servers that use the extest account. 
To resolve this issue, make sure that all Exchange servers on an Active Directory site that are using the extest account use the same regional settings. 

You can check the format for the current user, welcome screen, and new user account. To do this, click Region in Control Panel, click the Administrative tab, and then click Copy settings

You should set the same format for the welcome screen and the new user account for all Exchange servers that are using the extest account on the Active Directory site.

To change this information for a server, configure the date format. To do this, follow these steps: 

  1. In Control Panel, click Region, and then click Format for the user. 
  2. In Control Panel, click Region, click the Administrative tab, and then click Copy settings.  
  3. Use the two check boxes to copy the current user settings to the system settings for the welcome screen and the new user account.

Article ID: 2914460 – Last Review: February 14, 2014 – Revision: 3.0


Applies to
  • Microsoft Exchange Server 2010 Standard
  • Microsoft Exchange Server 2010 Enterprise

Read More:
"The task couldn’t sign in with user <domainename>extest_<id>" error message when test cmdlets fail

Microsoft Dynamics CRM Outlook client prompts for credentials

When accessing Microsoft Dynamics CRM records within the Microsoft Dynamics CRM for Microsoft Office Outlook client, a user may experience intermittent prompts for credentials.
The issue is due to an Internet Explorer problem which caused session cookies to be cleared out and require users to log in again.
This issue affects Internet Explorer 10 and 11.
Note This is a “FAST PUBLISH” article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use

(http://go.microsoft.com/fwlink/?LinkId=151500)

for other considerations.

Article ID: 2934024 – Last Review: February 14, 2014 – Revision: 2.0


Applies to
  • Microsoft Dynamics CRM 2011
  • Microsoft Dynamics CRM 2013
kbmbsmigrate kbsurveynew KB2934024

See original article:
Microsoft Dynamics CRM Outlook client prompts for credentials

"MigrationPermanentException" error when you try to move a mailbox from Exchange Online to an on-premises Exchange 2010 server in a hybrid deployment

Assume that you have an Exchange hybrid deployment that includes on-premises Exchange 2010 servers. When you try to offboard or move a mailbox from Exchange Online to an Exchange 2010 server in your on-premises environment, you get the following error message:
Error: MigrationPermanentException:

You shouldn’t migrate mailbox ‘‘ to Exchange 2010 or an earlier version while the user’s Instant Messaging contact list is stored in Exchange. If you do, the user could permanently lose access to their Instant Messaging contact list, which will cause serious data loss. The Exchange copy might be the only copy of this user’s contact list. To continue, please contact your Instant Messaging administrator and make sure that the user’s contact list is moved back to the Instant Messaging server. After this has been done, you should be able to complete this migration. If you must migrate the mailbox despite the potential data loss, you can do so by running ‎’Set-UMMailbox mailboxID -ImListMigrationCompleted $false‎’.

However, when you run the ‎Set-UMMailbox mailboxID -ImListMigrationCompleted $false‎ command as stated in the error message, you get the following error message:

The Mailbox ‘@contoso.com’ isn’t enabled for unified messaging.

This occurs if the Lync 2013 contacts of the user who is associated with the mailbox are stored in the unified contact store in Exchange. By default, if the user signed in to Lync 2013, the unified contact store is enabled for the user and the user’s Lync contacts are migrated from the Lync server to Exchange. 
Use the Set-Mailbox cmdlet together with the ImListMigrationCompleted parameter instead of the ‎Set-UMMailbox cmdlet. For example, run the following command:
Set-Mailbox @contoso.com -ImListMigrationCompleted $false

After you run the command, perform the mailbox move request. 

Note The $false setting in the ImListMigrationCompletedparameter indicates that the user’s contacts haven’t been migrated to Lync to preserve the contact list. Be aware that using these steps can result in potential data loss. Exchange 2010 doesn’t support the unified contact store feature in Lync 2013. Therefore, if you move a mailbox back to Exchange 2010 while the user’s Lync contacts are stored in the unified contact store, the user could lose access to their Lync contacts. You should first make sure that the user’s Lync contacts are moved back to Lync server before you move the mailbox to Exchange 2010.  

For more info about the Set-Mailbox cmdlet and the ImListMigrationCompleted parameter, go to Set-Mailbox

(http://technet.microsoft.com/en-us/library/bb123981(v=exchg.141).aspx)

.

Still need help? Go to the Office 365 Community

(http://community.office365.com/)

 website or the Exchange TechNet Forums

(http://social.technet.microsoft.com/Forums/exchange/en-us/home?category=exchange2010%2Cexchangeserver)

.

Article ID: 2932443 – Last Review: February 14, 2014 – Revision: 1.0


Applies to
  • Microsoft Exchange Online
  • Microsoft Exchange Server 2010 Enterprise
  • Microsoft Exchange Server 2010 Standard
o365e o365m o365022013 after upgrade o365 o365a hybrid KB2932443

View post:
"MigrationPermanentException" error when you try to move a mailbox from Exchange Online to an on-premises Exchange 2010 server in a hybrid deployment

Impersonation rights are not working in Office 365 Dedicated/ITAR

In Microsoft Office 365 Dedicated/ITAR, a user is a member of one of the following role groups but cannot impersonate Microsoft Exchange users:
  • EWS Impersonation role group in Exchange Server 2010
  • SSA-ApplicationImpersonation baseline role group or another role group that’s associated with the SSA_ApplicationImpersonation management role in Exchange Server 2013
This issue occurs if the custom application is set up incorrectly.
To resolve this issue, use EWSEditor to make sure that the roles in the O365 Dedicated/ITAR environment enable Exchange Web Service (EWS) impersonation. To do this, follow these steps:
  1. Download EWSEditor from http://ewseditor.codeplex.com

    (http://ewseditor.codeplex.com/)

    , and then extract the application.

  2. Open EWSEditor.exe.
  3. On the File menu, click New Exchange Service.
  4. By default, this prompts for your SMTP address. Use Autodiscover to determine the correct URL to connect to. If you know the EWS URL, you can clear the Use Autodiscover to get the Exchange Web Services URL check box and then enter the URL manually.
  5. Select the correct version of Exchange or the most recent version if your version isn’t listed.
  6. Select the Use the following credentials instead of the default Windows credentials check box, and then enter the account credentials that have impersonation rights. If you logged on to Windows through this account, this step isn’t necessary.
  7. Make sure that the Use impersonation to log on to another mailbox using the credentials specified on the credentials tab by identifying the mailbox Id below check box is selected, specify the criteria for the target user, and then click OK.

    Collapse this imageExpand this image

  8. You should be prompted by a “Do you want to automatically add the mailbox root to the tree view?” message. Click Yes.

    Collapse this imageExpand this image

  9. Expand the tree view. If you can see folders or content, impersonation rights are working.
  10. If you receive a “The account does not have permissions to…” error, contact Microsoft Online Services Support by online submission

    (http://support.microsoft.com/kb/2694621/
    )

    or by telephone

    (http://support.microsoft.com/kb/2573289/
    )

    .

Article ID: 2932679 – Last Review: February 13, 2014 – Revision: 2.0


Applies to
  • Microsoft Business Productivity Online Dedicated
  • Microsoft Business Productivity Online Suite Federal
vkbportal226 kbgraphxlink KB2932679

Taken from:
Impersonation rights are not working in Office 365 Dedicated/ITAR

Page 323 of 1,002« First...102030...321322323324325...330340350...Last »

Recent Comments

    Archives

    Categories