Web management takes forever to load, basically can’t do anything. When it loads many minutes later, its formatting is all whacked. Also will sometimes just give “cannot be reached”
Also when I go to image a machine from my site (remote site) it goes through the pxe boot process, before it goes to let me see the FOG pxe menu is just gives gibberish at the bottom.
This also stops machine trying to load the OS because it cannot get past this screen.
@george1421 Wish I had the time right now to run the tests, but with schools starting n a couple weeks, I might get to it by October. I can test your rewritten section though. I can pop that in and test a machine in a few seconds. It is just strange that 2 models, and only 2 models are being a pain. 745, 755, 760, and 780’s go thru without a hitch. BLEH!
Can say, we used to use the key combos to get into pxe, but it seems FOG has it so in order for someone do to anything “destructive” it requires a login. So even if kids or employees try to image the machine, or delete the host, they will be prompted. So we do not even use a starting key anymore. just set it to image and turn it on, walk away
@Tom-Elliott O ok. Well I will wake up from my dream then lol.
@Wayne-Workman If this is a thing in 2.0, thats awesome. I was just throwing it out there. I wasn’t sure if I could do that now, or not. And if I couldn’t I was just inquiring about it being a part of 2.0.
@Wayne-Workman Well I have the client on the master image, and being all the devices will be getting imaged this summer anyway, we were just doing it all in one motion.
Have a confirmation line at the end of the registration script. Doing a couple thousand registrations this summer, and it appears if you typo, you have to reboot and start over again. Could the confirmation be set as the last line, with a Y or N. Y would do the registration and move on, where the N would either clear it out and go back to the top and start over, or maybe retain the information typed in, then ENTER down to the line with the typo and make a quick change.
As always if there is a way to do this currently I will give it a shot, if not thanks for listening 
Is it possible to be able to have a PXE menu entry to access the management gui? That way changes could be while at the machine instead of relying on a mobile device, or using another machine to make changes?
If this is currently doable, how could I go about it? If not is this a possibility for 2.0?
Basically this would allow us to change OS types, or snapins if a machine moves to a different location. Would allow to do on the fly.
@Quazz I do not have anything further. Here is what I do have. this first script works for all devices with mechanical SATA, and SSD’s, but not M.2 SATA:
#!/bin/sh
osdiskpart=“/dev/sda2”;
driverver=“Win7”
mkdir /ntfs 2>/dev/null
mount.ntfs-3g “${osdiskpart}” /ntfs 2>/tmp/mntfail
mkdir /ntfs/Drivers 2>/dev/null
if [ -d “/ntfs/Windows/SysWOW64” ]
then
setarch=“x64”;
else
setarch=“x86”;
fi
machine=dmidecode -s system-product-name;
machine=“${machine%”${machine##[![:space:]]}“}”;
echo "Detected [${machine}] [${driverver}] with this arch [${setarch}] " >> /ntfs/Drivers/machine.txt
rm -f /tmp/mydrivers;
ln -s “/images/Drivers/${driverver}/${machine}/${setarch}/” /tmp/mydrivers;
if [ -d “/tmp/mydrivers” ]
then
cp -r /tmp/mydrivers/ /ntfs/Drivers;
fi
regfile=“/ntfs/Windows/System32/config/SOFTWARE”
key=“\Microsoft\Windows\CurrentVersion\DevicePath”
devpath=“%SystemRoot%\inf;C:\Drivers”;
reged -e “$regfile” &>/dev/null <<EOFREG
ed $key
$devpath
q
y
EOFREG
rm -f /tmp/mydrivers;
umount /ntfs
The following scirpt works with the M.2 SATA and mechanical SATAs, and the SSD’s. HOWEVER, it will not work with the OptiPlex 790’s nor 990’s They are the only two models giving the “space” problem.
#!/bin/sh
if [[ $hd == /dev/sda* ]]
then
osdiskpart=“/dev/sda2”;
else [[ $hd == /dev/nvme* ]]
osdiskpart="/dev/nvme0n1p2";
fi
driverver=“Win7”
mkdir /ntfs 2>/dev/null
mount.ntfs-3g “${osdiskpart}” /ntfs 2>/tmp/mntfail
mkdir /ntfs/Drivers 2>/dev/null
if [ -d “/ntfs/Windows/SysWOW64” ]
then
setarch=“x64”;
else
setarch=“x86”;
fi
machine=dmidecode -s system-product-name;
machine=“${machine%”${machine##[![:space:]]}“}”;
echo "Detected [${machine}] [${driverver}] with this arch [${setarch}] " >> /ntfs/Drivers/machine.txt
rm -f /tmp/mydrivers;
ln -s “/images/Drivers/${driverver}/${machine}/${setarch}/” /tmp/mydrivers;
if [ -d “/tmp/mydrivers” ]
then
cp -r /tmp/mydrivers/ /ntfs/Drivers;
fi
regfile=“/ntfs/Windows/System32/config/SOFTWARE”
key=“\Microsoft\Windows\CurrentVersion\DevicePath”
devpath=“%SystemRoot%\inf;C:\Drivers”;
reged -e “$regfile” &>/dev/null <<EOFREG
ed $key
$devpath
q
y
EOFREG
rm -f /tmp/mydrivers;
umount /ntfs
for now I reverted back to the first script for imaging as we only have 1 lab of the M.2 SATA machines. I have not had the time to look at this yet. If anyone has an idea on what to change for the scirpts I would be all ears, but for now I do not have a resolution. (due to time)
Running Rc2…I added some hosts. Created a group to give them all the same settings. Added them to group…set the location, image, and snapins. Told group to deploy. Image went thru fine…but only 1 actually installed all snapins. Other 4 just sat there doing nothing. I then booted to pxe menu and picked deploy image…went thru perfectly. When I sent another group it did the same thing.
So I then set the group, updated settings, then went to the machines and told them to deploy image from pxe menu…worked. but if deploying from group…something breaks.
@Quazz We only have 3 images, and currently we are deploying the 32bit one. All the images are the same. plus this image in particular, is the one that was captured, as it is on the subnet where the master node resides.
Tomorrow i will be back at the building, so I will be able to dive into it more.
@george1421 Oh I’m perfectly fine with the design. I just remember I puttyd in before on a debug machine…but could not remember how I did it.
@george1421 AH, so i have to set the password from the machine physically. That will have to wait i guess until Monday, don’t think I will be in at all this weekend.
@george1421 I got in earlier. I did a normal debug, and not a debug deploy… I am trying to putty into the machine now. I have done it before, during debug, but cant remember the credentials I used.
@george1421 when I type fog…it says…An error has been detected…fatal error unknown request type null
@george1421 When I get a few minutes I will give this a try.
Ok, so here is in interesting one. We use the golden image, postdownloadscripts method of driver deployment. everything works great until I encounter a OptiPlex 790, (and i think 990). When it comes time to copy the drivers over, it appears to mount /dev/sda2 which is correct, then errors out saying there is no space left on the device. Now i did encounter this with M.2 Sata drives trying to copy to the 1st partition and not the second, however in this case, it IS mounting the 2nd partition, which is correct.
I will also add, we altered the script to be able to distinguish between the normal SDA and the NVMe version. But it works for all other devices so far, except these two models.
I could post the script if needed. Anyone seen this before?
As a side note, I can image 790s at other locations, that do not have the special script section to tell the drives apart, but i need it in there as we have an entire lab that uses the M.2 Satas.
I know I should be using Multicast, but for whatever reason, it only works at the master node location, and I have not had the time to sit and mess with it. that probably wont come now, until October. I was just hoping to band-aid the throttle for this summer, then go look more into MC when I get the free time.
I believe I am correct in saying I can throttle the imaging speeds using the bitrate option in the storage node settings, but not sure what numbers I should put there.
My issue is I have two schools that share a connection, so I only used 1 FOG server. It works great for 1 or 2 machines. However if multiple machines are imaged the pipe seems to get flooded. If i recall correctly, there is 1GB between the schools. How can I use that option to say, only have imaging use 800M of that pipe.