Posts made by adukes40

@Tom-Elliott Its doing it again.

@Tom-Elliott i tried that earlier, only way it works is off run wakeonlan (mac) from the terminal

@Tom-Elliott far as I know, it shouldn’t be blocked. Is there a way I can tell on the Linux box?

@Wayne-Workman When I type that in, nothing happens.

http://10.103.72.49/fog/management/index.php?sub=wakeEmUp&mac=b8:ac:6f:3d:6e:a4 = nothing

SSH into 72.49, run WOL to the remote host = nothing

SSH into the remote node, run WOL = turns on.

@george1421 thats good to hear, I was thinking about using LTSB instead of Education, because of its simplicity. Don’t have to worry about the apps, or store, and all that mess.

do you use it, George?

Anyone played with the LTSB version of Win10 in their environment?

Server

• FOG Version: RC-11
• OS: Unbuntu 14.04

Client

• Service Version: 11.5
• OS: Win7

Description

WOL doesn’t seem to be working at remote sites (haven’t been able to test at master using GUI)

I installed the wakeonlan program on the remote server, and was able to WOL by typing in the MAC address. But it would not if I set a WOL task from the GUI

I also installed the WOL program on the master. I remoted in and shutdown a machine, then sent the WOL from the master server, and it seemed to work. However, like I said I have not been able to test sending it from the server yet. (might get to later tonight).

So I seems like my network is passing WOL packets, and clients seem to be waking, but not from the tasks created in the GUI.

@Seydoo Have you tried updating to RC-11?

There other I am seeing is sometimes the 1- snapins remove themselves from association after an image. I am looking at two hosts, where that just happened. 1- removes itself, but 2- and 3- always stay.

Goes hand-in-hand with

https://forums.fogproject.org/topic/8638/full-registration-causing-rogue-snapins-to-apply/

Ok, just tested this myself.

Soo… went to a machine. Registered it with snapin that wasn’t currently in the “rogue” list. When I check the snapins, the new snapin shows, along with the like 8 others, plus the 2 every machine gets. Which mean the next time a machines Regs thru PXE, it will be getting that snapin plus the other stuck in the loop.

@Tom-Elliott Just had a Tech register a machine today. Same outcome all the previous snapins, plus a new one from the room they were in this morning.

Havent had time ti test anything else yet.

@Tom-Elliott I will test some registrations today and see what happens. Getting bombed with early morning emails at the moment.

@Tom-Elliott

Database changed
mysql> DELETE FROM snapinAssoc WHERE saHostID NOT IN (SELECT hostID FROM hosts);
Query OK, 0 rows affected (0.02 sec)

mysql> DELETE FROM snapinAssoc WHERE saSnapinID NOT IN (SELECT sID FROM snapins);
Query OK, 1 row affected (0.01 sec)

mysql>

@Tom-Elliott You mean the DELETE mysql statement?

And the (SELECT hostID FROM hosts) sections is part I just run in the command correct? Im not actually getting hostID from the hosts table?

@Tom-Elliott Here is the Process that we are doing that seems to be causing it to happen (haven’t done the cli command yet)

1. Image random machine with snapin A, B, and C
2. image completes
3. Go to register new machine with snapin D, B and C
   (B and C are on every host)
4. New machine now has snapins A, B, C, and D

Now here is what I do not know, and can try to test today

I am unsure if the snapins being added are also machines that have been registered thru PXE, and those are the ones get stuck in this oddity. If I add snapins manually, thru the GUI, it seems to work fine.

@Tom-Elliott Registered new machine today. The stuck associations still happen, and a couple more have made their way into the list now on top of the ones from last time.

ON RC-11

Server

• FOG Version: Pull version 57
• OS: Ubuntu 14.04

Client

• Service Version: 11.2
• OS: Win 7

Description

Registering hosts through the PXE menu is causing the same snapins to apply even though they are not the ones being told to associate. Here is what I mean

I go to Full Reg a machine. Image ID, location ID, Hostname, stick and work. When it comes time for snapins, we apply 3 for every machine. Those 3 get applied, but then about another 4-5 snapins get applied as well in the background. When we go to deploy this image it will not complete due to the confusion I suppose. Now if w go into the GUI, and remove the extra ones, and update, it sticks and go through fine. But for some reason if Reg thru PXE, more than the set snapins are getting assigned. Here is a SS of one I Registered today:

This only ones that should be showing are 1-TS-140, 2-InstallScript1, and 2-InstallScript3 The other appear as associated as well.

As a side note, those extra ones, were machines imaged when my earlier snapin issue were occurring within the past week.

Something similar, I have all my nodes set to only do a max number of clients. I have my node set to 5, but I have 12 pickup and go today. They never went into the queue system after reaching the 5 allottment.