@csuther3 that’s strange. I tested on win10 enterprise and the start menu and search remains fine.

Something that might help you: I noticed the files copied totaled about 40 ish MB.

@george1421 said in FOS Capabilities:

The same would also be true if you wanted to mount a windows share, cifs would need to be enabled in busybox.

CIFS is enabled already - I’ve been working on imaging with Samba instead of NFS for the password protection it offers. NFS is the last big hole in fog.

You’re halfway there. There are two other spots to set the password in. Refer to this article, there’s a bit in there about credentials.

https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_FTP

Check this area here: Web interface -> Storage Management -> [node name] -> Max Clients

This setting is how you limit how many can image at one time. On my network I find that I get a shorter overall imaging time with many hosts if I limit this to two. Your case may be different though.

If multicast works in your environment I would suggest using that instead for the same image being pushed to many hosts.

@george1421 said in Master -Master Replication:

Right now FOG doesn’t have a real good way to limit what techs can do at each location. For example we would only want IT techs at site A to be able to image machines at site A and not site B. As well as the other way around. If you had FOG setup to automatically PXE boot into FOG, techs at site A could accidentally reimage a machine at site B.

Sounds like a great opportunity to solve a problem, to me. I could write a PHP service that would just undo any tasking that a tech does at a wrong site. In fact - I can write a stand-beside fog thingy that will let you assign locations to fog users. It can be a non-required extra field in the users table, and won’t affect FOG functionality.

At work, we don’t have problems with bandwidth between sites. It’s 1Gbps throughout 23 buildings separated by miles each. But we do have a potential problem with is techs doing things they shouldn’t be doing.

@andyroo54 said:

The idea is to hide all of that from users, so they just see a pretty picture… does that make sense?

I swap around from hide-menu to full menu depending on if I’m imaging a lab or not.

Do all of your systems display a pretty picture when the system is network booting? Mine don’t. What about the POST process? I don’t see why it matters so much. We’re not Apple.

@Bad-Day Yes lol. Run fixparts prior to uploading.

Alternatively, zero-out the drive with FOG’s normal-wipe task, or use DBAN, then build your image.

The problem happens because Windows Setup sucks at going from GPT to MBR. It doesn’t do it cleanly.

I would always recommend automatic DB backups.

@John-L-Clark said in [No Replication to second Fog server:

Finally got FTP to work after finding in the config.class.php the correct password for the user fog.

You shouldn’t need to ever manually modify that file in FOG. The installer builds it for you based on what’s inside of /opt/fog/.fogsettings. Please set the password that you want to use for FTP inside of that .fogsettings file and then re-run the installer. Then try to manually connect via FTP to the remote node using those new credentials and see if it works.

@Bad-Day Try to restore the image to another computer.

@x23piracy said in 0.11.4 RC4 AD Question:

@RLane Hi, are you using OEM? If so you can’t use SetupComplete.cmd but you can use firstlogoncommands in unattend.xml to call SetupComplete.cmd to get done automated i also create a local user and allow 1 autologon via unattend.xml.

Read the whole thread: https://forums.fogproject.org/topic/8097/fog-not-auto-joining-to-the-domain-requires-additional-restart-to-join-windows-10

Regards X23

Added this as a note in the wiki.
https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#FOG_Client_with_Sysprep

https://forums.fogproject.org/topic/3200/ipxe-boot-error
https://forums.fogproject.org/topic/4097/ipxe-could-not-boot-no-such-file-or-directory
https://forums.fogproject.org/topic/5588/general-guidance-fog-with-non-mod-dhcp/19

Also, that video is very old (published in 2012). You might want to consider using a tutorial from our Wiki, and you might even want to try out FOG Trunk since 1.2.0 is getting pretty dated and this is a fresh and new FOG server build.

As far as the problem goes, it’s probably still a DHCP issue. FOG doesn’t need a DNS entry to work, but absolutely requires that Option 066 and 067 get to the target hosts somehow.

Also - if your just looking to test FOG out, you would greatly simplify your troubles by using a physical machine. I don’t know why people keep trying to use Virtual Box. I’ve got nothing against it, but we see a lot of issues every week with Virtual Box and none of those issues would exist with a physical box. It doesn’t need to be anything fancy, an old core 2 duo or Pentium 4 would do just fine as a test box.

@MadsMagnus The “Product Key” field is for the OS. You can type your key in there, and the new fog client will activate that host with that key.

if you have a MAK key, you can use groups to assign it to many computers at once.

We have a fleet of laptops that each have their own key, took a hot minute to key all those into each host but it works perfectly. That host will always use that key, until it’s changed.

@george1421 said in how to setup FOG server on Isolated netowork:

@Wayne-Workman just created an updated document (that I can’t seem to find for setting up dnsmasq)

It’s still in the works. I think I’m overthinking the article. To me it’s easy to setup because I’ve done it several times. https://wiki.fogproject.org/wiki/index.php?title=ProxyDHCP_/dnsmasq-_DRAFT

The new snapinpacks article will get completed before this.

@Pascal-Gazaille I’ve updated our working hardware list with this model and the kernel argument.
https://wiki.fogproject.org/wiki/index.php?title=WorkingDevices#Devices

But for completeness of the records, what boot file are you using?

@Quazz arrowhead’s scripts do work. I can confirm this. The registry keys I mentioned about Win7 earlier in this thread are totally ignored by Win10 - I’ve already tried lol.

Microsoft takes one step forward, two steps back.

Their programmers are hard-coding values instead of using the registry that is ALREADY THERE! lol I hope someone from Microsoft reads this.

@george1421 said in how to setup FOG server on Isolated netowork:

@Wayne-Workman said in how to setup FOG server on Isolated netowork:

https://wiki.fogproject.org/wiki/index.php?title=ProxyDHCP_/dnsmasq-_DRAFT

Where is that post you crated that documented the fedora 23 install. You had a dnsmasq section there that was pretty darn good, short and clear. You could almost dump that section into the draft link from above.

It’s in the Fedora 21 Article. I suppose I can literally copy these optional steps to the CentOS and Fedora 23&24 articles, changing yum to dnf where needed.

https://wiki.fogproject.org/wiki/index.php?title=Fedora_21_Server#dnsmasq_.28if_using_ProxyDHCP.29_setup

@K.Hays Well that’s a different error and maybe a different problem - but it could be due to many things.

Firstly, I’d verify that the file exists inside of /tftpboot. If it’s there, I’d then check it’s permissions. If permissions are good, I’d then open the file and make sure the IP address at the bottom is good.

However, a photo of the error would help a lot, it would contain a lot of information that would help us help you.

@Quazz Arrowhead’s scripts work for Win10. The methods I posted way back work for Win7.

I’m going to put together an epic snapinpacks article as soon as I have a working dev environment setup to do it in. I’m in the process of building it now.