Ok.
In my case we do not use MDT.
Just personnalize Windows 10 image , sysprep, and upload on FOG.
In our FOG post install script this modify the unattend.xml to set computer name in reference with FOG before windows 10 boot.
Until now for Windows 7, Windows 10 1709 this work fine.
Hi,
I have problem to set computer name with sysprep with Windows 10 1803 (before with Windows 10 1709 it worked).
Windows generate random name WIN-xxxx insteasd of my name what i set in my sysprep response file XML
<ComputerName>UCXXXX</ComputerName>
I don’t understand because domain joined works
With the log of sysprep i juste see this but no info to resolve this :
2018-05-17 17:27:56, Info [0x060258] IBS GenerateName: Failed to read the Key UserData\FullName\Value from Blackboard defaulting to WIN
2018-05-17 17:27:56, Info [0x060259] IBS GenerateName: Failed to read the Key UserData\OrgName\Value from Blackboard
2018-05-17 17:27:56, Info [0x06025d] IBS Callback_ComputerName_Validate:Computer name is WIN-RSBIBOU3CAD
2018-05-17 17:27:56, Info [0x06025a] IBS Callback_ComputerName_Generate:Computer name [WIN-RSBIBOU3CAD] is valid.
2018-05-17 17:27:56, Info [setup.exe] OrchestrateSetComputerNameOnline: Set the computer name to WIN-RSBIBOU3CAD
Have you succeeded to sysprep new Windows 10 1803 with personnalize computer name ?
If yes how you do this ?
Regards.
Hi,
If i have 10 computers with a power management identical for all machines, it would be nice to see the schedule in section power management of a group.
Currently we see nothing.
Regards.
Hi,
Since FOG 1.5.0 in “power management” section when i add a task this not display what i add in the page (test with Firefox 58 and Chromiym 64).
This need complete refresh of the page to see the adding.
Idem to delete an existent.
Not blocking.
Regards.
@Tom-Elliott
Hi,
It’s ok but just a detail in fog.log we no longer see the list of shutdown/reboot which are programmed.
Have a good day.
@Tom-Elliott
Hi,
Thanks.
This problem is linked with scheduled tasks not work or not ?
Because i have checked my php.ini timezone and server and FOG GUI but tasks not launch (timezone Europe/Paris).
Regards.
Hi,
See my capture for this particular host :
Hi,
Since we have migrate to FOG 1.4.2 my computers not reboot as set in power management.
FOG Client version is v0.11.12
In fog.log no tracks just this :
------------------------------------------------------------------------------
--------------------------------PowerManagement-------------------------------
------------------------------------------------------------------------------
14/06/2017 17:14 Client-Info Client Version: 0.11.12
14/06/2017 17:14 Client-Info Client OS: Windows
14/06/2017 17:14 Client-Info Server Version: 1.4.2
14/06/2017 17:14 Middleware::Response Success
14/06/2017 17:14 PowerManagement Calculating tasks to unschedule
14/06/2017 17:14 PowerManagement Calculating tasks to schedule
------------------------------------------------------------------------------
An idea ?
Regards.
@Wayne-Workman
Hi,
Ok i understand.
Actually majority off our classroom reboot at the same time for software update in night (same time is residual effect with green fog on old version).
I will adjust power management (good amelioration in this version) for spread out this reboot.
Thanks.
Hi,
Organization Name: Université Rennes 2
Location (Optional) : Rennes, FRANCE
Approximate Number of systems: 2000-2500
How long: Since 2009
Add to this, if you want to be listed publicly on the WIKI, please provide a Logo you’d want used for this.
https://www.univ-rennes2.fr/system/files/UHB/SERVICE-COMMUNICATION/logosur2-png.zip
Hi,
Today it’s better but all the 30 minutes we have pic of 2 minutes.
In wiki it’s write (https://wiki.fogproject.org/wiki/index.php?title=FOG_Client
The frequency of the checkin-time determines how quickly the FOG Client will receive instructions from the FOG Server. If an image deployment is scheduled for a computer that is turned on, with a checkin-time of 60 seconds, means the FOG Client may begin initiating the task anywhere from 0 to 60 seconds + the random staggering time that is added. This same concept would apply to immediate power management tasks, snapin tasks, capture tasks, and so on. Scheduled tasks are not affected by this behavior, and if the target system is on when the scheduled task is to be ran, this will happen on time
How it’s possible to modify the random staggering range for spread over 10 minutes for example ?
Thanks.
@ablohowiak
Oh very thanks it’s works !
I was thinking test this before but maybe not with “imagereplicatorfogenabled” at off.
After few minutes cpu is ok.
Thanks.
@ablohowiak said in 1.3.4 - high cpu load - client login:
So no improvement with imagereplicatorglobalenabled off?
No
With this issue I’ve increase my client communication up to 30 minutes. >I will reduce when I know things have stabilized.
Where you have up to 30 minutes your client communication , “checkin time parameter” ?
@UWPVIOLATOR said in 1.3.4 - high cpu load - client login:
Increased MaxRequestWorkers from 150 to 500 in mpm_prefork_module
Hi,
Where you have put this parameter because i try in my apache2.conf in prefork module but not valid after i restart apache2
@Tom-Elliott Yes imagereplicatorglobalenabled is not checked
@UWPVIOLATOR
Just do this on Web interface / fog settings or after restart apache ?
@Tom-Elliott
Thanks for your response (my english is not very good).
Yes we have high CPU usage since we have deploy the new client (0.11.9) with GPO.
We have try to modify FOG_CLIENT_CHECKIN_TIME but we think value over 60 seconds are no effects.
In our client log we see in general a contact server every 60-200 seconds.
We have more than 1500 clients.
If the problem is here is it possible to modify checkin time to 15 minutes ?
Or if the problem is not this where i can find informations for identify in detail the source of the problem ?
Regards
@Tom-Elliott said in 1.3.4 - high cpu load - client login:
11
Hi,
We have the same problem.
Is this problem is resolved in RC10 ?
Or when RC11 available ?
Regards.
@Sebastian-Roth Ok thanks for your response.
I hope this will be possible in the future.
Or if it’s simple indication so that we can develop it ourselves.