[ 
https://issues.apache.org/jira/browse/VCL-1062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095092#comment-16095092
 ] 

ASF subversion and git services commented on VCL-1062:
------------------------------------------------------

Commit 1802521 from [~jfthomps] in branch 'vcl/trunk'
[ https://svn.apache.org/r1802521 ]

VCL-1062 - stop using Administrator account for Windows imaging reservations

requests.php: modified AJconnectRequest: removed check for imaging reservation 
and OStype being windows to set user to Administrator

utils.php: modified sendRDPfile: removed check for imaging reservation and 
OStype being windows to set user to Administrator

xmlrpcWrappers.php: modified XMLRPCgetRequestConnectData: removed check for 
imaging reservation and OStype being windows to set user to Administrator

> stop using Administrator account for Windows imaging reservations
> -----------------------------------------------------------------
>
>                 Key: VCL-1062
>                 URL: https://issues.apache.org/jira/browse/VCL-1062
>             Project: VCL
>          Issue Type: Improvement
>          Components: vcld (backend), web gui (frontend)
>            Reporter: Josh Thompson
>             Fix For: 2.5
>
>
> A problem was discovered when making an imaging reservation for an AD joined 
> Windows image where there is a logic problem between using the logged in 
> user's account from AD and using the local Administrator account for the 
> reservation. It is no longer necessary to use the Administrator account for 
> imaging reservation. Additionally, any reservation where the user would have 
> rights to select the reserved image as a base image can be captured. In these 
> cases, the Administrator account is not used anyway.
> The simplest solution, and one that helps to simplify the code overall, is to 
> just stop using the Administrator account for Windows imaging reservations 
> and simply always use the logged in user's account.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to