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.

Sign up for GitHub

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

Jump to bottom

Design experience for installing cmdlets as CurrentUser #23

Closed
markcowl opened this issue Nov 22, 2016 · 1 comment
Closed

Design experience for installing cmdlets as CurrentUser #23

markcowl opened this issue Nov 22, 2016 · 1 comment

Comments

@markcowl
Copy link
Owner

Description

Need to decide what the experience should be for installing as CurrentUser and how this mixes with installing for the machine scope.

We need to avoid conflicts between machine-scope cmdlets and current user scope cmdlets.

We could

  • Always install as CurrentUser
  • Always install in the machien scope
  • Allow users to choose, but enforce the choice once made
  • Allow users to choose and find a way for the default profile to make sense in these situations
@markcowl markcowl changed the title Design experience for installing cmdlets as CurerentUser Design experience for installing cmdlets as CurrentUser Nov 22, 2016
@viananth viananth mentioned this issue Dec 16, 2016
Closed
@viananth
Copy link
Collaborator

This issue was moved to Azure#3301

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@markcowl @viananth