Students cannot "connect/disconnect the virtual machine's CD/DVD devices.

I will start with this context (and apologies for the wall o ' text): I'm a newbie.  I took the course VMware local community college offers [VMware ESXI Server Enterprise (CIS197)], but I've not yet certified. And I don't have a real experience, except what I have taught myself so far.

I recently accepted a position of learning associated with the College (think: glorified lab tech). I was tasked to work with stuff from VMware in the laboratory (among other things such as Cisco and Juniper equipment). There is no pass-down information like the previous left the position four months ago.

We have a single host running ESXi 348481 4.1.0. "We have vCenter Server (5.5.0, 1312298), running on Windows Server (2008 R2, Enterprise Edition).  Access host and vCenter through two different IP, addresses using the vSphere client (either 5.5 or 4.1, using a single application - depends to know if I connect to the host or vCenter).

At that time, the host is using local storage only (we have plans to change this, but it will take time).  The host is not a production on its own server, because it does not have a school systems.  He does, however, run a number of virtual machines in the lab, students use (Linux, Microsoft, Web design, etc.).  So, right now, I can't take it down.

I was tasked to create a number of virtual machines that students can use to make the basic labs of Microsoft Windows 7.  So far, I have:
-Created users, one per student, on the host.
-Creating VMs, deploy one per student, I have a gold model vcenter.
-Creation of roles to limit the access of students to just their VM attributed, which they access via client vSphere.
-Created a Windows Server 2008 R2 domain controller that is also a DHCP server.
-Created a virtual network, which is accessible only by the Windows 7 virtual machines and is not visible outside the vSphere environment (if I said this right - he does not see the Internet or school network).

So far, it's all good.

However, I need to be able to allow students the ability to edit the ISO file on which their VM points in order to complete some laboratories. I guess they would use the button "connect/disconnect the virtual machine's CD/DVD devices" on the taskbar (or console window). It does not work.
I searched a lot and found that others have had the same problem.  However, all of the solutions I've tried so far have failed.  When they click 'Connect to ISO image on the data... store. "they get an error message means nothing to me,"an internal error has occurred in the vSphere Client. Details: Object Reference not set to an instance of an object. Contact VMware support if necessary.
The role that I use for students has these settings:
-Data store > Browse the data store
-Virtual Machine > Configuration > change the settings of the device
-Virtual Machine > Configuration > settings
-A bouquet under the virtual machine > Configuration >
-Configure CD media
-Console interaction
-Connection of the device
-On
-Power off
-(and more, which I don't believe are important to the question)
-State > create the snapshot
-State > go back to the snapshot

I tried "Virtual Machine > Configuration > add existing disk", "Virtual Machine > Configuration > add new disk" and "Virtual Machine > Configuration > add or remove an instrument" with no luck.

Either by the way, the root account can do all these things, but no other account can - not even a game as an administrator account.

I've seen mention I have apply the role in the data store.  It is perhaps part of the problem. I can't see the data store when I am connected to the host (wellll, I can, if I click on the host name, then on the Summary tab - but roles do not apply at this stage).  I see is 'Inventory' (which has virtual machines and Pools of resources), 'Rôles' and 'log files '.

I can see the data store when logged in vCenter. Roles of students, however, are defined on the host computer. If I clone the role of users in vCenter and change this role cloned to have "permissions" that those who are on the host computer and then apply it to the data store, it still does not work.

So, after all this (which I hope I've included all the necessary information), what can I do to allow the students to change ISO to which they are connected?

Of course, if I left something, or if someone has a question, please ask.  I want to get this resolved as soon as I can.

It turns out that I finally found the solution to the problem.

What 'fixed', it is sufficient to vSphere Web Client to vCenter, which then allowed us to use Single Sign-On (SSO).  This, in turn, allowed us to define users and roles in vCenter (rather than having set them up directly on the host computer) which have then been applied to the VMS of students and also to the data store.

Now, they can (de-) connect their ISOs at will.

I find it interesting that vSphere Client (application) shows the users (and the things that they have access to), but it won't let you set of users.

Tags: VMware

Similar Questions

  • VMware Fusion cannot connect to the Virtual Machine

    Then the Setup program tries to update to VMware Fusion 2.0.2 to 2.0.4 to a standstill during the process, and now I can't start Fuison, I get the messge seen below. I have an installed registration number and the software is registered.

    Running 10.5.6 on a MacPro double 2.8 quad. XP Pro under Fusion.

    MRomine wrote:

    I have an installed registration number

    Do you mean the serial number?  In any case restart the Mac and if this does not make a difference then uninstall/reinstall VMware Fusion and restart the Mac later.  Note: VMware Fusion of uninstalling/reinstalling does not remove your Virtual Machines.

  • Unable to connect to the virtual machine after adding new eSATA drive

    Hello.

    I'm trying to connect my new 2 TB drive in VMWare Workstation. It is connected via eSATA to the host computer, and it works. I added the drive to the desktop as a new "physical disk." But now I can not power the workstation the most.

    (1) when I start the VMWare Workstation it right ask admin (it didn't need before).

    (2) when I turn on the prompt does not charge even the bios. It shows a rear screen with the logo of VMWare for a while and then stop saying: "VMware Workstation cannot connect to the virtual machine. Make sure that you have the rights to run the program and access all directories that it uses and access rights to all directories for temporary files. »

    The host is running Windows 7 x 64. The workstation runs under the standard user account.

    Thank you.

    Hmmm - it's unexpected - works for me here - only difference: I tried with only 1 TB disks.

    You start Workstatiion as an administrator?

    _________________________

    VMX-settings- WS FAQ -[MOAcd | http://sanbarrow.com/moa241.html]- VMDK-manual

  • Disable the Internet connection for the virtual machine.

    Is it possible to disable the internet connection to the virtual machine from Windows XP with on the neutralization of him on my Mac?  I just want to connect to the internet if/when updates are required.  Any other time.

    I run Windows XP Pro SP1 on VMware Fusion v. 2.0.1

    You have a virtual NETWORK adapter, Fusion UI calls it just a network adapter (which, due to a bad design, choice flowing from the settings box, but it's another criticism for another time...) This screenshot shows a disconnected virtual NIC:

  • Cannot connect to the virtual store of Toshiba

    Nice day.

    I am from Slovakia. I bought online for my small son Tablet Toshiba Journe. We cannot connect to the virtual store of Toshiba. The worst thing is that I don't ever account of Toshiba's e-store. Unique number I found is the tablet in the user manual and PIN: GMH300087E10. Can you tell me please give access to the store online, but either way or help me to recover the virtual store. Son would be very happy.

    Thank you. Palo

    Hey. Write me a mail, I will send you instructions on the use of this tablet. Online store does not work me and once I have already reset the account.

    Roman

  • whenever I have to connect to the virtual machine asks me to enter login and password I can't save the credentials

    Hi, I used Windows Virtual PC XP mode for awhile and I just do a fresh install, and I'm having a problem that I seem not to be able to solve.

    After you enable the integration features, I got to the Windows Security login screen. I typed in the login and the password, but I accidentally made a mistake and could not connect. I clicked on cancel and was then in the XP login screen, where I entered then the right login and password and it me connected to the virtual machine XP without problem.

    Now, the problem I have is every time I connect to computer virtual it asks me the login and the password on the login screen of XP and I don't have the option to connect using the login Windows Security screen, so it do not give me an option to save my password and login information. So, to make things worse is that moment every time I have to resize the virtual pc it then asks me to log in again.

    Is it possible to return me to the Windows security login screen where can I put my login instead of the XP login screen when it is not an option?

    Hi Richard,

    The question you posted would be better suited in the TechNet Forums. I would recommend posting your query in the TechNet Forums.

    TechNet Forum

    http://social.technet.Microsoft.com/forums/en-us/w7itpronetworking/threads

     

    Hope this information helps.

  • Smart card reader does not correctly connect once the virtual machine is restored from sleep using the vmrum controls

    Smart card reader does not correctly connect once the virtual machine is restored from sleep using the vmrum controls

    Scenario is,

    1. smart card reader is connected to the VM with card inserted in

    2 initiate a prompt suspension of the VM toolbar

    3. now to resume the virtual machine by using vmrun command into the host machine

    WS t vmrun start xxx.vmx

    Now, the recovery of VM but the smart card reader that was previously connected does not work properly in VM that is to say, sometimes after CV chip card reader driver is uninstalling and a few other times, chip connected to the drive is not available on a virtual computer

    My requirement is after power, smart card reader can stay connected to the virtual computer with the already installed driver and the smart card.

    Kindly help with this problem.

    Host operating system: Victoire 2012 R2

    The VM OS: win 10 x 64

    Thank you!!

    Dear all,

    I had a work around for this problem. By adding "usb.autoConnect.device0 ="0xVID:0xPID"" this statement to the VMX file, solves this problem, that is, whenever the VM is wake-up by clicking on the link CV or using vmrun commands, it connects the unit in question automatically and it is charging correctly with his driver. Obtaining smart card detected after sleep\hibernate with no problems.

    VID & PID is respective ID of the device that can be seen in the properties of the Device Manager "Device Instance path".

    For more information about this, visit VMware KB: automatic connection of USB devices to the virtual machine power on

    ~ Surendra

  • Not allowed to connect to the virtual machine after archive / installation of the Tiger

    I made an installation of archive / install OS 10.4 as part of the maintenance of the system. Today, VMware does not connect to the virtual machine and wants me to check my right to use the program and its directories.

    I recently bought VM Fusion and bought the license / registered. Something to do with installing the OS, maybe, but everything else works well.

    I don't have reinstall Fusion as part of the installation of archive / install.

    I would say that (this will not affect your VMS) because it is an easy thing to do and should decide on problems of permissions on the application itself.

  • Unable to connect to the virtual machine after they are created

    I installed VMware view and connected to my server Vcenter. Composer, I installed the server vcenter and View manager recognizes it.

    I created a virtual Windows Vista machine, is joined to the domain and instant, it.

    I then created a persistent office pool and allowed users to access.  I can see the virtual machine created the VCenter

    However, the view Client cannot access the virtual machine (he can see the office pool) bit tells me that the customer is not available.

    Any ideas on what I missed?

    Go to the desktop the pool in view Administrator resources and check the status, it should say "Ready".  If this is not the one usually means that there is something blocking the port 4001 of the agent on the view connection server.  I got this when deploying a pool on a different subnet and there is a network between the areas of the network firewall.  The Vista firewall can sometimes be reset on the deployed virtual check computer so who has not been reactivated and adjust the GPO if necessary.

  • "Unable to connect to MKS" when connecting to the virtual machine shared

    Hello

    I have a handful of Shared VMs Im trying to access remotely with VMware Workstation Pro 12 (same version on the client and the host - two Windows 10 machines). I am able to connect to the host that shares virtual machines, I can see all the virtual machines shared, open the virtual machine (as in it opens in a tab within the workstation) and virtually no action on the virtual machine including all power options, instant, change settings, etc.. The problem is that if I turn on a virtual computer (or connect to an existing virtual machine under tension, I get the following error and Im not able to access the actual console since it remains as a black screen.

    Unable to connect to the MKS: (name of user and password) Login incorrect.

    I also noticed that on the client Windows Event Viewer is to launch the following warning events at the same time that the error in the Workstation has been lifted - Im not seeing any on the host are thrown.

    vmware1.png

    vmware2.png

    I've seen a lot of posts here with users who run the question and he usually ended up being a network problem. I turned off the Windows Firewall on both machines, checked ports 443 and 902 listening on the host and Im in telnet from the client to the host on port 902. I also saw another suggestion for updating the client Windows hosts file to include [host name] [IP address] and [FQDN of the host name] [ip address], but this subject seems not helped either.

    Suggestions in this regard does not happen what keeps or where to find more information about the cause?

    Thank you!

    Post edited by: Tim Graffam

    Thank you for using the workstation. I think that this will solve your problem.

    Unable to connect to the MKS: (name of user and password) Login incorrect

  • Unable to connect to the virtual machine via telnet

    Hi all

    The VM on Vcenter everything is perfect with the network connection. I can't do a ping of the virtual machine remotely but I can not connect via telnet.

    For the same reason? And even more, I have disabled the fiewalls of the virtual machine (Windows 2008 R2).

    The error that says: could not open connection to the host, on port 23: Connect failed

    Can you please let me know how to solve this problem?

    Since there is nothing blocking the traffic of the virtual machine in ESXi, you can begin troubleshooting in the guest OS. For example is running telnet server and configured to accept connections?

    André

  • No network connection between the virtual machines on different hosts ESXi

    I have several 5.0 ESXi hosts in a cluster managed by vCenter Server 5 and I have network problems:

    1. [Host A] running a virtual machine can ping any other computer virtual running on the [host A] great!
    2. A virtual machine running on host [B] can ping any other virtual machine running on [B] home - very well!
    3. [host A] (from the ESXi console) can ping any virtual machine running on [B] home - even better!
    4. [B] home (from the ESXi console) can ping any virtual machine running [host A] - beautiful set!
    5. A virtual machine running [host A] can not ping any virtual computer running on host [B] and vice versa - bad, very bad!

    So basically the problem is that the virtual machines can communicate on hosts. It is a major problem that I need to fix, for obvious reasons.

    Networking on all hosts is configured exactly the same way: a unique and standard vSwitch with a pair of gigabit network cards grouped, vmkernels configured for the vMotion, NFS and network management and a group of ports configured for the VIRTUAL local area network used by the VMs. (vMotion works fine on hosts, storage vMotion works very well too.) All virtual machines are servers Windows (2003 and 2008).

    Reason #3 and #4 above, my assumption is that #5 must be the result of an ESXi/vCenter configuration issue and not a problem with the switches of material upstream. Is this a reasonable assumption?

    Whatever it is, can anyone offer suggestions on how can I fix? It is quite annoying as I'm pretty sure that these hosts are configured in the same manner as those of our production cluster, which does not at all these problems!

    Thanks in advance for any help you guys can provide.

    To be honest, it looks like a problem with your physical network-

    How is the physical network configured - are NIC connects it to the same physical switches? Are the virtual machines on the same subnet? If this is not the case, they are able to ping the gateway sbnet? Can you piing host IP address from the virtual machines?

    I also moved it to a forum more approiate.

  • regarding the connection of the virtual machine to the external network

    Hi all

    I'm new to vmware and I have two virtual machines with windows operating system 7. How to connect to the external network?
    can I assign a NATed IP to them?

    If the need to talk about virtual computer internally, you can add all the VM in the same VSS(vswitch 1) at the same port group Network2 VLAN40. for virtual machines on that VLAN can communicate among themselves without problem and configure all virtual machines with IPs in VLAN40. no need for an another vs.

    For internet access, first check with your network administrator, if the VLAN has a routing or this VLAN has access to the DNS server that provide internet or the proxy server for internet access. He will confirm. or you can also check if this virtual machine are able to ping your DNS server or proxy servers. If its power of ping so it has access to this network. Configure the virtual machines that you configure a physical computer for internet access.

    If the VLAN has access to the internet, even that you configure the physical server with connection DNS and proxy for internet access only the configuraiton even here too in the virtual machine.

  • Could not power on VM: no space is available on the device: cannot power on the virtual machine.

    VMware esx ei, 3.5.0 123629

    Physical memory: 64 GB

    Hard drive: 1.63 TB

    7 virtual machines. 5 of them are configured with 4 GB memory and 2 of them with 2 GB of memory. I am able to power on 3 virtual machines with 4 GB of memory.

    When I try to turn on 4th VM with 2 GB of memory, I get this error message "could not power on VM: no space is available on the device: cannot power on VM.»

    I would like to know if this is the limitation of the ESX Server? How should I size the memory for VMS if I want to run every 7 virtual machines to the

    Moreover, given that I have 64 GB of physical memory. Is there documentation that provides a report of the maximum allowed memory configurable

    compared to the virtual memory?

    Thank you

    Ganesh.

    Ganesh,

    Memory reservations are defined based on VM by VM.

    You can allocate more memory to the virtual machines you have in your host (it's not really a good idea to go crazy with the overcommitment of memory, but some level of excessive pressure is used in general).  Memory applied to your VM resources are shares, bookings and VMkernel Swap limits.

    Just to illustrate:

    You allocate 8 GB memory to a virtual computer.  If you take all the parameters by default, ESX will allot a 8 GB VMkernel Swap file in the base directory of your VM (it will have the extension ".vswp") this VMkernel Swap file is a safety net.  Your virtual machine, at this stage, can consume up to 8 GB of memory If physics is available from the host.  If the memory of your host is overcommitted, some of the available memory 8 GB could be allocated on 8 GB VMkernel Swap file.

    If you set a reserve of memory - 2 GB - this means that the vmkernel will still award the first 2 GB of memory used by the virtual machine to the physical memory.  This is not means that the 2 GB of memory reserved is carved off the coast and completely dedicated to the virtual machine.  This means that the vmkernel offers up to 2 GB of RAM to the VM when and if she needs to use it.  It is a guarantee that the memory will be available upon request.  Because of this guarantee of the VMkernel, VMkernel swap file only has to make sure that the 6 GB memory is satisfied (4 GB total less the 2 GB reserved), so the VMkernel Swap file is only 6 GB in size.

    Actions are a mechanism for prioritization and limits are a cap on physical memory ever allocated to the VM.

    You can set up any number of memory for the virtual machines that you want - frankly, overcommitment of memory for ESX is a very good thing, but you must be vigilant about watching your systems if approve you.  If you have 64 GB of RAM, and you only configure your virtual machines to use total 32G, then you lose 32 GB of RAM.  If you allocate, say, 96 GB of RAM (total) to your virtual machines, then you look at a 50% overcommitment.  What to watch in overcommitting memory is application performance (and more importantly - perception of the user of this performance) and also the memory ballooning and VMkernel Swapping activity.  Those who can both will be in graphics performance in VirtualCenter.  I would recommend reading the Guide to management resources for more details.

    Hope that provides an overview.

    Thank you

    -jk

  • Cannot depend on the virtual machine after reboot

    Hello world

    Thanks for reading this post.

    My version VM ESXI4.1.0, 348481.

    Here's my problem:

    One day my VM was hanged, and I tried to restart.

    After the reboot, it can be turn on. And I tried to remove the inventory and to recreate the virtual machine.

    However, I can't find the. VMX file in the data store.

    So I tried to create a new virtual machine and put the files in this folder, but it can also work.

    Please see the capture screen, (http://clip2net.com/s/2aNUG)

    Could someone give me guidance and advice how to solve?

    Thank you very much.

    According to the latest vmware.log file, you have tried to access one of the files base/flat with a wrong header file (40 GB)! This hopefully not bad data on the virtual disk. In any case, I've recreated the missing files (see attachment), so you should be able to redo the work of the virtual machine. Because the vmware.log file did not help, I've recreated the instant chain according to the timestamps of the delta file.

    Please follow it below mentioned steps exactly to avoid problems in case something does not work as expacted:

    • Make sure the flat files as well as files 2 6 delta are still in place (not renamed,...)
    • remove the virtual machine from the inventory of the host (right-click-> "Remove from inventory") ESXi
    • delete the temporary/second .vmx unless there is a special need for it
    • Download the files from the .zip file in the folder of the virtual machine on the data store
    • Click right newly downloaded virtual machine's .vmx file and choose "add to the inventory.
    • create a new snapshot (this is important!)
    • Turn on the virtual machine

    If something is not or you have questions, please send back before moving on to the other steps.

    If everything works as expected you should consider the 'Delete All' snapshots in snapshot Manager. This will release not only almost 200 GB of disk space, but can also improve the performance of the virtual machine. Because the size of the snapshot, remove snapshots may take some time, probably in hours!)

    André

Maybe you are looking for