Could we have the web interface indicate that a storage node is correctly connected passwords match ect… maybe a green dot like the ping status when its added or listed in the all storage nodes list. A second indicator that all the images are in sync with the main repository.
Joseph Hales
@Joseph Hales
Best posts made by Joseph Hales
-
Storage Nodes
-
RE: Added nodes, updated everything to 3429. Can no longer image.
Don’t forget that around SVN 3410 and up the storage node installer resets the storage password when run. It should display the new password at the end of the install.
-
RE: Missing legacy client
We’re not using the new client yet I upgraded to SVN 3463 this morning which fixed the missing client issue.
-
RE: FOG Snapin Task Queued
Chrome has a special enterprise installer available here. Your runwith command is msiexec, the run with argument is /i and the command line switches are /qn.
-
RE: Trying to upgrade from 1.2.0 to latest svn
He has 1.2 he is upgrading to SVN when it happens.
-
RE: Storms, corrupted MBR, save the images?
I try and keep a USB drive backup of the images offline as well as the configuration save to permit an easy rebuild from scratch if necessary. Most users update images rarely enough that this is not a huge burden.
-
RE: Tips to new FOG server
It really depends on usage. How many clients, how many images, how large are your images, compression level, number of images sent at a time?
-
RE: Issue with ftp_login on CentOS 7, FOG 1.2.0
As I understand it 4 things need to match the Operating system password for the fog user, the storage management password and username fog, the tftp password under the web ui in fog settings and finally the storageftpuser / storageftppassword in the /opt/fog/.fogsettings file. After they all match restart the fog services or just reboot the server.
-
RE: Uninstall and install Citrix receiver.
/silent should be in the Snapin Arguments field.
Latest posts made by Joseph Hales
-
RE: SVN vs GIT redux
Maybe add that note to the wiki here and include the command to upgrade to release candidate as well as working branch for the less adventurous.
-
RE: AD join works with legacy client fails with new client
@Joe-Schmitt @Sebastian-Roth ok entered the ad password again for the new client cleared and re checked it for the problematic host and it is now working. When the new client first came out was the entry always plain text or did that get added in a later SVN maybe i had it encrypted from before?
-
RE: AD join works with legacy client fails with new client
@Sebastian-Roth Both client, fog server, and domain controller time settings match including time zone. My server password isn’t unusually exotic it is just Uppercase and lower case letters and numbers no special characters.
-
AD join works with legacy client fails with new client
Running Version 1.4.4
SVN Revision: 6077 (checkout says 6078 but management page still says 6077)
Ubuntu Server 14.04.3 all updates current
Client
Windows 10 running FOG client
[Log Follows]11/28/2017 1:40 PM Main Overriding exception handling 11/28/2017 1:40 PM Main Bootstrapping Zazzles 11/28/2017 1:40 PM Controller Initialize 11/28/2017 1:40 PM Controller Start 11/28/2017 1:40 PM Service Starting service 11/28/2017 1:40 PM Bus Became bus server 11/28/2017 1:40 PM Bus Emmiting message on channel: Status 11/28/2017 1:40 PM Service Invoking early JIT compilation on needed binaries ------------------------------------------------------------------------------ --------------------------------Authentication-------------------------------- ------------------------------------------------------------------------------ 11/28/2017 1:40 PM Client-Info Version: 0.11.12 11/28/2017 1:40 PM Client-Info OS: Windows 11/28/2017 1:40 PM Middleware::Authentication Waiting for authentication timeout to pass 11/28/2017 1:40 PM Middleware::Communication Download: http://10.200.10.150/fog/management/other/ssl/srvpublic.crt 11/28/2017 1:40 PM Data::RSA FOG Server CA cert found 11/28/2017 1:40 PM Middleware::Authentication Cert OK 11/28/2017 1:40 PM Middleware::Communication POST URL: http://10.200.10.150/fog/management/index.php?sub=requestClientInfo&authorize&newService 11/28/2017 1:40 PM Middleware::Response Success 11/28/2017 1:40 PM Middleware::Authentication Authenticated 11/28/2017 1:40 PM Middleware::Communication URL: http://10.200.10.150/fog/management/index.php?sub=requestClientInfo&configure&newService&json 11/28/2017 1:40 PM Middleware::Response Success 11/28/2017 1:40 PM Middleware::Communication URL: http://10.200.10.150/fog/management/index.php?sub=requestClientInfo&mac=D8:9E:F3:10:F0:96&newService&json 11/28/2017 1:40 PM Middleware::Response Success 11/28/2017 1:40 PM Middleware::Communication URL: http://10.200.10.150/fog/service/getversion.php?clientver&newService&json 11/28/2017 1:40 PM Middleware::Communication URL: http://10.200.10.150/fog/service/getversion.php?newService&json 11/28/2017 1:40 PM Service Creating user agent cache 11/28/2017 1:40 PM Middleware::Response Invalid time 11/28/2017 1:40 PM Middleware::Response No Printers 11/28/2017 1:40 PM Middleware::Response Module is disabled globally on the FOG server 11/28/2017 1:40 PM Service Initializing modules ------------------------------------------------------------------------------ ---------------------------------ClientUpdater-------------------------------- ------------------------------------------------------------------------------ 11/28/2017 1:40 PM Client-Info Client Version: 0.11.12 11/28/2017 1:40 PM Client-Info Client OS: Windows 11/28/2017 1:40 PM Client-Info Server Version: 1.4.4 11/28/2017 1:40 PM Middleware::Response Success ------------------------------------------------------------------------------ ------------------------------------------------------------------------------ ----------------------------------TaskReboot---------------------------------- ------------------------------------------------------------------------------ 11/28/2017 1:40 PM Client-Info Client Version: 0.11.12 11/28/2017 1:40 PM Client-Info Client OS: Windows 11/28/2017 1:40 PM Client-Info Server Version: 1.4.4 11/28/2017 1:40 PM Middleware::Response Success ------------------------------------------------------------------------------ ------------------------------------------------------------------------------ --------------------------------HostnameChanger------------------------------- ------------------------------------------------------------------------------ 11/28/2017 1:40 PM Client-Info Client Version: 0.11.12 11/28/2017 1:40 PM Client-Info Client OS: Windows 11/28/2017 1:40 PM Client-Info Server Version: 1.4.4 11/28/2017 1:40 PM Middleware::Response Success 11/28/2017 1:40 PM HostnameChanger Checking Hostname 11/28/2017 1:40 PM HostnameChanger Hostname is correct 11/28/2017 1:40 PM HostnameChanger Attempting to join domain 11/28/2017 1:40 PM HostnameChanger Logon failure: unknown username or bad password, code = 1326 ------------------------------------------------------------------------------
Note older windows 7 machines running the legacy client do not show this error.
-
RE: Fog Client fails to authenticate
@sebastian-roth I have been busy with other things and finally revisited this issue. Recreating the certificate and tokens fixed my authentication problem I may have and AD join issue but will troubleshoot further before I open a new topic on it.
-
RE: "Seems like you are trying to restore to an empty disk" issue
Two other things to check are the bios versions identical, and is secure boot on or off.
-
RE: Uninstall and install Citrix receiver.
/silent should be in the Snapin Arguments field.
-
RE: Fog Client 11.12 not renaming computer/joining domain (Could not authenticate)
Also if you add the host to a group it will force the reset encryption button to appear in group management you can try that. This appears to be the same issue I am seeing in https://forums.fogproject.org/topic/10167/fog-client-fails-to-authenticate/11 but we haven’t got an answer there yet either but you can try some of the same steps yourself.
-
RE: W7 Image: Disk read Error after imaging
Then I think you need to try what @sudburr suggested and wipe the drive fully before imaging.