locked
Software Deployment - Intermittent problems RRS feed

  • Question

  • Hello - I just start using SCE in a test environment.  We have been looking for a solution for Hyper V management as well as simple software deployment.  On the software deployment side, things aren't going very well.  I have two managed windows clients - and the certificate and group policy settings seem to be good.  While trying to deploy several different packages, they fail intermittently.  One machine is a Windows 7 client, the other XP SP3.  It is very inconsistent:  sometimes the software install will work for the Windows 7, sometimes XP and vice versa.  When it doesn't seem to work, I don't notice blatant error messages in the WindowsUpdate log.  It will report as unknown, or downloaded but not installed. 

    Where should I start with this? It's been quite frustrating. 

     

    Thanks in advance,

     

    Andrew

    Tuesday, June 28, 2011 7:32 PM

Answers

  • Hello Andrew,

    To resolve the unknown atatus error, you can try these steps:

    1.Check whether these software package list in the folder \UpdateSrervicePackages\
     
    2. Check whether UpdateSrervicePackages directory has the following permission:
     
      a. Full control to WSUS Administrators group.
      b. Read/write access for the NetworkService account
      c. Read access for Everyone.
     
    3.Check "c:\windows\software distribution\Download" on client compputer to see whether software package has been download.
     
    4. Check whether "Configure Automatic Update" has been modified.
     
    5. Please clearing the BITs queue on the problematical computer:

    To clear the BITs queue, you can use the steps outlined in the following:

    You cannot download new updates from a server that is running Windows Server Update Services
    http://support.microsoft.com/default.aspx?scid=kb;EN-US;920649
     
    6. Please follow the below steps to force client computer to find software package.
     
    1). On a “Unknown” client, stop the Automatic Update service via services.msc.

    2). Rename the windowsupdate.log (under %windir%) to windowsupdate1.log, and then start the Automatic Update service.

    3). Run “wuauclt /detectnow” command.

    4). Wait for 10 minutes and then run “wuauclt /reportnow” command.

    5). We will get a new %windir%\windowsupdate.log file. Please check if any error message will be logged.

    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.
    • Marked as answer by Yog Li Wednesday, July 6, 2011 11:19 AM
    Thursday, June 30, 2011 11:23 AM

All replies

  • Hello Andrew,

    To resolve the unknown atatus error, you can try these steps:

    1.Check whether these software package list in the folder \UpdateSrervicePackages\
     
    2. Check whether UpdateSrervicePackages directory has the following permission:
     
      a. Full control to WSUS Administrators group.
      b. Read/write access for the NetworkService account
      c. Read access for Everyone.
     
    3.Check "c:\windows\software distribution\Download" on client compputer to see whether software package has been download.
     
    4. Check whether "Configure Automatic Update" has been modified.
     
    5. Please clearing the BITs queue on the problematical computer:

    To clear the BITs queue, you can use the steps outlined in the following:

    You cannot download new updates from a server that is running Windows Server Update Services
    http://support.microsoft.com/default.aspx?scid=kb;EN-US;920649
     
    6. Please follow the below steps to force client computer to find software package.
     
    1). On a “Unknown” client, stop the Automatic Update service via services.msc.

    2). Rename the windowsupdate.log (under %windir%) to windowsupdate1.log, and then start the Automatic Update service.

    3). Run “wuauclt /detectnow” command.

    4). Wait for 10 minutes and then run “wuauclt /reportnow” command.

    5). We will get a new %windir%\windowsupdate.log file. Please check if any error message will be logged.

    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.
    • Marked as answer by Yog Li Wednesday, July 6, 2011 11:19 AM
    Thursday, June 30, 2011 11:23 AM
  • Hi Andrew,

    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 -- 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, July 6, 2011 11:19 AM