Hi Tom,

Is it possible to change color for snapin that are not ebabled (when uncheck “snapin enabled”) ? Maybe grey, or change display / order to put them at the end of snapin page ?

Thanks,
Matthieu

@Tom-Elliott It’s ok now, I suppose it was a database bug, topic can be closed.
Just a question, there must be a shutdown / reboot after snapin installation? I can choose one or the other but not none… (if I uncheck both reboot is selected automaticaly)

@Tom-Elliott Ok, you’re right I think it’s related to database because since 1.5-RC, fog sql backup is empty (0kb) in /home/fogdbbackup. But export databse in web management is ok.
How can I run db cleanup/troubleshooting steps ?
Thanks

Same message for me, and my snapin is not modified…
So any solution to update snapin for the moment.

Server

• FOG Version: 1.5.0-RC3
• OS: Debian 8

Client

• Service Version: 0.11.12
• OS: Win10

Description

Hi,

I try to modify snapin on 1.5.0-RC3, and when I click “update” I have a blank page with message “{“msg”:“Snapin updated!”,“title”:“Snapin Update Success”}” but snapin is not modified…

Thanks
Matthieu

@Quazz Yes, but this time I was lucky it was my smallest image with few software ! But it will be problematic for other images with dizains of software… Can you close the topic ? Thanks

Ok so I restart my image from scratch with usb installation key containing creators update and no problem to capture image with sysprep, resizing works fine and I can deploy on smaller SSD
So it was certainly a bug in my previous image, thanks for your help

@Tom-Elliott I don’t know, it’s the 500 MB parttion created by windows at installation There’s the same on my own computer.
But I think I understood what happened : it’s directly related to my previous problem with this image : https://forums.fogproject.org/topic/10313/error-capture-windows-10-creator-update-sysprep-could-not-open-inode-xxxxxx-through-the-library
I have 3 image Win10, for 2 of them after upgrade to 1703 no problem, but for the one which give me some trouble, I already have problem to capture image due to “inode” errror message precisely when resizing sda2…
But no solution fot the moment

No way, I create new image but once again sda2 is not resized… It’s a big problem for me, 3 pc of direction failed with deployment and people can’t work

@Quazz Ok I’ll take a look to this topic.
But you’re right about resizing, usually I saw “resizing /sda2” (or something like that…) during few second just before partclone capture image, but on this image I don’t see this line, it’s too quick…

@Quazz I’m sure image type is single disk resizable, I’ve just check in fog.

Here is a capture on PC with SSD 128GB (in french, sorry ;))

I will try to look during capture if I saw text about resizing

@Quazz No I didn’t see that, it appears on partclone screen during capture ?

Same problem on 3 other computers with SSD 120GB instead of 128GB, I need to fix this issue in one hour :(n

@Quazz I capture this image once again, on another config but still with SSD 128GB, and unable to deploy it on the 2 laptops, same error…

@Quazz Hi,
I test multiple modification, but always same result :

• I delete “:2” (empty file)
• I replaced by “2” (without ":)
• I replaced by “1”
• I replaced by “:1”

Server

• FOG Version: 1.4.4
• OS: Debian 8

Client

• Service Version: 0.11.12
• OS: Win10

Description

Hi,

I have an image made on PC with SSD 128GB, I need to depoy this image on 2 laptop with SSD 60GB, and partclone give me error “Target partition size is smaller than source”

d1.fixed_size_partitions
:2

d1.minimum.partitions :
label: dos
label-id: 0x86308630
device: /dev/sda
unit: sectors
/dev/sda1 : start= 2048, size= 63840, type=7, bootable
/dev/sda2 : start= 1094144, size= 248975360, type=7

d1.partitions :
label: dos
label-id: 0x86308630
device: /dev/sda
unit: sectors
/dev/sda1 : start= 2048, size= 1092096, type=7, bootable
/dev/sda2 : start= 1094144, size= 248975360, type=7

Thanks for your help !
Matthieu

Same problem here with Firefox and Edge
So I suppose Cert is really expired !

@x23piracy It works great ! Thanks a lot

@x23piracy Thanks, I’ll try this next morning

Server

• FOG Version: 1.4.3
• OS: Debian 8.8

Client

• Service Version: 0.11.12
• OS: Win 10 1703

Description

Hi,

I found 2 other topics with same problem (April 2017) but no one seems resolved…
https://forums.fogproject.org/topic/9881/could-not-open-inode-xxxxxx-through-the-library-windows-10-sysprep-capture
https://forums.fogproject.org/topic/9918/could-not-open-inode-xxxxxx-through-the-library

So I try to update my Win 10 images to Creators update (1703) (3 differents images) and after update I removed uneeded Metro Apps and I ran sysprep (with unattend.xml) before capturing image. No problem on 2 images, but for the other one, and I don’t knw why, each time I try to capture image after sysprep I had the error :

If no sysprep before capture it’s ok, but once sysprep is done it’s KO. And if I take a look to disk management, I saw this (system partition is resized to 31Mb instead of 533) :

Any idea ?
Any help would be appreciate, thanks !