@Wayne-Workman If you look at the scripts you see that it makes perfectly sense what Tom is saying. In capture we usually create a text file called d1.original.swapuuids where we store the UUID of the original SWAP partition. In deploy we generate a new SWAP partition on the target system using the saved UUID. So there shouldn’t be a need to modify /etc/fstab at all!

I haven’t tested this in a while as I am too busy with other things. Just saying that this is how I think FOG is behaving. Same as Tom does. Anyone keen to try this and see if we have an issue in the scripts?

https://github.com/FOGProject/fogproject/blob/dev-branch/src/buildroot/package/fog/scripts/usr/share/fog/lib/partition-funcs.sh#L309
https://github.com/FOGProject/fogproject/blob/dev-branch/src/buildroot/package/fog/scripts/usr/share/fog/lib/partition-funcs.sh#L377

@Wayne-Workman said in Windows FOG storage node and multicasting mess:

If it’s configured correctly, it should be immediate. Did you enable the graph for the storage node? Did you assign the storage node to the correct storage group and enable it? When installing the storage node, did you input the correct fogstorage password?

God, I’m striking out left and right. I changed the settings in /opt/fog/.fogsettings, but didn’t re-install, expecting the changes to be instant. What a dope I am…

Thanks for the info on changing the IP of the node. That’s not too bad and you’re right, having the latest of everything every time would be good.

@Joe-Schmitt Just to add a little more detail here.

As I posted before. I have MDT build my reference image using the lite touch process. Once the process is kicked off I don’t touch the reference image until its time for sysprep. I have the fog client installed via an application in MDT. This is the command I use to install the FOG Client.

@Echo Off start /wait msiexec.exe /i FOGService.msi /quiet USETRAY="0" WEBADDRESS="192.168.1.53" net stop "FogService" sc config "FogService" start= disabled

I know this thread is two years old.

Still I love both projects, FOG and GLPI! And I would love to see this work. So thank you guys for all the good work!
As FOG already does HW inventory, would be nice to use it in GLPI, so I don’t have to install ocsinventory and another client.

Hey Alexandre,

still around? Does your FOGTRansfert GLPI plugin work with FOG 1.3?
And I’ve seen that GLPI has newer version too, I couldn’t install the plugin.
Could you update the plugin please?

I’m not a coder, but if I can help, let me know.

Cheers
Eduardo

@Kiweegie said in Snapin Questions:

While Jbobs description of snapins as files which get executed remotely is spot on, the real benefit of using snapins is in conjunction with silent switches so the installation happens without your users seeing anything going on. This avoids them having to call the Helpdesk because “some weird screen just popped up on my 'puter!”

I wanted to say that if you’re using the new FOG Client, there will never be a display from a snapin - ever. At least not directly. This is because all snapins with the new FOG Client run as the SYSTEM user, which is prohibited from displaying anything to the user at all in Windows. This is by design of Windows itself. If your snapin isn’t silent, or properly configured to run silently, your snapin will infinitely hang. Hanging is a sure sign of a snapin waiting for input that will never come.

We need a wiki article on Printer Management.

@george1421 said in Microsoft Surface Pro 4 with Surface Docking Station - Unable to get boot file:

@Wayne-Workman Do you think we have enough discrete bits of information to make a wiki page on the surface pro 4? As these devices become more popular I can see the volume of quesitons increase. Having one location (you look here->) would add real value from a support perspective.

I still want to do this, will start work on it maybe tomorrow - it may take the entire morning to do, this will be a large article.

@Wayne-Workman said in Microsoft Surface Pro 4 with Surface Docking Station - Unable to get boot file:

@kwetiaw I’m linking threads that deal with the Surface Pro 4 here for you to read through. All of the below threads are marked as solved. As George already said, I’d like to compile all of this information into a single #wiki article, but I don’t have a SP4 to test with. I will be out for several days after tonight.

https://forums.fogproject.org/topic/6515/surface-pro-4-won-t-get-to-registration-menu

https://forums.fogproject.org/topic/8181/surface-pro-4-image-capture

https://forums.fogproject.org/topic/7660/surface-pro-4-on-7977

https://forums.fogproject.org/topic/7353/surface-pro-4-unable-to-image

https://forums.fogproject.org/topic/8323/several-problems-with-surface-pro-4

@moses said in What does the "Host changes every cycle" flag do?:

PS: The Active Directory page on the wiki makes no mention of this setting.

It is now.
https://wiki.fogproject.org/wiki/index.php?title=Active_Directory_-_FOG_Setting

@tokejepsen Cool. Thanks for posting the video, I’m sure it’ll help people for a long time in the future.

@Wayne-Workman Nice! I haven’t had to do a batch of those 4’s in a minute, but more are coming soon. My boss was perplexed at how seemingly complicated it was to get the Pro 4 to netboot/image (USB Hub was the only way to do it). Thanks for the good news!

Thanks 🙂

Windows updates event can be triggered with:

wuauclt.exe /detectnow

Not many folks use that feature, since imaging is far faster than trying to repair an infected os.

Keep watching this thread tho. Someone might speak up.

For the record, Dell normally has Linux based firmware update packages. You could update firmware with fog using postdownloadscripts.

@george1421worked perfectly. thanks!

UEFI is just a hell lot more complex than legacy BIOS is. This does not make it slower per se but on top of that a lot of the UEFI implementations are badly flawed. Feel free to take a tour through the iPXE code and see all the things that need to be done to properly boot UEFI machines…

So simple. Thanks!

@Joe-Schmitt, that was what I imagined the case to be, thank you for the clarification.

-Anthony

Note 2:

The only reason why I had a swap partition I believe was because initially I added a new drive to my VM and initially moved all my images over to that drive… I ended up transferring my images back to the original drive and removing the second drive all together. Despite removing the drive the Swap remained.