Desktop Manager Hook 2.7b1

• 

  Permanently deleted user

  • February 15, 2011 14:23

  Bonjour, merci de cette annonce, pourriez vous m'indiquer comment télécharger cette mise à jour ?

  0

  Comment actions Permalink
• 

  Permanently deleted user

  • February 15, 2011 14:46

  http://extranet.cooperteam.com/SoftDelivery/Download/20110214/DskMgrDeliveryHook27b1.zip

  0

  Comment actions Permalink
• 

  Permanently deleted user

  • March 23, 2011 04:37

  Thanks very much John.

  I assume that, to install this hook, we simply remove the existing "Hook" document from DM and copy in this document and then refresh the reference document?

  Will the clients then simply update themselves with the new binary?

  0

  Comment actions Permalink
• 

  Permanently deleted user

  • March 23, 2011 11:50

  Dear Terry,

   

  do not forget also to change the version number when you upload the new file, otherwise it will not work and the clients do not get the update!

   

  Best regards,

  Susanne

  0

  Comment actions Permalink
• 

  Permanently deleted user

  • March 23, 2011 12:09

  Hi Suzanne,

   

  Can I just ask for clarification (sorry if I didn't understand at first)?

  By copying the new "Hook" document from the downloaded database and pasting it into our DM database (after first removing the original "Hook" document), we need to change the version number on that new "Hook" document? We need to change it to suit the other Binary documents in the "Install Files" view (2.7a)? Or do we change the version associated with the other Binary documents to suit the new "Hook" document (2.7b1)?

   

  I'm not sure what exactly needs to be changed.  Cheers!  T.

  0

  Comment actions Permalink
• 

  John

  • March 23, 2011 12:27

  Hello,

  Please, let me moderate this discussion : How to install and deploy new Desktop Manager component ?

  • You downloaded a new version of one of the 5 Desktop Manager component.
    
  • Open your current Desktop Manager database, update the binary as below :

  1. Open the document Desktop Manager component document
  2. Edit the document
  3. Delete the current component attached in the document
  4. Attach the new version of the component (that you saved temporary in your local workstation)
  5. update the VERSION field to 2.7b1
  6. check that the Reference document is showing the new version of this particular component.

  Remark : Terry's solution (delete and copy/paste the component document) is not recommended. I don't say that it's doesn't work, but I think it more risky (in term of mistake, like leaving 2 Desktop Manager Hook documents, or creating replication conflict).

  When the new component is applied ?
  
  If the Setup documents have activated (from the second tab "Product Installation") the Option "Update DskMgr Dll and Exe", then, on the next synchronization (or execution), the new binary will be extracted and replaced on the user's workstation.

  At last, if you want to do it safely, you can also update temporary the ACL of Desktop Manager database, to disallow end-user to access the Desktop Manager database while you update Desktop Manager components.

  hope this helps,

  0

  Comment actions Permalink
• 

  Permanently deleted user

  • March 23, 2011 12:30

  Thanks very much John - I understand now.  Cheers!  T.

  0

  Comment actions Permalink
• 

  Permanently deleted user

  • March 23, 2011 12:43

  Thank you, John! A very detailed and clear explanation!

  0

  Comment actions Permalink

Please sign in to leave a comment.