Topics created by John Johnson

I found out that the error was caused because the fog account was not recreated when we upgraded. All is well now except for name changing and getting them on the domain automatically. I think that is also a password issue.

@john-johnson Check that host with disk diagnostics and ram diagnostics. Often these tests are built into firmware and you can select them when the device is just powering on. Generally though, if the errors are not excessive it’s normally fine.

@Wayne-Workman said in Word - temp environmental variable:

@John-Johnson What is it that you did? I’m asking for future readers.

I kept it offline until I could get Administrator activated. Once logged into Administrator my user account was safe from Microsoft’s unwanted pushed apps.

@Wayne-Workman Hell, whenever I try to upgrade Ubuntu even Ubuntu gets messed up and I need to spend time to fix it.

FOG 1.2.0 and the legacy fog client does not support windows 10. You need the newer version of fog (1.3.0-rcX at the time of this post) and the new fog client (0.9.X or newer) for win10 support.

For sure you will need the 1.3.0 series for native FOG server support for uefi firmware, gpt disk format, NVMe disks, and Win10 support running on current hardware (i.e. latests FOS engine running linux 4.7).

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

1.3.0 is really the trunk/“beta” version currently. It isn’t quite yet to release. Granted if every stable trunk was released as a final version, we would be at FOG 5782.2.0 by now.
@Tom-Elliott has been working on gpt partitions recently trying to get it perfect. Give the trunk a go

https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk

AWESOME! Glad you got it working 🙂

edit (nano or vi) " /etc/default/tftpd-hpa " and add “sleep 30” on the top line so it looks like :

[I][B]sleep 30[/B][/I]
[I][B]# /etc/default/tftpd-hpa[/B][/I]
[I][B]# FOG Modified version[/B][/I]
[I][B]TFTP_USERNAME=“root”[/B][/I]
[I][B]TFTP_DIRECTORY=“/tftpboot”[/B][/I]
[I][B]TFTP_ADDRESS=“0.0.0.0:69”[/B][/I]
[I][B]TFTP_OPTIONS=“-s”[/B][/I]

will have to restart the service or reboot

Maybe you should change the memory_limit parameter in the php.ini.

Client couldnt mount nfs, so in GUI menu I created a new Node Storage with a new group storage for that node. Now i Can Upload Image on client, but slowly (less that 1Gb/min) without mounting nfs.

But looking for a solution for my first goal.

It looks like the InstallRite website is completely shut down. My problem with SFX is creating answer files to make the deployment unattended. I just wish it was user friendly.

[url]http://www.epsilonsquared.com/[/url]

Also, the upload goes to /images/dev/[mac addr] until the image is completely uploaded and moved to it’s final home at the end of the imaging processes. The chances of the upload process leaving you imageless is small, but the chance your new image is worthless due to some configuration issue, is medium.

If you have a large number of devices, you can create a new image definition and upload it just to make sure it works, then run a simple SQL statement to point all devices that used the old image ID to the new image ID.

I’m sure there will be training this year. There has been training the last 3 years in a row 😃

Seems like the Google Toolbar is causing issues with Internet Explorer. Disabling the toolbar has improved things.

Fog .32 is up and running. Very nice interface.

Now I am waiting for .33 to come out.