Reply To: Task sequence UI import from ini file

  • Roddy Gelberty

    Member
    10 July 2020 at 1:59 am

    Sure Paul,
    Please find the fields example from one of the INI file, the information which goes in
    to these ini files like Store Address, IP address these information is
    only available to enter by field technician at the time of Deployment.
    [General]store_number =00000address =city =Some CityCountry =USProvince =N/Acontact =Store Managertype =Cpetrol =0timezone =GMTdaylight =1remarks =cc_connect_type =4credit =1market =0000

    Three .ini files have fields like above, the information which goes in to these ini files like Store Address, IP address these information is only available to enter by field technician at the time of Deployment, once these .ini files are saved with updated information to C:\Store directory on 2016 hyper-v server, we have power shell scripts in place which will inject these .ini files to VM.

DCOM hardening issue.

This application fails to authenticate with WMI on the SCCM server because Microsoft has not yet hardened DCOM on their Windows Preinstallation Environment. We are working on a different approach, but it will only be released during the first quarter of 2024. But until that time, the only workaround will be to uninstall the update corresponding to KB5004442.