...would be to use 'Roaming Profiles' and 'Mandatory User Profiles'.
User profiles contain settings for the network environment, such as desktop configuration and menu options.
Making changes to the 'Default User' profile only affects new users upon *FISRT* logon. Any changes are then saved to that particular user's 'NTUSER.DAT' file.
When a new user is created (try it and see) no profile is created until that user logs on for the first time. Hence the message "Windows is preparing the desktop for first time use." or such upon first logon (say when you've just installed Windows).
When that user logs onto the console for the first time (interactive logon), the userinit.exe process uses the 'Default User' profile and copies all networking items, shortcuts, desktop items, registry entries,etc, creates a new profile with the user's name, then saves it to the 'ntuser.dat' file.
To avoid all these profiles from being created with multiple screensavers, desktops, etc, you create a 'Roaming Profile' on a server, and when the user logs on, this profile is downloaded to the local machine, cached and used to display the desktop, run the screensaver, perform folder redirection, etc. Once the user logs off, changes are saved to the local cache and the server profile.
The only way to stop the user saving changes is to rename the ntuser.dat to ntuser.man, thus creating a 'Mandatory Profile'. The user can make changes while logged on, but once they log off, no changes are saved.