locked
Approved software is not deploying RRS feed

  • Question

  • I've created 4 software packages and approved each of them for deployment to a test group. However, they are not being installed.

    Machines 1 and 2 displayed the yellow "updates available" icon in the system tray, and I chose to run the updates right then and get them. However, I left machines 3-5 alone to see if they'd update automatically.

    That was a week ago. All 5 machines seem to be getting updates just fine, but none of them are automatically getting software packages. All machines are identically imaged and have nothing else installed on them. They all show up error-free. Ideas?
    Friday, July 31, 2009 6:06 PM

Answers

  • Hello dgarden,

    From your description, It seems not a problem but the regular function. The installation schedule of the software depends on how you configured the software package, and the settings of Automatic Updates:

    If you set a deadline, the software is automatically installed at the deadline.

    If you configured the package as optional, the software is added to Add or Remove Programs in Control Panel on the managed computer, and the user can install it at any time.

    If you did not set a deadline, and the installation is mandatory (you did not configure it as optional) the installation time depends on how Automatic Updates is configured on the computer:

    • If Automatic Updates is configured to automatically download and install at a certain time, the software installs automatically at that time unless the user has already manually installed it.
    • If Automatic Updates is configured for automatic download and manual install, the user can install the software at any time.
    • If Automatic Updates is configured to notify users about updates, the software is installed immediately upon the user's approval of the notification message.


    Click the link below for more information:

    About Software Deployment in System Center Essentials
    http://technet.microsoft.com/en-us/library/bb422798.aspx

    How to Create a Package and Deploy Software in System Center Essentials
    http://technet.microsoft.com/en-us/library/bb422906.aspx

    Hope it helps,


    Yog Li - MSFT
    • Marked as answer by Yog Li Monday, August 10, 2009 11:48 AM
    Monday, August 3, 2009 8:04 AM

All replies

  • Hello dgarden,

    From your description, It seems not a problem but the regular function. The installation schedule of the software depends on how you configured the software package, and the settings of Automatic Updates:

    If you set a deadline, the software is automatically installed at the deadline.

    If you configured the package as optional, the software is added to Add or Remove Programs in Control Panel on the managed computer, and the user can install it at any time.

    If you did not set a deadline, and the installation is mandatory (you did not configure it as optional) the installation time depends on how Automatic Updates is configured on the computer:

    • If Automatic Updates is configured to automatically download and install at a certain time, the software installs automatically at that time unless the user has already manually installed it.
    • If Automatic Updates is configured for automatic download and manual install, the user can install the software at any time.
    • If Automatic Updates is configured to notify users about updates, the software is installed immediately upon the user's approval of the notification message.


    Click the link below for more information:

    About Software Deployment in System Center Essentials
    http://technet.microsoft.com/en-us/library/bb422798.aspx

    How to Create a Package and Deploy Software in System Center Essentials
    http://technet.microsoft.com/en-us/library/bb422906.aspx

    Hope it helps,


    Yog Li - MSFT
    • Marked as answer by Yog Li Monday, August 10, 2009 11:48 AM
    Monday, August 3, 2009 8:04 AM
  • Hi,

    As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as "Answered" as the previous steps should be helpful for many similar scenarios.

    In addition, we’d love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems.

    Thanks,


    Yog Li - MSFT
    Friday, August 7, 2009 12:17 PM
  • Hello dgarden,


    Our support engineer has been working continuously on this issue. Here are some more questions that will help us to narrow down the source of a problem:
     

    Do you create a new update id, or delete the old update (instead of expiring it), and create the new update with the same update id? In this case you will have a cached update id in a datastore, and might not recognize that this update is actually a new one. That might be why the new update is only applicable after deleting the datastore.

     

    1.       Does this issue occurs immediately after publishing new updates?

    2.       Does it happen every time they publish new updates? Or is it only sometimes new updates make trouble, and sometimes all new updates got installed smoothly?

    3.       Are these only the specific new updates that having trouble to be applicable? Or is it older updates suddenly stopped being applicable too?

    4.       Are these newly published updates supposed to be applicable to all client machines, or only for some of them? and whether these “some” subset of client machines are the ones that experience trouble?

    5.       Are there specific client machines that always having these problems with new updates? (I remember you said there are no specific clients, but please confirm).

     


    Research from the support engineers so far:

    This seems to be an issue with AU agent (atleast at high level)  since looking like  from SCE console it does inform  that the client needs the software but at the client, nothing is detected.  We/WSUS support engineer  have been working with windows update agent product group and per last discussion with him, they feel the customer may have re published an update with the same update ID and that’s why it’s causing this issue. Still investigating the issue


    Possible workaround:

    Try deleting the Datastore.edb file by stopping the update service and then restarting the service. Basically try to stop the AU service on the client that has the problem and then delete the “datastore.edb” file”

     
    Hope it helps,


    Yog Li - MSFT
    Thursday, August 20, 2009 10:48 AM