Prev
Next
Forums User Experience Lawson Smart Office

LSO and Windows Roaming Profiles

 3 Replies
 0 Subscribed to this topic
 11 Subscribed to this forum
Sort:
Author
Messages
JimMNH
Veteran Member
Posts: 60
Veteran Member
4/3/2012 8:27 PM
    We've recently encountered an issue with using LSO on client machines using Windows Roaming Profiles.  LSO is deployed as a Microsoft ClickOnce application which both Microsoft and now Lawson support states does not work with Windows Roaming Profiles (Lawson is to update their client requirements documentation for LSO because of this ticket).  ClickOnce does put LSO data and binaries in an area which is not picked up by Windows Roaming Profiles.  This is true for both LSO 9 and 10.  The workaround I devised is basically to substitute the default shortcut for a URL shortcut that goes directly to the .application file on the LSO server so the client first checks to see if ClickOnce pieces are needed, downloads them if needed, then launches LSO.  Since this is done in the user context administrator privs are not needed for this install if run.  If the pieces are there already the client simply launches LSO.     http://serverURL:port/LSO...tps://serverURL:port   This still creates a delay of roughly a minute for some of our Windows Roaming users as this install must happen at first login at the beginning of their day.  Anyone else devised a better solution for this?
    Massimo Emilione
    Advanced Member
    Posts: 29
    Advanced Member
    4/5/2012 12:42 PM
      Jim,

      We;ve been working closely with LSO and Matt Allbee at Lawson and have brought this up on Monday. We have been working through this issue for 2 weeks now with them as we just rolled out our first windows 7 pc with the new roaming profiles policy. It seems funny that it is coincidence that they sent out that article. Lawson has stated the issue is not with LSO but with Microsoft's deployment of the presentation foundation product. Which is pretty funny since they started the roaming profile on Win7. We have pushed the topic to Matt but I am sure it will be some time before it is resolved. In the meantime we are working with our helpdesk to go around the roaming profile in our own network until it is resolved. Our Helpdesk has asked us to use the MSI method, but i do not feel comfortable with that method due to lack of support of a non standard deployment of a lawson product.

      Mark Cook and myself will be attending Inforum and will be bringing a full list of things that we have address with Matt Allbee. Will you be attending?
      Massimo Emilione
      Advanced Member
      Posts: 29
      Advanced Member
      4/5/2012 12:44 PM
        what is the entire url, for some reason it is getting cut off. I would like to test your method out.
        JimMNH
        Veteran Member
        Posts: 60
        Veteran Member
        4/9/2012 6:22 PM
          simply going against the .application file with a URL shortcut
          http://{server}:19005/LSO/LawsonClient.application?server=https://{server}:19006https://{server}:19006