@sebastian-roth
So I made a Windows 10 image and ran a command to remove Edge and made IE11 Default Browser. I also installed Office and removed Windows 10 Apps. I tried the shutdown -s -t 0
command before capturing the image. I got the same result. I tried then making an image without running Edge removal and Windows 10 apps and still same result, and I then tried making a whole new image with compression at 4 and it gets stuck a 4%.
Posts made by imagingmaster21
-
RE: Capturing Windows 10 Error Virtual Machine Environment
-
RE: Capturing Windows 10 Error Virtual Machine Environment
@sebastian-roth
@george1421
Here is the screenshot of the contents of the d1.partitions file:
-
RE: Capturing Windows 10 Error Virtual Machine Environment
@george1421
I tried doing that still with no luck, here is my settings for the image. It seems to be capturing fine. -
RE: Capturing Windows 10 Error Virtual Machine Environment
@george1421
I am going to try that command since I am not using sysprep. Do you think removing Edge would also cause an issue, or any of the other Windows 10 Apps? -
RE: Capturing Windows 10 Error Virtual Machine Environment
So when you make a Windows 10 Machine, lets say you install Office 2016 on it. When I did that and captured it, it captured fine. But when I deployed it to one machine when it starts up after imaging it says Windows Recovery Options. Is there something else you have to do before you capture an image with program installations. Also this image does have Edge removed.
-
RE: Capturing Windows 10 Error Virtual Machine Environment
Just tested it and everything seems fine. Now will there be a difference when I do this on actual machine that have UEFI BIOS?
-
RE: Capturing Windows 10 Error Virtual Machine Environment
@george1421
I think I got it working. Seems to be capturing now. I used another Win 10 machine I made. -
RE: Capturing Windows 10 Error Virtual Machine Environment
@george1421
Here is the results of running the lsblk command. -
RE: Capturing Windows 10 Error Virtual Machine Environment
@george1421 see my extra post, didn’t hit reply to you by mistake.
-
RE: Capturing Windows 10 Error Virtual Machine Environment
Thank you for you’re response. I booted into PXE and it did not give me a option to type that command in just gave me the same results. And I did cancel the tasks like you said. Should I try PXE without any tasks? And then run that command.
For the environment I am using VirtualBox. I attached screenshots below of all the settings for the Windows 10 VM that is getting this error.
-
Capturing Windows 10 Error Virtual Machine Environment
Server
- FOG Version: 1.4.4
- OS: Ubuntu Server 16.04
Client
- Service Version: Windows 10
- OS: Windows 10
Description
I am new to using FOG, and I am using a Virtual Enviornment to test it out before putting it on an actual network. I have my FOG server setup and is working fine as far as I know. I have a Windows 10 VM that I made, with nothing special on it. I tried doing a task on it of capturing the image, after doing the regist ration on it through PXE boot. When I went to PXE boot after creating the capture task and referencing it to a Win 10 Image in FOG I get the following error as attached. Is there something I might be skipping in my Win 10 machine or my FOG server?
Server
- FOG Version:
- OS:
Client
- Service Version:
- OS:
Description
Server
- FOG Version: 1.4.4
- OS: Ubuntu Server 16.04
Client
- Service Version: Windows 10
- OS: Windows 10
Description
I am new to using FOG, and I am using a Virtual Enviornment to test it out before putting it on an actual network. I have my FOG server setup and is working fine as far as I know. I have a Windows 10 VM that I made, with nothing special on it. I tried doing a task on it of capturing the image, after doing the registration on it through PXE boot. When I went to PXE boot after creating the capture task and referencing it to a Win 10 Image in FOG I get the following error as attached. Is there something I might be skipping in my Win 10 machine or my FOG server?