@Sebastian-Roth I never thought of that. That is highly likely. the log-on asks for name and then a server rout. Thank you!
Posts made by agray
-
RE: Issues with copying software configs?
-
RE: Issues with copying software configs?
@Sebastian-Roth One of them. There are 13 people that will be using that PC. All accounts where set up, including IBM Notes, on the PC before Cloning.
-
RE: Issues with copying software configs?
@Sebastian-Roth It was more out of curiosity, to my understanding, we my be abandoning the entire project anyway. But a possible answer would ease my curiosity because like you said, fog clones the entire disk.
FOG version: 1.5.5
Software: IBM Notes (Basic), not sure the version number. -
Issues with copying software configs?
Is there a known issue with fog not coping all the configs for certain software?
I just created an image of our dispatchers PCs and when i went to deploy, a software they use required me to fill out all the info again. The info being, where to point to for the profiles. -
RE: FOG Post install script for Win Driver injection
@george1421 Thank you! all is appreciated! I’m sorry for the bombardment of questions.
-
RE: Image creation fail
@george1421 is it normal for this install for me not to re-enter all the information like the first install?
-
RE: Image creation fail
@george1421 Internet access and, if swapping networks, the updateip scrip are required right?
-
RE: FOG Post install script for Win Driver injection
@george1421 From what I’m getting from all the threads, the unattend.xml file is required with win10 now. Is that no longer the case?
If it is, is that required to be edited in the master image before cloned?
Later in your 2017 ed thread you gave an update on the 1703+ Win, saying “add the following lines to your setupcomplete.cmd batch file.” That batch file already created, if not, where can i find code for it, or it that it in the code box? -
RE: Image creation fail
I did, then reinstalled fog because i was told it would fix it.
Since the reinstall, I havn’t touched the fog user account. -
RE: FOG Post install script for Win Driver injection
@george1421 fog.ad-the 3rd post
I’m not getting anything of this either. Looking at the thread here, and here (https://forums.fogproject.org/topic/11126/using-fog-postinstall-scripts-for-windows-driver-injection-2017-ed) the scripts are different. What is right? What do you name everything/make the file type? -
Image creation fail
When attempting to make my first image, i was presented with the following error: https://ibb.co/rfRm0QJ.
All help is appriciated. -
RE: FOG Post install script for Win Driver injection
@george1421 Why do you have lines 7-12 REMed out? I know very very very little bash so this is like looking at french for me.
-
RE: Failed to create Snapin Error
@Sebastian-Roth Actually, before I go any further, is it required for fog to see the internet after install?
-
RE: Failed to create Snapin Error
@Sebastian-Roth So i will need to reinstall according to the network with internet, swap it to the one without and run the script?
-
RE: Failed to create Snapin Error
@Sebastian-Roth No problem, I tend to ramble a lot and it can get lost is all the junk.
@Sebastian-Roth said in Failed to create Snapin Error:
So you are switching between two different networks (just for the installation part). So did you use one of our helper scripts when you initially switched from your internet subnet to the isolated network?
Yes I am. I was unaware there where helper scripts.
The forum I was using as a tutorial said to put in the ip for the final network, that might be what messed everything up. Is there a better tutorial out there? If not, could you walk me through the process of getting this set up properly?
The server is on subnet where it can see the internet, allowing us to update/install.@Sebastian-Roth said in Failed to create Snapin Error:
Maybe it would have been all easier if I’d just tried to help you manually fix the permissions.
Would have been easier but this way whatever I messed up previously can be fixed. I appreciate all your help!
-
RE: Utilizing Postscripts (Rename, JoinDomain, Drivers, Snapins)
@Lee-Rowlett Would this still work with Win 10? If so, is this how you would do it?
if [ $osid == “5” -o $osid == “6” -o $osid == “7” -o $osid == "8" ]; #8 being for Win 10
Is there anything else I would need to change?
-
RE: Failed to create Snapin Error
@Sebastian-Roth To answer your question(s), with the the previous given information, I won’t be able to access http://192.168.1.105//fog//maintenance/backup_db.php without swapping to the other router.
Here is the apache2_error.log[Wed Jan 09 09:33:37.473360 2019] [mpm_event:notice] [pid 23383:tid 140627289242560] AH00489: Apache/2.4.37 (Ubuntu) configured -- resuming normal operations [Wed Jan 09 09:33:37.473447 2019] [core:notice] [pid 23383:tid 140627289242560] AH00094: Command line: '/usr/sbin/apache2' [Wed Jan 09 09:34:09.246470 2019] [mpm_event:notice] [pid 23383:tid 140627289242560] AH00491: caught SIGTERM, shutting down [Wed Jan 09 09:34:09.320087 2019] [mpm_prefork:notice] [pid 29677] AH00163: Apache/2.4.37 (Ubuntu) configured -- resuming normal operations [Wed Jan 09 09:34:09.320188 2019] [core:notice] [pid 29677] AH00094: Command line: '/usr/sbin/apache2' [Wed Jan 09 09:34:09.593440 2019] [mpm_prefork:notice] [pid 29677] AH00169: caught SIGTERM, shutting down [Wed Jan 09 09:34:09.665904 2019] [mpm_prefork:notice] [pid 29738] AH00163: Apache/2.4.37 (Ubuntu) configured -- resuming normal operations [Wed Jan 09 09:34:09.665935 2019] [core:notice] [pid 29738] AH00094: Command line: '/usr/sbin/apache2' [Wed Jan 09 09:35:26.974997 2019] [mpm_prefork:notice] [pid 29738] AH00169: caught SIGTERM, shutting down [Wed Jan 09 09:35:43.214380 2019] [mpm_prefork:notice] [pid 5964] AH00163: Apache/2.4.37 (Ubuntu) OpenSSL/1.1.1a configured -- resuming normal operations [Wed Jan 09 09:35:43.214422 2019] [core:notice] [pid 5964] AH00094: Command line: '/usr/sbin/apache2'
and the php7.1-fpm.log
[07-Jan-2019 10:32:37] NOTICE: fpm is running, pid 28129 [07-Jan-2019 10:32:37] NOTICE: ready to handle connections [07-Jan-2019 10:32:37] NOTICE: systemd monitor interval set to 10000ms [07-Jan-2019 10:32:42] NOTICE: Terminating ... [07-Jan-2019 10:32:42] NOTICE: exiting, bye-bye! [07-Jan-2019 10:32:42] NOTICE: fpm is running, pid 28847 [07-Jan-2019 10:32:42] NOTICE: ready to handle connections [07-Jan-2019 10:32:42] NOTICE: systemd monitor interval set to 10000ms [07-Jan-2019 10:32:45] NOTICE: Terminating ... [07-Jan-2019 10:32:45] NOTICE: exiting, bye-bye! [07-Jan-2019 10:32:45] NOTICE: fpm is running, pid 28943 [07-Jan-2019 10:32:45] NOTICE: ready to handle connections [07-Jan-2019 10:32:45] NOTICE: systemd monitor interval set to 10000ms [07-Jan-2019 10:32:47] NOTICE: Terminating ... [07-Jan-2019 10:32:47] NOTICE: exiting, bye-bye! [07-Jan-2019 10:32:47] NOTICE: fpm is running, pid 29267 [07-Jan-2019 10:32:47] NOTICE: ready to handle connections [07-Jan-2019 10:32:47] NOTICE: systemd monitor interval set to 10000ms [07-Jan-2019 10:32:52] NOTICE: Terminating ... [07-Jan-2019 10:32:52] NOTICE: exiting, bye-bye! [07-Jan-2019 10:32:52] NOTICE: fpm is running, pid 29633 [07-Jan-2019 10:32:52] NOTICE: ready to handle connections [07-Jan-2019 10:32:52] NOTICE: systemd monitor interval set to 10000ms [07-Jan-2019 10:32:58] NOTICE: Terminating ... [07-Jan-2019 10:32:58] NOTICE: exiting, bye-bye! [07-Jan-2019 10:32:58] NOTICE: fpm is running, pid 30572 [07-Jan-2019 10:32:58] NOTICE: ready to handle connections [07-Jan-2019 10:32:58] NOTICE: systemd monitor interval set to 10000ms [07-Jan-2019 10:34:13] NOTICE: Terminating ... [07-Jan-2019 10:34:13] NOTICE: exiting, bye-bye! [07-Jan-2019 10:37:22] NOTICE: fpm is running, pid 5686 [07-Jan-2019 10:37:22] NOTICE: ready to handle connections [07-Jan-2019 10:37:22] NOTICE: systemd monitor interval set to 10000ms [07-Jan-2019 10:43:19] NOTICE: Terminating ... [07-Jan-2019 10:43:19] NOTICE: exiting, bye-bye! [07-Jan-2019 10:49:24] NOTICE: fpm is running, pid 22683 [07-Jan-2019 10:49:24] NOTICE: ready to handle connections [07-Jan-2019 10:49:24] NOTICE: systemd monitor interval set to 10000ms [07-Jan-2019 10:49:30] NOTICE: Terminating ... [07-Jan-2019 10:49:30] NOTICE: exiting, bye-bye! [07-Jan-2019 10:49:30] NOTICE: fpm is running, pid 23947 [07-Jan-2019 10:49:30] NOTICE: ready to handle connections [07-Jan-2019 10:49:30] NOTICE: systemd monitor interval set to 10000ms [07-Jan-2019 10:49:33] NOTICE: Terminating ... [07-Jan-2019 10:49:33] NOTICE: exiting, bye-bye! [07-Jan-2019 10:49:33] NOTICE: fpm is running, pid 24043 [07-Jan-2019 10:49:33] NOTICE: ready to handle connections [07-Jan-2019 10:49:33] NOTICE: systemd monitor interval set to 10000ms [07-Jan-2019 10:49:34] NOTICE: Terminating ... [07-Jan-2019 10:49:34] NOTICE: exiting, bye-bye! [07-Jan-2019 10:49:34] NOTICE: fpm is running, pid 24340 [07-Jan-2019 10:49:34] NOTICE: ready to handle connections [07-Jan-2019 10:49:34] NOTICE: systemd monitor interval set to 10000ms [07-Jan-2019 10:49:41] NOTICE: Terminating ... [07-Jan-2019 10:49:41] NOTICE: exiting, bye-bye! [07-Jan-2019 10:49:41] NOTICE: fpm is running, pid 24679 [07-Jan-2019 10:49:41] NOTICE: ready to handle connections [07-Jan-2019 10:49:41] NOTICE: systemd monitor interval set to 10000ms [07-Jan-2019 10:49:47] NOTICE: Terminating ... [07-Jan-2019 10:49:47] NOTICE: exiting, bye-bye! [07-Jan-2019 10:49:47] NOTICE: fpm is running, pid 25540 [07-Jan-2019 10:49:47] NOTICE: ready to handle connections [07-Jan-2019 10:49:47] NOTICE: systemd monitor interval set to 10000ms [07-Jan-2019 10:50:19] NOTICE: Terminating ... [07-Jan-2019 10:50:19] NOTICE: exiting, bye-bye! [07-Jan-2019 10:51:59] NOTICE: fpm is running, pid 29626 [07-Jan-2019 10:51:59] NOTICE: ready to handle connections [07-Jan-2019 10:51:59] NOTICE: systemd monitor interval set to 10000ms [09-Jan-2019 09:17:10] NOTICE: Terminating ... [09-Jan-2019 09:17:10] NOTICE: exiting, bye-bye! [09-Jan-2019 09:22:39] NOTICE: fpm is running, pid 29230 [09-Jan-2019 09:22:39] NOTICE: ready to handle connections [09-Jan-2019 09:22:39] NOTICE: systemd monitor interval set to 10000ms [09-Jan-2019 09:22:45] NOTICE: Terminating ... [09-Jan-2019 09:22:45] NOTICE: exiting, bye-bye! [09-Jan-2019 09:22:45] NOTICE: fpm is running, pid 30529 [09-Jan-2019 09:22:45] NOTICE: ready to handle connections [09-Jan-2019 09:22:45] NOTICE: systemd monitor interval set to 10000ms [09-Jan-2019 09:22:48] NOTICE: Terminating ... [09-Jan-2019 09:22:48] NOTICE: exiting, bye-bye! [09-Jan-2019 09:22:49] NOTICE: fpm is running, pid 30631 [09-Jan-2019 09:22:49] NOTICE: ready to handle connections [09-Jan-2019 09:22:49] NOTICE: systemd monitor interval set to 10000ms [09-Jan-2019 09:22:50] NOTICE: Terminating ... [09-Jan-2019 09:22:50] NOTICE: exiting, bye-bye! [09-Jan-2019 09:22:50] NOTICE: fpm is running, pid 30928 [09-Jan-2019 09:22:50] NOTICE: ready to handle connections [09-Jan-2019 09:22:50] NOTICE: systemd monitor interval set to 10000ms [09-Jan-2019 09:22:56] NOTICE: Terminating ... [09-Jan-2019 09:22:56] NOTICE: exiting, bye-bye! [09-Jan-2019 09:22:56] NOTICE: fpm is running, pid 31289 [09-Jan-2019 09:22:56] NOTICE: ready to handle connections [09-Jan-2019 09:22:56] NOTICE: systemd monitor interval set to 10000ms [09-Jan-2019 09:23:02] NOTICE: Terminating ... [09-Jan-2019 09:23:02] NOTICE: exiting, bye-bye! [09-Jan-2019 09:23:02] NOTICE: fpm is running, pid 32176 [09-Jan-2019 09:23:02] NOTICE: ready to handle connections [09-Jan-2019 09:23:02] NOTICE: systemd monitor interval set to 10000ms [09-Jan-2019 09:24:33] NOTICE: Terminating ... [09-Jan-2019 09:24:33] NOTICE: exiting, bye-bye! [09-Jan-2019 09:26:02] NOTICE: fpm is running, pid 14391 [09-Jan-2019 09:26:02] NOTICE: ready to handle connections [09-Jan-2019 09:26:02] NOTICE: systemd monitor interval set to 10000ms [09-Jan-2019 09:28:01] NOTICE: Terminating ... [09-Jan-2019 09:28:01] NOTICE: exiting, bye-bye! [09-Jan-2019 09:34:31] NOTICE: fpm is running, pid 31215 [09-Jan-2019 09:34:31] NOTICE: ready to handle connections [09-Jan-2019 09:34:31] NOTICE: systemd monitor interval set to 10000ms [09-Jan-2019 09:34:37] NOTICE: Terminating ... [09-Jan-2019 09:34:37] NOTICE: exiting, bye-bye! [09-Jan-2019 09:34:37] NOTICE: fpm is running, pid 32501 [09-Jan-2019 09:34:37] NOTICE: ready to handle connections [09-Jan-2019 09:34:37] NOTICE: systemd monitor interval set to 10000ms [09-Jan-2019 09:34:41] NOTICE: Terminating ... [09-Jan-2019 09:34:41] NOTICE: exiting, bye-bye! [09-Jan-2019 09:34:41] NOTICE: fpm is running, pid 32597 [09-Jan-2019 09:34:41] NOTICE: ready to handle connections [09-Jan-2019 09:34:41] NOTICE: systemd monitor interval set to 10000ms [09-Jan-2019 09:34:42] NOTICE: Terminating ... [09-Jan-2019 09:34:42] NOTICE: exiting, bye-bye! [09-Jan-2019 09:34:42] NOTICE: fpm is running, pid 435 [09-Jan-2019 09:34:42] NOTICE: ready to handle connections [09-Jan-2019 09:34:42] NOTICE: systemd monitor interval set to 10000ms [09-Jan-2019 09:34:48] NOTICE: Terminating ... [09-Jan-2019 09:34:48] NOTICE: exiting, bye-bye! [09-Jan-2019 09:34:48] NOTICE: fpm is running, pid 810 [09-Jan-2019 09:34:48] NOTICE: ready to handle connections [09-Jan-2019 09:34:48] NOTICE: systemd monitor interval set to 10000ms [09-Jan-2019 09:34:54] NOTICE: Terminating ... [09-Jan-2019 09:34:54] NOTICE: exiting, bye-bye! [09-Jan-2019 09:34:54] NOTICE: fpm is running, pid 1884 [09-Jan-2019 09:34:54] NOTICE: ready to handle connections [09-Jan-2019 09:34:54] NOTICE: systemd monitor interval set to 10000ms [09-Jan-2019 09:35:26] NOTICE: Terminating ... [09-Jan-2019 09:35:26] NOTICE: exiting, bye-bye! [09-Jan-2019 09:35:43] NOTICE: fpm is running, pid 5960 [09-Jan-2019 09:35:43] NOTICE: ready to handle connections [09-Jan-2019 09:35:43] NOTICE: systemd monitor interval set to 10000ms
-
RE: Failed to create Snapin Error
@Sebastian-Roth The ip 192.168.1.105 it the address it will be on after installed. The address it’s on while connected to the internet is 192.168.105.238
The end goal is to have the server on an isolated network without being able to to see the outside world, I was following the instructions here, https://wiki.fogproject.org/wiki/index.php/FOG_on_an_Isolated_Network.That being said, I know to install fog, it is required to have internet access so I put it on our main network, where it can see the outside world. After it’s downloaded, I will be removing it from our network and back to it’s isolated one.
The reasoning for this is our network is 100% static. In the past we have tried putting DHCP in small spots for various reasons and it messed up some of our copiers/printers since they can have multiple IPs.
Since fog requires DHCP we bought a router and just set it on a closed network (the isolated network) with 4 outputs, 1 being the server, no inputs.