@davidedpg10 My FOG Server is Version 1.3.0-RC-8, thanks for the suggesting I state it. @george1421
The FOG Client associated with it seems to be 0.11.5

@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>

@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.