What is the process behind RM profile reset on CC4?

[andyturpie]

Afternoon,

 

I've been searching for answers to this question, but cannot find them anywhere to be honest. When a login profile becomes corrupt, what actually has to be done to repair the profile or create a new one? I suppose this question could pertain to both Vanilla/RM networks.

 

The reason I ask there are some RM services and packages (OneDrive Mapper) which require a bulk profile clean on restricted (pupil) users and with 1600 plus accounts it is quite a tedious task to do via the RMMC - I was wondering if anyone knows the process behind and if there was a script out there that could be modified to automate this task more easily? Surely it just can't be the Appdata folder which is targeted and there is more to the process than meets the eye?

[NB9457]

I'd assume if they have roaming profiles, it'd either delete/recreate them too as they can cause issues if they become corrupt. If you're still paying for RM support, contact them and I imagine they'd be able to give the instructions or do it for you as obviously they'll have their own way of doing things!

[andyturpie]

Yes they are roaming, however to cut down the hassle, I run a regular delprof2 task across the site so issues are minimized, I would say that in the years we have had CC4, we have only had around 3 or 4 actual profile corruptions, which I think is pretty good going?

[NB9457]

Yes they are roaming, however to cut down the hassle, I run a regular delprof2 task across the site so issues are minimized, I would say that in the years we have had CC4, we have only had around 3 or 4 actual profile corruptions, which I think is pretty good going?

 

That's very good going! But I'd assume it means roaming profiles, in which case, you'd be able to do it via powershell, off the top off my head I'm not sure what the command would be. That being said, I know on our vanilla network, if we completely delete the profile, it remakes a new one at login, this is what I sometimes do, or create a new one.

[Snoochieboochies]

On CC4:

 

Make sure the user is logged off and manually delete the users profile off the server.

 

If the user is still having trouble on a specific PC, delet the local user profile from that PC from System Properties> User Profiles.

[Techykev]

Not sure I understand how it is a "tedious task" using the RMMC? Surely this is where CC4 RMMC comes into its own, the students must be logged off, in the RMMC expand the Users, select Students, Ctrl +A to select all accounts then click Tasks, Users, Reset Profile and voila 5 minutes later and all 1600 student accounts are reset in AD. Next time the students log on they will download a clean default profile.

 

Snoochieboochies way will not work, it will take considerable time and effort to manually delete each profile and deleting just the local profile from the PC will mean next time the student tries to log on they will get the "User profile cannot be loaded" error. You also have to delete the registry key in the profile list, I will dig out the registry path if you need me to.

[SLS_]

...deleting just the local profile from the PC will mean next time the student tries to log on they will get the "User profile cannot be loaded" error. You also have to delete the registry key in the profile list, I will dig out the registry path if you need me to.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\ProfileList\

Edited April 9, 2017 by SLS_

[ajs]

Afternoon,

The reason I ask there are some RM services and packages (OneDrive Mapper) which require a bulk profile clean on restricted (pupil) users and with 1600 plus accounts it is quite a tedious task to do via the RMMC - I was wondering if anyone knows the process behind and if there was a script out there that could be modified to automate this task more easily? Surely it just can't be the Appdata folder which is targeted and there is more to the process than meets the eye?

 

 

The main thing that the process tries to do in CC4 is to copy over a default NTUSER.DAT from a copy of the RM Default Profile on the server into each user's profile directory (you can tell if it's worked either by checking for error messages in the Event Logs, RM logfiles or checking that the NTUSER.DAT file on the server is 512KB). I can't recall if it touches any other aspect of the user's profile unfortunately.

 

When the user logs in, unless the profile on the station is completely corrupted, it should recreate user-specific aspects of the profile and then save it all back to the server when they log off.