I've build the image for openstack via https://github.com/cloudbase/windows-openstack-imaging-tools It's Win10 Pro N
PS C:\Users\Admin> [System.Environment]::OSVersion.Version Major Minor Build Revision ----- ----- ----- -------- 10 0 19041 0 The issue you've linked seems relevant, but in my case even `net use` doesn't work when `ansible_become_pass` is set, i've found out that that when i use bacome w/o password all steps are executed in the same logon session (i've check it with subsequent win_whoami), when become is used with password defined logon session ids are different, but it should work, cause `cmdkey` sees the target's creds. So workarounds for me: 1. delete ansible_become_pass var 2. define usename/password (for initial connection) for ansible_become_pass. And the one more strange thing is that Error code may vary, sometimes it's 86, sometimes it's - "The user name or password is incorrect, Win32ErrorCode 1326" - this one is far beyond my understanding. My initial task was to mount share for java app which works via nssm under Local System Account privelegies (i guess it's the same as runas + SYSTEM user), so for that purpose (thx to your blog's article) i've used "global" scope mapping. пятница, 19 июня 2020 г., 2:59:27 UTC+3 пользователь Jordan Borean написал: > > There's been a recent issue on this problem > https://github.com/ansible-collections/community.windows/issues/96. I > can't say I've experienced this problem personally as if you have a > credential Windows should be using that to connect to the network path. Are > you potentially on a newer build of Windows 10? > -- You received this message because you are subscribed to the Google Groups "Ansible Project" 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/ansible-project/5cbab99b-7b4f-465a-a155-a803ce20da13o%40googlegroups.com.
