Page 22 of 749« First...10...2021222324...304050...Last »

A description of the support of the localized Outlook client in Exchange 2000 Server

This article describes the support of the localized Microsoft Outlook client in Microsoft Exchange 2000 Server.

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
In Microsoft Exchange Server 5.5, you had to add a code page to Microsoft Windows NT Server and locales to Exchange Server to enable the support of multiple languages. In Exchange 2000, however, this situation has changed.

In a multiple language or localized environment, some user display names may be in English and others may be in localized languages, such as, German, French, or Chinese. When an Outlook client views the global address book, the display names may be not sorted correctly.

Exchange 2000 does not have an independent directory service, and Exchange 2000 is closely integrated with Microsoft Windows 2000 Active Directory. When a Microsoft Outlook 2000 client attempts to obtain the global address book, the client directly contacts the preferred global catalog. For an earlier-version Outlook client, Exchange 2000 server can obtain the global address book from global catalog and forward it to the client.

To have the global address book sorted correctly, you must configure Windows 2000 domain controller and global catalog to support the languages that are going to be used. To do so, you must perform the following steps on all global catalogs and domain controllers:

  1. In Control Panel, double-click Regional Options.
  2. On the General tab, under the Language settings for the system section, click to select the check box for the language that is going to be supported.
  3. Restart your computer for the changes to take affect.
  4. Start Registry Editor (Regedit.exe).
  5. Click to expand the following subkey in the registry:

    HKEY_LOCAL_MACHINE/Software/Microsoft/Ntds/Language

  6. Right-click Language, point to New, and then click DWORD Value. Enter a name for the string, and then press ENTER.
  7. Right-click the DWORD value that you just created, and then click Modify. In Value data, enter the value of the locale identification (ID) that you want to support.
  8. Restart the global catalogs and domain controllers.

For list of locale identification (LCID) numbers, visit the following Microsoft Web site:

http://office.microsoft.com/en-us/word-help/locale-identification-numbers-for-language-specific-files-HA010351417.aspx

(http://office.microsoft.com/en-us/word-help/locale-identification-numbers-for-language-specific-files-HA010351417.aspx)

Article ID: 301314 – Last Review: August 1, 2014 – Revision: 4.0


Applies to
  • Microsoft Exchange 2000 Server Standard Edition
kbnosurvey kbhowto kbarchive KB301314

Link:
A description of the support of the localized Outlook client in Exchange 2000 Server

"403 Sorry! Access denied" error when a user tries to sign in to Outlook Web App in Office 365

403
Sorry! Access denied :(

The page may not be available or you might not have permission to open the page. Please contact your administrator for the required credentials. For new credentials to take effect, you have to close this window and log on again

Taken from:
"403 Sorry! Access denied" error when a user tries to sign in to Outlook Web App in Office 365

How to change your user photo in Office 365 by using Outlook Web App

This article describes how to use Outlook Web App to change your user photo that’s displayed in Exchange Online in Office 365, Lync 2013, and Lync Web App. 
To use Outlook Web App to update your user photo in Exchange Online, Lync 2013, and Lync Web App, follow these steps: 
  1. Sign in to Outlook Web App.
  2. Click Settings (

    Collapse this imageExpand this image

    ), click Options, and then on the My account page, click Edit information.

  3. On the account information page, click photo, click change, and then click Browse.
  4. Browse to the picture that you want to use for your user photo, and then select it.
  5. Wait for the picture to upload. This may take some time, depending on the size of the picture and the network connection.
  6. Click save.
In Office 365, user photos are stored in the following locations:
  • A low-resolution photo (less than 100 KB) is stored in the user’s ThumbnailPhoto attribute in Active Directory. This is the photo that’s synchronized to Office 365 in a hybrid environment. Low-resolution photos are used by Lync 2010.
  • A high-resolution photo is stored in the root directory of the user’s Exchange Online mailbox.  High-resolution photos are displayed in Exchange Online, Lync 2013, and Lync Web App.

Still need help? Go to the Office 365 Community

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

website.

Article ID: 2986893 – Last Review: July 31, 2014 – Revision: 2.0


Applies to
  • Microsoft Exchange Online
  • Microsoft Lync Online
  • Microsoft Lync 2013
  • Microsoft Lync Web App
o365e o365p o365m o365022013 o365 o365a kbgraphic kbgraphxlink KB2986893

View article:
How to change your user photo in Office 365 by using Outlook Web App

July 8, 2014 update for Office 2010 spelling and grammar check feature (KB2881028)

This article describes update KB2881028 for Microsoft Office 2010 that was released on July 8, 2014. 

This update include the latest fix for spelling and grammar check feature in Office 2010. It updates some dictionaries and grammar rules.

Windows Update

Use Windows Update

(http://update.microsoft.com/microsoftupdate/v6/default.aspx)

to automatically download and install the update.

Download Center

This update is also available for manual download and install from the Microsoft Download Center. If you are not sure what platform (32-bit or 64-bit) you’re running, see Am I running 32-bit or 64-bit Office

(http://office.microsoft.com/en-001/support/am-i-running-32-bit-or-64-bit-office-HA010361023.aspx)

.

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

Virus-scan claim

Collapse this imageExpand this image

Microsoft scanned this file for viruses, using 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 it.

Collapse this imageExpand this image

Restart information

You do not have to restart the computer after you install this update.

Prerequisites

To apply this update, you must have either Microsoft Office 2010 Service Pack 1 (SP1) or Service Pack 2 (SP2) installed. For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:

2460049

(http://support.microsoft.com/kb/2687455/en-us)

Description of Office 2010 SP1

2687455

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

Description of Office 2010 SP2

File Information

Collapse this imageExpand this image

This update contains the files that are listed in the following tables.

32-bit

proof-en-us.msp file information

Collapse this tableExpand this table

File name File version File size Date Time
Css7data0009.dll 14.0.7125.5000 495,864 14-May-2014 21:41
Mscss7cm_en.dub 14.0.7125.5000 3,072 13-May-2014 14:43
Mscss7en.dll 14.0.7005.1000 307,336 31-Oct-2012 04:41
Mscss7wre_en.dub 14.0.7125.5000 102,912 13-May-2014 14:43
Msgr3en.dll 3.1.0.17519 3,214,056 12-Sep-2011 17:06
Mshy7en.dll 14.0.7005.1000 182,888 31-Oct-2012 04:41
Mshy7en.lex 14.0.7001.1000 475,136 23-Aug-2012 05:26
Mssp7en.dll 14.0.7107.5000 1,589,448 07-Aug-2013 11:27
Mssp7en.dub Not Applicable 416 13-May-2014 14:44
Mssp7en.lex 14.0.7125.5000 1,277,952 13-May-2014 14:44
Msth7en.dll 14.0.7005.1000 342,648 31-Oct-2012 04:41
Msth7en.lex 14.0.7125.5000 4,259,840 13-May-2014 14:43
Nl7models0009.dll 14.0.7125.5000 5,785,848 14-May-2014 21:41

64-bit

proof-en-us.msp file information

Collapse this tableExpand this table

File name File version File size Date Time
Css7data0009.dll 14.0.7125.5000 595,192 14-May-2014 21:41
Mscss7cm_en.dub 14.0.7125.5000 3,584 13-May-2014 14:47
Mscss7en.dll 14.0.7005.1000 480,904 31-Oct-2012 04:46
Mscss7wre_en.dub 14.0.7125.5000 103,424 13-May-2014 14:47
Mshy7en.dll 14.0.7005.1000 224,376 31-Oct-2012 04:46
Mshy7en.lex 14.0.7001.1000 475,648 23-Aug-2012 05:45
Mssp7en.dll 14.0.7107.5000 2,025,160 07-Aug-2013 11:42
Mssp7en.dub Not Applicable 416 13-May-2014 14:47
Mssp7en.lex 14.0.7125.5000 1,278,464 13-May-2014 14:47
Msth7en.dll 14.0.7005.1000 455,288 31-Oct-2012 04:46
Msth7en.lex 14.0.7125.5000 4,260,352 13-May-2014 14:46
Nl7models0009.dll 14.0.7125.5000 5,786,360 14-May-2014 21:41

How to uninstall this update

Collapse this imageExpand this image

Windows 7, Windows Vista and Windows XP

  1. Click Start, and then click Run.
  2. Type Appwiz.cpl, and then click OK.
  3. Use one of the following procedures, depending on the operating system that you are running.
    • Windows 7 and Windows Vista

      1. Click View installed updates.
      2. In the list of updates, locate and click update KB2881028, and then click Uninstall.
    • Windows XP
      1. Click to select the Show updates check box.
      2. In the list of updates, locate and click update KB2881028, and then click Remove.

Windows 8

  1. Swipe in from the right edge of the screen, and then tap Search. If you are using a mouse, point to the lower-right corner of the screen, and then click Search.
  2. Type windows update, tap or click Settings, and then tap or click View installed updates in the search results.
  3. In the list of updates, locate and then tap or click update KB2881028, and then tap or click Uninstall.

Collapse this imageExpand this image

The Office System TechCenter contains the latest administrative updates and strategic deployment resources for all Versions of Office. For more information about the Office System TechCenter, go to the following Microsoft website:

Article ID: 2881028 – Last Review: July 31, 2014 – Revision: 2.0


Applies to
  • Microsoft Office Home and Business 2010
  • Microsoft Office Home and Student 2010
  • Microsoft Office Professional 2010
  • Microsoft Office Professional Academic 2010
  • Microsoft Office Professional Plus 2010
  • Microsoft Office Standard 2010
  • Microsoft Office Starter 2010
atdownload kbsurveynew kbexpertisebeginner KB2881028

Read more here:
July 8, 2014 update for Office 2010 spelling and grammar check feature (KB2881028)

WCF Service does not start automatically when messages are available through MSMQ

An IIS application pool is hosting two distinct WCF services where one uses the net.msmq binding and the other uses msmq.formatname binding. When messages to the WCF service that use the net.msmq binding are pending in the MSMQ queue, the WCF service will not automatically start.
This is by design. WAS is designed so that when a single IIS application pool has multiple WCF services that use mixed msmq binding types, the msmq.formatname service takes precedence, and the flag to restart the net.msmq service is set to ” no “. Therefore only the service that uses msmq.formatname will automatically start the w3wp process for that application pool when messages become available in the MSMQ queue.
The workaround is to use two separate application pools for your WCF services, separating the two different msmq bindings.

Article ID: 2974327 – Last Review: July 31, 2014 – Revision: 1.0


Applies to
  • Windows Communication Foundation 3.0
  • Windows Communication Foundation 3.5
  • Windows Communication Foundation 4
  • Windows Communication Foundation 4.5
  • Microsoft Internet Information Services 7.0
  • Microsoft Internet Information Services 7.5
  • Microsoft Internet Information Services 8.0
  • Microsoft Internet Information Services 8.5

Read More:
WCF Service does not start automatically when messages are available through MSMQ

Auto-replies aren’t generated in an Office 365 dedicated High Availability (ANSI-D) environment

Consider the following scenario: 
  • In a Microsoft Office 365 dedicated High Availability (ANSI-D) environment, you set a mailbox to forward messages to an alternative recipient by using the ForwardingSMTPAddress parameter. That is, you set messages to be delivered to both the original recipient and the forwarded recipient.
  • You also set up an auto-reply of some type for the mailbox. For example, the auto-reply is a Microsoft Outlook rule or an out-of-office (OOF) message.

In this scenario, the message is forwarded as expected. However, the auto-reply isn’t generated.

In Office 365 dedicated ANSI-D, the XLOOP header limit for a given message is set to one (1). This issue occurs because the following forwarding or auto-reply options increase the XLOOP header value: These options can’t be used in combination. 
If you must use both message forwarding and an OOF message or an Outlook auto-reply rule, you should use the ForwardingAddress parameter instead of the ForwardingSMTPAddress parameter when you set up mailbox forwarding.

Note The ForwardingSMTPAddress parameter can take any valid SMTP address as an input. However, the ForwardingAddress parameter requires a Microsoft Exchange Server user object as its value. The object may be a mailbox-enabled user, a mail-enabled user, or a mail-enabled contact. If no such object exists in the Office 365 dedicated environment, you must create a new user or contact in Active Directory Domain Services (AD DS) for the on-premises environment and then synchronize to Office 365 through Microsoft Managed Services Service Provisioning Provider (MMSSPP). 

To set up mailbox forwarding to use an Exchange Server object, run the following cmdlets:

Set-Mailbox John@contoso.com –ForwardingSMTPAddress $NULL
Set-Mailbox John@contoso.com –ForwardingAddress Mike@wingtiptoys.com

Article ID: 2988783 – Last Review: July 30, 2014 – Revision: 1.0


Applies to
  • Microsoft Business Productivity Online Dedicated
  • Microsoft Business Productivity Online Suite Federal

Link:
Auto-replies aren’t generated in an Office 365 dedicated High Availability (ANSI-D) environment

Your mailbox can’t be accessed or has limited functionality after a mailbox plan is changed from Kiosk to another plan in Office 365 dedicated/ITAR

In Microsoft Office 365 dedicated/ITAR, you can’t access your mailbox, or the mailbox experiences limited functionality of a specific feature. This behavior occurs after a mailbox plan is changed from Exchange Online Kiosk D to Exchange Online Plan 1D or Exchange Online Plan 2D.
This behavior occurs because the client access settings aren’t set for the Exchange Online Plan 1D or Exchange Online Plan 2D in the mailbox plan provisioning process.
The provisioning process that uses the SetMailboxType script is replaced by the mailbox plan provisioning process in Microsoft Office 365 dedicated/ITAR. This process includes the 13.1 version (for Exchange Server 2010) and the 2013 version (for Exchange Server 2013).

The mailbox plan provisioning process uses the following client access settings, depending on the plan class.

Collapse this tableExpand this table

Plan class Customer managed settings Settings managed by the mailbox plan provisioning process only
Standard (Exchange Online Plan 1D or Exchange Online Plan 2D plans)
  • MAPIBlockOutlookVersions
  • ActiveSyncEnabled
  • EWSEnabled
  • IMAPEnabled
  • MAPIEnabled
  • OWAEnabled
  • POPEnabled
  • OWAMailboxPolicy
Exchange Online Kiosk D
  • ActiveSyncEnabled
  • OWAEnabled
  • POPEnabled
  • MAPIBlockOutlookVersions
  • EWSEnabled
  • IMAPEnabled
  • MAPIEnabled
  • OWAMailboxPolicy

Notes

  • For the Exchange Online Plan 1D and Exchange Online Plan 2D plans, all settings are customer managed. Therefore, no changes are made to these settings when you move to these plans.
  • For the Exchange Online Kiosk D plan, several settings are fully managed by the mailbox plan provisioning process. These settings are maintained on each run of the script. Customer managed settings aren’t changed. 

Changes made by the mailbox plan provisioning process

The mailbox plan provisioning process makes changes to a mailbox object in the following scenarios.

Scenario 1: Initial processing of a mailbox (for Exchange Server 2010 only)

The mailbox plan provisioning process sets all access and quota settings to their default values for both customer managed and mailbox plan provisioning process-managed clients. In Exchange Server 2013, Microsoft Managed Services Service Provisioning Provider (MMSSPP) applies the client access and quota settings when the mailbox is created.

Scenario 2: Changes of the plan in the plan class (Exchange Online Plan 1D to Exchange Online Plan 2D)

Only the quota is updated (if it’s different) because client access settings that are customer managed aren’t updated.

Scenario 3: Changes of the plan class

  • Exchange Online Plan 1D or Exchange Online Plan 2D to Exchange Online Kiosk D

    The mailbox quota is updated (if it’s different). The client access settings that are managed by the mailbox plan provisioning process are updated.

  • Exchange Online Kiosk D to Exchange Online Plan 1D or Exchange Online Plan 2D

    The mailbox quota is updated (if it’s different). No client access settings are changed because all the settings are customer managed.

Scenario 4: Management of the Exchange Online Kiosk D plan settings

The Mailbox Plans provisioning process sets any of the settings to the plan defaults if there are any changes.

Scenario 5: Mailbox moved from on-premises Lotus Notes environment (Exchange Server 2010 only)

The mailbox plan provisioning process sets all access and quota settings to their default values for both customer-managed and mailbox plan provisioning process-managed clients. In Exchange Server 2013, MMSSPP applies the quota and client access settings when the mailbox is created.

Scenario 6: Mailbox moved from on-premises Exchange environment

The mailbox quota is set. Any other client access settings that are managed by the mailbox plan provisioning process are updated.

This behavior is by design.

Article ID: 2987640 – Last Review: July 30, 2014 – Revision: 1.0


Applies to
  • Microsoft Business Productivity Online Dedicated
  • Microsoft Business Productivity Online Suite Federal

Visit link:
Your mailbox can’t be accessed or has limited functionality after a mailbox plan is changed from Kiosk to another plan in Office 365 dedicated/ITAR

Apostrophe and dash not supported in user SIP address in a Lync Server 2010 or Lync Server 2013 environment

Microsoft Lync Server 2010 and Microsoft Lync Server 2013 do not support user SIP addresses that contain an apostrophe (‘) or a dash (-). 

If a user (user A) uses a SIP address that contains an apostrophe (‘) or a dash (-), the user may encounter multiple issues intermittently. For example, user A may encounter the following issues:
  • A user (user B) cannot join a Lync meeting that is created by user A.
  • A user (user B) cannot add user A as a contact by inputting user A’s SIP address. Additionally, user B receives the following error message:
  • User A receives a warning when he or she signs in to a Lync client.
  • User A misses meetings on a Lync client.
  • User A loses access to an important communication and collaboration tool.

Article ID: 2716467 – Last Review: July 30, 2014 – Revision: 3.0


Applies to
  • Microsoft Lync Server 2010 Enterprise Edition
  • Microsoft Lync Server 2010 Standard Edition
  • Microsoft Lync Server 2013
kbqfe kbsurveynew kbexpertiseinter kberrmsg KB2716467

Read More:
Apostrophe and dash not supported in user SIP address in a Lync Server 2010 or Lync Server 2013 environment

Only OWA Light mode is available when you access an Office 365 dedicated/ITAR mailbox

When you use Internet Explorer 8 to access a Microsoft Office 365 dedicated/ITAR mailbox in Microsoft Exchange Server 2013, only Microsoft Outlook Web App (OWA) Light mode is available.

This is expected behavior. OWA Light mode is the only option that you have when you use Internet Explorer 8 in Exchange Server 2013.

For more information about browser support, see What’s new for Outlook Web App in Exchange 2013

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

.

Article ID: 2987965 – Last Review: July 29, 2014 – Revision: 1.0


Applies to
  • Microsoft Business Productivity Online Dedicated
  • Microsoft Business Productivity Online Suite Federal

More here:
Only OWA Light mode is available when you access an Office 365 dedicated/ITAR mailbox

You can’t manage Send As and Send on Behalf permissions for shared mailboxes in the EAC in Office 365 dedicated/ITAR

When you sign in to the Exchange admin center (EAC) in Microsoft Office 365 dedicated/ITAR, you see limited options to set the permissions of a shared mailbox. The options to individually manage the “Send As” and “Send on Behalf” permissions are available for user mailboxes. However, only the option to manage full mailbox permissions are available for shared mailboxes.
This issue occurs because the “Send As” and “Send on Behalf” permissions can’t be managed in the EAC.
To work around this issue, add the “Send As” and “Send on Behalf” permissions by using Windows Remote PowerShell. To do this, follow the instructions on the following Microsoft TechNet website:
For more information about shared mailboxes, see the following Microsoft TechNet website:
Shared Mailboxes

(http://technet.microsoft.com/en-us/library/jj150498%28v=exchg.150%29.aspx)

Article ID: 2988058 – Last Review: July 29, 2014 – Revision: 1.0


Applies to
  • Microsoft Business Productivity Online Dedicated
  • Microsoft Business Productivity Online Suite Federal

Original post:
You can’t manage Send As and Send on Behalf permissions for shared mailboxes in the EAC in Office 365 dedicated/ITAR

Page 22 of 749« First...10...2021222324...304050...Last »

Recent Comments

    Archives

    Categories