Problems installing a Virtual machine from K2000
We have the possibility to install both Windows 7 and Windows 8 from KACE. For a while we have been testing new software and because of that new images deployed from KACE. I have tried to perform a network install on both VMware Player 7 and VMware workstation 11 but the installation process halts after a couple of minutes. The error-message states that a driver/program is not a valid 32-bit software. A consultant suggested this is because the virtualization software lacks a BIOS. In VMware workstadion you can decide if you want to se BIOS or a UEFI. If I choose a BIOS I get the same error as when I am using VMware player and when I use UEFI it seems like it can't perform a network boot. In both VMware workstation and VMware player I set the NIC in bridged mode.
Any suggestions?
Any suggestions?
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
anonymous_9363
9 years ago
The good news is that you now know that the consultant has no clue what he/she is talking about and his/her services can be dispensed with.
Does KBE allow you access to DOS, like SCCM does, so that you can view local logs?
Does KBE allow you access to DOS, like SCCM does, so that you can view local logs?
Posted by:
hutcha4113
9 years ago
When you boot up the VM, are you getting to the Scripting/Image screen - or does it fail before then? Reason I ask is we had the same issue when trying to boot up in Hyper V. The PXE portion would work fine, but as it was loading the KBE it would fail part way through (can't remember the error).
The issue was the VM NIC adapter. We needed the Adapter that is installed as part of the VM to be "Emulated (Legacy)" and not "Synthetic". The Synthentic is newer in Hyper V and allows more features, etc., but does not like being used with PXE booting.
Work around for us was to install both Emulated and Synthetic on the VM configuration - PXE boot it and install the image. Once the system is loaded - remove the emulated adapter from both the OS and VM config (OS first).
The issue was the VM NIC adapter. We needed the Adapter that is installed as part of the VM to be "Emulated (Legacy)" and not "Synthetic". The Synthentic is newer in Hyper V and allows more features, etc., but does not like being used with PXE booting.
Work around for us was to install both Emulated and Synthetic on the VM configuration - PXE boot it and install the image. Once the system is loaded - remove the emulated adapter from both the OS and VM config (OS first).
Comments:
-
I have googeled this and everywhere says I have to edit the .VMX-file manually. I have talked to the same consultant as mentioned above and he says I have to use either E1000 or WMXNET as NIC but that I have to choose this in the GUI. If I edit the .VMX-file manually it doesn't work.
Any tips on where to find this in the GUI for VMware workstation 11? - MesaMe 9 years ago-
Sorry..not familiar with VMware. In Hyper V you use the Hyper V management console, right click on the VM, and edit the hardware properties. One of the options is to add a NIC - so we select the appropriate one. - hutcha4113 9 years ago
Posted by:
MesaMe
9 years ago
I get the scripting/image screen and I get the same error whichever option I choose.
How did you install the Emulated and Synthetic on the VM configuration?