Open remkolansaat opened 3 years ago
Is it possible to stop ccmexec before launching bisf to avoid the problem above , or will bisf then decide that preperation of sscm is not avaible due to stopped service?
fixed in developer branch
Great job, thanks
Reopen issue, some customer have issue again. SCCM service is not stopped.
ok goodluck if you have new code I am happy to test it ...
my workaround is to set ccmexec to manual before final reboot of sccm taskseqeuence deployment
received from another customer today
think I found the problem with the SCCM client. With the BIS-F you should also set the start type of the SCCM service to "Manual". With us it was set to "Automatic (delayed)". I also learned that if you delete the settings when sealing and the machine shuts down despite the service being stopped, a smscfg.ini is created in the Windows folder (whatever). That's why you delete the settings again when you personalize. But when the service is already running, it comes to mess. And the start of the service by BIS-F makes no sense, because it is already running. I set the service to manual and now it looks good
I suspect this changed created issue 313. I've added notes under issue 313 to explain why.
Thanks Jerermy, here is the direct link to issue 313 for all others https://github.com/EUCweb/BIS-F/issues/313
regards
Matthias
Am 7. Sept. 2023, 04:25 +0200 schrieb Jeremy Saunders @.***>:
I suspect this changed created issue 313. I've added notes under issue 313 to explain why. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you modified the open/close state.Message ID: @.***>
Hello, when sealing bisf step "10_PrepBISF_SCCM" hangs on stopping sccm client service : Invoke-BISFService -ServiceName $appService -Action Stop It seems that the function waits for ever , the sccm agents is not responding and the service status is stopping... and stays at stoppings for ever.
Solution request : It would be great if the function will kill ccmexec.exe after a timeout of 5 min
The problem is a sccm agent not responding on stop command , so its not really a bisf bug ....