Leaked source code of windows server 2003
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

309 lines
13 KiB

  1. -------------------------------------------------------
  2. README for
  3. Microsoft Internet Explorer 6 Administration Kit
  4. July 2001
  5. -------------------------------------------------------
  6. (c) Copyright Microsoft Corporation 2001. All rights reserved.
  7. This document provides complementary or late-breaking information to
  8. supplement the Microsoft Internet Explorer Administration Kit (IEAK)
  9. documentation. You can also look at the Microsoft Web site at
  10. http://www.microsoft.com/windows/ieak/ for the latest information.
  11. For the most current information on browser issues, please refer to
  12. the online documentation that is installed with Internet Explorer 6.
  13. --------
  14. CONTENTS
  15. --------
  16. WHAT'S NEW FOR IEAK 6
  17. GENERAL SETUP REQUIREMENTS
  18. WHAT ELSE YOU SHOULD KNOW
  19. KNOWN ISSUES
  20. CORPORATE ADMINISTRATORS
  21. WHAT'S NEW FOR IEAK 6
  22. =======================
  23. IEAK 6 includes:
  24. - User Rights Deployment. Corporate Administrators can now deploy
  25. Internet Explorer directly to users who do not have Administrator-
  26. level access. Using tools such as SMS to initiate the install
  27. with Administrator privileges, users can log on after the system
  28. restarts and complete the setup process without using scripts or
  29. multiple reboots.
  30. - More Robust Custom Component Installation. You can now specify
  31. when a custom component gets installed and that it installs only
  32. if the Internet Explorer installation was successful.
  33. - SMS Status Reporting. Packages that are configured for SMS
  34. deployment can now report the status of installation to the
  35. SMS Server.
  36. - Desktop Management. Desktop and Quick Launch shortcuts such as
  37. Outlook Express, "View Channels," and "Connect to the Internet"
  38. can now be eliminated from your users' desktops to reduce clutter
  39. and reduce support incidents.
  40. For a detailed list of new features and improvements, see the
  41. "What's New" section in the IEAK Help.
  42. NOTE: The customizations installed by the IEAK during Internet
  43. Explorer Setup will always overwrite previous customizations.
  44. Even if no Internet Explorer components need to be installed,
  45. your customizations overwrite the old installation. Previous
  46. options, including the branding version number and
  47. configuration identifier, are no longer necessary.
  48. GENERAL SETUP REQUIREMENTS
  49. ==========================
  50. Before you can use the IEAK, you must install Internet Explorer 6.
  51. Before starting the Internet Explorer Customization Wizard, calculate
  52. the amount of disk space required for the components that you want to
  53. install:
  54. - Depending on the number of components you download, you will need
  55. up to 100 MB of disk space.
  56. - For every custom package you generate and every media type you
  57. select, you need additional disk space equal to the size of the
  58. package for each media type. You also need temporary disk space to
  59. create and compress each media type.
  60. For more information on each of the Microsoft components, see the
  61. IEAK Help.
  62. WHAT ELSE YOU SHOULD KNOW
  63. =========================
  64. You can customize and brand Internet Explorer in more ways than ever.
  65. The increased customization possible with IEAK 6, however, prohibits
  66. a certain amount of backward compatibility with the .ins files that
  67. store your branding information.
  68. The .ins files that you create with IEAK 6 can brand Internet Explorer
  69. 6. They cannot brand earlier versions of Internet Explorer. However,
  70. you can brand Internet Explorer 6.0 with the .ins files that you
  71. created in IEAK 5.x.
  72. Example 1: You use IEAK 6 to create three separate versions of
  73. Internet Explorer. You name the .ins files ver1.ins, ver2.ins, and
  74. ver3.ins. You use these files to brand your three versions of
  75. Internet Explorer 6.
  76. Example 2: In the past, you created three versions of Internet
  77. Explorer with IEAK 5.5. You named the .ins files market1.ins,
  78. market2.ins, and market3.ins. You now use these previously created
  79. .ins files to brand your three versions of Internet Explorer 6.
  80. KNOWN ISSUES
  81. ============
  82. - Packages created with IEAK 4.x and earlier will not be able to
  83. apply settings to Internet Explorer 6 installations.
  84. - Toolbar icon customizations will show a default system icon for the
  85. disabled state.
  86. - Automatic detection does not work if you use an .ins file as the
  87. Web Proxy AutoDiscovery (WPAD) data file (wpad.dat).
  88. - According to the Help topic "Automatic Detection and Configuration
  89. of Browser Settings," the wpad.dat file can be a .pac, .jvs, .js,
  90. or .ins automatic configuration file. This is incorrect. The browser
  91. does not interpret an .ins file generated by the IEAK, but instead
  92. interprets only a renamed proxy automatic configuration file or a
  93. .pac, .jvs, or .js file. Workaround: Set up automatic detection as
  94. specified in the Help file. Specify the wpad.dat file as a
  95. redirector to your .ins file.
  96. >>>To specify a redirection for wpad.dat in Microsoft Internet
  97. Information Server (IIS):
  98. 1. In the Microsoft Management Console (MMC), start Internet Service
  99. Manager.
  100. 2. Locate the wpad.dat file (usually located at the root of the Web
  101. server).
  102. 3. Right-click the wpad.dat file, and then click Properties. On the
  103. File tab, click "A redirection to a URL." Browse to the .ins
  104. file, which can be located anywhere on the server.
  105. - During Kiosk mode signup, the Internet Connection Wizard could fall
  106. behind the Kiosk mode window on Windows 2000 computers.
  107. - When you import connection settings on a Windows 2000 computer,
  108. only settings that can be applied to any Win32 client are imported.
  109. - When you import connection settings on a Windows 98 computer, if
  110. "Record a Log File for this Connection" is selected, the setting
  111. is not imported into the package.
  112. - The newest version of CMAK is available in Windows 2000 Server and
  113. in the Windows 2000 Admin Pack. To use an older version of CMAK
  114. without Windows 2000 Server, you can install IEAK 5.01 and then
  115. upgrade to IEAK 6.
  116. - If you are upgrading from IEAK 4, the IEAK 4 Start Menu link will
  117. not be removed. You can remove it manually by browsing to the Start
  118. Menu directory and deleting the link.
  119. - End users running Windows 2000 cannot individually customize their
  120. installation of the package. All Windows Update components will be
  121. installed.
  122. - If the .ins file resides on an HTTPS server, users who previously
  123. set "Do not save encrypted pages to disk" cannot complete signup.
  124. - Pay careful attention to the AutoComplete feature options.
  125. AutoComplete can store important or personal information in
  126. various scenarios. Depending on your situation, these features
  127. should be configured appropriately or turned off completely.
  128. - When you use a previously generated .ins file in a new session of
  129. the Internet Explorer Customization Wizard, note that some of the
  130. feature settings or file paths may have changed. Errors produced
  131. during package generation may be caused by this previously created
  132. .ins file. To ensure that your new package is generated correctly,
  133. validate all settings and file paths before finishing the
  134. Customization Wizard.
  135. - If you build a package to an existing directory using the Internet
  136. Explorer Customization Wizard, disabling Setup Customizations
  137. through Feature Selection will delete the previously created
  138. ie6sites.dat. To avoid this, do not disable Setup Customizations
  139. when building to an existing directory.
  140. - If you run the Internet Explorer Customization Wizard using
  141. different roles, it is recommended that you build to different
  142. directories. This will prevent any inapplicable settings from
  143. being included in the custom package.
  144. - In Microsoft Outlook Express, pre-subscribed newsgroups are
  145. configured only if a news server is also specified.
  146. - The Outlook Express junk mail filtering option, in Stage 5 of
  147. the Internet Explorer Customization Wizard, has no effect on
  148. the computer on which Outlook Express is currently installed.
  149. - On Asian platforms, the Internet Explorer Customization Wizard
  150. may appear in a large font when the computer is first restarted.
  151. To resolve this issue, restart the computer again.
  152. - The ISP File Wizard, included in the IEAK Toolkit, will install
  153. only on a computer that has the Visual Basic 4.0 run-time
  154. components installed. It will install normally on a Windows 98
  155. computer.
  156. - If you build a package for CD-ROM distribution, the Autorun
  157. program provides a link to "More Information". You can customize
  158. this to display a text file. The text file must be smaller than
  159. 100 KB to appear correctly.
  160. - The help topic Filetypes indicates that .pdf files are used for SMS
  161. deployment. However, .pdf files are not used. The file name IE5.pdf
  162. is incorrect. Instead, the file IE6-sms.sms is used.
  163. - The help topic Filetypes mentions the file IE5Setup.exe. This is
  164. incorrect and should read IE6Setup.exe.
  165. - The help topic Setup Information File (.inf) Definition contains
  166. two typographical errors. The information in the section "Update
  167. Config.sys Sections under the subheading "Stacks item" should read:
  168. Stacks=dos-stacks-values
  169. Sets the number and size of stacks in the Config.sys file. The
  170. Installer compares the existing value with the proposed value and
  171. always sets the stacks to the larger of the two values. For example,
  172. if Config.sys contains stacks=9,218 and an .inf file contains
  173. stacks=5,256, the installer sets the new value to stacks=9,218.
  174. legal-dos-stacks-value
  175. A legal MS-DOS stacks value.
  176. The first code block in the section "Optional Components section"
  177. under the subheading Include should read:
  178. [Optional Components]
  179. InstallMyToys
  180. InstallOtherApps
  181. CORPORATE ADMINISTRATORS
  182. =========================
  183. - To be able to deploy Internet Explorer to users who do not have
  184. Administrator-level access, you should select "Enable user access
  185. log on after restart" on the User Experience page of the IEAK
  186. Wizard. This option is available only to corporate administrators
  187. when the package is built solely as a "flat" package--otherwise,
  188. this option is not enabled.
  189. - If you enable User Rights Deployment, certain customizations will
  190. not be applied during setup for users without Administrator-level
  191. access on Windows 2000 and Windows NT4. These customizations must
  192. be deployed with Windows 2000 Group Policy or Windows NT4 Policy
  193. editor. More information is available at http://ieak.microsoft.com/.
  194. - If you enable User Rights Deployment and select to install the
  195. Windows Desktop Update, users without Administrator-level access
  196. who log on after setup on Windows 2000 will see two errors
  197. referring to shdoc401.dll. Neither error is harmful, and setup will
  198. continue after the user dismisses them. For information about
  199. avoiding these errors, please consult http://ieak.microsoft.com/.
  200. - When you are creating an SMS package from ie6-sms.sms and
  201. distributing IEAK6 through SMS 2.0 or later, the wrong status may
  202. appear. This happens because the status MIF file is being generated
  203. with a wrong "VERSION=". The version in the MIF file is set to 55,
  204. but the version in ie6-sms.sms is set to 6. To correct this problem,
  205. change all "VERSION=" parameters in ie6-sms.sms to 55 before
  206. creating a package from it.
  207. >>>To install the Office 2000 Resource Kit on the same computer as
  208. IEAK 6, follow these instructions carefully:
  209. If you HAVE NOT installed IEAK 6, you must:
  210. 1. Install the Office 2000 Resource Kit (it will install
  211. an older IEAK).
  212. 2. Install IEAK 6 as an upgrade.
  213. If you HAVE already installed IEAK 6, you must:
  214. 1. Uninstall IEAK 6.
  215. 2. Install the Office 2000 Resource Kit (it will install
  216. an older IEAK).
  217. 3. Reinstall the IEAK 6 as an upgrade.
  218. - Custom Components selected to "Install After System Restart" will
  219. not install on Windows Terminal Server.
  220. - If you are importing your current Active Desktop settings, turn on
  221. the Channel bar, and do not include channels. The installed package
  222. displays an empty Channel bar on the desktop.
  223. - If you are distributing the Web Desktop Update on Windows NT 4.0
  224. workstations, and your users are not at the Administrator level,
  225. you must use Policy Editor to manage the Web Desktop Update
  226. restrictions. These restrictions are not applied during Internet
  227. Explorer Setup or during automatic configuration. This is not an
  228. issue if your users are at the Administrator level.
  229. - When you use the policy to allow controls only from trusted
  230. publishers, be aware that Internet Explorer Setup and automatic
  231. configuration with .cab files will not work if the .cab files are
  232. not signed and the publisher is not on the trusted publisher list.
  233. Also, Automatic Install will not work when you use this policy.