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.

Here’s instructions on that. https://wiki.fogproject.org/wiki/index.php?title=Upgrade_to_trunk

@iyoung Yes. Make a new thread, put it in tutorials.

There are no scheduled release dates. FOG is entirely worked in free time of the developers, so it would be impossible to schedule any target dates, realistically.

That being said 1.3 is on RC11 right now, so you can perhaps draw some conclusions from that.

Soon TM

@Wayne-Workman absolutely weird.
I used the same technique with snap in pack on different folder and it worked without issue in the past. Only this time around with system32 folder.

I even tried with xcopy!

Anyway, thanks for your help, appreciate it and I will check further to see if AV is a culprit here.

Cheers

@george1421 I prefer /etc/sysconfig/network-scripts/ifcfg-xxx now after I learned more. Before that yes I clung to the cli graphical tool for dear life.

@wcheung said in Host Machine and images:

What i find interesting is that Lenovo X1 Carbons (Gen 1 - 4) do not have ethernet ports, it used a proprietary connector OR a USB3.0 ethernet adapter that have a MAC id on them.

Fog can work with these devices fine. They have Wifi MAC addresses that would be used for management through FOG after imaging is over. If you have many of these devices there will be a little more effort for re-imaging if you’re environment is not mega-automated. If your environment is not mega-automated then the workload is not higher.