Monitor resolution problem with XP machines

Archived from groups: microsoft.public.windowsxp.configuration_manage (More info?)

We are deploying 2000 HP desktops with an identical Windows XP image and are
running into a problem with display resolution on some of the machines. The
issue is that machines with different monitors, such as flat panels, are
defaulting to a different display resolution. This is not surprising, but
what is is that we can't seem to permanently set a resolution, it always goes
back to a default.

For instance, a machine with a monitor that identifies its best resolution
as 1024x768 will default to that resolution while an old monitor with a best
display resolution of 800x600 will default to 800x600. When we change the
display resolution in XP for a user to 800x600 from the default 1024x768, it
will change accordingly. However, when we log off the machine or reboot and
log back in as the same user, the resolution will revert back to the default.

Our organization uses mandatory profiles and group policies to set user
enviroments. NTFS file permissions are used to prevent access to certain
areas of the local drive. We have written roaming and mandatory profiles up
after making the display adjustment and the display will still revert back to
the default after the account logs in again.

The other interesting item is that the resolution will not revert back to
the default until approximately 5-10 seconds after the user's desktop
appears. 5-10 seconds after the desktop appears, the monitor goes black and
a second later the resolution reverts back to the monitor's default.

All hardware in the PCs are identical and so is the image. The PCs are HP
5000 and the graphics cards are Intel Extreme 2.

Under Windows 2000, once the display was set it stayed that way, no matter
what the monitor's best resolution was. This is a new problem for us now
that we have been moving to XP. We do not encounter this problem on these
same machines running a Win 2000 image.

All hardware in the PCs are identical and so is the image. The PCs are HP
5000 and the graphics cards are Intel Extreme 2.

We thought the fact that this problem happens on machines only when running
XP and not 2000 was interesting. We are not sure if there is a difference in
display or monitor drivers between XP and 2000 or whether there is something
else we are missing.

Any thoughts?

Thanks!