Posts made by adukes40

Can this be suppressed on snap-ins with the Reboot after install radio button selected?

I do not need the warning, and it will save me 2 minutes on imaging. If it can’t I can just have the PS script do the reboot instead.

@Wayne-Workman batting .1000 so far lol. maybe a trip to the casino is in order

@Wayne-Workman hmm… i haven’t been doing that. wonder if it is causing issues

@Wayne-Workman … you beat me to it. I was just reading that section about an hour ago, and was getting ready to link that, hopefully it was still a viable solution

OK, so after listening to the Q&A video for the second go around, looking for details I may missed I came across the part where Michael was talking about the Smart Notebook software used in all his schools on teacher computers. As we use this software as well I thought of a way he could use the snap-ins to do the single installs her does that the images don’t cover.

First off I assume he uses the Smart Install Manager to create an MST to automate the MSI install. (we do) However, this means that the MSI and MST needs to be in the same directory.

Looking at the Snap-in pane, I choose the MSI template. and it fills in most of the information needed. Here is the kicker though. When going to add the file, it seems snapins only allow for one file upload per snapin. However, the MSI and MST needs to be uploaded, and then part of the argument needs to call that MST so the MSI installs with the custom settings.

I know I am on the right track. (for me as well as hopefully, Michael)

So I am thinking there are three ways to accomplish this…

1. use the snapin if it is capable of such an install (multiple file upload)
2. snapin script to copy the files to the local machine, then run the MSI, and call the MST
3. have the files on a network share, then use a snapin to script run the MSI from the network share. and calling the MST

the command to run the installer is this:

msiexec /i “[Path]\SMARTEducationSoftware.msi” TRANSFORMS=“[MST file]”

Anyone have other ideas, or am I covering it in here? Would also like to know about the multiple file upload for snapins.

Thanks.

I created a new image called Win7x32

Then went to hosts and set it there:

then to basic tasks, capture:

then i click create and get the 500 error. it all looks correct to me unless I am missing something.

[Fri May 27 15:36:24.463223 2016] [:error] [pid 1125] [client 10.106.10.5:9861] PHP Fatal error: Call to a member function isValid() on null in /var/www/html/fog/lib/fog/host.class.php on line 525, referer: http://10.103.72.49/fog/management/index.php?node=host&sub=deploy&id=15&type=2

@abibbas I am fairly new to FOG, but i believe that is an older version and they are going to suggest upgrading to the latest trunk version.

https://wiki.fogproject.org/wiki/index.php?title=Upgrade_to_trunk

but to be safe you can wait for one of them to confirm that statement

@abibbas Are you able to screenshot the page?

@abibbas He needs the number in the cloud. Like here is 7911:

Located at the top of the web interface of the server. http://<SERVERIP>/fog/management

7911

@Wayne-Workman

Also, no reboot is performed unless you specify a reboot in the snapin’s settings, or in whatever script/program you might be running.

Yea, I got that part. And if appending a 1 then a 2 in front of the snapins, that might just accomplish what I want to do…basically on the first auto login, have a PS snapin run, do a reboot, then on second auto logon, run another PS snapin, and reboot. After that second reboot the machine will be done.

@Tom-Elliott and it looks like the node now has the 3 bat files. Thanks

@Tom-Elliott now looks like this:

drwxr-xr-x 3 fog root 4096 May 24 14:29 snapins

@Tom-Elliott conf looks like:

anonymous_enable=NO
local_enable=YES
write_enable=YES
local_umask=022
dirmessage_enable=YES
xferlog_enable=YES
connect_from_port_20=YES
xferlog_std_format=YES
listen=YES
pam_service_name=vsftpd
userlist_enable=NO
tcp_wrappers=YES
seccomp_sandbox=NO

Rights look like:

drwxr-xr-x 3 root root 4096 May 24 14:29 snapins

If you would rather have screenshots let me know and I will get those instead of copy/paste

Edit: Forgot to add, version 7895 now.

So I am just trying to understand how they work

I was trying to figure out is I add 3 snap-ins to a host with reboot options, if the host will run the first snapin, reboot, run the 2nd, reboot, run the 3rd. But when i notice you can move their order around, I am assuming all snapings run during a single logon, then reboot once the last one runs.

Am I correct in saying that? If not, what is the process for them. Thank you

Ok, updated again and I am still not having snapin replication working. Here is what the log shows:

mirror: Access failed: 553 Could not create file. (test.bat)
[05-26-16 9:04:30 pm] * Started sync for Snapin test3
lftp -e ‘set ftp:list-options -a;set net:max-retries 10;set net:timeout 30; set net:limit-total-rate 0:1024000; mirror -c -R -i test.bat --ignore-time -vvv --exclude ‘dev/’ --exclude ‘ssl/’ --exclude ‘CA/’ --delete-first /opt/fog/snapins /opt/fog/snapins; exit’ -u fog,[Protected] 10.106.2.149
[05-26-16 9:04:30 pm] | CMD:
[05-26-16 9:04:30 pm] * Starting Sync Actions
mirror: Access failed: 553 Could not create file. (caBOYSGYM.bat)
[05-26-16 9:04:29 pm] | Snapin name: test3
[05-26-16 9:04:29 pm] * Found Snapin to transfer to 2 node(s)
[05-26-16 9:04:29 pm] * Started sync for Snapin test2
lftp -e ‘set ftp:list-options -a;set net:max-retries 10;set net:timeout 30; set net:limit-total-rate 0:1024000; mirror -c -R -i caBOYSGYM.bat --ignore-time -vvv --exclude ‘dev/’ --exclude ‘ssl/’ --exclude ‘CA/’ --delete-first /opt/fog/snapins /opt/fog/snapins; exit’ -u fog,[Protected] 10.106.2.149
[05-26-16 9:04:29 pm] | CMD:
[05-26-16 9:04:29 pm] * Starting Sync Actions

@Sebastian-Roth And with that said, I will say although I am very new to FOG and Linux, I will try to help if I can. Wayne has been great and I had a good talk with George as well. The community here is great and full of knowledge.

So far FOG is great and I am trying to learn/understand as much as i can about it.

That’s what I figured. thanks for clarification.

I thought of a scenario I think i know the answer to, but just want to make sure.

On the Main server i create a new image and assigned it to a group thats not set to replicate (for testing purposes). I am physically at the storage node site, and create an image. When i go to push it up, will it attempt to upload that to the local node, and not replicate, or will it upload across the WAN to the Main, then not replicate?

I assume it is the latter.

(just trying to get my testing/creation VMs setup the way they need to be.)