Closed dskaram closed 5 years ago
Some fields to consider with would be
* Host name * Domain name * Share credentials * Share location * Placeholder text for syntax * Short text describing instructions to mount
* Ability to push multiple SMB shares down to different share locations * Pre define domain field * Description of SMB Share / Mount * Push down via a Group Policy * Generic hostname, with user to input share name, ID and password * Long Term, SSO for seamless access
For first iteration - this will just allow the policy to specify a fixed list of urls, and those urls will appear in the new share selection/input combo box.
Keep the bug open after the initial commits for further iterations.
This implementation is deprecated and SMB is now supported natively in Chrome OS since 71.
crbug.com/913691 and crbug.com/878502 track policy support/premount for Chrome 73.
Since Chrome 71, SMB is now natively supported by Chrome OS and this Chrome extension/app is deprecated. The new implementation is an order magnitude or two faster and much more reliable.
On Chrome 71 or higher you can:
Open the files app Click the "three dot menu" in the top right Choose "Add New Service" Choose "SMB file share"
A dialog in settings will open (in 72 and later it's a standalone dialog). Enter your share information as before.
You can uninstall the chrome app as it will be deprecated in the near future.
If you have bugs with the new implementation you can open them at crbug.com under component "Platform>Apps>FileManager"
For the enterprise use case, admins need to configure the app with policies e.g. the default share location.
This is crucial for enterprise deployments as the only alternative is fanning out instructions to users via email and that is not a viable alternative in companies, especially large ones where these configurations might differ across deployments.
This is an enterprise feature which is described fully here
https://www.chromium.org/administrators/configuring-policy-for-extensions