© 2006 Microsoft Corporation. All rights reserved.
Learning Essentials for Microsoft® Office is a desktop application that works with Microsoft Office to provide students and teachers a custom Office environment. Learning Essentials includes curriculum-based templates and toolbars for Microsoft Office Word, Microsoft Office PowerPoint®, and Microsoft Office Excel. It also includes academic tutorials and project assistance from leading education publishers. This guide describes the options available for curriculum and IT administrators to customize and deploy Learning Essentials.
Compliance with License Requirements
New Features in Learning Essentials
Planning the Deployment of Learning Essentials
Deciding Where to Store Content and the User Center File
Customizing the User Center File
If you perform a remote deployment of Learning Essentials for Microsoft® Office in your organization, you accept the Software License Terms (formerly “End User License Agreement” or “EULA”) for Learning Essentials for Microsoft Office on behalf of each end user in your organization.
For more information on the licensing rights to Learning Essentials for Microsoft Office products, refer to the Software License Terms that accompany the software.
This release of Learning Essentials includes support for SCORM® output using HunterStone THESIS and four new features designed to assist curriculum and IT administrators:
When you install Learning Essentials in a network environment, you must make the following decisions:
Learning Essentials for Microsoft Office requires the following minimum system configuration:
It is recommended that you install Learning Essentials content and the User Center file centrally only if the client computers are always connected to the network. The following table provides guidelines for when to centralize content and when to store content locally.
| For these computers... | Consider storing content... |
| Desktop computers for educators (classroom location) | Centrally |
| Portable computers for educators (sometimes on network) | Locally |
| Shared computers for students (classroom location) | Centrally |
| Shared computers for students (laboratory location) | Centrally |
| Shared portable computers for students (mobile carts, guaranteed wireless access) | Centrally |
| Shared portable computers for students (mobile carts, with no guaranteed wireless access or with inconsistent coverage) | Locally |
Follow these steps to store content in a shared folder on a server or in a SharePoint document library.
Note If you store content in a SharePoint document library, make sure that the files with the .exe and .chm file extensions are not blocked. If EXE and CHM file types are blocked, users will not be able to access Help and other product features. Open SharePoint Central Administration and under Security Configuration, click Manage blocked file types, and then delete the .exe and .chm file extensions from the list.
Note The default root folder contains a Teacher folder and a Student folder, as well as content folders from add-in content created by using the Content Development Kit. If you do not want users to be able to access all the folders under the root folder, copy only those folders that you want users to be able to access. However, if you do not store the Teacher and Student folders in a common root content folder, educators will not have access to the content for students and some links may be broken. This can be avoided by explicitly using the full path in links, instead of using the ContentDir subkey in the registry. For more information about the ContentDir registry subkey, see Registry Subkeys later in this guide.
You can modify the User Center file for educators or students. The default filenames are Teacher TOC.xml and Student TOC.xml. Both files are located in the root content folder.
Note If you select an add-in that is already merged into the User Center file that you selected, duplicate entries are not displayed.
This section describes the methods that you can use to install Learning Essentials remotely.
Important
If you are managing computers in an Active Directory® directory service environment, you can use the Software Installation and Maintenance feature of Group Policy to deploy Learning Essentials on client computers. You can use a logon script with a batch file. If you assign the script to the user, it runs when the user logs on. If you assign the script to the computer, it is run on startup. Alternatively, you can use a Group Policy object to publish a .zap file. Users will need to go to Add or Remove Programs to initiate Setup.
If you are not already using an
update management solution such as Microsoft Systems Management Server (SMS) 2003 or
Software Update Services (SUS), we recommend that you use Group Policy for
managing the deployment of software. For information about Group Policy, see the following white paper:
Group Policy Infrastructure White Paper. For information about using SMS 2003 to deploy applications, see the SMS 2003 documentation.
Note To see whether a remote installation was successful, view the system log on the client computer.
Learning Essentials has four main Windows Installer Package (.msi) files.
The registry subkeys for Learning Essentials are:
These subkeys are located at:
\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Learning Essentials\1.0\<language>\Student\
and
\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Learning Essentials\1.0\<language>\Teacher\
where Student contains the subkeys for Learning Essentials for Students, Teacher contains the subkeys for Learning Essentials for Educators, and <language> is a code specified in Appendix A.
The TOCPath subkey is used to provide the path to the User Center file. If you set this subkey, Setup disables customization on client computers by setting the DisableCustomization subkey to 1. The ContentDir subkey is used to provide the path to the content. If you want to change the storage location for the content after Learning Essentials is installed, simply update the ContentDir registry subkey.
The TOC Version subkey is used to specify when client computers must get new User Center files. You can assign it any value that indicates a version. For example, you can provide a version number or a date for the value. TOC Version is located in the following subkeys, in addition to the subkeys in the HKEY_LOCAL_MACHINE subtree:
\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Learning Essentials\1.0\<language>\Teacher\TOC Version
and
\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Learning Essentials\1.0\<language>\Student\TOC Version
The behavior of the TOC Version subkey in the HKEY_LOCAL_MACHINE subtree is described in the following table.
| Value | Behavior | Notes |
| ALWAYS | Learning Essentials checks for a new User Center file each time a user opens the User Center. | With this setting, the User Center file is always up-to-date on client computers so you do not need to push changes to computers when a User Center file is updated. However, each time a user opens the User Center, Learning Essentials must connect to the network, look for, and download an available User Center file update. This increases network traffic and makes starting the User Center slower. |
| A string indicating the version. For example, a version number or date. | Learning Essentials checks for a new User Center file when the subkey value in the HKEY_CURRENT_USER subtree is different from the value in the HKEY_LOCAL_MACHINE subtree. | This setting reduces network traffic and makes starting the User Center faster. However, each time you modify the User Center file, you must push a new value for the TOC Version registry subkey to the HKEY_LOCAL_MACHINE subtree. |
The following table lists the options that you can specify when you install Learning Essentials. To provide a parameter that includes a space, use quotation marks around the parameter.
When you update the User Center file, push a new value for the TOC Version registry subkey to the HKEY_LOCAL_MACHINE subtree. You can do this by creating a batch file to update the TOC Version subkey value and running this batch file remotely.
For more information, visit the following Microsoft Web sites:
Learning Essentials for Microsoft Office Home Page
SharePoint Products and Technologies Home Page
The following table lists the codes used for each language in the Registry, the Documents and Settings folder, and the Program Files folder.
Language Code Arabic ar Dutch nl English (United Kingdom) en-gb (use en\gb for the Programs Files folder) English (United States) en-us (use en\us for the Program Files folder) Finish fi French (France) fr-fr (use fr\fr for the Programs Files folder) German de Italian it Norwegian no Portuguese (Brazil) pt-br (use pt\br for the Program Files folder) Russian ru Spanish es Swedish sv
Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted in examples herein are fictitious. No association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.
© 2006 Microsoft Corporation. All rights reserved. Microsoft, MS-DOS, Windows, Windows Server, Windows Vista, Active Directory, PowerPoint, and SharePoint are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
All other trademarks are property of their respective owners.