Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Windows Roaming Profile Support #4340

Closed
MTRichards opened this issue Jan 8, 2016 · 3 comments
Closed

Windows Roaming Profile Support #4340

MTRichards opened this issue Jan 8, 2016 · 3 comments
Assignees
Labels
p2-high Escalation, on top of current planning, release blocker research
Milestone

Comments

@MTRichards
Copy link

Opening this as a placeholder for discussing the support of windows roaming profiles, and defining requirements. At the outset, the user story looks like this:

As an admin, I want to be able to support roaming profiles with the desktop sync client so that my users can access their files when they log in even if they are roaming onto a different PC.

Acceptance Criteria:

  • Specify a path (in ownBrander?) that is not the default path, so that the files can be synced to the user's roaming profile storage, rather than to this specific pc. Path should include variables.
  • Not entirely sure...?
@MTRichards MTRichards added this to the 2.2-next milestone Jan 8, 2016
@MTRichards MTRichards added research p2-high Escalation, on top of current planning, release blocker labels Jan 8, 2016
@MTRichards
Copy link
Author

Need to flesh this out for 2.2.0.

@guruz
Copy link
Contributor

guruz commented Jan 8, 2016

@dragotin
Copy link
Contributor

duplicate of #684

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
p2-high Escalation, on top of current planning, release blocker research
Projects
None yet
Development

No branches or pull requests

4 participants