Windows PowerShell 1.0 English-Language Installation Package for Windows XP (KB926139)

Download Link

Source Link

Windows PowerShell includes:

• More than 130 command-line tools (called "cmdlets") for performing common system administration tasks, such as managing services, processes, event logs, certificates, the registry, and using Windows Management Instrumentation (WMI).

• Command-line tools are designed to be easy to learn and easy to use with standard naming conventions and common parameters, and simple tools for sorting, filtering, and formatting data and objects.

• Support for existing scripting languages and existing command-line tools, and multiple versions of Windows, including Windows XP, Windows Server 2003, Windows Vista™, and Windows Server code name “Longhorn".

• Features that enable users to navigate data stores, like the registry and certificate stores, as if they were a file system.

• Standard utilities for managing Windows data in different stores and formats, including Active Directory Service Interfaces (ADSI), Windows Management Instrumentation (WMI), Component Object Model (COM) objects, ActiveX Data Objects (ADO), HTML, and XML.

• Sophisticated expression parsing and .NET Framework object manipulation at the command line, including pipelining of objects help IT professionals to work more efficiently and effectively.

• An extensible interface that enables independent software vendors and enterprise developers to build custom cmdlets to meet unique application and system administration requirements.

Which version should I install?

• English. If you are running an English-language version of Windows, or a version of Windows localized for a language other than German, Spanish, French, Italian, Japanese, Korean, Portuguese, Russian, Chinese Simplified, or Chinese Traditional, use the Download link on this page to install an English-language version of Windows PowerShell 1.0. For more information, see Knowledge Base article 926139.

• Localized. If you are running a localized version of Windows for German, Spanish, French, Italian, Japanese, Korean, Portuguese, Russian, Chinese Simplified, or Chinese Traditional, use the Windows PowerShell 1.0 Localized Installation Package. For more information, see Knowledge Base article 926140.

• MUI Language Pack. If you are running a multilingual interface (MUI) versions of Windows, which displays the Windows interface in multiple languages, install the English-language version of Windows PowerShell 1.0, and then install the Windows PowerShell 1.0 MUI Language Pack. The MUI Language Pack does not include the Windows PowerShell program. For more information, see Knowledge Base article 926141.

Before installing Windows PowerShell 1.0, you must uninstall any other versions of Windows PowerShell 1.0. You do not need to restart your computer after installing Windows PowerShell 1.0 unless files from other versions of Windows PowerShell 1.0 are being used by another program during the installation.

Microsoft Exchange Server Outlook Web Access Web Administration

Download Link


The Outlook Web Access (OWA) administration tool provides web-based UI for all administrator tunable OWA settings. It provides a list of all servers in the domain and allows administration of OWA settings on all Front-end and Back-end servers. The tool ensures that settings are correctly written to the server’s registry and provides inline documentation for all configurable features.

Language Selection in Exchange 2007 OWA

Per-user options

Although many Exchange customers standardize on a single language, individual users may feel more comfortable working in a particular language. Microsoft, for example, standardized on U.S. English, but it has offices and employees from all over the world. Some of them may feel more comfortable using applications in their native languages, while still communicating in U.S. English. In Exchange 2003, OWA used the user's client language. That is, it used whatever language IE was set to. While this worked in some cases, it didn't solve the problem in many others. For example, a user at an airport kiosk in New York may have had to use OWA in U.S. English, when this user would have preferred Japanese.

In Exchange 2007, we've made this experience better for everyone, whether you're using OWA from a personal machine or an airport kiosk. The first time a user logs on, OWA displays the Regional Language selection page. The language he chooses here will be the language OWA uses for menus, labels, and other text.

Users can change the language selection in the Options page:

Global options

In many cases, forcing users to choose a language on first log on can be important. However, this doesn't have to be the case. Administrators can use the OWA admin tasks to configure the language users see when the log on to OWA as well as the language of the forms-based authentication (FBA) login page. Users are still free to change the language for their individual OWA profile. The -DefaultClientLanguage and -LogonAndErrorLanguage parameters to Set-OwaVirtualDirectory control the default language for OWA and the FBA login page, respectively. LogonAndErrorLanguage also sets the language that error messages are presented in if the user's language selection can't be read. Both of these parameters take a locale identifier (LCID), which is just a number between 0 and 99999999. A value of 0, which is the default, means that the language selection is undefined, so the user should be prompted. For example, to set the default client, logon, and error languages to English - UK (LCID 2057):

[MSH]> Set-OwaVirtualDirectory -identity "owa (Default Web Site)" -DefaultClientLanguage:2057 -LogonAndErrorLanguage:2057

Solving "e-mail address already exists in this organization" using LDAP query in AD

Link Source

A administrator is having a problem creating an SMTP proxy address for a mailbox. The message they get when they try to add as an SMTP address is "This e-mail address already exists in this organization. ID no: c10312e7 Microsoft Active Directory - Exchange Extension".

The SMTP address the admin is trying to assign is already assigned to another mail-enabled object (mailbox, mail-enabled user, contact, or mail-enabled group.) I suggested doing an LDIFDE dump to LDF file of the entire directory and seaching through that file. Rich Matheisen suggested a better and far faster way.

Using the Windows 2003 Active Directory Users and Computers utility, right click on the domain, choose Find. In the Find: dropdown list, choose "Custom Search" and in the In: dropdown list, choose "Entire Directory". Click the Advanced property page and enter the following LDAP query (in my example, at least):

Click Find and you should find the object that already has that SMTP address.