{"action":"opened","issue":{"url":"https://api.github.com/repos/dotnet/dotnet-ci/issues/185","repository_url":"https://api.github.com/repos/dotnet/dotnet-ci","labels_url":"https://api.github.com/repos/dotnet/dotnet-ci/issues/185/labels{/name}","comments_url":"https://api.github.com/repos/dotnet/dotnet-ci/issues/185/comments","events_url":"https://api.github.com/repos/dotnet/dotnet-ci/issues/185/events","html_url":"https://github.com/dotnet/dotnet-ci/issues/185","id":134986091,"number":185,"title":"Windows auto-image setup script should be reworked","user":{"login":"mmitche","id":8725170,"avatar_url":"https://avatars.githubusercontent.com/u/8725170?v=3","gravatar_id":"","url":"https://api.github.com/users/mmitche","html_url":"https://github.com/mmitche","followers_url":"https://api.github.com/users/mmitche/followers","following_url":"https://api.github.com/users/mmitche/following{/other_user}","gists_url":"https://api.github.com/users/mmitche/gists{/gist_id}","starred_url":"https://api.github.com/users/mmitche/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mmitche/subscriptions","organizations_url":"https://api.github.com/users/mmitche/orgs","repos_url":"https://api.github.com/users/mmitche/repos","events_url":"https://api.github.com/users/mmitche/events{/privacy}","received_events_url":"https://api.github.com/users/mmitche/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-02-19T21:58:54Z","updated_at":"2016-02-19T21:58:54Z","closed_at":null,"body":"Currently, there are some issues with the auto-image setup script on windows.\r\n\r\nWe need to have desktop access and the VM needs to connect to Jenkins (this is vs. SSH on Linux, which is simpler).  To do this, today the setup script installs a startup task (on log-in) as dotnet-bot, then sets up auto-login for dotnet-bot.  It then restarts the machine.  The issue here is that the script is running as the system user, and there seems to be some level of non-determinism in how long it takes for the full dotnet-bot user to appear.  There was a wait installed of about 5 minutes which helps, but this is inefficient.\r\n\r\nThe suggested workflow is to add the auto login into first, then restart.\r\n\r\n1) Download files as necessary (maybe put a loop here to avoid 404s)\r\n2) Install user as auto-login\r\n3) Put connection script into legacy startup folder??\r\n\r\n/cc @tannergooding "}}