Free eBook: Microsoft Office 365: Connect and Collaborate Virtually Anywhere, Anytime

Microsoft released Microsoft Office 365: Connect and Collaborate Virtually Anywhere, Anytime (ISBN 9780735656949), by Katherine Murray, as a free eBook.

To download your free PDF eBook, click here or click on the picture. Updates to this eBook, as well as additional eBook formats, will become available in the future, so check this blog for updates.

Introduction

Let’s hear it for freedom. Freedom from your desk. Freedom from those ­boring managers’ meetings. Freedom to work anywhere, with anyone, anytime, on almost any device. Sounds good, right?

Office 365 is Microsoft’s smart and simple answer to cloud computing. Using the various programs in Office 365, you can do all the tasks you’re used to doing in your favorite Office applications—write documents, create presentations, check email, manage your calendar, crunch numbers, and more—and then share what you create in real time on a team site, design and publish a website, and even create and host live online meetings while you’re traveling on the train, sitting in a coffee shop, or dialing in on your phone.

This book shows you how you can use cloud computing—and ­specifically, ­Office 365—to get more done, collaborate more easily, and work more ­flexibly than you ever have before. From the necessary how-tos about ­creating and administering your Office 365 account and working with the various Office 365 programs to sharing files with your team, creating a team site, using Office Web Apps, and holding online meetings, you’ll discover how easy it is to work online and off, accessing and sharing your files whenever you need to. After you learn about each of the core programs, you can try strategies for building successful teams, and get some good ideas on practical ways you can put all this cloud power to work.

Who This Book Is For

Microsoft Office 365: Connect and Collaborate Virtually Anywhere, Anytime is all about cloud solutions for small businesses, focusing on the core software services (Microsoft Exchange Online, Microsoft SharePoint Online, Office Web Apps, and Microsoft Lync), and demonstrating ways you can create, manage, and lead teams effectively using the communications and collaborative online tools.

A Quick Roadmap

Microsoft Office 365: Connect and Collaborate Virtually Anywhere, Anytime is organized in three parts to help you learn about different aspects of setting up and ­working with Office 365.

Part I, “Finding Your Place in the Cloud,” takes a look at the way people are working in the cloud today and introduces you to Office 365. Chapter 1 looks closely at teams, both inside and outside the office environment, and it takes a look at the way Office 365 offers a greener choice for small businesses. Chapter 2 shows you how to create an Office 365 account and set up a profile, and it gives you a big-picture tour of Office 365 so that you can begin planning just what you want to do with the tools. Chapter 3 is for the team manager or person who will be managing the Office 365 site; you’ll learn how to ­customize the site, add mobile devices, and set up and manage Microsoft Exchange, Microsoft SharePoint, and Microsoft Lync online.

Part II, “Teamwork in the Cloud,” is your guide to setting up, organizing, ­managing, and helping your team be successful using Office 365. ­Chapter 4 spotlights all the team features you can use to get everybody on the same page, calendar-wise; you’ll also find out how to share files, hold online ­meetings, instant message each other, and broadcast presentations. Chapter 5 walks you through creating, editing, and sharing a team site. Chapter 6 shows you how to create document libraries, share files with team members, and manage the files in SharePoint Online. You’ll also find out about working with file versions, tracking file changes, and comparing and merging files. Chapter 7 shows you how to create and use workflows to keep your team moving in the right direction, and Chapter 8 introduces all things Web App by shining a light on the capabilities of the various tools and showing you how to work with files online, coauthor documents, edit worksheets, broadcast presentations, and share notebooks. Chapter 9 rounds out this part of Office 365 by focusing on mobile technologies: find out how to use the various Office Mobile applications to review, edit, and share the files you develop with your team.

Part III, “Connecting in Real Time,” shows you how to use the ­communication and instant-messaging options in Office 365 to stay in touch with your team in real time. In Chapter 10, “Email and Organize with Office 365,” you learn how to use Outlook Web App to import and manage contacts, set email preferences, organize mail ­folders, work with your calendars and tasks, and more. Chapter 11, “Talking it Over with Microsoft Lync,” shows you how to connect in real time to other online users through instant ­messaging, voice calls, and online chats. You’ll learn how to manage transcripts, invite others to the ­conversation, and host web meetings. Chapter 12, “Designing Your ­Public Website,” shows you how to use the web tools in Office 365 to create a ­website to ­showcase your products and services and give your customers a sense of who you are and what you offer. Chapter 13, “Integrating Office 365,” presents a set of examples that show how you and your team can use the ­various tools in Office 365 together to create and share business projects.

untitled

Preventing Automatic Service Pack 1 Update to Windows 7 and Windows Server 2008 R2

Microsoft began to distribute Windows 7 and Windows Server 2008 R2 Service Pack 1 (SP1) as a high-priority update through Automatic Updates. However, as with most large corporate environments, IT organizations may want to delay the introduction of a new Service Pack until they have tested compatibility with internal applications and sites.

Microsoft created a tool called “Windows Service Pack Blocker Tool Kit” to stop it from updating your servers and workstations without your permission. Unlike the Blocker Toolkit for IE9, this tool does have an expiration date – the 22nd of February 2012. The tool and can be configured either by running the registry file on the client machines or through Group Policy in domain joined environments.

Download

Download details: www.microsoft.com/downloads/en/details.aspx?FamilyID=D7C9A07A-5267-4BD6-87D0-E2A72099EDB7

The tool can be used with:

  • Windows 7 Service Pack 1
  • Windows Server 2008 R2 Service Pack 1

Toolkit Components

The tool contains three components. All of them function primarily to set or clear a specific registry key that is used to detect and block download of Service Packs from Windows Update. You need to only use one of the components, the one that best serves your organization’s computer management infrastructure.

The components are:

  • A Microsoft-signed executable
  • A script
  • An ADM template

Registry key

The executable creates a registry key on the computer on which it is runs that blocks or unblocks (depending on the command-line option used) the delivery of a Service Pack to that computer through Windows Update. The key used is HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate.

Key value name: DoNotAllowSP

  • When the key value name is not defined, distribution is not blocked.
  • When the key value name is set to 0, distribution is not blocked.
  • When the key value name is set to 1, distribution is blocked.

Blocker Script

The script does the same thing as the executable, but allows you to specify the remote machine name on which to block or unblock delivery of Service Packs.

When the ‘/B’ command line option is used, the key value name ‘DoNotAllowSP‘ is created and its value set to 1. This value blocks delivery of a Service Pack to the computer through Automatic Update or Windows Update.

When the ‘/U’ command line option is used, the previously created registry value that temporarily blocked the delivery of a Service Pack to the computer through Automatic Update or Windows Update is removed. If the value does not exist on the computer on which it is run, no action is taken.

Note: The executable and script have been tested only as a command-line tool and not in conjunction with other systems management tools or remote execution mechanisms.

Group Policy Administrative Template (.ADM file)

The ADM template allows administrators to import group policy settings to block or unblock delivery of Service Packs into their Group Policy environment. Administrators can then use Group Policy to centrally execute the action across systems in their environment.

Add the .ADM file to the Group Policy by going to Computer Configuration > Administrative Templates. Right click and select Add/Remote Templates. Browse to the location of the .ADM file and click Ok.

Windows 7 and Windows Server 2008 R2 SP1 Blocker: Group Policy Settings

Users running Windows 7 and Windows Server 2008 R2 will see the policy setting under Computer Configuration > Administrative Templates > Classic Administrative Templates (ADM) > Windows Components > Windows Update.

Block Windows 7 and Windows Server 2008 R2 SP1 automatic updates

Please note that this toolkit will not prevent the installation of the service pack from CD/DVD, or from the stand-alone download package. This simply prevents Windows 7 and Windows Server 2008 R2 Service Pack 1 (SP1) from being delivered over Windows Update.

ThinApp VMware View 4.6 Client

image image

image image

image image

image image

image image

image image

image

Reboot and then setup continues
 
image image
 image image

 image image

 image image

 image image

 image image

 image image

Edit Package.ini

Add the following line under:
[VMware View Client.exe]
Source=%ProgramFilesDir%\VMware\VMware View\Client\bin\wswc.exe
;Change ReadOnlyData to bin\Package.ro.tvr to build with old versions(4.6.0 or earlier) of tools
ReadOnlyData=Package.ro.tvr
WorkingDirectory=%ProgramFilesDir%\VMware\VMware View\Client\bin\
ObjectTypes=VMware_VDM_Client;VMware_VDM_Client.1
Shortcuts=%Desktop%;%Programs%\VMware;%AppData%\Microsoft\Internet Explorer\Quick Launch

Commandline=%ProgramFilesDir%\VMware\VMware View\Client\bin\wswc –serverurl viewdemo.wardvissers.nl

Open Project Folder:
Remove the following Folders

%AppData%
%Common Desktop%
%Common Programs%
%Desktop%
%drive_C%
%Local AppData%
%Personal%
%Profile%
%Program Files Common%
%SystemRoot%

Then Click on Build

image image

Issue with MDT 2010 Update 1 and Windows AIK for Windows 7 SP1

With the release of the Windows AIK for Windows 7 SP1 supplement (see Windows AIK for Windows 7 SP1 Released for details), there is a new version 3.1 version of Windows PE available. If you plan to install this update, you need to be aware of an issue when using this with MDT 2010 Update 1.

With MDT 2010, Deployment Workbench will look for a “boot.wim” file from one of the imported operating systems that has the same build number as Windows AIK (e.g. “boot.wim” from a Windows 7 RC, build 7100, operating system to go with the Windows AIK for Windows 7 RC). If it finds a match, it will use that WIM instead. Why do we do this? Because the “boot.wim” contains the Windows Recovery Environment (Windows RE), a component that isn’t available in Windows AIK.

So let’s get a little more specific. First, some background details:

  • The build number for the RTM version of Windows 7 is 6.1.7600.16385.
  • The build number for Windows AIK for Windows 7, released with Windows 7 RTM, is also 6.1.7600.16385. This is stored in the registry.
  • The build number for Windows 7 SP1 is 6.1.7601.17514.
  • The build number for the files included in the Windows 7 AIK for Windows 7 SP1 supplement, including Windows PE 3.1 and all the Windows PE feature packs, is also 6.1.7601.17514. But since this supplement is installed by replacing files in the Windows AIK installation directory using XCOPY, the registry isn’t updated so MDT still thinks the Windows 7 RTM version (6.1.7600.16385) of Windows AIK is installed.

Now, let’s assume that you have Windows 7 RTM x86 installation files present in your deployment share, and you haven’t installed the Windows 7 AIK for Windows 7 SP1 supplement. MDT’s processing when creating a boot image will look like this:

  • Is there a boot.wim available with the same version number as Windows AIK (6.1.7600.16385 = 6.1.7600.13685)? Yes, copy it to a temporary folder and mount it.
  • Inject the required Windows PE optional components from the Windows AIK installation directory into this mounted boot image.
  • Inject the needed MDT scripts.
  • Commit the changes to the WIM file and copy it to the deployment share.

Now, install the Windows 7 AIK for Windows 7 SP1 supplement and update the deployment share:

  • Is there a boot.wim available with the same version number as Windows AIK (6.1.7600.16385 = 6.1.7600.13685)? Yes (because MDT doesn’t know that Windows AIK has been updated, the registry still says it is version 6.1.7600.16385), copy it to a temporary folder and mount it.
  • Try to Inject the required Windows PE feature packs from the Windows AIK installation directory into this mounted boot image. All fail, because they are for Windows PE 3.1 and won’t work with the Windows PE 3.0 boot image copied from the Windows 7 RTM files.
  • Stop.

The actual error will look something like this (repeated for each Windows PE feature pack):

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385
Image Version: 6.1.7600.16385
Processing 1 of 1 – Adding package WinPE-HTA-Package~31bf3856ad364e35~x86~~6.1.7601.17514
Error: 0x800f081e
The specified package is not applicable to this image.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
Exit code = –2146498530
DISM /Add-Package failed for component C:\Program Files\Windows AIK\Tools\PETools\amd64\WinPE_FPs\winpe-hta.cab, rc = -2146498530.

Solution:

Modify the Settings.xml file in the deployment share’s “Control” folder to tell MDT to never use the boot.wim. The settings look like this:

<Boot.x86.UseBootWim>True</Boot.x86.UseBootWim>
<Boot.x64.UseBootWim>True</Boot.x64.UseBootWim>

They should be changed to instead say:

<Boot.x86.UseBootWim>False</Boot.x86.UseBootWim>
<Boot.x64.UseBootWim>False</Boot.x64.UseBootWim>

As a result of this change, MDT will no longer use the boot.wim from the Windows 7 RTM installation files. Instead, it will always use the winpe.wim from Windows AIK. And since the Windows PE feature packs in Windows AIK should always match the winpe.wim in Windows AIK, this will always work.

Note that this will never be an issue with MDT-generated boot images used with ConfigMgr 2007, as MDT will always use the winpe.wim from Windows AIK when generating these. (ConfigMgr 2007 doesn’t yet support Windows PE 3.1, so don’t install the Windows AIK for Windows 7 SP1 supplement yet if you are using ConfigMgr.)

More info check: Issue with MDT 2010 Update 1 and Windows AIK for Windows 7 SP1 Supplement

VMware Workstation 7.1.4

    What’s New

    Support for Windows 7 SP1

    Security Fixes

    • Workstation 7.1.4 addresses a local privilege escalation in the vmrun utility

      VMware vmrun is a utility that is used to perform various tasks on virtual machines. The vmrun utility runs on any platform with VIX libraries installed. It is installed in Workstation by default. In non-standard filesystem configurations, an attacker with the ability to place files into a predefined library path could take execution control of vmrun. This issue is present only in the version of vmrun that runs on Linux

      The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-1126 to this issue.

        Other Resolved Issues

        • In Workstation 7.1, the default main memory VA cache size (mainMem.vaCacheSize) for 32-bit Windows guests was reduced to accommodate 3D emulation memory requirements. However, the reduced value resulted in performance loss. For 7.1.4, the default main memory VA cache size has been be increased to 1000 MB and performance is improved.

        • Because Workstation failed to identify more than 10 USB host controllers in newer Windows guests, some USB devices did not appear in the Removable Devices menu. Now Workstation shows all USB devices in the Removable Devices menu as long as they are connected to the first identified 16 USB controllers.

        • When using the Capture Movie option, the captured video stopped playing around the 1GB mark if the video file exceeded 1GB. Now you can capture and play video files that are greater than 1GB. 

        • On Windows host systems that have more than 4GB of memory, Workstation sometimes crashed during cryptographic operations, for example, when performing disk encryption.

        • VMware Tools upgrade could be started by a non-administrator user from the VMware Tools Control Panel in a Windows guest. In this release, only administrator users can start VMware Tools upgrade from the VMware Tools Control Panel. To prevent non-administrator users from starting VMware Tools upgrade from a guest by using other applications, set isolation.tools.autoinstall.disable to TRUE in the virtual machine configuration (.vmx) file.

        • When a virtual machine running on a Windows host was used to access an Omron Industrial CP1L Programmable Logic Controller, Workstation generated an unrecoverable error.

        • When using NAT virtual networking on Windows hosts, the traceroute command did not work when used within virtual machines.

        • Workstation crashed with an access violation when a user tried to open the sidebar after closing all tabs in Quick Switch mode. 

        • The VMware Tools HGFS provider DLL caused a deadlock when making calls to the WNetAddConnection2 function from an application such as eEye Rentina in a Windows guest operating system.

        • There was no option to disable guest time sync when a host resumes. Now you can set time.synchronize.resume.host to FALSE in the virtual machine configuration (.vmx) file to disable guest time sync when a host resumes. See VMware Knowledge Base Article 1189 for other time sync options.

        • Setting a hidden attribute on a file in a shared folder from a Windows guest on a Linux host failed with an error. This problem caused applications such as SVN checkout to fail when checking out to shared folders on Linux hosts from Windows guests

        How to demote a Exchange 2007 CCR Cluster with Load balanced CAS/HUB Servers

        I used the following steps to do this.

        1. All public folders and system folders that are housed on the Exchange 2007 CCR Cluster computer must be replicated to another Exchange 2007/2010 computer that is in the site.

        2. Verify the contents of the public folder store with the following Powershell commands
        Get-PublicFolderStatistics -server <Exchange 2007_Server_Name> | fl | out-file d:\PFstat.txt

        Get-PublicFolder -server < Exchange 2007_Server_Name > \ -recurse | fl | out-file d:\PFIPMSub.txt

        Get-PublicFolder -server < Exchange 2007_Server_Name > \non_ipm_subtree -recurse | fl | out-file d:\PFNonIPMSub.txt.

        3. Remove the replicas from the public folder store

        MoveAllReplicas.ps1 -Server ccrclustername –NewServer newservername

        4. Remove the public folder store

        Remove–PublicFolderDatabase –Identity "Public_Folder_Store_Name"

        5. Change the server that is responsible for generating the Offline Address Lists

        Move-OfflineAddressBook –Identity OfflineAddressBookIdParameter -Server ServerIdParameter

        6. Move the Routing Group Connectors by using the following command:

        Get-RoutingGroupConnector | where {$_.SourceTransportServers -like "<First Exchange 2007 server>"} | Set-RoutingGroupConnector -SourceTransportServers "<Second Exchange 2007 server>"
        Get-RoutingGroupConnector | where {$_.TargetTransportServers -like "<First Exchange 2007 server>"} | Set-RoutingGroupConnector -TargetTransportServers <Second Exchange 2007 server>

        7. To modify any Send connectors that have the first Exchange 2007 server as the source transport server, run the following commands:

        Get-SendConnector | where {$_.SourceTransportServers -like "<First Exchange 2007 server>"} | Set-SendConnector -SourceTransportServers "<Second Exchange 2007 server>"

        8.Important:
        How to use the Exchange Server SP1 2007 Setup wizard to remove Exchange 2007

        1. Log on to the server from which you want to remove Exchange 2007.

        2. Open Control Panel, and then double-click Programs and Features.

        3. In Programs and Features, select Microsoft Exchange Server 2007, and then click Uninstall.

          If you click Change instead of Uninstall, you can add server roles, but you cannot remove server roles.

        4. In the Exchange Server 2007 SP1 Setup wizard, on the Exchange Maintenance Mode page, click Next.

        5. On the Server Role Selection page, clear all the server role check boxes, clear the Management Tools check box, and then click Next.

          By default, all server roles are selected. This indicates that no server roles will be removed. To remove a server role, you must clear the appropriate check box.

        6. On the Readiness Checks page, after the check completes, click Uninstall.

        7. On the Completion page, click Finish.

        8. (Optional) If you are removing Exchange from a Mailbox server, remove the Exchange database files (*.edb) and storage group log files (*.log).

          If you reinstall the Mailbox server role on this server, you must first remove the database and log files from the server.

        9. (Optional) Remove the setup log files that are located at %systemdrive%\ExchangeSetupLogs.

        10. (Optional) Remove the following virtual servers that are created for Exchange 2007 under the Default Web Site in IIS:

          • Microsoft-Server-ActiveSync
          • OAB
          • Owa

          When you remove Exchange 2007, neither IIS nor these virtual servers are removed

        9.  First Remove the Passive Mailbox Node

        10. Second the Primary Mailbox Role

        11. Remove the CAS/HUB’s Role on the nodes
        Important: NOT AT THE SAME TIME

        12. Demote the Cluster

        13. Demote the NLB Cluster

        14. Remove the Servers from the domain

        15. Shutdown the Servers

        16. Take a cold bier when you are don with testing and everything works Winking smile

        Clipboard Copy and Paste option is disabled in vSphere Client 4.1

        I upgraded my home test server to ESXi 4.1 and I the Clipboard Functie is disabled by default and that is so annying

        Solution:

        Starting with vSphere 4.1, the Copy and Paste options are, by default, disabled for security reasons.

        To be able to copy and paste between the guest operating system and the remote console, you must enable the Copy and Paste options using the vSphere Client. Alternatively, you can use RDP (Remote Desktop Protocol) to connect to the Windows virtual machines.

        To enable this option for a specific virtual machine:

        1. Log into a vCenter Server system using the vSphere Client and power off the virtual machine.
        2. Select the virtual machine and click the Summary tab.
        3. Click Edit Settings.
        4. Navigate to Options > Advanced > General and click Configuration Parameters.
        5. Click Add Row and type the following values in the Name and Value columns:

          • isolation.tools.copy.disable – false
          • isolation.tools.paste.disable – false
            Note: These options override any settings made in the VMware Tools control panel of the guest operating system.

        6. Click OK to close the Configuration Parameters dialog, and click OK again to close the Virtual Machine Properties dialog.
        7. Power on the virtual machine.

        Note: If you vMotion a virtual machine to a host where the isolation.tools.*="FALSE" is already set, the copy and paste options are automatically activated for that virtual machine.

        To enable this option for all the virtual machines in the ESX/ESXi host:

        1. Log in to the ESX/ESXi host as a root user and open the /etc/vmware/config file using a text editor.
        2. Add these entries to the file:
          isolation.tools.copy.disable="FALSE"
          isolation.tools.paste.disable="FALSE"
        3. Save and close the file. The Copy and Paste options are only enabled when the virtual machines restart or resume the next time.

        For more information, see the Limiting Exposure of Sensitive Data Copied to the Clipboard section of the  ESX Configuration Guide.

        http://kb.vmware.com/kb/1026437

        FREE Exchange 2010 Training available

        Exchange 2010 Upgrade and Deployment (HOLO)

        This 300 level hands-on labs online course (including seven hands-on labs) will prepare learners with the knowledge to engage with customers to help them implement best practices for smooth Exchange 2010 upgrades and deployments. These hands-on labs online (HOLOs) are provided at no charge to Microsoft partners, and provide IT Professionals with the essential information they need to setup, deploy, and configure Microsoft Exchange Server 2010.  The course will address gaps in knowledge around topics such as new features, upgrade paths, tools and processes to support upgrade and deployment planning.

        Training includes the following curriculum:

        Course (Online): Using Exchange 2010 Tools to Plan a Deployment (Part 1)

        Course (Online): Using Exchange Tools to Plan a Deployment (Part 2)

        Course (Online): Exchange 2010 Setup, Deployment, and Server Role Configuration

        Course (Online): Configuring Mail Flow and Outlook Web Access

        Course (Online): Moving Mailboxes to Exchange 2010

        Course (Online): Moving Other Services to Exchange 2010 (Part 1)

        Course (Online): Moving Other Services to Exchange 2010 (Part 2)
        exchange 2010

        Thanks to

        Bryan Von Axelson

        Enable Windows 7 Features through Group Policy

        I love Windows 7. But there is one thing a hate about Windows 7.
        There is no nice way to enable Windows 7 Features trough Group Policy.

        So I created a small visual basis script that i used as a startup script.

        It checks if adsnapins.txt exist in the program files files. If exsist do nothing if it don’t exsist enable the feature.

        Windows7ADSnapIns.vbs

        ‘Installeerd Windows 7 AD Management Snapins.
        ’13-07-2010 Ward Vissers

        Set fso = CreateObject("Scripting.FileSystemObject")

        If Not (fso.FileExists("C:\Program Files\adsnapins.txt")) Then
            Dim Wsh
            Set wsh = CreateObject("WScript.Shell")
            wsh.run "dism /online /enable-feature /featurename:RemoteServerAdministrationTools", ,1
            wsh.run "dism /online /enable-feature /featurename:RemoteServerAdministrationTools-Roles", ,1
            wsh.run "dism /online /enable-feature /featurename:RemoteServerAdministrationTools-Roles-AD", ,1
            wsh.run "dism /online /enable-feature /featurename:RemoteServerAdministrationTools-Roles-AD-DS", ,1
            wsh.run "dism /online /enable-feature /featurename:RemoteServerAdministrationTools-Roles-AD-DS-SnapIns", ,1
            fso.CopyFile "\\ad.local\afs\install\Windows7Feature\adsnapins.txt", "C:\Program Files\adsnapins.txt"

        End If

        Set fso = Nothing

        Enable the Change Password feature with Outlook Web Access on a Windows 2003 Exchange 2007 Server

        First Step create the IISADMPWD virtual directory, do the following:

        1. Click Start, point to Programs, point to Administrative Tools, and then click Internet Services Manager.  
        2. Right-click the default Web site, point to New, and then click Virtual Directory. image
        3. In the Virtual Directory Creation wizard, type IISADMPWD in the Alias box, and then click Next.
          image 
        4. In the Directory box, type c:\windows\system32\inetsrv\iisadmpwd or the location where your hard disk is your default hard disk, and then click Next.
          image
        5. Verify that only the Read and Run script check boxes are selected, such as the ASP check box, click Next, and then click Finish.
          image  image
        6. Verify that the IISADMPWD virtual directory has only basic authentication is set
          image
        7. If you use Windows 2003/IIS 6.0, verify that the application pool is set to MSExchangeOWAAppPool
          image 
        8. Register the IISpwchg.dll file in the Iisadmpwd directory:
          Click Start, and then click Run.
          In the Open box, type the following, and then press ENTER:
          regsvr32 c:\windows\system32\inetsrv\iisadmpwd\iispwchg.dll
        9. Configure the PasswordChangeFlags property in the metabase to make sure that the Password Change functionality is enabled:
          Click Start, and then click Run.
          In the Open box, type cmd, and then press ENTER.
          Locate the C:\Inetpub\Adminscripts directory.
          Type the following command, and then press ENTER:
          cscript.exe adsutil.vbs set w3svc/passwordchangeflags 1

          0: This is the default value. This value indicates that you must use a Secure Sockets Layer (SSL) connection when you change the password.
          1: This value permits password changes on non-secure ports. This value is useful if SSL is not enabled.
          2: This value disables the Password Change functionality.
          4: This value disables the advance notification of password expiration.

        10. Do not forget to enable Active Server Pages.
          image 
          Source http://support.microsoft.com/kb/297121

        Translate »