@Avaryan said in Deploy Windows 10 and ClassicShell:

Has anyone here tried to deploy Windows 10 using ClassicShell to bring back the Windows 7 Start Menu? I was thinking about using it.

Hi, installing ClassicShell within an Image works, even why should it not work?
But like all the others say, i also think the win 10 startmenu is okay for me, i can deal with the tiny tile’s.

Your users may should decide if they can deal with it or not, you can also deploy it as snapin if a user wants it.

alt text

Regards X23

@Tom-Elliott said in Export and Import Images from different Fog servers:

1.3 rcs and trunk brought the capability to import and export elements individually where anything prior did not. So if you’re exporting or importing from one 1.3 to another you should be fine. In 1.2.0 and earlier only db export and host exports where available. 1.0.0 brought the db export capability which 0.32 and earlier did not have thus possibility.

Hopefully this helps define what you’re asking about.

Thanks Tom, exporting / importing the csv image list and using WinSCP to transfer the image files is working with 1.3 RC.

@mm-Ekimia I’m confused what you’re trying to replicate.

While I understand you may not want to wait 5 minutes, it seems a bit extraordinary to be working so hard to come up with a FOG like solution that doesn’t involve actually use FOG as it was intended. All this time to image 20 HDD’s would’ve taken about an hour worth of time including the 5 minute pxe boot time if you simply just grabbed a few extra laptops, registered and then tasked them.

Of note with this, it sounds like these Skylake laptops are attempting to boot VIA UEFI? UEFI booting is supported with FOG but as far as the implementation as handled from the NIC itself is outside of “FOG’s” realm of control. If it’s taking UEFI NIC booting 5 minutes, why not just tell the BIOS to boot nic in legacy mode? (Of which I’m pretty sure will NOT take 5 minutes to boot).

Now here’s where I’m confused about why you need to create, essentially, a FOG like solution on your side.

You don’t want to wait the 5 minutes of booting into the NIC. This is the ONLY reason, as far as I can see, as to why you don’t want to just use FOG as it was intended. Now we’ve been a week at this with back and forth information. When you initially made the posting asking for assistance, if you had installed FOG, had 5 of these laptops, inserted an HDD into each one, booted the system through PXE and telling that system to image. Run this 4 times, you’d have all 20 HDD’s complete within about an hour (give or take a little).

If you had 20 laptops all at once, you’d probably be done in about 30 minutes to an hour if you ran it through a multicast task.

I don’t know what the end goal is. I think FOG is perfectly capable of imaging these disks regardless of how long PXE takes to load up. You’d have been done by now if you had just waited the extra 5 minutes or so per system.

Thanks! I did notice the 10 second delay stuff.

That would be great, since here we hire new guys to work for us during the summer.

Having a test to run the new blood through would cut my downtime to train the newbies up by a good bit.

@JJ-Fullmer

:urls set msdart-url http://192.168.1.155/2-MSDART :MENU menu colour --rgb 0xff0000 0 || cpair --foreground 1 1 || cpair --foreground 0 3 || cpair --foreground 4 4 || item --gap -- ------------------------------------- item fog.local Boot from hard disk item msdart6x86 Microsoft DaRT for Windows Vista 32bit item msdart6x64 Microsoft DaRT for Windows Vista 64bit item msdart7x86 Microsoft DaRT for Windows 7 32bit item msdart7x64 Microsoft DaRT for Windows 7 64bit item msdart81x86 Microsoft DaRT for Windows 8.1 32bit item msdart81x64 Microsoft DaRT for Windows 8.1 64bit item fog.return Return to previous menu choose --default fog.local --timeout 5000000 target && goto ${target} :fog.local sanboot --no-describe --drive 0x80 || goto MENU :msdart6x86 initrd ${msdart-url}/MSDaRT60x86.iso chain memdisk iso raw :msdart6x64 initrd ${msdart-url}/MSDaRT60x64.iso chain memdisk iso raw :msdart7x86 initrd ${msdart-url}/MSDaRT70x86.iso chain memdisk iso raw :msdart7x64 initrd ${msdart-url}/MSDaRT70x64.iso chain memdisk iso raw :msdart81x86 initrd ${msdart-url}/MSDaRT8.1x86.iso chain memdisk iso raw :msdart81x64 initrd ${msdart-url}/MSDaRT8.1x64.iso chain memdisk iso raw :fog.return chain http://${fog-ip}/${fog-webroot}/service/ipxe/boot.php?mac=${net0/mac} || prompt goto MENU

@FallingWax yes. We have no generic accounts in fog. Everyone has their own account. This enables tracking in the history table however we have yet to need it.

With a user account per person you also know who last imaged, who images were made by, who snapins were made by, and so on. Those items are in the web interface.

Thanks, Wayne. I’ll test this out shortly and report back my findings 🙂

I think the only improvement would be seen under high usage, like simultaneous unicast deployments. And even then, you’d only see that increase if you have more than a 1Gbps network link to the server. You’d need 10Gbps to see the difference, otherwise you will cap at 1Gbps which is already filled completely by mechanical drives with 3 simultaneous unicast deployments.

For those that find themselves here:
https://forums.fogproject.org/topic/8762/change-image-id-number

@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