Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 5 subscribers
  • Views 9386 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Custom POACFG File doesnt apply during installation

dooty22

i have an issue with a lenovo laptop which requires a hotkey F6 before its operable. This needs to be automated as I cant have someone doing this hotkey routine everytime a laptop gets imaged.

I got one laptop working using the hotkey "shift-F6", run the sgnhwinfo tool to gather the xml config, copied the config into the standard poacfg.xml file (using an xml editor yes) , copied this into my package (same directory as the msi) and then run the following to install

msiexec /i SGNClient.msi /qn ADDLOCAL=Client,Authentication,CredentialProvider,BaseEncryption,SectorBasedEncryption POACFG=POACFG.xml REBOOT=ReallySuppress

The install completes with no errors, but the POACFG file seems to be ignored, the laptop is unbootable without the hotkey operation again, and the poacfg placed into c:\program files does not include my changes.

Am i missing something ??

thanks

:51594


This thread was automatically locked due to age.
  • 0

    You need to specify the full path of your poacfg.xml file in POACFG parameter.

    e.g. POACFG=C:\temp\POACFG.xml

    :51610
  • 0

    In my experience you will not get an error running this command even if something goes wrong.

    You can produce a verbose log file which will tell you whether each step was successful.

    You need to use the /l*v switch followed by a file path.

    So in your example it could be msiexec /i SGNClient.msi /qn ADDLOCAL=Client,Authentication,CredentialProvider,BaseEncryption,SectorBasedEncryption POACFG=c:\POACFG.xml REBOOT=ReallySuppress c:\Sophos-Install.log

    :51616
  • 0

    Yes, I think the fact the msi doesnt error out or report any issue threw me a bit.

    But I tested as advised putting in the whole path into my sccm task sequence step and this seems to be working (ie the POA is no longer just locking up the job post install)

    thanks for the responses

    :51646
Unfiltered HTML