Remember the end goal for NTLite is about making your install media and also your resulting OS smaller in every way possible its up to the end user how far they go and what features they require and don't require. NTLite is all about minimizing overhead and OneDrive is just extra overhead that many people don't use. Not sure what you are really trying to ask here your questions is sort of a misnomer really. I keep seeing several different commentaries from around different forums (usually folks building super lean gaming builds) that seem to indicate that it might be in one's best interest to "remove" the OneDrive feature from an actual Windows initial deployment from resourcing, background activity and so on. Wanted to check in here and see what the crew is doing these days with this - or if you are using OneDrive at all? Over here I can simply use SyncBack Pro on a local machine and create my own custom sync processes without having ANY Once drive crap running in the background. Then to take this to the next level - I see even more interesting angles where one could simply map a local drive to their OneDrive location and sync things up to the cloud as needed with way more control that the OneDrive app could ever provide. Been working on some new deployment Windows 10 ISOs using NT Lite etc - and I keep seeing several different commentaries from around different forums (usually folks building super lean gaming builds) that seem to indicate that it might be in one's best interest to "remove" the OneDrive feature from an actual Windows initial deployment from resourcing, background activity and so on - and then IF the user actually needs it - to add it back in after the fact with a manual install.Īgain - need to understand why this method would be preferable.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |