@redbob I’ve updated the wiki to include details for creating a user in FOG in 1.4.0 and 1.5.0. Future readers can find that information here: https://wiki.fogproject.org/wiki/index.php?title=Password_Central#Web_Interface

First I have to get the legal bit out of the way. Microsoft OEM EULA licenses do not allow you to clone an OEM image and deploy it to another computer. You must have a MS Volume license key for this. You only need one volume license key per version of windows OS you need to deploy. So the cost is not bad.

I do think we have something lost in what you say.

Do you what to take a single partition and deploy it to another computer or another partition on the same computer?

@sourceminer Although I can’t say for sure what’s going on in your case I am fairly sure that FOG does not restore the wrong image.

How do you see it’s the “wrong” image? Wrong name in the output on screen or wrong content on the PC after deploy? Maybe you re-captured the image and it’s been overwritten with the “wrong” content?

I’ve not done any more work on this. The best solution is still to have permanent tunnels from site to site via a routing appliance like a Cisco router or checkpoint router or PFSense router or some other router solution.

@sabotage Put a small server at each site. The hardware can be your choosing. You could use small and low-end servers if you have the money, or you could use old desktops for it. Up to you. Then setup your main FOG Server at HQ, and install all the site’s boxes as fog storage nodes. The storage-node installation process allows you to attach it to a main fog server. Then setup the location plugin and configure all your locations. We have documentation for this in our wiki. But…

For now - you really should just setup a test FOG Server at your HQ and just try things out. Generally, newbies of FOG have lots of questions about basic stuff.

No Problem. Thank you

@mron said in Boot Windows or Linux with FOG?:

I’ll set three PCs aside.

Also be aware you can do your testing with 2 systems (1 fog server, and 1 system to load virtual box on). Then with virtual box you can create as many target systems as needed. Some people develop their golden image in a virtual environment to take advantage of snapshots (moment in time backups) while they perfect their golden image. Its easy to rewind your configuration to a snapshot point then reinstalling from DVD. (for example if you forget to make a modification before you sysprep the image).

@loosus456 said in By 2020, Intel is ending support for legacy/BIOS/non-UEFI:

At least in older Dell firmware (unsure about newer ones), turning on UEFI would remove the PXE-on-wake option

Ah OK. thats a firmware option inside the firmware. Interesting…

I know at least in bios mode Dells had an option called PXE boot on next boot cycle. If I remember correctly with Dell’s CCTK you can tell the system boot pxe on the next system boot. That is a one shot function. You could deploy this instruction using CCTK and a FOG snapin.

@smcadm you have to create the snapin by yourself in the webif. Check the snapin section.

@sebastian-roth Great! Thanks.

@sebastian-roth thx, at the bottom it’s nearly what I look for.
But how can I set a default parameter as a Path for example in the snapin screen, but overwrite it if I set a parameter…?

regarding the example on the link:

{
“taskTypeID”: <IDOFTASKTYPE>,
“taskName”: “robocopysync”,
“destination”: “<path>”,
“source”: “<path>”
}
Can I use them like this?

0_1510746465332_Bildschirmfoto zu 2017-11-15 12-46-58.png

And regarding the API: Whats the difference between a SnapinTask and a SnapinJob?

TIA

@bmick10 said in Updating Fog to newer version and Pending Mac Addresses:

just wondering if it is always something that breaks locally or if things can be affected by developers or fog employees.

We aren’t employees, FOG is supported entirely by a community of volunteers that help out at their own discretion, of their own accord. There’s no money involved besides donations - which are never expected but always appreciated. You can help out too, just by answering questions you can answer or writing tutorials or documentation, videos, etc. You’ll find that you will learn a ton just by reading the stuff that’s posted here.

As for if things are affected or not by the devs - if you re-run the fog installer, it would get the latest kernel and init in order to support the latest hardware - but no web-core changes or DB changes are made unless you actually go get the latest version of FOG. As for your OS, when you re-run the installer it makes sure it has the latest version of the packages it needs, everything else is left unchanged. Ubuntu is notorious for resetting customized configuration files during updates, which in turn cause problems - this is of course compounded because Ubuntu by default automatically updates and most people aren’t knowledgeable enough about Linux to rip out that functionality.

@george1421 I’ll do some more testing Monday and get back with the results.

Thank you for your answers.

@FredG Sure we could go with a list of lables but what bugs me is that lables are just kind of like a sticky note. Very much volatile and therefor I don’t think it’s worth the effort to add this to FOG. I would like to come up with a more reliable / robust way of actually detecting if a partition is system or recovery or …

Thanks George and Wayne - I’ll submit my request for wiki account now.

@dpotesta50 (snarky: I did amend my original post to reduce the snark level).

The unattend.xml and setupcomplete.cmd files are something created by your previous admin to tweak your windows 10 build post image deployment with company/site specific settings. You may want to review these files to understand why he felt the need to do this. I can tell you its common practice to use the unattend.xml and setupcomplete.cmd files. So the short answer is yes you may need them.

If you don’t have them, and your previous admin used them, I can tell you how to collect them (assuming they are in your master image today). Take a computer and deploy your standard image to it, when FOG is done, power off the computer. Take the hard drive out and add it as a second drive temporarily in another computer. This will give you access to the media to collect these files.

“default” is not used.

And I say again, FOG doesn’t do this natively. How you configure your machines is how you configure them. FOG Just captures a replica of the hard drive. It will deploy that replica to many other systems.

@george1421 said in Passing host variable to iPXE menu:

@sebastian-roth I don’t think this is possible here. I think we have the chicken and egg situation here. dhcp knows about the computer’s name because the client tells it during dhcp negotiations. In this case, the client is a new born and doesn’t know enough to tell the dhcp server its name. To get it to work correctly the OP may have to setup dhcp reservations to inform the dhcp server what the client associated with mac address xxxx is.

Exactly this. We should used to furnish boxes with the hostname through DHCP (using option 012) but it requires manually configuring reservations.