<li><strong>If you want to login to supportXMR.com in order to change
the minimum payout threshold, you can first run your VMs with the
startup-script generated by the <ahref="file:///home/leonidas/git_workspace/azurecloudminingscript.github.io/Turn_your_Azure_Free_Credits_into_Cryptocurrency.html">quickstart-instructions</a>
startup-script generated by the <ahref="Turn_your_Azure_Free_Credits_into_Cryptocurrency.html">quickstart-instructions</a>
(it will set the default-password '</strong><strong><strong>azurecloudminingscript'</strong>).
</strong>After you have submitted a share the login will be
created and you can change the password through the GUI at
...
...
@@ -418,6 +418,26 @@
Sumokoin.</strong><br>
<strong></strong></li>
</ul>
<li><strong>Many pools support assigning a worker-ID to your miners.</strong>
The pools typically display the achieved hash-rate for each
worker-ID separately. Read the pool's documentation to find out how
it works exactly. Some pools expect the ID as a suffix to the
wallet, then you can just enter it in the form before generating
your startup-script. Other pools (like supportXMR) expect the ID in
the password-field. In that case you can edit the generated
startup-script by hand. Additionally, there are some variables which
you can use as well (compare it to the startup script generated by
the <strong><ahref="Turn_your_Azure_Free_Credits_into_Cryptocurrency.html">quickstart-instructions</a>
</strong>to see how it should look like):</li>
<ul>
<li>${AZ_BATCH_POOL_ID} : The name of the
azure-pool used</li>
<li>${AZ_BATCH_ACCOUNT_NAME} : The name of the
azure-batch-account used</li>
<li>${AZ_BATCH_NODE_ID} : The name of the
azure-pool-node. Typically this is a complicated name with some
special characters. Use at your own risk!</li>
</ul>
<li><strong>Azure has a standard-limit of 20 low-priority-cores per
region</strong>. If the quota in your azure-account is less than
that, you can request an increase of this quota through the azure