Topics created by ITCC

I got this fixed.
i think they fixed it without me but i had an open ticket and was talking iPXE and swapping files and all sorts.

Anyway new firmware 1.21 now working.

you’re right, you can’t use the RAID. this is already off.
I can image the machines, The point is that is doesn’t flow. it needs another reboot so just a little harder to leave them to it. (got quite a few to do 🙂 )

the 2nd is indeed windows but i was wondering if the FOG agent reboot isn’t a full reboot of some kind (what’s the command used by agent) shutdown -r ??
it’s last task would have been joining the domain.

It feels like a FastBoot thing the more i think about it, just didn’t get time to test. If FOG inventory is “fastbooting” it might be skipping where it then boot back into the PXE to continue the deployment

And windows might apply the auto login details from the unattend.xml but not get a full reboot, more like waking from a hibernate (caused by they way FOG agent reboots the system after joining the domain)

@ITCC Switch your DHCP config to point to ipxe.pxe instead of undionly.kpxe and the issue should go away.

@ITCC Let us know what exactly you are trying to achieve. The AD settings are meant to be used for domain join and from what you write I get the impression that you want to misuse “Name Change/AD Join Forced reboot” to forcefully log off people from their machines. Maybe this is just a misunderstanding on my side but you keep calling it “force logout” and therefore I get the impression.

There are other ways of doing this. The web is full of it:

https://answers.microsoft.com/en-us/windows/forum/windows_7-security/how-to-force-logoff-from-command-line/8e7507e0-12c8-4ac7-8d5e-a1917e4af997 (using shutdown /l /f command) https://social.technet.microsoft.com/Forums/en-US/1c525aa7-5b09-45fb-ad47-56c41f1df2bc/force-user-logoff?forum=win10itprogeneral (using GPOs)

If you can’t make it work this way you need to explain to us what exactly you want to do. We won’t change this otherwise!

Just as a side node: I have not really looked into what needs to be changed but I can imagine this being a change in the fog-client code as well. There are many other things that needs fixing before we’d get to change that in fog-client.

You are more than welcome to dig through the code yourself and implement the change. I am not saying it cannot be done.

As we have had so many requests about this topic I have tried to sort this out and properly fix it. Turned out to be quite hard but I hope I got it now without causing any other harm.

@Tom-Elliott Can you please take a look at this commit and let me know if something jumps at you that could cause us trouble. I mean I have tested things a bit but as I had to change code right in the FOGController class I am unsure about side effects this might cause. What do you think?

Same issue for me

If anyone else needs this:

I cheated but it worked for my needs
My personal notes =

Imagelog cleanup
Downloaded MySQL Workbench to complete tasks

See records to be deleted.
SELECT * FROM fog.imagingLog where ilImageName NOT LIKE ‘%<latest image name>%’;

Delete Records (Rerun command until effected rows =0) - due to safety feature in Workbench
DELETE FROM fog.imagingLog where ilImageName NOT LIKE ‘<latest image name>’ LIMIT 1000;

@itcc Two ways.

Manually: https://wiki.fogproject.org/wiki/index.php?title=Change_FOG_Server_IP_Address With a tool: https://github.com/FOGProject/fog-community-scripts/tree/master/updateIP

@itcc correct

@ITCC Please update to RC’s if you can?

I don’t know what’s causing it to create “false” entries in the database, though I cannot get it to replicate the problem in the current code I’m working with.

@ITCC this would definitely be a feature request. Power Management takes the approach of “If the user is away, they get logged off, and the machine is shut off”. You may be better off to use either GPO or snapins to achieve this. For example, schedule a CRON snapin that just checks if any users are logged on, otherwise it shutsdown.

@ITCC I’d make sure on both fronts.

Yes, tick the box in the fog settings, but the “checkbox” is typically checked on hosts even if they’re not “enforcing”. This because it get’s its information from the FOG Settings -> Active Directory Defaults -> Similar named checkbox setting.

Just because this is checked on the host does not mean it’s actually set. It’s not because I like making people confused, but rather how the checkbox is checked. I can’t know which method you’re intending for while being able to auto-set the box when you do want to enable domain join and what not, so this is set based on the value in the default location specified above.

@Joe-Schmitt Done. Also put links from the FOG Client article and an older article to it as well.
https://wiki.fogproject.org/wiki/index.php?title=Power_Management

Check in time cannot be changed. The checking time out can be but this is not what you’re looking for.

It is highly doubtful checkins are causing issues as they are not spamming the server very often (one check every 5 seconds per machine.) If it were a server spamming issue it would most likely come from progress reporting as that checks in every 3 seconds. However the slowdown on images is the main issue as quazz and Wayne pointed out.

While I suppose removing intermediary requests could help lessen the work stop/start, this would be primarily micro-optimizing as all the checkin does is update state, if needed, and decide if it is safe to start doing the tasking.

any progression on this my FOG fellows?

@ITCC You need to run installfog.sh again after updating .fogsettings

@Lee-Rowlett I’ll be expanding on that article soon to cover image sharing. The video was meant to be an introduction.

Confirmed and should be fixed in latest. Sorry.

@george1421 said in Uploading image breaks source machine, 7, Win10:

Just had an idea, what if the developers could put a command line switch in to install it but set the service to disabled.

Great idea, asking @joe-schmitt to read this.

@ITCC So it’s okay to solve this as it wasn’t a bug?

Note, that a quick wipe doesn’t wipe the data off a drive. This means the BOOT bits are still present, even though the partition layout is not available to be used. This is why you’re seeing GRUB, but not able to do anything.