Issuing New Laptops | User Passwords

[tommyday]

As the end of the school year approaches, we are revisiting our laptop imaging and distribution processes. When we issue a new laptop to a current user, we move all of their user data from the current institutional laptop to the new, set up the environment etc. This has a sticky scenario with it where need to have their password to get this accomplished. Wondering if others can share how they transition users to replacement laptops and if/how you collect/store any passwords.

 

Thanks, Tom

[Blue_Cookeh]

Simply put, we don't take user's passwords.

 

If I'm swapping a laptop out I assume (and users know this) that all data is stored in places where we have folder redirection in place. This way, I have a quick scan through SCCM to see what was installed on the old laptop in case they have anything non-standard, add those onto the new laptop after we've deployed the OS to it, and pass it onto the user for first login.

 

Keeps their account secure, keeps me out of their stuff, and makes my job with rebuilds easier

 

In the case of Windows laptops, MBAM will force encryption, in the case of Macs I'll manually enable FileVault on an admin account.

Edited April 27, 2015 by Blue_Cookeh

[witch]

I agree - all data is stored in a redirected user area on the server

However, if you have to do it then why not set a password for the user, do what you have to do and then make them change it straight away.

[tommyday]

Thanks for the input. Some data is saved in Google Drive but users rely heavily on saving to their Documents/ folder, iMovie data etc. As for the password, yes changing it for them is an option, we'll just have to make a full proof plan for the keychain mess etc

 

Appreciate your time!