Persistant mandatory profile issues...
I've been having ongoing problems with W7 mandatory profiles.
The problem is the fact that W7 machines randomly allow access to certain pupils, while others get a failed logon. When these symptoms occur some pupils occasionally have the deployed printers greyed out too.
The problem can be temporarily fixed by deleting the profiles and registry profile information.
All pupils use the same V2 mandatory profile from a server 2003 DC. The profile was created using the windows enabler method.
Group policy is managed from a W7 RSAT admin workstation with the central store populated with .admx files.
I am aware that lots has changed in the V2 profiles, including roaming registry settings that are no longer as flexible as it was in XP. :mad: Grrrr! why cant printer settings stay with the profile too.
I am currently trying to create a profile using the official microsoft method but sysprep is giving me a couple of problems. I'm hoping that a profile created in the proper sense will help ease some of the problems with logging on and off (which seem like registry problems to me)
I have managed to create the unattend.xml file with <CopyProfile>true</CopyProfile> set to "true" in the specialise pass. I have also run the commands as documented by microsoft to initiate the copy of the customised local profile over the default user profile, however when the machine reboots I get an error saying "Windows could not finish configuring the system. To attempt to resume configuration, restart the computer."
The computer then gets stuck in a loop with this message on every reboot.
Suffice to say, I'm not the biggest fan of V2 profiles at the moment. I like windows 7, and i'd like as many pupils to have the chance to use it as is possible but it cant happen when things are as twitchy as they are. I hope microsoft continue work to try and ease the compatibility issues with thier V2 profiles. I noticed the slow loading of blank backgrounds has been fixed already.
Any input welcome :D