interactiveSession=True mode produces a lot of problems
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.3k
- Forks
- 763
- PR merge metrics
- No merged PRs in 30d
Description
Hi everyone,
I've got an installer that only can be installed, when I'm in interactiveSession=True credentials mode: I don't know why it is like that, but after a lot of trying I accepted the fact, that I need to use the interactiveSession=True mode.
While it works on some Windows machines, I get on other Windows machines the error message Guest Operation Manager could not be contacted, even though the status of VMware tool is toolsOk. On some other machines I get an different error message saying something like Failed to authenticate with the guest operating system using the supplied credentials: Which is certainly not true, as i can login to the machine with the same credentials when I use the interactiveSession=False mode.
I really need help. I don't know what to do, to fix this problem. I'm very grateful for any help you guys could offer!
Thanks a lot!
With the very best wishes,
Tupsik
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The report provides no source files or tests; start at the credential-handling entry point for interactiveSession=True and reproduce the two reported errors on the affected Windows machines. Done would require a confirmed cause and an actionable fix or documented resolution that explains the differing authentication behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- authentication, infrastructure
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100