Thinking about it, I don't use it in my current jobs but in my last one it was set as start-up, as elsiegee said., not log on or off
hmm, getting close to 100 machines, not including staff laptops but does include the netbooks but they dont belong to a single person.
Well ive currently only deployed the script to the couple of machines in my room so i could keep an eye on them. Maybe i should just stick to manual... :confused:
The office users only use the PC on their desk and don't logon to multile machines, so I've never had a profile corruption with these people... (Famous last words!)
I wouldn't simply because our 'typical' user will try on around 5 or 6 computers in 2 or 3 different areas and just forget where she did this.
The dirty profile will then just hang around until it finds her again.
Maybe you could just activate it for the afternoon/morning after someone reports a corupt profile? (Apply the gpo and shutdown all the pc's at night it will ensure it's run on startup in the morning, you can then remove the gpo again), you could even go as far as only activating it in the rooms that have issues.
Modify the script so you can add the username of the profile you want deleted? and just leave that active for 24 hours?
Oh, good ideas Mossj...i like it...
Happened again, on the pc i have opposite me (which has the script applied) User logged on, no background no icons. She'd tried to log off and it hung. so i rebooted the PC and it worked fine. Starting to get annoyed with this profile thing! :mad:
We get mess when people get to a PC that is locked and just switch it off and on so they can login - leaving a local profile that then gets in the way when the original user logs in on that PC again - irritating - but can't find a solution - its a people thing not a computer one.
For pupils I usually set them up with a single, pre-configured mandatory profile. From Year 2 upwards they have their own individual logon names. This allows teachers to monitor pupil progress and over time, pupils have a portfolio of work when they leave in Year 6 to secondary school.
Staff on the other hand usually have their own profiles, but again, pre-configured by myself to minimise problems.
If by chance a user profile becomes corrupt (for whatever reason), the really simple solution is to give the new profile a unique name, such as "jbloggs1", "jbloggs2" within Active Directory. Naming the profile differently will ignore the existing old profile (possibly cached on workstations), which was named just "jbloggs".
You'll also find inevitably that workstations will require re-imaging due to corruption or users incorrectly shutting down machines, so in the process cached profiles will be deleted anyway.
E.G when I logon my profile folder on the machine is "mossj", but on the server it is "mossjPROFILE"
from what I read/understand (on this forum) with a Madatory profile you can still have seperate logins but the users profile is always the same as a master copy, hence it cannot currupt...
Yes you can have usernames and profiles named differently.Quote:
Are you sure this would work as profiles under document and settings are saved under our usernames....
My username could by jbloggs and my profile could be jbloggs1234, so this would read:
My home directory would have to read (as a recommendation):
just so you know, staff roaming...kids mandatory...
There are various methods to deploy/use, roaming/local, standard/mandatory profiles.Quote:
the users profile is always the same as a master copy, hence it cannot currupt...
In a network environment the server usually plays a big role in profiles. Roaming profiles (for example) would be stored in a profiles$ share.Quote:
Yes but we are not talking about on the server
Within Active Directory if you changed the profile name from:
Then created/copied a profile within Profiles$ named jbloggs2, the computer you're logging onto would ignore existing profiles named jbloggs and download the new/updated profile named jbloggs2.
Sorry Little-Miss, I didn't mean to imply that your network was small and insignificant, all I meant was that hopefully as the corruption doesnt happen often, and you don't have a school of 500-odd machines, you wouldnt come across it too often and so it wouldnt be such a big thing to delete the profiles manually occasionally!
However, you seem to have a bit of a bigger than usual problem. Did someone else set up the profiles?
I have looked at our system and one school definitely has delprof running when the computers shut down at night. This seems to help a bit.
lol thats ok Witchy, i didnt take it that way.
The guy who helped with my new DC install set them up. They set up the same way Michael has mentioned. \\SERVERNAME\PROFILES$
im getting a little worried :(