@twilems No idea. If the cause is the same, then probably.

@george1421 said in Apache Issue:

@avaryan Interesting, how many computers do you have checking into this FOG server?

I don’t know the exact number, but likely more than a thousand. There’s over 2,500 Windows computers in AD that would have the client on it.

Anyway, it’s been about 4 hours now and the web ui is still running well. I’d say that solved the issue.
Bonus: Got the FOG server updated.

Nvm. Fixed. Ran the following from the troubleshooting page.
https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_MySQL

DELETE FROM `hosts` WHERE `hostID` = '0'; DELETE FROM `hostMAC` WHERE hmID = '0' OR `hmHostID` = '0'; DELETE FROM `groupMembers` WHERE `gmID` = '0' OR `gmHostID` = '0' OR `gmGroupID` = '0'; DELETE FROM `snapinGroupAssoc` WHERE `sgaID` = '0' OR `sgaSnapinID` = '0' OR `sgaStorageGroupID` = '0'; DELETE from `snapinAssoc` WHERE `saID` = '0' OR `saHostID` = '0' OR `saSnapinID` = '0'; DELETE FROM `hosts` WHERE `hostID` NOT IN (SELECT `hmHostID` FROM `hostMAC` WHERE `hmPrimary` = '1'); DELETE FROM `hosts` WHERE `hostID` NOT IN (SELECT `hmHostID` FROM `hostMAC`); DELETE FROM `hostMAC` WHERE `hmhostID` NOT IN (SELECT `hostID` FROM `hosts`); DELETE FROM `snapinAssoc` WHERE `saHostID` NOT IN (SELECT `hostID` FROM `hosts`); DELETE FROM `groupMembers` WHERE `gmHostID` NOT IN (SELECT `hostID` FROM `hosts`); DELETE FROM `tasks` WHERE `taskStateID` IN ("1","2","3"); DELETE FROM `snapinTasks` WHERE `stState` in ("1","2","3");

Can you unset the filter after “checking” the boxes to see if they’re all being checked accidentally?

@Sebastian-Roth Multicasting is working, so I don’t think it was a port issue. I ended up making another session for those 6.

I had another session afterwards with 25 computers (different model) that worked.

Issue only observed on Dell OptiPlex 3020 so far.

@Avaryan No.

But I might suggesting upping in 128 increments (128, 256, 384, 512, etc…)

NOTE: I moved all the posts about testing the iPXE binaries: https://forums.fogproject.org/topic/10789/boot-file-testing-for-sr

@Tom-Elliott said in Delete Image - Migrate Hosts:

If you know you’re going to be deleting an image, why would changing the associated host’s image matter? What if you wanted to use different images on different “currently associated” hosts?

This, I would think, should be thought of before removing the image. Just thinking out loud. I’m not saying this isn’t a good feature request, just thinking about the logistics of such a thing.

Fair enough.

Idea. On the ‘Membership’ page for an image. You already have all the associated hosts there, as well as the checkboxes and the option to delete hosts from that image.

How about, under that, add the option to choose a different image? This way a user could quickly select new images for whichever hosts he/she wants.

@george1421 said in Upgrade from Trunk to 1.4.2 Failed:

@Avaryan Now that you know your password attempt to log into your database from the linux command line mysql -u root -p fog then provide your database password.

Our live FOG server is now on 1.4.2, revision 6072. Thanks! Now to figure out how that password got changed…

edit: You can mark this as solved.

@Tom-Elliott Ok, thanks. I think everything is working now.

Hi,

i boot all my iso’s that way:

initrd http://${fog-ip}/iso/acronis2017.iso chain memdisk iso raw || goto MENU :easeuspms initrd http://${fog-ip}/iso/easeuspms.iso chain memdisk iso raw || goto MENU :aomeipau initrd http://${fog-ip}/iso/aomeipau.iso chain memdisk iso raw || goto MENU :veeam initrd http://${fog-ip}/iso/veeam.iso chain memdisk iso raw || goto MENU :erd2005 initrd http://${fog-ip}/iso/erd2005.iso chain memdisk iso raw || goto MENU :dart7 initrd http://${fog-ip}/iso/dart7.iso chain memdisk iso raw || goto MENU :dart8 initrd http://${fog-ip}/iso/dart8.iso chain memdisk iso raw || goto MENU :dart81 initrd http://${fog-ip}/iso/dart81.iso chain memdisk iso raw || goto MENU :dart10 initrd http://${fog-ip}/iso/dart10.iso chain memdisk iso raw || goto MENU :dban initrd http://${fog-ip}/iso/dban_2.3.0.iso chain memdisk iso raw || goto MENU

Here is my complete menu: https://pastebin.com/zWBnT5c0

@Avaryan SVN or a package download most likely.

You can safely delete that directory and intialize git in /root where it will create the folders as needed. These are only the installation folders (as in everything needed to install FOG, not where everything is installed), they don’t contain any settings or the like.

@Avaryan We depend on the community to tell us what works. Please let us know how it goes, generally this stuff is posted here and later put into the documentation:
https://forums.fogproject.org/topic/2987/hardware-currently-working-with-fog-v1-x-x

@Avaryan Awesome tutorial, thank you for giving back.

unless you’re specifically testing the ipxe boot file, you can just set up a line in the default.ipxe file like this

:bootme # redirected to dev server for test environments ##test-computer iseq ${serial} F8HLK02 && chain http://test-server/fog/service/ipxe/boot.php##params || # normal fog server chain http://normal-fogserver/fog/service/ipxe/boot.php##params

@Avaryan That works.

Did not mean to insinuate that it was the fault of the FOG client, as I’ve seen it before even when not using FOG.

Do you know of a way to have it use the original Administrator user folder and not create a new one?

For reference:
When creating the image I’m hitting Ctrl + Shift + F3 to boot to Audit mode during the Windows install.

During the Specialize phase of sysprep with the Microsoft Windows Deployment component I’m creating a synchronous command to activate the admin account.
net user administrator /active:yes

During the OOBE phase I set the password as well as auto logon details.

This is really a minor issue, but there have been times where it would have been helpful to be able to deploy files straight to the admin desktop; which would be difficult if the directory name isn’t always the same.

Using Microsoft Deployment Toolkit right now to scan my extracted driver installers. Seems like it’s organizing it all for me.

@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