The Easy Button – A story about Corruption, Portability, Office 365, User Profile bloat, ProfileDisk, non-persistent Data Indexing and more…
20 Min read – User profiles have been around for many years. According to Wikipedia the user-profiling scheme in force today owes its origins to Windows NT, which stored its profiles within the system folder itself, typically under C:WINNTProfiles. Windows 2000 saw the change to a separate “Documents and Settings” folder for profiles, and in this respect, is virtually identical to Windows XP and Windows Server 2003.
Of course, the way that user profiles behave, interact with the underlying Operating System, the different ‘types’ of profiles available and how they are managed has also drastically changed throughout the years. With many more advancements, currently being developed and on the way.
A few topics I’d like to touch on:
- Large user profiles
- Office 365 and its drawbacks, on and offline caching
- The concept of a ProfileDisk
- Data indexing for non-persistent
- But wait, that’s not all – VHD containers
- Size does matter
- Profile Portability
- A unique combination – ProfileDisk + Profile Portability
- Data outside of the user profile
- User-authored data
- Profile/data corruption, then what?
- How to handle existing (Roaming) profiles
- Infrastructural needs and components overview
- Integration with ProfileUnity
- ProfileUnity agent
- Main configuration steps
- Concluding – Why we are different
If you’d like to read this blog offline, print it etc. here’s a PDF copy for your convenience.
Via the fine folks at Liquidware.