Errata

The following text should be inserted in Chapter 3 before the "Conflicts" section (**NOTE: due to space constraints, we are unable to make this change in
a reprint**):

Windows Millenium Edition (Me)

Windows Me is an attractive OS for communal workstations. It shows
greater compatibility with older hardware and software than Windows
2000, and unlike Windows 9x, it has file protection features.
Specifically, System File Protection (SFP) and System Restore.

The SFP runs as a background process, monitoring any changes made to a
protected database of files. If one of these files is deleted, or
replaced with a version not authorized by Microsoft, the SFP will
invisibly replace the file from a hidden copy on the hard drive. System
Restore automatically monitors and records changes made to essential
Windows system files; files with a .sys, .exe, .com, .vxd, or .dll
extension. System Restore does not record changes made to user created
files. If Windows begins to function improperly, using Restore points
the user can rollback the computer to an earlier date when it was
functioning properly. See the Microsoft Knowledgebase article Q267951
for more information on these file protection features.

Using System Policies with Windows Me

Unfortunately, Microsoft clearly states that Windows Me does not
support the use of the system policy editor, since it does not support
the use of a policy file (see Knowledgebase article Q266271). But never
being one to listen to advice, I decided to look into using Windows Me
with system policies.

The registry settings necessary for using system policies, Remote
Update and Enable User Profiles, exist in Windows Me. Automatic Remote
Update is typically enabled by default. Upon enabling user profiles, I
discovered that Windows Me will in fact automatically download from the
network, and import into its registry, the computer and user policies
found within a Config.pol file. I have successfully used the Admin.adm
template, as well as many of the Shell.adm policies in a number of
different User policies on these workstations. I was also able to
replicate the same user conflicts that occur in Windows 9x.

In spite of this success, it is important to note that policy use was
less than perfect if Active Desktop was enabled. Wallpaper settings, in
particular, are completely ignored. With Active Desktop disabled, I was
unable to find any problems with the templates I tested.

Since I have not completed any long term testing, and in light of
Microsoft's warning, I am not quite ready to whole-heartedly endorse
the use of policies on a Window Me workstation. However, the file
protection features make its use tempting enough for me to agree that
it is worth trying on a few test workstations. I would suggest first
disabling Active Desktop on the workstation itself and also within the
Config.pol file. This can be accomplished on the workstation by
selecting the option to use Windows classic desktop--found under
the General tab of the Control Panel applet Folder Options. In the
policy file it can be disabled using the user policy Desktop->Desktop
Restrictions->Disable Active Desktop found in the Shell.adm template.
See Chapter 4 for more information on using templates to create a
policy file.

"Specific computer policy is applied to the registry"

Should read:

"Default computer policy may be active for any corresponding computer
setting left in the grayed position"

Since the Windows NT logon processor does not support setting
environment variables in Windows 9x workstations, use the utility
winset.ext (available in the Windows 98 Resource Kit). The syntax is
the same as for the MS-DOS Set command. To set the username variable,
you can use the following command in the Windows NT logon script or
from a batch file:

WINSET USERNAME=%USERNAME%

It should read:

Since the Windows NT logon processor does not support setting
environment variables in Windows 9x workstations, use the two utilities
winset.exe (available in the Windows 98 Resource Kit) and putinenv.exe
(available for download at http://www.orca.bc.ca/win95/putinenv.exe).

To set the username variable in a Windows 9x workstation, copy
putinenv.exe and winset.exe to the domain controller's NETLOGON share,
then add these lines to the login script or a batch file:

\servernameNETLOGONPUTINENV L
\servernameNETLOGONWINSET USERNAME=%USERNAME%

"If you would like to limit access to individual applets not listed
in the standard policy templates, you can create..."

Should read:

"If you have Windows NT workstations and would like to limit access to
individual applets not listed in the standard policy templates, you
can create..."

"...applets from being displayed in Windows 9x or Windows NT4
workstations."

to:

"...applets from being displayed in Windows NT4 workstations."