neonetman Posted October 11, 2017 Posted October 11, 2017 We are currently running SCVMM 2008 sucesfully. I've recently created a batch of 32 users on our curriculum domain, each identical (created via a software utility). If I log in to the PC with some of the users, and then access SCVMM web portal, they will connect to VM's with no issues at all, however other users come up with a message saying Virtual Machine Manager lost the connection to the virtual machine because another connection was established to this machine This is related to the user account used to logon to the the PC rather than which P it is, or which user logs in the SCVMM console I've tried a compare and contrast between a user that works and a user that doesn't, cleared the appdata an checked for hidden files in the documents folder. All these users use the same mandatory profile. I'm absolutely at a loss on this so hoping you can help Cheers
neonetman Posted October 12, 2017 Author Posted October 12, 2017 It's a worry if no-one is able to help with this.
Steve21 Posted October 12, 2017 Posted October 12, 2017 If I'm honest I started reading it and got confused half way through as to what you were trying to do I'm going to assume you're trying to use these for a virtual lab? And giving people access to logon to the self service portal? (If you're on about 08 still). If so you'd need to ensure that the users connecting actually have access to manage the VM in that way, as if you're not clicking remember credentials etc it pulls the details across from the one you're logged on and not connecting with so they would probably get rejected etc. What permissions do these users have, and what are they actually connecting to the portal with? Steve
neonetman Posted October 12, 2017 Author Posted October 12, 2017 The user login to our curricum network as normal, and then use those same credentials to login to the VMM portal. Once logged in there, they have been granted ownership of a single VM (one per user, so each user gets a different VM) on a seperate sandboxed network. The idea is they start and then connect to the virtual machine and then login to that with credentials from that network. This works with about 50% of users, however the other 50% get the error message when conencting the the VM.
Steve21 Posted October 12, 2017 Posted October 12, 2017 One of the ones that broken, when you connect try to disable the save cred option and see if that gets the same error again Steve
neonetman Posted October 12, 2017 Author Posted October 12, 2017 I've already tried both with saved and non-saved creds - it makes no difference
Steve21 Posted October 12, 2017 Posted October 12, 2017 Could you do a screenie of their azman setup if there's nothing special on it Saves typing a few things. Steve
Steve21 Posted October 12, 2017 Posted October 12, 2017 Azman is where the permissions for users to connect/manage the servers are stored. If you run azman.msc on the HyperV and connect to it's auth database at ProgramData\Microsoft\Virtual Machine Manager think it's called initialstore on 08 Or are you adding the permissions another way? Steve
Fazza Posted October 12, 2017 Posted October 12, 2017 azman? Lost me there.. azman=Windows Authorization Manager https://msdn.microsoft.com/en-us/library/bb897401.aspx
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now