0xe0000100 при установке windows server 2012
— I have a Windows 2012 Server Datacenter (host) up and running (Roles: Fileserver and Hyper-V)
— When trying to install Windows 2012 Server Essentials as a Virtual Machine I get the error:
«Windows installation encountered an unexpected error. Verfiy the installation sources are accessible, and restart the installation.
directly after Keyboard-Language selection and pressing «Install now».
— it does not matter whether I try installing from an ISO or from a CD.
— Already downloaded the ISO 5+ times and tried again — same error.
— Already re-installed the host (complete HDD-Erase) — same error.
— tried to find my way at command-prompt level of the installation — no luck.
— an installation of Windows2012 Server (Standard/Datacenter) as VM works without any problem.
I found that when I had this same issue, I was not giving the Hyper-v enough memory to pass the Hardware check. I upped the startup memory to at least 2048MB and that was enough to get the server to image in Hyper-v.
Hopefully that works for you as well.
What is the size of disk you have allocated for windows server_2012_essentials installation? Can you provide information what step install fails as provided in screenshots on this page http://blogs.technet.com/b/sbs/archive/2012/08/13/windows-server-2012-essentials-deployment.aspx
Dynamically expanding virtual hard disk
current file size: 4 MB
maximum disk size: 127 GB
(also tried it with english time/curreny/keyboard setting)
Setup Step 2:
clicking «Install now» (no screenshot)
Setup Step 3:
error occurs quite fast after clicking «Install now» from step2
Do you have an idea about what might be wrong?
I already downloaded the iso from msdn around 5-7 times (using two different internet connections). I even tried downloading two different languages of the iso (en/de) — same behaviour.
Never got an error from the downloadmanager though..
Can you try the installation with a fixed VHD? Say around 100 GB?
downloaded the iso once again and added a 127GB «Fixed size virtual hard disk» vhdx and 2nd try a vhd
Same behaviour, still no luck.
It was some time ago that I installed a virtual server on HyperV but when I did so, I found I had to use different NIC cards. Something about the NIC configuration was not what the HyperV was looking for. Note, though, my situation is different as I have the SBS 2011 (not essentials) on a hard server and have the Virtual Server (with many virtuals) connect to the hard SBS 2011 server. I am not running the essentials server on a virtual machine.
Still, check the NIC cards. I believe I also had to disable «Large Send Offload (IPv4)» in order to get it to work. In my case, that was a hack but there may be others who will understand what that was about and how it may apply (or not) here. And it is also possible there is no relation between my problem in yours.
Ok, only one NIC was active on my host — activated both of them and network drivers are (still) up-to-date (intel w2012 certified) — reinstalled them though.
«Large Send Offload (IPv4)» — seems to be quite a hack, you are right — though I tried it with the virtual adapter. No luck.
I already had an 2012 Essentials working on that machine before (in a VM).. Same hardware, onboard raid 1. Disabled raid, formatted all the drives (data/partitions) and reinstalled the host. Everything’s working fine (working/new install of win2013server). I do need an Essentials version though.
Do you have a clue what could be wrong?
I’m still working off of HyperV on 2008 R2, but there, we have an option on the settings for the virtual to install from a DVD in lieu of the iso. Can you install from disk?
Hmm, also, the hack was for the machine adaptor, not the virtual adaptor.
There is a screen on the settings for «BIOS — Boot from CD». Is there anything in there that might lead you to take another approach?
1. Already tried an installation from dvd — didn’t make a difference..
2. My host is down for the moment — still — I only have the two networks and the virtual one. Where can I find the «machine adaptor»?
3. not sure what you mean. I tried booting from the ISO and I tried booting from the DVD. Also tried the «repair» cmd of the setup..
Is there any chance of getting more info durring setup?
Machine adaptor. saying this as an attempt to distinguish between a virtual machine with virtual adaptors and a physical machine with physical (inside the box where you can touch them, pull them out, put them back in) adaptors.
Maybe I am not fully understanding the problem.
Your network(s) are served up by physical machines that connect to the internet which are down (host is down for the moment). You are trying to run a virtual machine from within the network that hosts Small Business Essentials. When you install the Small Business Essentials as a virtual machine, I assume (hopefully this is correct) that you also have a HyperV box that you are installing the virtual copy to. That machine has settings that are configurable and those configurations are what my assumptions are based on. If you tweak those configurations, it will enable you to «set-up» Small Business Essentials on your network.
There are a couple other issues that I’m not fully up to speed on. When a Small Business Server starts to install, it installs just like a Windows Server. when the installation nears the end, a series of scripts run to turn on Windows features that make it the Small Business Essentials server. But for the start of the installation, it should install as though it were just another Windows Server being placed on a virtual.
What I think is different here is that the environment it installs to (your virtual host — the physical machine where you have enabled the two NICs — the adaptors if you will) will at some point, attempt to establish that server on the domain as an Enterprise level domain controller. It is more than likely that when the installation begins, it searches first to establish that it can create that environment. I think what you need to focus on it how you have that virtual host set up and how it interfaces with the rest of your network.
I’m out of my element here because I have the SBS on a hardened machine. I also have a virtual HyperV server running on that SBS network but I have not tried to put a virtual network inside the HyperV server although, I know it is far more common that the way I run my domain. But the basics should be the same. The hardware must be setup to be compatible with the type of installation you are trying to create.
thank you for your answer and the advices. Good to see someone who has a clue. Maybe I don’t understand but still I am sure you can help me:
Just to make sure, we understood each other:
1. There is ONE host server (windows 2012 datacenter / member of: workgroup).
2. this host (up and running, no connection problems) is running Hyper-V Role.
3. No tweaking in ANY settings.
4. We can not install Windows 2012 Essentials as VM on that host. The installation process stops quite at the beginning(see the pictures of my thread opening posts).
5. There is no domain controller on that network.
6. We can install any other Server OS on that host though.
The installation of Windows 2012 Essentials does not work in our environment.
I think that Windows Essentials also requires that it have full control of at least one NIC card. Physical control of the card and not just virtual control. Can anyone on the list verify this?
Meanwhile, I think Essentials comes with virtual so why not install the Essentials directly to the machine running the workgroup and add the virtuals to that machine?
I don’t quite understand your mail, saying that Essentials needs full control of at least one NIC card.
My Hyper-V is configured to use one NIC. What do you mean exactly?
Windows 2012 Essentials — as far as I know — does not allow Hyper-V role — therefore I can not use it as «Base» Operating System (my system is supposed to run some VM’s). Moreover Essentials Server requires to be a Domain Controller. That’s the reason why my 2012 Datacenter Host is just member of Workgroup.
As told before, I think the installation process exits quite at the beginning — I don’t even get to the point to enter the licence key/choose the installation destination. Still an installation of Win2012 DC/Standard does not have this problem. It is just with the 2012 Essentials.
Isn’t there any chance to obtain a more detailed error information during setup?
I may be reading this wrong:
I take the above to mean that one places a copy of Essentials on a box, and then adds a couple of virtual machines to run, (in addition to the LOB — Exchange, SQL, SharePoint, WSUS, and so on) In the older SBS, the OS required two NICs. primarily because it came with a packet reader at the gateway. But they did away with that with SBS 2008 and required a single NIC which would then reach out and control whatever NAT or routing system was available at the front end of the domain. From this observation, I always think of Essentials/SBS as an extension of the router firewall that allows the environment to operate as an Enterprise domain.
Based on that, I put a conservative machine with a single NIC against the firewall and installed SBS 2011 and then added a HyperV server as one of the machines inside the Enterprise domain. That second server machine houses my virtuals and it is not the SBS server.
But it sounds like the Essentials machine you are installing is on an outside network (workgroup) behind a NAT. So, in order for Essentials to do its «protection — domain configuration» thing, it wants to access a physical NIC (not virtual) that will allow it to connect to whatever NAT is available which normally provides DNS and DHCP. At that point, it will have physical control of the network.
If I understand your situation correctly, you want to have a internet connecting domain — inside of another domain — in this case a workgroup. If you do that, it seems to me that you’ll still need to provide the copy of Essentials with a physical NIC that connects to some kind of routing device. So perhaps if you had three physical NICS, one that is spare, the other two to provide the «happier» environment for the HyperV (happier with two than one was my initial experience with HyperV). Then the two from the virtual would provide the NAT-like domain, and the third spare NIC could connect to that NAT. But honestly, this is going beyond my experience. It sounds overly complicated to me.
Maybe keep the whole thing as simple as possible. For example, using your data-center, install Essentials directly to that machine and set it up with your NAT’d internet connection. Next, call Go-Daddy and get a remote.mymachine.com certificate, and once the domain is up, add the HyperV role from the Essentials machine. I think from my reading of the piece below, that you can do that. But the key here is «can also run» and I think that means it needs the NIC so that it blends seamlessly into the gateway of the domain it will seek to create.
«A single license of Standard allows it to run as a Hyper-V host and support two additional virtual operating system environments, one of which could be used to run Exchange Server and the other could be used to run another workload, such as a line-of-business application.
Essentials can also run as a virtual operating system environment on the same physical server to provide the core services for managing, monitoring, and helping to keep the entire environment protected and secure.»