Went through and imaged a new laptop with a 1703 image was able to make some changes and take an image from 1703 just fine. Upgraded to 1709 and got the same inode error, something must have change I’m going to try to sysprep the image to see if that helps but sysprep has been failing for me on 1709 as well.
J
Best posts made by Jarl2.0
-
RE: Error 'Could not open inode 'XXXXXX" through the library'posted in FOG Problems