[jbosstools-issues] [JBoss JIRA] (TOOLSDOC-536) Shared install on Windows will only use private folders for updates/workspace if the shared install folder is read only

[Misha Ali (JIRA)]

    [ https://issues.jboss.org/browse/TOOLSDOC-536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13269094#comment-13269094 ] 

Misha Ali commented on TOOLSDOC-536:
------------------------------------

This is potentially worth documenting in the new Forge doc if it is still valid. [~supriya.bharadwaj], since you recently worked on Forge, can you touch base with the relevant SMEs about whether this is still valid for devstudio or if we can just close this as outdated?

> Shared install on Windows will only use private folders for updates/workspace if the shared install folder is read only
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: TOOLSDOC-536
>                 URL: https://issues.jboss.org/browse/TOOLSDOC-536
>             Project: Documentation for JBoss Tools and Developer Studio
>          Issue Type: Story
>          Components: Installation Guide
>    Affects Versions: 4.2.0.Final
>            Reporter: Nick Boldt
>            Assignee: Michelle Murray
>         Attachments: jbds8b2-windows8.1-child-user-private-install-updated-via-central.png, jbds8b2-windows8.1-shared-install-readonly-now-installs-into-users-kid-.eclipse-folder.png, jbds8b2-windows8.1-standard-user-install-error-in-central.png, jbds8b2-windows8.1-standard-user-private-install-was-able-to-update-via-central.png, jbds8b2-windows8.1-standard-user-shared-install-last-used-by-dummy-launched-by-kid-error.png, jbds8b2-windows8.1-standard-user-shared-install-last-used-by-dummy-launched-by-kid-error2.png, jbds8b2-windows8.1-standard-user-shared-install-last-used-by-dummy-launched-by-kid.png, jbds8b2-windows8.1-standard-user-shared-install-was-able-to-install-into-shared-install-folder.png, w-shared-install-jbdevstudio-security-permissions-remove-authenticated-users.png, w-shared-install-jbdevstudio-security-permissions.png, win81pro-details.png
>
>
> To test the user experience on Windows, I created three accounts:
> * nboldt (my own admin user)
> * {color:orange}*dummy*{color} (a standard user)
> * {color:green}*kid*{color} (a child user, which is a standard user but with Family Safety logging - http://windows.microsoft.com/en-ca/windows-8/create-child-account )
> Both the child and standard users were able to install JBDS into their own home folders and perform an installation from Central:
> !jbds8b2-windows8.1-child-user-private-install-updated-via-central.png!
> !jbds8b2-windows8.1-standard-user-private-install-was-able-to-update-via-central.png!
> ------
> However, there are problems when using an Admin user-installed shared install folder for JBDS.
> Steps to repro:
> *As nboldt / admin user* 
> * install JBDS 8.0.0.Beta2 (B104) into W:\shared-install\jbdevstudio (using default ownership/permissions)
> *As dummy / standard user*
> * Log in
> * Launch the shared JBDS
> * Install something from Central
> !jbds8b2-windows8.1-standard-user-shared-install-was-able-to-install-into-shared-install-folder.png!
> *PROBLEM*: standard user should not be able to install new features into the shared install folder
> *As kid / child user*
> * Log in
> * Launch the shared JBDS
> * Noted that the suggested path for workspace was the one last used by *dummy user*, to which that user doesn't have read permission
> !jbds8b2-windows8.1-standard-user-shared-install-last-used-by-dummy-launched-by-kid.png!
> !jbds8b2-windows8.1-standard-user-shared-install-last-used-by-dummy-launched-by-kid-error.png!
> !jbds8b2-windows8.1-standard-user-shared-install-last-used-by-dummy-launched-by-kid-error2.png!
> *PROBLEM*: should default to current user's home dir, not another user's previous workspace selection



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)