Jump to content


GarthMJ

Moderators
  • Posts

    1,939
  • Joined

  • Last visited

  • Days Won

    92

Posts posted by GarthMJ

  1. I know that you don't like the answer but in a nutshell, it is right. Think about it. 

    How does a CM client know that there are new source files? At a high level, the processes is a follows.

    1. Source Files are updated.
    2. CM is told to update source files
    3. CM creates the package for replication.
    4. CM update the source version within db.
    5. CM create a policy stating there is a new version for package x.
    6. DP are told to update source files
    7. DP actually get new source files. 
    8. CM update the source version within db.
    9. Client contact MP and for all policies
    10. All policies are evaluated
    11. Client run package x, notices that it's version does not match package x
    12. Client downloads new source files
    13. Client run package x.

    If client do not see the latest version of the package then something is wrong in step 1-4. Once step 5 happens, all clients will wait for the newest source files to be on their DP once the policies are evaluated.

     

     

     

     

  2. 2 hours ago, Kingskawn said:

    I did the testing with a logged admin and running psexec -i -s cmd. I launched the command as in the command line of the TS:

    "Windows_Application\install_acs_64_allusers.js" /Q
    This doens't work when OSD is used. I think the software is failed (in the TS) because it doesn't finish in time. We now will use the app deployment toolkit to have a better control and logging. Maybe we discover something new.

     

    4

    And exactly what happened when you ran the Psexec command? Did you try trying the cmd using the 32bit cmd too? 

    It is easy to prove the timeout as it will show within the logs that the install timed out.

     

  3. 5 hours ago, Kingskawn said:

    Hi Marlew, did you find a solution on your question? We have ACS too and deployment of the package is working but through OSD it doesn't. The JS file which is used to install all the rest is calling other scripts.
    I'll try launching it with the system account

     

    And what happens when you run it with the local system account?

    Have you contacted IBM about this yet? 

  4. Is there a reason why are you are not using email subscriptions? 

    To answer your question, it will depend on how you setup SSRS, as to what rights are needed by SSRS to create a file subscription. in a nutshell, give SSRS full file and share rights. the users will only need read rights. 

  5. Tip, when posted log, post the whole log file and not a screenshot, The text is too small to read. 

    You either have a problem with your detection method OR your install is spawning another thread on the computer which completes after the detection occurs. In either case, you need to figure out what is going on and fix it. 

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.