I will be reviewing the link to your tutorial that @george1421 posted below, thank you for the input! We do not want users on the network using the windows store and seeing as Microsoft ‘locked down’ Windows 10 Pro in a push to get people on Enterprise, eliminating it from the base image became the decision. Your calculator implementation is a good idea. I also did not realize that the Windows 10 ‘shutdown’ isn’t the ideal state (thanks @george1421!) for capturing the sysprepped image.
Posts made by foggerj
-
RE: "Could not open inode XXXXXX through the library..." Windows 10 Sysprep Capture
-
RE: "Could not open inode XXXXXX through the library..." Windows 10 Sysprep Capture
Update: I was able to get the image to capture after changing the image setting from Single disk - Resizeable to Raw Image.
Now I suppose my question is - what effect will this have on my image and its deployability? -
"Could not open inode XXXXXX through the library..." Windows 10 Sysprep Capture
Server
- FOG Version: 1.3.5
- OS: Ubuntu 16.04 LTS
Client
- Service Version:
- OS: Windows 10 Professional
Description
I have been testing creating a Windows 10 Professional image to get a clean universal image that doesn’t include the provisioned Windows store and apps. I have an unattend.xml file that executes a setupcomplete.cmd, which executes a slmgr call and sets the FOG client to automatic start then reboots the machine. Using powershell I remove all provisioned windows apps (Get-AppxProvisionedPackage -Online | Remove-AppxProvisionedPackage -Online) and installed windows apps (Get-AppxPackage -AllUsers | Remove-AppxPackage), and sysprep the machine (virtualized as i intend to use the image for different hardware). I set the host to capture the image and it comes up with the following error regarding opening an inode (MAC/IPs removed):
There is no error from sysprep and the machine (without capture) boots and finishes install as it is supposed to. I haven’t been able to find much on this error, and was wondering what I can do to capture this image?NOTE: This only occurs if I perform the aforementioned removal of windows apps.
-
RE: FOG Newbie: 1st IMG Optiplex & Win 10
Problems resolved. Capturing and deploying images works successfully. I believe I had a bad image and mismatched settings (UEFI/BIOS). Thank you for your input Wayne/George, it will definitely help me moving forward.
-
RE: FOG Newbie: 1st IMG Optiplex & Win 10
@george1421 Thank you George, very good info and I appreciate the links!
I captured the image in legacy mode. I would like to get this off the ground using UEFI mode if I can. As I mentioned in my reply to Wayne, I wasn’t aware of needing the client for sysprep, so I will try that as well. I’m still learning (aren’t we all?).
Judging by the information you both have provided me, it sounds like I have a botched image due to a combination of legacy/uefi confusion as well as sysprep/fog client issues. I have a bit of work ahead of me in reinstalling/reimaging/testing.
This has been very helpful, I will repost when I am able (likely Monday).
-
RE: FOG Newbie: 1st IMG Optiplex & Win 10
@Wayne-Workman I wasn’t aware of the FOG client until after I captured the image. The reboot is happening when attempting to load the OS, whether I allow it to load the FOG pxe menu or load straight from disk.
I will attempt to capture an image without sysprep, I haven’t attempted that yet. I’ll repost here when I do.
-
FOG Newbie: 1st IMG Optiplex & Win 10
This will be my first post as a member. I’m new to both these forums and the FOG product. I like what capabilities FOG offers, but I’m having an issue with my very first image.
FOG: 1.3.5 R6067 installed on Ubuntu Server 16.04 LTS
Workstation is a Dell OptiPlex 3040 that was installed with Windows 10 Professional prior to beginning this process.I configured my FOG with the recommended settings as per the User/Admin guides. I sysprepped the Windows 10 Pro image, rebooted it, and captured it with FOG with no issues. I then attempted to deploy the same image back to the machine to verify everything worked as it should. What happened next was a boot loop. I attempted various troubleshooting that included changing the bootfile from undionly.kpxe to undionly.kkpxe to ipxe.efi. I have tried all combinations of Host BIOS/EFI Exit Type and redeployed the image several times.
I am about to leave for the day and my first goal in the morning will be to attempt to perform a clean install and capture another image. I did, however, want to reach out to you good folks hoping you may have some insight in to what may be happening or what settings I maybe should be investigating.
Thanks!