Home Dashboard Directory Help
Search

Cannot create Isolated Environments in MTLM 2012 Update 1 and SCVMM 2012 SP1 by juapepa


Status: 

Closed
 as Duplicate Help for as Duplicate


4
0
Sign in
to vote
Type: Bug
ID: 780033
Opened: 2/26/2013 8:02:25 AM
Access Restriction: Public
1
Workaround(s)
view
4
User(s) can reproduce this bug

Description


I can create Standard and SCVMM environments by MTLM, but it doesn't work when I enable network isolation. MTLM displays the following error message: "TF259180: Team Foundation Server Could not find a network adapter in the VM".

If I go to SCVMM to see more details, I can see that one job "Create virtual machine" has failed. This shows the error: "Error (11427) The ownership for this object cannot be changed because the new owner is not a member of a user role that has access to this object"

In the properties of the virtual machine, I can see that the user role has not been changed and the internal network card has not been created.

I am sure the service account which is running the jobs is administrator in SCVMM and in the host where the machines are deployed.

All I know is that it worked before applying SP1 to SCVMM (upgrading hosts to Windows Server 2012) and Update 1 to TFS and Visual Studio.
Details
Sign in to post a comment.
Posted by Microsoft on 2/26/2013 at 11:28 PM
Thank you for submitting feedback on Visual Studio and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by Microsoft on 2/26/2013 at 8:50 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.
Posted by juapepa on 2/26/2013 at 8:04 AM
I reported this problem in the forum: http://social.msdn.microsoft.com/Forums/en-US/vsmantest/thread/cb91a9ee-d959-46cb-9bcf-406ef94d2ed5. They replied with the following work around: "So there is kind of a work around but it's tedious. Create a new environment with the VMs you want but don't enable Network Isolation. Start up the env and allow the test agents to go to the ready state. Shutdown the env and store in the library. After it's stored go to the library and enable NI on the env. When you deploy this env from the library it'll set up NI correctly. This tells me that deploying from the library is skipping the code path that is causing the problem."