@george1421 Can confirm that this is the fix. Recently just deployed 650 EliteDesk 800 G2 SFF’s and upgrading to trunk (using the newer kernel) fixed it.
Best posts made by RLane
-
RE: HP EliteDesk 800 G2 compatibility
-
RE: Groups can no longer hold more than one member (Trunk 7825)
Here was another thread that contained the same issue:
https://forums.fogproject.org/topic/7473/7703-groups-bugged/20
I believe it was fixed in the latest revision update. @Tom-Elliott can correct me if I’m wrong.
-
Ideal FOG Setup
Hi -
So I’ve been a member here for a long time and been using FOG since 0.32. I love it, love the community and environment. I also appreciate all of the work and effort that the dev’s put into it.
I’ve noticed one of the key organizations that use FOG are those of you in the educational sector. As a network admin, I’m responsible for the imaging of machines over the summer. I do this every year to keep everything fresh and up to date, along with making changes that the teachers request in labs.
Now that summer is approaching (students have a day left here) – what is the ideal setup for FOG?
-
I’m running 1.2.0 right now - Ubuntu 14.04
-
I am not using any trunk releases
-
After reading about the trunk speeds being so much quicker for gig server and gig client imaging, I’m convinced I should upgrade
-
The client seems promising and should be available soon – another reason I’m convinced I should upgrade
Obviously Tom already said that the next stable release will be soon, however, should I rebuild my FOG server (export users, client, etc.) and rebuild it fresh and use the trunk builds?
Should I wait until later in the summer for an upcoming stable reason?
I’m curious to see what everyone thinks.
Thanks!
-
-
RE: FOG + Powershell (WinUpdate) Question
@Mentaloid That’s actually a pretty nifty idea… let me upload a new image without the script running from my batch file. The more I use FOG, the more I start to realize it’s designed to make life easy…
-
RE: Automated Deployment
Welp, I’m sorry for bugging everybody. After working on this all day and night, I found that the wrong unattend file was being used… with a restart set to hit 25 seconds after the first user logs in.
On a happy note, my Win10 deployment is finalized, so thanks all for that.
Sorry @joe-schmitt @george1421
Latest posts made by RLane
-
RE: Domain Join Not working
What does your C:\fog.log say? What version of FOG are you using and what OS are you deploying? Windows 10? Windows 7?
-
RE: Client doesn't join domain after deploy
I ran into a similar issue here - it would always ask me to press OK on the domain/network screenshot you posted. It would hang the FOG client and prevent it from rebooting for the hostname/domain join and changes.
My post is here:
https://forums.fogproject.org/topic/10479/windows-10-1703-sysprep-question
-
RE: Windows 10 1703 - Sysprep Question
As a temporary solution, I have removed the auto login portion of my unattend.xml file … I’m not sure if this is the ideal solution but it worked.
When I remove the autologin portion, I do not need to force FOG to rename when users are logged in. In the past, 1511 and 1607, it didn’t seem to mind the local administrator account being logged in after an imaging task to rename, join domain and reboot. It appears it matters now?
If I keep the autologin, I have to ensure FOG is set to force changes despite a user being logged in. For those using my unattend - remove this:
<AutoLogon> <Password> <Value>password here</Value> <PlainText>false</PlainText> </Password> <Enabled>true</Enabled> <LogonCount>1</LogonCount> <Username>administrator</Username> </AutoLogon>
If I had to guess, 1703 had a couple of changes that will require a FOG Client update.
-
RE: Windows 10 1703 - Sysprep Question
Thanks for that. I’m wondering if anybody else has had success with 1703. If they have, there’s a chance that it is an issue on my head rather than some changes within Windows affecting the client.
My SetupComplete is below:
@ECHO OFF TITLE Post Sysprep Configuration Script REM *** Activating Windows TITLE Activating Windows 10... cscript slmgr.vbs /skms kms.domain.org cscript slmgr.vbs /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX cscript slmgr.vbs /ato REM *** Activate Office TITLE Activating Office... cscript "C:\Program Files (x86)\Microsoft Office\Office16\ospp.vbs" /sethst:kms.domain.org cscript "C:\Program Files (x86)\Microsoft Office\Office16\ospp.vbs" /act REM *** Starting FOG Service after boot TITLE Start FOG Service... sc config FOGService start= auto shutdown -t 0 -r REM *** Finalize Script Actions and Cleanup the Scripting Environment TITLE Finalizing Script Actions... DEL /Q /F c:\Windows\System32\Sysprep\unattend.xml DEL /Q /F c:\Windows\panther\unattend.xml RD /S /Q c:\windows\setup\scripts
And my unattend file is:
<?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <servicing></servicing> <settings pass="windowsPE"> <component name="Microsoft-Windows-PnpCustomizationsWinPE" 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"> <DriverPaths> <PathAndCredentials wcm:action="add" wcm:keyValue="b895faa4"> <Path>C:\Windows\Drivers</Path> </PathAndCredentials> </DriverPaths> </component> </settings> <settings pass="generalize"> <component name="Microsoft-Windows-Security-SPP" 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"> <SkipRearm>1</SkipRearm> </component> </settings> <settings pass="specialize"> <component name="Microsoft-Windows-Security-SPP-UX" 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"> <SkipAutoActivation>true</SkipAutoActivation> </component> <component name="Microsoft-Windows-Deployment" 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"> <RunSynchronous> <RunSynchronousCommand wcm:action="add"> <Description>Activates Built-in Administrator account</Description> <Order>1</Order> <Path>net user administrator /active:yes</Path> </RunSynchronousCommand> </RunSynchronous> </component> <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"> <DesktopOptimization> <ShowWindowsStoreAppsOnTaskbar>false</ShowWindowsStoreAppsOnTaskbar> <GoToDesktopOnSignIn>false</GoToDesktopOnSignIn> </DesktopOptimization> <TimeZone>Eastern Standard Time</TimeZone> <RegisteredOrganization>*school here*</RegisteredOrganization> <RegisteredOwner>*school here*</RegisteredOwner> <CopyProfile>true</CopyProfile> <ComputerName>*</ComputerName> </component> </settings> <settings pass="oobeSystem"> <component name="Microsoft-Windows-International-Core" 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"> <InputLocale>en-us</InputLocale> <SystemLocale>en-us</SystemLocale> <UILanguage>en-us</UILanguage> <UserLocale>en-us</UserLocale> </component> <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> <ProtectYourPC>1</ProtectYourPC> <HideEULAPage>true</HideEULAPage> <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE> <HideOnlineAccountScreens>true</HideOnlineAccountScreens> <HideOEMRegistrationScreen>true</HideOEMRegistrationScreen> <HideLocalAccountScreen>false</HideLocalAccountScreen> </OOBE> <UserAccounts> <AdministratorPassword> <Value>password here</Value> <PlainText>false</PlainText> </AdministratorPassword> <LocalAccounts> <LocalAccount wcm:action="add"> <Password> <Value>password here</Value> <PlainText>false</PlainText> </Password> <Name>Administrator</Name> <Group>Administrators</Group> <DisplayName>Administrator</DisplayName> <Description>Local Administrator</Description> </LocalAccount> </LocalAccounts> </UserAccounts> <VisualEffects> <FontSmoothing>ClearType</FontSmoothing> </VisualEffects> <RegisteredOrganization>*school here*</RegisteredOrganization> <RegisteredOwner>*school here*</RegisteredOwner> <TimeZone>Eastern Standard Time</TimeZone> <AutoLogon> <Password> <Value>password here</Value> <PlainText>false</PlainText> </Password> <Enabled>true</Enabled> <LogonCount>1</LogonCount> <Username>administrator</Username> </AutoLogon> </component> </settings> <cpi:offlineImage cpi:source="wim:c:location:/sw_dvd5_win_edu_10_1703_64bit_english_mlf_x21-36554/sources/install.wim#Windows 10 Education" xmlns:cpi="urn:schemas-microsoft-com:cpi" /> </unattend>
-
Windows 10 1703 - Sysprep Question
Server
- FOG Version: 1.4.4 (SVN 6077)
- OS: CentOS 7 x64
Client
- Service Version: 1.0.12
- OS: Windows 10 - 1703 Education
Description
After messing around with Windows 10 1703, I figured I would give sysprep a try. I used the same unattend file as I did in 1511 and 1607.
Very basic - activate the built in administrator account, set a password, etc. On previous Windows 10 builds, I always had 1 AutoLogin in the unattend.xml file. Normally, the FOG client service would be activated from the SetupComplete.cmd (using the two sections from the Wiki) … but for some reason, despite starting, it never reboots. I can post an example log tomorrow when I’m back in the office, however it was an issue with the hostname changer. It would not change the name because the default (AutoLogin) administrator user was logged in. Was this a change within Windows or with how the latest version of the client handles renaming/joining domain?
It’s worth noting that if I set the unattend file to 0 auto logins, it does not automatically reboot. If I select within the GUI to force hostname/domain joining despite a user being logged in - it works.
-
RE: Windows 10 Client 0.11.4 Windows Service
@Joe-Schmitt There isn’t because the service is not starting until a manual reboot. In event viewer, it shows that the service failed to start after 3000 ms or something, failed twice like this.
Good news though… works well on an SSD. Any machine with a 7200 HDD, it doesn’t start the service in time. I haven’t had a computer fail yet with an SSD.
-
RE: Windows 10 Client 0.11.4 Windows Service
@Joe-Schmitt I did. I’ve tried with the reboot - didn’t work. I’ve tried with automatic-delay - didn’t work either.
-
RE: 0.11.4 RC4 AD Question
SetupComplete.cmd
@ECHO OFF TITLE Post Sysprep Configuration Script REM *** Activating Windows TITLE Activating Windows 10... cscript slmgr.vbs /skm sx.org cscript slmgr.vbs /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX cscript slmgr.vbs /ato REM *** Activate Office TITLE Activating Office... cscript "C:\Program Files (x86)\Microsoft Office\Office16\ospp.vbs" /sethst:x.org cscript "C:\Program Files (x86)\Microsoft Office\Office16\ospp.vbs" /act REM *** Starting FOG Service after boot TITLE Start FOG Service... sc config FOGService start= auto net start FOGService REM *** Finalize Script Actions and Cleanup the Scripting Environment TITLE Finalizing Script Actions... DEL /Q /F c:\Windows\System32\Sysprep\unattend.xml DEL /Q /F c:\Windows\panther\unattend.xml RD /S /Q c:\windows\setup\scripts
Unattend.xml
<?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <servicing></servicing> <settings pass="windowsPE"> <component name="Microsoft-Windows-PnpCustomizationsWinPE" 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"> <DriverPaths> <PathAndCredentials wcm:action="add" wcm:keyValue="b895faa4"> <Path>C:\Windows\Drivers</Path> </PathAndCredentials> </DriverPaths> </component> </settings> <settings pass="generalize"> <component name="Microsoft-Windows-Security-SPP" 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"> <SkipRearm>1</SkipRearm> </component> </settings> <settings pass="specialize"> <component name="Microsoft-Windows-Security-SPP-UX" 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"> <SkipAutoActivation>true</SkipAutoActivation> </component> <component name="Microsoft-Windows-Deployment" 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"> <RunSynchronous> <RunSynchronousCommand wcm:action="add"> <Description>Activates Built-in Administrator account</Description> <Order>1</Order> <Path>net user administrator /active:yes</Path> </RunSynchronousCommand> </RunSynchronous> </component> <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"> <DesktopOptimization> <ShowWindowsStoreAppsOnTaskbar>false</ShowWindowsStoreAppsOnTaskbar> <GoToDesktopOnSignIn>false</GoToDesktopOnSignIn> </DesktopOptimization> <OEMInformation> <Logo>C:\Windows\System32\oobe\info\info.bmp</Logo> <Manufacturer>Hewlett Packard</Manufacturer> <SupportHours></SupportHours> <SupportURL></SupportURL> </OEMInformation> <TimeZone>Eastern Standard Time</TimeZone> <RegisteredOrganization>Name Here</RegisteredOrganization> <RegisteredOwner>Name Here</RegisteredOwner> <CopyProfile>true</CopyProfile> <ComputerName>*</ComputerName> </component> </settings> <settings pass="oobeSystem"> <component name="Microsoft-Windows-International-Core" 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"> <InputLocale>en-us</InputLocale> <SystemLocale>en-us</SystemLocale> <UILanguage>en-us</UILanguage> <UserLocale>en-us</UserLocale> </component> <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> <ProtectYourPC>1</ProtectYourPC> <HideEULAPage>true</HideEULAPage> <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE> <HideOnlineAccountScreens>true</HideOnlineAccountScreens> <HideOEMRegistrationScreen>true</HideOEMRegistrationScreen> <HideLocalAccountScreen>false</HideLocalAccountScreen> </OOBE> <UserAccounts> <AdministratorPassword> <Value>pw_here</Value> <PlainText>false</PlainText> </AdministratorPassword> <LocalAccounts> <LocalAccount wcm:action="add"> <Password> <Value>pw_here</Value> <PlainText>false</PlainText> </Password> <Name>Administrator</Name> <Group>Administrators</Group> <DisplayName>Administrator</DisplayName> <Description>Local Administrator</Description> </LocalAccount> </LocalAccounts> </UserAccounts> <VisualEffects> <FontSmoothing>ClearType</FontSmoothing> </VisualEffects> <RegisteredOrganization>Name</RegisteredOrganization> <RegisteredOwner>Name</RegisteredOwner> <TimeZone>Eastern Standard Time</TimeZone> <AutoLogon> <Password> <Value>pw_here</Value> <PlainText>false</PlainText> </Password> <Enabled>true</Enabled> <LogonCount>1</LogonCount> <Username>administrator</Username> </AutoLogon> </component> </settings> <cpi:offlineImage cpi:source="wim:c:/users/laner/desktop/windows%2010%20deployment/sw_dvd5_win_edu_10_1511.1_64bit_english_mlf_x20-93836/sources/install.wim#Windows 10 Education VL" xmlns:cpi="urn:schemas-microsoft-com:cpi" /> </unattend>
Windows 10 for Education x64.
-
RE: Windows 10 Client 0.11.4 Windows Service
@x23piracy I’m not using OEM. I’m using a KMS key - Windows 10 x64 for Education. I had no issue with the same setupcomplete.cmd and unattend file with 0.11.2. After upgrading to the RC’s, it began to give me issues.
-
RE: Windows 10 Client 0.11.4 Windows Service
Cross posting here:
https://forums.fogproject.org/topic/8206/0-11-4-rc4-ad-question/
Same issue I’m having. You marked it as solved, I’m assuming you just set the service to start as delayed prior to sysprepping and that solved it?