- Virtualization
- Windows Server 2016
- Installation
- Windows OS
- VMware
Error installing virtual machine with Server 2019
Error installing virtual machine with Server 2019
I am in the process of setting up a Lenovo ST550 server. I am using the Lenovo ROK version of Server 2019.
The installation up to getting HyperV functioning has gone well.
When I create a virtual machine, I get to the install operating system and all goes well until it gets to the features install portion, I get the following error:
"windows cannot copy files from D:\sources to C:$Windows.~LS\Sources. Make sure all files required for installation are available, and restart the installation. error code 0x80070001"
I have tried with the Windows trial version of Server 2019, and it works fine. My problem using it was that it would not accept the licence key that came with the Server 2019 from Lenovo.
The ISO file that I am using [from Lenovo] is installed on a USB drive that is formatted NTFS. The boot .wim is 531,550 kb. while the one from the trial version is 534,731 kb
I am in the process of setting up a Lenovo ST550 server. I am using the Lenovo ROK version of Server 2019.
The installation up to getting HyperV functioning has gone well.
When I create a virtual machine, I get to the install operating system and all goes well until it gets to the features install portion, I get the following error:
"windows cannot copy files from D:\sources to C:$Windows.~LS\Sources. Make sure all files required for installation are available, and restart the installation. error code 0x80070001"
I have tried with the Windows trial version of Server 2019, and it works fine. My problem using it was that it would not accept the licence key that came with the Server 2019 from Lenovo.
The ISO file that I am using [from Lenovo] is installed on a USB drive that is formatted NTFS. The boot .wim is 531,550 kb. while the one from the trial version is 534,731 kb
Drop the .ISO file from Lenovo onto the second partition into a folder called ISOs.
Point the VM's "optical" drive to that file to mount it. While in Settings move the Optical drive up to the top in Boot Order. Drop Network to the bottom.
Start the VM and hit the space bar to boot from the installer.
I have two very thorough EE articles on all things Hyper-V:
Some Hyper-V Hardware and Software Best Practices
Practical Hyper-V Performance Expectations
Some PowerShell Guides:
PowerShell Guide - Standalone Hyper-V Server
PowerShell Guide - New VM PowerShell
PowerShell Guide - New-VM Template: Single VHDX File
PowerShell Guide - New-VM Template: Dual VHDX Files
Here are some focused articles:
Set up PDCe NTP Domain Time in a Virtualized Setting
Slipstream Updates Using DISM and OSCDImg
Protecting a Backup Repository from Malware and Ransomware
Disaster Preparedness: KVM/IP + USB Flash = Recovery. Here’s a Guide
Point the VM's "optical" drive to that file to mount it. While in Settings move the Optical drive up to the top in Boot Order. Drop Network to the bottom.
Start the VM and hit the space bar to boot from the installer.
I have two very thorough EE articles on all things Hyper-V:
Some Hyper-V Hardware and Software Best Practices
Practical Hyper-V Performance Expectations
Some PowerShell Guides:
PowerShell Guide - Standalone Hyper-V Server
PowerShell Guide - New VM PowerShell
PowerShell Guide - New-VM Template: Single VHDX File
PowerShell Guide - New-VM Template: Dual VHDX Files
Here are some focused articles:
Set up PDCe NTP Domain Time in a Virtualized Setting
Slipstream Updates Using DISM and OSCDImg
Protecting a Backup Repository from Malware and Ransomware
Disaster Preparedness: KVM/IP + USB Flash = Recovery. Here’s a Guide
Wouldn't a reseller only kit require the system on which the OS is installed follows the reseller, Lenovo, in this case. When virtualizing, the OS install detection does not match vendor requirement.
Not whether ROK Type OS extend to virtualization.
Not whether ROK Type OS extend to virtualization.
The setup I have configured is that I have two 1 TB drives as Raid 1. I partitioned the drive at 320 GB and installed Server 2019. I then installed Hyper V. The remaining 700 or so GB is the space I use to install the virtual machines. That space is known as Drive E. I made a folder ISOs and put my ISO file into it. The ISO file is created from the DVD that came from Lenovo. I created the ISO using Express Burn. I have used this in the past with other installations, and it has worked fine.
During the machine creation, I pointed to the ISO file in the folder ISOs, and all seemed to go fine. The installation failed with the same message after installing features.
The part number of the Server 2019 from Lenovo is 7S050015WW and it is recommended for the server I have with one processor and 16 cores. This allows Virtual Machine Incensing for 2 VMs.
The server is part number LEN−7X10A0AUNA.
Is there a better way to create the ISO. As I mentioned this worked fine when in the past, but that was with Server 2016 Standard
During the machine creation, I pointed to the ISO file in the folder ISOs, and all seemed to go fine. The installation failed with the same message after installing features.
The part number of the Server 2019 from Lenovo is 7S050015WW and it is recommended for the server I have with one processor and 16 cores. This allows Virtual Machine Incensing for 2 VMs.
The server is part number LEN−7X10A0AUNA.
Is there a better way to create the ISO. As I mentioned this worked fine when in the past, but that was with Server 2016 Standard
Try using CDBurnerXP to create the image of the optical disk.
We used to use it a lot but have since built a library of installer ISOs.
The trial version should allow:
We used to use it a lot but have since built a library of installer ISOs.
The trial version should allow:
slmgr -ipk aaaa-1234-bbbb-5678-cccc
slmgr -ato
I think the issue here is that the installer is trying to confirm it us running on a Lenovo systems, which in this VM it is not accessing the HW bios.
Lenovo ROK needs to see that it is on Lenovo hardware, https://support.lenovo.com/il/en/solutions/ht000616 solves that for older OS but may apply to 2019 as well but your error is rather different.
In the 2016 installations that I did last April and August, I used the Lenovo 2016 ROK versions. I had not issues installing the HyperV and two instances of server 2016
In the 2016 ROK version they may have included inthe VM bios information what was needed that is not part of the 2019 version you have.
Potentially, the version upgraded versus original OEM telease soothe VM bios info was replaced with the upgrade.
Potentially, the version upgraded versus original OEM telease soothe VM bios info was replaced with the upgrade.
I am contacting Lenovo for guidance on this. As soon as I have information, I will post it here, and evaluate.
The CDBurner XP did not create an ISO because of the size of the boot.wim
The CDBurner XP did not create an ISO because of the size of the boot.wim
Folks,
It has been a while, but the issue is resolved. Both arnold and andyalder identified the problem. The solution took a bit more digging. Philip's comment on copying the ISO to the server worked well in the end.
First Lenovo provided a link to a file similar to the ones andyalder identified, but the latest one was for Server 2012 R2.
The solution was to download a trial version from Microsoft and then do the following:
Steps :
1. Download and install the Windows Server Evaluation ISO appropriate for the OS license that was purchased (note that Standard Edition and Datacenter Edition are contained in the same ISO).
2. Once the OS is installed, Login as administrator and open a Window command line
3. On the command line, Run one of the following commands (depending on the Windows Edition):
a. If Windows Server Standard:
DISM /online /Set-Edition:ServerStandar
b. If Windows Server Datacenter:
DISM /online /Set-Edition:ServerDatacen
Note that “XXXXX-XXXXX-XXXXX-XXXXX-X
4. Observe the successful updating of the OS installation (similar to shown below) and then Press Y to restart the server.
5. Once the server has rebooted, the following command can be used to verify proper OS activation:
From a Windows Command line, type:
slmgr.vbs /dlv
It worked and I am up and running
Again, thanks to all
It has been a while, but the issue is resolved. Both arnold and andyalder identified the problem. The solution took a bit more digging. Philip's comment on copying the ISO to the server worked well in the end.
First Lenovo provided a link to a file similar to the ones andyalder identified, but the latest one was for Server 2012 R2.
The solution was to download a trial version from Microsoft and then do the following:
Steps :
1. Download and install the Windows Server Evaluation ISO appropriate for the OS license that was purchased (note that Standard Edition and Datacenter Edition are contained in the same ISO).
2. Once the OS is installed, Login as administrator and open a Window command line
3. On the command line, Run one of the following commands (depending on the Windows Edition):
a. If Windows Server Standard:
DISM /online /Set-Edition:ServerStandar
b. If Windows Server Datacenter:
DISM /online /Set-Edition:ServerDatacen
Note that “XXXXX-XXXXX-XXXXX-XXXXX-X
4. Observe the successful updating of the OS installation (similar to shown below) and then Press Y to restart the server.
5. Once the server has rebooted, the following command can be used to verify proper OS activation:
From a Windows Command line, type:
slmgr.vbs /dlv
It worked and I am up and running
Again, thanks to all
Explore More ContentExplore courses, solutions, and other research materials related to this topic.
-
![]()
received a Solution
VCenter 6.7 New Install on Windows Server 2016 - Could not get certificate fingerprint from host -
![]()
wrote an Article
![]()
Windows 10 Problems and Solutions - 2019
-
![]()
created a Video
![]()
Exchange 2019 - Install Exchange 2019 Unattended
-
Explore Cloud Class® ![]()
Certification: MCSE Microsoft Certified Systems Engineer - Installation, Storage, and Compute with Windows Server 2016
