Posts made by davidedpg10

@sudburr I agree. The proposed interface with navigation on the side is pretty sleek. But the word management is just a tad overused. It looks good though

I think perhaps having small text underneath the icons (not too intrusive) stating what they are (such as images, hosts, groups etc) could make it a bit nicer to navigate. just a thought. What do other people think about that?

Hey guys, I know some people were trying to install FOG on a raspberry pi a while back, I don’t know how that went, but the latest stable release says it has native support for Raspbian, has anyone attempted FOG 1.4 yet? if so has it worked well?

Has anyone experienced something similar to this? I just upgraded to 1.3.5-RC1 and the issue is still there

@Raymond-Bell Yes they are all enabled by default, and they are enabled prior to pushing the image to the machines, however they all get unchecked specifically for the machines I imaged.

Server

• FOG Version: 1.3.4
• OS: Ubuntu 14.04LTS

Client

• Service Version: 0.11.9
• OS: Windows 10 Enterprise

Description

I have just reimaged 2 machines, and both had all services turned on prior to being imaged, however after the Windows image was pushed all of the services under “Service Settings” on the FOG Web GUI were turned off which then causes the client not to be renamed or to run snapins. However if the services are re-enabled after the imaging process is done, the client will run snapins prior to changing its hostname. which then causes my powershell script to join computers to domain with a name I don’t intend for them to have.

@Raymond-Bell I have now confirmed it, for whatever reason, reimaging a computer causes all of the services to become unchecked, it explains why the computers have not been renamed correctly prior to running snapins

@Raymond-Bell It’s very possible that the hostname-changer is unchecked, it’s been happening to me lately, but the problem is that it might somehow be unchecking itself. I have it to be checked by default, but when I added a new client, it had all services off which caused me to have some problems with machines joining the domain with their default name. So just something to keep in mind. I don’t know what’s been causing that though.

@Joe-Schmitt Thank you, that was a very detailed explanation and it does clear things up. I appreciate it. Hopefully the TL;DR: Messages can be implemented, I am sure that would help greatly as well.

@george1421 I had read about the VBScript option, I can use msg.exe if I send it directly to the computer name (and it will do what I need, meaning it will display it even if nobody is logged in so in the lock screen). The problem is that if the DNS records have not updated, the computer name is not recognized and msg.exe is pretty much useless if I am sending it to a remote computer. I wanted something which I could deploy or send from fog (given that fog will deliver regardless of computer name) and display info/variables/notifications even on the lock screen. I can send a powershell script from fog which displays the computer name variable, but it is ran in the background and the messagebox containing the computer name never pops up(the script works if I run it manually on my computer). so that’s why I was wondering if there was a way to use fog for notifications and messages purposes.

I administer a lab environment, currently containing about 45-50 computers in total (Not an insanely big setup), all spread out in different sections of a building. Recently I have had to re-image all of them and also redo our naming-scheme due to some organizational changes. I have been trying to find a way to display the computer name environmental variable on the screens regardless if anyone is logged into them or not. For this msg.exe works most of the time (albeit a very simple message box), but if the name changes have not taken effect it does not work correctly. Also I have to send it from a specific computer, as deploying a powershell script seems to keep it all hidden and it will not display the box. My question is, is there a way to reuse the Shutdown GUI on the Fog client to display either notifications for my users, or in this case display a variable on the screen so I can make sure things are in the right order? or would this feature be too difficult to implement?

Thank you very much. You guys are awesome!

:::::EDIT: Fog Version = 1.3.0 Official release- OS: Ubuntu 14.04
This one it’s not a huge pressing matter (at least to me) and perhaps other issues take precedence. But The “Host and Users” section of the Reports submenu, used to show me a list of hosts along with the users that had logged into it as well as the time and date they had logged in. Now it doesn’t show anything
The information is still saved in the database, given that if I select a specific machine in “Login history” it will show the users that have logged into that specific machine.
(i dont even know why I scratched the usernames, I’m sure you could still figure them out if you tried)
but the opposite action will not work either, selecting only the username and no specific machine will return nothing, it would be a nice feature if someone wanted to figure out what machines a person logged into without going through each machine.

@Tom-Elliott yes it is, Please mark this thread as solved, and thank you for your help.

@Wayne-Workman My apologies, it was in fact an SCCM Deployment. I did not fully understand how SCCM deployments worked, I did not realize that once set, it will check periodically if it is still compliant with said deployment. It’s not a one time deal.

@Joe-Schmitt
I will recheck the GPO, the log file got pretty big as the issue has been happening around every 3 hours. I have also checked SCCM deployments and nothing seems to be scheduled. I have embedded the log. Thank you guys for helping.0_1483037359489_fog.log

@Tom-Elliott I just checked and I do not see any GPO pushing any installations.
The log does say “12/29/2016 10:18 AM Service Invoking early JIT compilation on needed binaries” which makes me think that the new client is pulling and installing the old client… I even disabled client updater supposedly, but the log seems to think I have disabled user tracker apparently.

 12/29/2016 10:16 AM Client-Info Client Version: 0.11.7
 12/29/2016 10:16 AM Client-Info Client OS:      Windows
 12/29/2016 10:16 AM Client-Info Server Version: 1.3.0
 12/29/2016 10:16 AM Middleware::Response Success
------------------------------------------------------------------------------

 12/29/2016 10:16 AM Service Sleeping for 131 seconds
 12/29/2016 10:16 AM Controller Stop
 12/29/2016 10:16 AM Service Stop requested
 12/29/2016 10:16 AM Bus {
  "self": true,
  "channel": "Status",
  "data": "{\r\n  \"action\": \"unload\"\r\n}"
}
 12/29/2016 10:16 AM Bus Emmiting message on channel: Status
 12/29/2016 10:18 AM Main Overriding exception handling
 12/29/2016 10:18 AM Main Bootstrapping Zazzles
 12/29/2016 10:18 AM Controller Initialize
 12/29/2016 10:18 AM Zazzles Creating main thread
 12/29/2016 10:18 AM Zazzles Service construction complete
 12/29/2016 10:18 AM Controller Start

 12/29/2016 10:18 AM Service Starting service
 12/29/2016 10:18 AM Bus Became bus server
 12/29/2016 10:18 AM Bus {
  "self": true,
  "channel": "Status",
  "data": "{\r\n  \"action\": \"load\"\r\n}"
}
 12/29/2016 10:18 AM Bus Emmiting message on channel: Status
 12/29/2016 10:18 AM Service Invoking early JIT compilation on needed binaries

------------------------------------------------------------------------------
--------------------------------Authentication--------------------------------
------------------------------------------------------------------------------
 12/29/2016 10:18 AM Client-Info Version: 0.11.5
 12/29/2016 10:18 AM Client-Info OS:      Windows
 12/29/2016 10:18 AM Middleware::Authentication Waiting for authentication timeout to pass
 12/29/2016 10:18 AM Middleware::Communication Download: http://192.168.50.237/fog/management/other/ssl/srvpublic.crt
 12/29/2016 10:18 AM Data::RSA FOG Server CA cert found
 12/29/2016 10:18 AM Middleware::Authentication Cert OK
 12/29/2016 10:18 AM Middleware::Communication POST URL: http://192.168.50.237/fog/management/index.php?sub=requestClientInfo&authorize&newService
 12/29/2016 10:18 AM Middleware::Response Success
 12/29/2016 10:18 AM Middleware::Authentication Authenticated

 12/29/2016 10:18 AM Bus Registering ParseBus in channel Power
 12/29/2016 10:18 AM Log Unhandled exception caught
 12/29/2016 10:18 AM Log     Terminating: True
 12/29/2016 10:18 AM Log     Hash code: 13539942

This is the log portion about client updater and user tracker.

------------------------------------------------------------------------------
----------------------------------UserTracker---------------------------------
------------------------------------------------------------------------------
 12/29/2016 10:14 AM Client-Info Client Version: 0.11.7
 12/29/2016 10:14 AM Client-Info Client OS:      Windows
 12/29/2016 10:14 AM Client-Info Server Version: 1.3.0
 12/29/2016 10:14 AM Middleware::Response Success
------------------------------------------------------------------------------

 12/29/2016 10:14 AM Service Sleeping for 104 seconds
 12/29/2016 10:16 AM Middleware::Communication URL: http://192.168.50.237/fog/management/index.php?sub=requestClientInfo&configure&newService&json
 12/29/2016 10:16 AM Middleware::Response Success
 12/29/2016 10:16 AM Service ERROR: Invalid promptTime, using default
 12/29/2016 10:16 AM Middleware::Communication Download: http://192.168.50.237/fog/management/other/banner.jpg
 12/29/2016 10:16 AM Middleware::Communication URL: http://192.168.50.237/fog/management/index.php?sub=requestClientInfo&mac=F4:CE:46:2D:DE:7F||00:00:00:00:00:00:00:E0&newService&json
 12/29/2016 10:16 AM Middleware::Response Success
 12/29/2016 10:16 AM Middleware::Communication URL: http://192.168.50.237/fog/service/getversion.php?clientver&newService&json
 12/29/2016 10:16 AM Middleware::Communication URL: http://192.168.50.237/fog/service/getversion.php?newService&json

 12/29/2016 10:16 AM Service Creating user agent cache
 12/29/2016 10:16 AM Middleware::Response Success
 12/29/2016 10:16 AM Middleware::Response Module is disabled globally on the FOG server
 12/29/2016 10:16 AM Middleware::Response Module is disabled globally on the FOG server

------------------------------------------------------------------------------
---------------------------------ClientUpdater--------------------------------
------------------------------------------------------------------------------
 12/29/2016 10:16 AM Client-Info Client Version: 0.11.7
 12/29/2016 10:16 AM Client-Info Client OS:      Windows
 12/29/2016 10:16 AM Client-Info Server Version: 1.3.0
 12/29/2016 10:16 AM Middleware::Response Success
------------------------------------------------------------------------------

Server

• FOG Version: 1.3.0 REV 6050
• OS: Ubuntu 14.04

Client

• Service Version: 0.11.7
• OS: Windows 10 Enterprise MSDN

Description

I recently upgraded Fog from rc21 to the oficial 1.3.0 release, (I was on the 0.11.5 client too). I have a computer (that I know of) that somehow it keeps getting client 0.11.5 reinstalled and it ends up with both clients, after which it crashes and restarts, and after that it does not run FOGService. Here is the last part of the log.

------------------------------------------------------------------------------
----------------------------------UserTracker---------------------------------
------------------------------------------------------------------------------
 12/29/2016 8:31 AM Client-Info Client Version: 0.11.7
 12/29/2016 8:31 AM Client-Info Client OS:      Windows
 12/29/2016 8:31 AM Client-Info Server Version: 1.3.0
 12/29/2016 8:31 AM Middleware::Response Success
------------------------------------------------------------------------------

 12/29/2016 8:31 AM Service Sleeping for 91 seconds
 12/29/2016 8:31 AM Controller Stop
 12/29/2016 8:31 AM Service Stop requested
 12/29/2016 8:31 AM Bus {
  "self": true,
  "channel": "Status",
  "data": "{\r\n  \"action\": \"unload\"\r\n}"
}
 12/29/2016 8:31 AM Bus Emmiting message on channel: Status
 12/29/2016 8:33 AM Main Overriding exception handling
 12/29/2016 8:33 AM Main Bootstrapping Zazzles
 12/29/2016 8:33 AM Controller Initialize
 12/29/2016 8:33 AM Zazzles Creating main thread
 12/29/2016 8:33 AM Zazzles Service construction complete
 12/29/2016 8:33 AM Controller Start

 12/29/2016 8:33 AM Service Starting service
 12/29/2016 8:33 AM Bus Became bus server
 12/29/2016 8:33 AM Bus {
  "self": true,
  "channel": "Status",
  "data": "{\r\n  \"action\": \"load\"\r\n}"
}
 12/29/2016 8:33 AM Bus Emmiting message on channel: Status
 12/29/2016 8:33 AM Service Invoking early JIT compilation on needed binaries

------------------------------------------------------------------------------
--------------------------------Authentication--------------------------------
------------------------------------------------------------------------------
 12/29/2016 8:33 AM Client-Info Version: 0.11.5
 12/29/2016 8:33 AM Client-Info OS:      Windows
 12/29/2016 8:33 AM Middleware::Authentication Waiting for authentication timeout to pass
 12/29/2016 8:33 AM Middleware::Communication Download: http://192.168.50.237/fog/management/other/ssl/srvpublic.crt
 12/29/2016 8:33 AM Data::RSA FOG Server CA cert found
 12/29/2016 8:33 AM Middleware::Authentication Cert OK
 12/29/2016 8:33 AM Middleware::Communication POST URL: http://192.168.50.237/fog/management/index.php?sub=requestClientInfo&authorize&newService
 12/29/2016 8:33 AM Middleware::Response Success
 12/29/2016 8:33 AM Middleware::Authentication Authenticated


 12/29/2016 8:33 AM Bus Registering ParseBus in channel Power
 12/29/2016 8:33 AM Log Unhandled exception caught
 12/29/2016 8:33 AM Log     Terminating: True
 12/29/2016 8:33 AM Log     Hash code: 13539942

@jscharfenberg

I run this on powershell

Get-AppxPackage -AllUsers | Remove-AppxPackage

And then I use this sysprep unattend file. It works really well in my environment.

<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">

<!-- Autounattend_x64_BIOS_sample.xml

This file automates the Windows installation.

    Before using this file:
     * Replace ProductKey with a product key for the edition of Windows you are installing
       (example: Windows 8 Pro)
       Note:
          The product key used in Microsoft-Windows-Setup\UserData\ProductKey\Key 
          can be used many times in different installations and is not used to activate Windows. 
          It is only used to choose which edition of Windows to install. 
          
          The individual product key is either specified by the user, or by setting 
          Microsoft-Windows-Shell-Setup\ProductKey.
    * Set the default language to your own:
      Replace "en-US" with your language code in Microsoft-Windows-International-Core-WinPE\SetupUILanguage. 
      For a list of languages, see http://go.microsoft.com/fwlink/?LinkId=206620.
    * OEMs: Replace OEMInformation with your support information

    To use this file: 
       Save this file on the root of a USB flash drive with the filename: Autounattend.xml
       Put the Windows DVD and the USB key into a new x64-BIOS PC.
-->


   <settings pass="specialize">
       <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <CopyProfile>true</CopyProfile>
       </component>
   </settings>
   <settings pass="windowsPE">
       <component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
           <SetupUILanguage>
               <UILanguage>en-US</UILanguage>
           </SetupUILanguage>
           <InputLocale>en-US</InputLocale>
           <SystemLocale>en-US</SystemLocale>
           <UILanguage>en-US</UILanguage>
           <UserLocale>en-US</UserLocale>
       </component>
       <component name="Microsoft-Windows-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
           <UserData>
               <AcceptEula>true</AcceptEula>
           </UserData>
       </component>
   </settings>
<settings pass="oobeSystem">
 <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <OOBE>
   <HideEULAPage>true</HideEULAPage>
   <HideLocalAccountScreen>true</HideLocalAccountScreen>
   <HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
   <HideOnlineAccountScreens>true</HideOnlineAccountScreens>
   <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
   <SkipUserOOBE>true</SkipUserOOBE>
   <SkipMachineOOBE>true</SkipMachineOOBE>
  </OOBE>
 </component>
</settings>
</unattend>

@Joe-Schmitt I am using MSI, as it was what I used before,
This is the command I used to use "msiexec /i C:\FOGService.msi /passive USETRAY=“0” HTTPS=“0” WEBADDRESS=“192.168.50.237” WEBROOT=“/fog” ROOTLOG=“0” " I attempted to do run it with the new installer named “FOG Service Installer.msi” but it appears that none of the previously automated parameters work, and uppon logging with msiexec, they were not queried or invoked at any point in the manual installation.