May also want to check to see if the computer object already exists in AD. If the account does exist, the join account also needs the ability to modify that account either by virtue of being the creator/owner or by having the permission to modify computer objects in the target OU.
Posts made by Daniel Miller
-
RE: Access Denied, code = 5
-
RE: FOG Snapin Does not Finish
@UWPVIOLATOR If you can’t get the application to behave with respect to the restarts, you could always create a snapin pack bundling the executable with a script. In the script, you could check to see if the application was already installed and of the correct version, then if it wasn’t perform the install. if you wanted to kick off the application and then do something like loop while the executable was running, you might want to play with the
start
command, something likestart "" installer.exe -args
. https://ss64.com/nt/start.html@george1421 the /k flag runs the specified command then leaves the command window open. https://ss64.com/nt/cmd.html
-
RE: When installing Fog IP issues
@nonamejason The means by which interface addressing is managed by default has changed a number of times over the years. Which version of Ubunutu Server is this box and how did you add in the 20.31 address?
-
RE: Auto Run Tasks Every Monday of the week
When confirming your task you are presented three options for scheduling: Instant, Delayed, and Schedule Cron-style. It sounds like you want the last option.
-
RE: MSI vs SmartInstaller
The smart installer is capable of installing the fog client on Windows, macOS, and Linux.
-
RE: client 0.11.17 do not install with MSI
@Sebastian-Roth Looks good from this end.
-
RE: Fake folder taking up all storage
I believe you are misunderstanding that result from
df
. That line says that there is a volume of size 88GB with a filesystem currently housing 33MB of data that is mounted under the directory/Images
. Separating the content of /images (where FOG keeps the captured image data by default) is a common practice, but in your case it seems there may be a capital ‘i’ in the directory name. If you installed FOG without reusing the previous settings, it may be the case that you are not seeing all the space that was available to you previously due to this naming mismatch. If you want to use this volume for storing you images, you can change the location of the image store to/Images
in your storage node configuration. -
RE: FOG Image Deploy Slowness
Do you have your network configured for Gigabit ethernet to the client and server? The magnitude of that change that sounds suspiciously like a change in media speed someplace down to 100MBit.
Are these unicast or multicast deployments?
Have there been any changes to the network infrastructure or switch configuration?
Are you able to see if your switches are auto-negotiating to the correct speed with the clients you are deploying, the fog server, and any intermediary switches? -
RE: How do you auto add printers to a host when provisioning?
The process you describe is the intended behavior, but I believe @george1421 worked on a persistent group plugin. Have a look through https://forums.fogproject.org/topic/8836/basic-persistent-groups-and-1-3-0rc16 a read through and see if it matches what you are attempting. I haven’t played with persistent groups personally, but the plugin is in the menus under version 1.5.7
-
RE: windows 10: deployment in different parts of the network fails
@fogusnew If you have the fog client installed in a sysprepped image you are deploying, the fogservice should be disabled prior to the sysprep.
https://wiki.fogproject.org/wiki/index.php/FOG_Client#FOG_Client_with_Sysprep
I wouldn’t think this would present intermittently in one room but not another, but I have seen weirder things happen. You might want to recapture with the fog service disabled and the service start configured inSetupComplete.cmd
and reattempt the deployment and see how things behave then. -
RE: Fog Client Authentication Issue
@LJedi need to complete the statement with a
;
; that is the line continuation prompt. -
RE: Group - Image Association overrides other group image
@stefan said in Group - Image Association overrides other group image:
I created for my 16 laptops two groups with all 16 hosts, only difference is the name of the group and the image file (other fields are blank in the create group settings).
That is expected behavior. Actions performed on a group act on all hosts that are members of that group at that time. If all 16 machines are in both group A and group B, any action performed on either group will affect all 16 machines. Can you explain what behavior you are wanting to see?
-
RE: Updated Ubuntu and now cannot get to fog gui
@IdahoTech apt logs should be in
/var/log/apt/history.log
and/var/log/apt/term.log
-
RE: Updated Ubuntu and now cannot get to fog gui
Was there a security update to mariadb in all that mess? May want to have a read through Ubuntu is FOG’s enemy.
-
RE: client 0.11.17 do not install with MSI
@Sebastian-Roth
OK, I was able to replicate the error with 0.11.17 with a command line installation using:msiexec /i FOGService.msi /quiet USETRAY="1" HTTPS="1" WEBADDRESS="192.168.137.11" WEBROOT="/fog" ROOTLOG="1" /l*v "FOGService.msi.log"
I was also able to replicate the issue on 0.11.16 using the same command line.
MSI (s) (04:10) [14:51:08:538]: Invoking remote custom action. DLL: C:\windows\Installer\MSI34C8.tmp, Entrypoint: InstallCert SFXCA: Extracting custom action to temporary directory: C:\windows\Installer\MSI34C8.tmp-\ SFXCA: Binding to CLR version v4.0.30319 Calling custom action SetupHelper!SetupHelper.CustomActions.InstallCert MSI (s) (04!08) [14:51:09:303]: Note: 1: 2205 2: 3: Error MSI (s) (04!08) [14:51:09:303]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709 MSI (s) (04!08) [14:51:09:303]: Product: FOG Service -- Unable to install CA certificate Unable to install CA certificate ...[clip]... MSI (s) (04:10) [14:51:09:741]: Note: 1: 2205 2: 3: Error MSI (s) (04:10) [14:51:09:741]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1708 MSI (s) (04:10) [14:51:09:741]: Note: 1: 2205 2: 3: Error MSI (s) (04:10) [14:51:09:741]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709 MSI (s) (04:10) [14:51:09:741]: Product: FOG Service -- Installation failed. MSI (s) (04:10) [14:51:09:741]: Windows Installer installed the product. Product Name: FOG Service. Product Version: 0.11.16. Product Language: 1033. Manufacturer: FOG. Installation success or error status: 1603.
will need to dig into who is trying to talk to what, where, and how…
-
RE: client 0.11.17 do not install with MSI
Installing the release msi interactively and targeting a non-https FOG installation is successful and functions as expected on one of my test systems, so I don’t think there is anything inherently wrong with the installation logic. Going to spin up an https fog instance to test against
-
RE: client 0.11.17 do not install with MSI
There is always that chance, but I would have thought the case statement I added would have eliminated any changes to the windows and linux install process. let me poke around it
-
RE: Starting cmain( )...
@kmonroe79 said in Starting cmain( )...:
What exit type or other FOG configuration settings need to be applied, so that computers will boot REGARDLESS of model?
I don’t think there is one answer to this question. There are far too many combinations of hardware, firmware, and site configurations for one set of settings to work for everyone. I suspect that is why the exit settings exist for both the server (FOG Configuration \ iPXE Menu Settings \ Boot Exit Settings) and the individual hosts; the server can be configured to take care of the bulk of machines and exceptions made for those that don’t work with those settings.
-
RE: Starting cmain( )...
I have a lab of Lenovo M73 and am currently using SANBOOT and REFIND_EFI
-
RE: Snapin queued forever
@renanserrou Seem to be a number of http error 500 reported in the log. Can you post the apache error and php-fpm logs from the fog server as well?