I don't think I understand this. >>An elevated command is run through a scheduled task and for that task to work correctly, both the username and password must be set on the task definition
Okay, but same goes for regular WinRm connection except the scheduled task part. For a regular WinRm connection also both the username and password must be provided. So I do not see substantial difference here. Is there? >> You can created a scheduled task under different users hence why the username and password is set independently from the standard winrm username and password. Similarly, you might want to create a WinRm connection under a different user too, yet, packer supports that only for elevated user. It would be interested to find out why the distinction. As you can see I was not able to make sense of your explanation - could you please expand? Thanks, Andrew On Thursday, 16 November 2017 09:32:37 UTC+13, Jordan Borean wrote: > > An elevated command is run through a scheduled task and for that task to > work correctly, both the username and password must be set on the task > definition. You can created a scheduled task under different users hence > why the username and password is set independently from the standard winrm > username and password. > -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/packer/issues IRC: #packer-tool on Freenode --- You received this message because you are subscribed to the Google Groups "Packer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/2fdcf7d9-13b6-4613-a184-7dc33eeeb9c1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
