@george1421 said in Win 10 image:

@jackiejack You can, but they are mostly wrong for your current setup.

No what I mean is for the SIM part. Can I follow it? Or this one:
https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/settings-for-automating-oobe
Or this one
http://searchenterprisedesktop.techtarget.com/tip/Create-a-hands-free-Windows-10-install-image-for-the-OOBE

See what particular scares me is section 25 v 2 b vi of https://forums.fogproject.org/assets/uploads/files/1469134024622-fog-universal-image-setup-win-7.pdf?v=78s341l4bha

she says

It seems odd to add this twice, but otherwise after sysprep it will still
prompt for an initial local account name. It may be possible to remove
the OOBE section, but I haven’t experimented with it.

Since I wanted a fully automated install of win 10 (with 2 admin accounts) should I follow this windows 7 guide? Or use the other links?

Or create the local admin accounts in audit mode first (not in SIM) then SkipUserOOBE but they say that is deprecated.

@develroo Check with your hardware (or tell us what it is and we can help you find it) to see if it contains a UUID field? When the PXE rom sends the first dhcp discover packet if it fills out the UUID field in the dhcp discover packet then you might be able to do something.

If that field is populated and unique per hardware model then you can dynamically switch between by either creating profiles in Windows 2012 dhcp or use isc-dhcp or dnsmasq both on your FOG server to make the dynamic changes.

From Lexmark’s site

Download then run the executable. Tell it to extract for later installation.

Find this:

C:\Lexmark\Lexmark_MS510_Series_ADU_Installation_Package\InstallationPackage\InstallationPackage\Drivers\Print\GDI\LMADUP40.inf

@sebastian-roth said in FOG server with dhcp client registration:

@Pikmin I don’t like guessing much so we should just take a look at the facts - the packets on the network that is. So get your client ready but don’t start it yet. Go to your FOG server and install tcpdump (sudo apt-get install tcpdump or sudo yum install tcpdump). Then run the following command and substitute x.x.x.x with the client’s IP address: tcpdump -w /tmp/boot_issue.pcap host x.x.x.x

Leave that command sitting there, boot up the client till it shows the error “Either DHCP failed or …”. Now stop tcpdump (Ctrl+c). Upload the generated file /tmp/boot_issue.pcap to your dropbox/google drive and post a link here or send me a private message if you don’t want to share this with the rest of the world.

I just went through the process of doing this when I discovered that after issuing spanning-tree portfast on all the interfaces it appears to be working now, so that’s the solution like in the other thread.
Thanks again for all your help george1421 and Sebastian Roth, I won’t forget the porfast setting ever again

@bc601 There’s only one way to create groups via Host Management - that’s by selecting the hosts you want in the new group, then at the bottom of the page put a group name into the ‘Create new group’ field. Then click Update.

Also, you can add hosts to an existing group via the dropdown at the bottom of host management. You can also create new groups via Group Management.

@erlon111 Sounds like fast boot is enabled… always disable fast boot when using cloning software!

@lebowski while its not dynamic data fog does install/alter files in

/var/www/html/fog
/etc/<apache_config>

You could (might want to) consolidate /images and move it into /opt/fog/images you can do that with a loop mount or when you install FOG point to that location instead of the default location of /images.

If you are going to use dnsmasq for your setup then /etc/dnsmasq.conf and /etc/dnsmasq.d

The other issue is installing/upgrading fog. If you use the github method you need a location to clone the repository.

@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.