That's the method we used in our student computer labs going back to the NT4 days and on to XP. I'm not involved with that these days, but I think it continues to be used here.
The only issue I can think of is that often the profile doesn't get deleted as it's supposed to. I'm guessing this is because of the profile not getting unloaded fully at logoff (a problem that seems to persist across Windows versions). There's at least one way to use GP for this. Under Administrative Templates\System\User Profiles, there is the setting "Delete user profiles older than......". I know on at least one lab GPO, they set this to 1 day and schedule a task to reboot at 3 AM each day. It seems like the Guest Group method is better. Charlie Sullivan Sr. Windows Systems Administrator From: [email protected] [mailto:[email protected]] On Behalf Of James Rankin Sent: Sunday, March 16, 2014 10:30 AM To: [email protected] Subject: [NTSysADM] Making user accounts members of Guests We generally configure a lot of our implementations where we like to use a local profile (for reasons of certificates, and also to avoid storing template profiles on the network), but we like the profile to be discarded at logoff time as we use third-party software for saving profile settings. Previously we used to do this by "spoofing" a temporary profile - when the user logs off, we edit the Registry key that tells Windows what the profile type is, changing it to "temporary" so that the OS flushes the profile when the user logs off. However - I could just do this by making all users members of the Guests group, as Guest profiles are automatically flushed at logoff too (unless they're Administrators). So, my question is - are there any possible unforeseen side-effects from making all my Domain Users members of the local Guests group on all my XenApp servers? Cheers, -- James Rankin --------------------- RCL - Senior Technical Consultant (ACA, CCA, MCTS) | The Virtualization Practice Analyst - Desktop Virtualization http://appsensebigot.blogspot.co.uk
