Sign in
 
Home2012Previous VersionsLibraryForumsGallery
System Center TechCenter >
> 
> 
Software Package Says It's Installed but Not Showing Up on Workstation

Answered Software Package Says It's Installed but Not Showing Up on Workstation

  • Sunday, April 10, 2011 7:43 PM
     
     
    Sign In to Vote
    0

    Ok, this is my first attempt at creating and installing a software deployment package and this is what's happening:

    I have a test workstation running Windows 7 Professional SP1 that I'm trying to deploy the package to.  I created the package just fine which in this test it's Adobe Acrobat 9 Professional.  It's an .exe file instead of a .msi in case that matters.

    I selected the option to deploy/install the application with a set deadline.  On the workstation, I ran wuauclt /detectnow to see that it showed up fine which it did.  Windows Update then asked if I wanted to download this update like any other and I clicked "Cancel" instead of "OK" because I didn't want to do this.  I want to be able to deploy a package and have it install on it's own.

    Now, when I check the workstation via SCE 2010 Console and run the Software Deployment Status it shows that status is "Installed" and Approved on 4/7/10 at 8:02 pm which is when I ran the task.  When I check the workstation the application hasn't installed, it's not showing up in Add/Remove programs regardless if I'm logged in as a domain admin or a local admin.  I know it's not suppose to show up in Add/Remove unless I publish it but I've tried going back and changing it to this option and it still doesn't show up.

    http://screencast.com/t/ZGJ4dSESv

    When I go to the Software section of the console it shows that the application was successfully deployed and it shows that it's been approved for installation successfully.

    http://screencast.com/t/LF6kiiD7PYi

    Can anyone tell me what's going on? What did I do wrong? What to do to reset this and try again to accomplish what I want?

     


     

All Replies

  • Tuesday, April 12, 2011 10:37 AM
    Moderator
     
     Answered
    Sign In to Vote
    1

    Hello,

    This behaviour is by design. You did nothing wrong.

    You have approved the software package to the managed computer and the local administrator on the computer detected and downloaded the software package. The deployment status will be unsuccessful only if the local adminstrator accepted the installation but the installation failed. It is successful even the local administrator canceled the installation.

    You have canceled the installation, so the software was not installed on the managed computer. I'm sure you cannot find it on the managed computer.

    To install a program silently, you should use the paticular install parameter for the program. For example, it could be /qn or /quiet. When you creating the software package, input the paramenters in the Installation Properties.

    Thanks,

    Yog Li -- Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
     
  • Wednesday, April 13, 2011 4:59 PM
     
     
    Sign In to Vote
    0

    Ok, I'm a bit confused on what you've said.  You first said "The deployment status will be unsuccessful only if the local adminstrator accepted the installation but the installation failed.  It is successful even the local administrator canceled the installation."

    So, since I'm the Administrator that logged into the workstation and saw that it was offered as an update but cancelled instead of clicking OK.  You're saying that the install was still successful?

    But...

    You then said "You have canceled the installation, so the software was not installed on the managed computer.  I'm sure you cannot find it on the managed computer."

    That is correct, I did cancel the installation, so why did you say that it was installed successfully anyway on your previous statement?  You're correct again, the managed computer does not have the application installed since I can't find it anywhere.

    So, are you saying that in order to install it successfully I have to re-deploy it and accept the install via Windows Update? or use a silent parameter when I re-deploy it if I want that option?

    Is that about right?

    Also, if I re-deploy it and select a set deadline and do not force the install using wuauclt /detectnow or updatenow it should install based on the schedule I have set in my Group Policy correct? If I want this to happen this way will it work even if I don't use a "silent" parameter or must I use that in order to accomplish the application installing automatically?

    I want to basically install this or any application without having any user intervention.  I just want them to log onto their workstations and see that the application is installed.

    Thanks for your help


     
  • Friday, April 22, 2011 12:05 PM
    Moderator
     
     
    Sign In to Vote
    0

    Hello,

    When I say "It is successful", I mean the SCE server successfully transfered the software package to the managed computer. It doesn't mean the software has been installed on the managed computer successfully.

    By default, managed computers contact the SCE server to check for updates approximately every 22 hours. You can choose to install the update manually with notification or automatically with schedule time in the setting of “Configure Automatic Setting” within the Group Policy Setting.

    1. If the deadline is set after the next scheduled installation time, the update will be installed normally according the schedule.

    2. If the update is not installed successfully at the previous schedule time, it will be installed mandatory at next detection time If the deadline is after the scheduled installation time but before the next detection time.

    For example, the update has been approved at 0:00 AM, as a result, that the client should contact the server before 22:00 (due to the default 22 hour frequency).

    Also, let’s assume that the scheduled installation time is 22:30 every day, and the deadline was previously set to 23:00 on that day. 

    At 22:00, the managed computer contacts the SCE server, detects the update and downloads it. However, it will installs the update at 22:30, according to the installation schedule specified in group policy. 

    After downloading the update, if there is some problem with installation (such as the client is shutdown), the update will be installed mandatory at next detection time, at 20:00 next day (another 22 hours after the last detection). 

    Here is some information for you reference to set deadline: 

     1. Approve that update at least 1 day before the deadline time (to ensure that the client computers can get information regarding the new update from the SCE server within the 22 hours).

     2. An appropriate deadline time is configured.

     3. Ensure the client computer is online to get the approval and deadline information of the new update from the SCE server. 

    Please note that we can also run “wuauclt /detectnow” to force the client computer to detect the updates immediately, instead of waiting for 22 hours. 

    Hope it helps.

    Yog Li -- Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
     
  • Friday, May 06, 2011 9:31 PM
     
     
    Sign In to Vote
    0

    Yog Li,

    Ok, I think I'm following you here but I'm not 100% sure.  So, to avoid further confusion on my part let's just say that I want to start this process over from scratch.

    How do I go about doing this? Do I simply go back into the SCE console and do what I did in the beginning meaning...I approve the install again, chose a specific time, use the wuauclt /detectnow, but this time click "OK" to install on the Windows Update window rather than cancel like I did last time?

    I have my group policy schedule set for 3 AM on Wednesdays, but as I'm testing the deployment of an application I do not want to wait until that time obviously.

    Here is a scenario of what I want to do:

    1. Deploy this task during normal business hours

    2. Force it to install during this time and not at 3 AM by using wuauclt /detectnow as described above

    That's it, this is all I'm trying to accomplish.