ReleaseEngineering/How To/Self Provision a TaskCluster Windows Instance: Difference between revisions

ReleaseEngineering/How To/Self Provision a TaskCluster Windows Instance (view source)

Revision as of 16:21, 30 May 2018

1,871 bytes added , 30 May 2018

Added info about running commands as Administrator

Pmoore

Confirmed users

142

edits

@@ Line 31: / Line 31: @@
     - 'generic-worker:allow-rdp:aws-provisioner-v1/gecko-t-win7-32'
-) Run the task, and when it starts, go to ''Run Artifacts'' to see the <code>rdpInfo.txt</code> file appear with rdp connection information.<br />
+) If you will require administrator privileges:
-) Enter the connection information into your RDP client of choice.<br />
-) Connect with screen resolution 1280x1024 ! Note, it is '''important''' to use this resolution for gecko tests, since this is the screen size used by the tests, and the screen size cannot change once you have made a connection.
+.1) Ensure you have scope <code>generic-worker:os-group:Administrators</code> in https://tools.taskcluster.net/credentials/
+If you do not have the scope, request it using a [https://bugzilla.mozilla.org/enter_bug.cgi?product=Taskcluster&component=Service%20Request Service Request] or by asking in <code>#taskcluster</code> IRC channel.
+.2) Add the following to the task payload:
+ scopes:
+   - generic-worker:os-group:Administrators
+ payload:
+   osGroups:
+     - Administrators
+) Run the task, and when it starts, go to ''Run Artifacts'' to see the <code>rdpInfo.txt</code> file appear with rdp connection information.<br />
+) Enter the connection information into your RDP client of choice.<br />
+) Connect with screen resolution 1280x1024 ! Note, it is '''important''' to use this resolution for gecko tests, since this is the screen size used by the tests, and the screen size cannot change once you have made a connection.
+== Performing operations as Administrator ==
+Until [https://bugzil.la/1465374 bug 1465374] is resolved this can be a little tricky.
+) Make sure you followed step 5 above!<br />
+) Open a regular command shell (e.g. ''Start Menu'' -> ''Run'' -> <code>cmd.exe</code>)<br />
+) From there check which users are in the Administrators group:
+ C:\Windows\System32>net localgroup Administrators
+ Alias name     Administrators
+ Comment        Administrators have complete and unrestricted access to the computer/domain
+ Members
+ -------------------------------------------------------------------------------
+ Administrator
+ task_1527672240
+ The command completed successfully.
+) Check the user you are logged in as is one of the above listed users:
+ C:\Windows\System32>whoami
+ i-015fe55bb8553\task_1527672240
+) Open a new UAC elevated command shell:
+ C:\Windows\System32>powershell.exe Start-Process cmd.exe -Verb runAs
+) This will require you enter Administrative credentials. You will be presented with a prompt similar to this:
+[[File:Screen Shot 2018-05-30 at 12.13.51.png|none|Screenshot of dialogue box asking for Administrative credentials]]
+Click on ''More choices'' and select the task user, and copy/paste the task password (<code>Ctrl-V</code>).
+You should now have a command shell running as Administrator!
 == Rerunning tasks after they have completed ==