locked
Deploying F-secure in TS RRS feed

  • Question

  • Hi

    I am having problems when installing F-secure 9.01 client in task sequence. Simply to tell...it wont restart the machine.

    I run the msi package with command /quiet /forcerestart (works fine on windows).
    I have also chosen from the program properties "After running" both program restarts computer and Configmanager restarts the computer.

    None of those seem to work. CM logs just say that F-secure installation has finished and the installation is now waiting some...kind of ...interaction from the user.

    So any tips and tricks anyone? :)

    thanks!

     

     

    Thursday, May 27, 2010 4:49 AM

Answers

  • Ah ok, you need to click the box that says something like  "Allow Restart outside of maintenance window" so it will restart when it is finished and not wait for MW.  Otherwise it will wait for the windows which is what you don't want.
    http://www.sccm-tools.com http://sms-hints-tricks.blogspot.com
    • Proposed as answer by Robinson Zhang Tuesday, June 1, 2010 2:41 AM
    • Marked as answer by gncd Tuesday, June 1, 2010 9:00 AM
    Tuesday, June 1, 2010 1:35 AM

All replies

  • Remove the /forcerestart parameter (see http://technet.microsoft.com/en-us/library/bb632898.aspx and search for 3010) and use a task sequence step that restarts the computer.
    Thursday, May 27, 2010 6:40 AM
  • Also do you have a Maintenance window blocking the application from restarting?
    http://www.sccm-tools.com http://sms-hints-tricks.blogspot.com
    Thursday, May 27, 2010 1:27 PM
  • You could restart the computer by using a TS.
    Friday, May 28, 2010 2:22 AM
  • You could restart the computer by using a TS.

    Do you mean TS task sequence?

    Well I have tried also to do task sequence step that would tell that I need restart now. This just wont work because the Installation finishes up and starts to wait something.

     

    Here is CM status message about the situation.

    The program for advertisement "CM12009E" ("CM1000C9" - "F-secure 9.01") returned an exit code of "1641"(""), which indicates the operation was successful but a restart of the system is required for the operation to be complete. A restart might be pending because there is no maintenance window open. The restart will occur at the next available maintenance window. A status message indicating final success will be sent after the system has been restarted.

    Systems Management Server (SMS) determines status for each program it executes. Any program dependencies will not be executed until after the restart occurs. If SMS cannot find or correlate any installation status Management Information Format (MIF) files for the program, it uses the program's exit code to determine status.

    Monday, May 31, 2010 1:22 PM
  • Ah ok, you need to click the box that says something like  "Allow Restart outside of maintenance window" so it will restart when it is finished and not wait for MW.  Otherwise it will wait for the windows which is what you don't want.
    http://www.sccm-tools.com http://sms-hints-tricks.blogspot.com
    • Proposed as answer by Robinson Zhang Tuesday, June 1, 2010 2:41 AM
    • Marked as answer by gncd Tuesday, June 1, 2010 9:00 AM
    Tuesday, June 1, 2010 1:35 AM
  • This actually looks good. I can't test it right now. But I consider this as a solved case.

    Thank you! :)

    Tuesday, June 1, 2010 9:00 AM
  • Have the same problem, F-secure is the last bit in the operating system deployment TS. After F-secure has been installed it restarts once, but then it opens a new TS saying that it want's to configure Configmgr client and the background is saying "Setup is preparing computer for the first use" or so, the thing it says when it first boots to dropped OS. And then it just is there, hours, days after the Config mgr configuration message disappears or finishes. If I press F8 I can get a command prompt and shutdown the machine from there cleanly, otherwise hard reset does the trick. After that, the machine seems to be ok, but in the SCCM Console the Computer object is not Obsolete!

    Where to start debugging this? Windows 7 64-bit, F-Secure 9.01, SCCM 2007SP2 R2.

    Wednesday, June 23, 2010 3:20 PM