Login
Register
Search
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Forums
User Experience
Lawson Smart Office
LSO and Windows Roaming Profiles
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
Taha Kidwai
Past 24 Hours:
0
Prev. 24 Hours:
0
Overall:
4992
People Online:
Visitors:
62
Members:
0
Total:
62
Online Now:
New Topics
Top Forum Posters
Name
Points
Greg Moeller
4184
David Williams
3349
Kat V
2984
Woozy
1973
Jimmy Chiu
1883
Kwane McNeal
1437
Ragu Raghavan
1377
Roger French
1315
mark.cook
1244
Chris Martin
825
Forums
Filtered Topics
Unanswered
Unresolved
Active Topics
Most Liked
Most Replies
Search Forums
Advanced Search
Prev
Next
Forums
User Experience
Lawson Smart Office
LSO and Windows Roaming Profiles
Please
login
to post a reply.
3 Replies
0
Subscribed to this topic
13 Subscribed to this forum
Sort:
Oldest First
Most Recent First
Author
Messages
JimMNH
Veteran Member
Posts: 60
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/LawsonClient.application?server=https://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
New Poster
Congrats on posting!
4/5/2012 12:42 PM
Split
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
New Poster
Congrats on posting!
4/5/2012 12:44 PM
Split
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
4/9/2012 6:22 PM
Split
simply going against the .application file with a URL shortcut
http://{
server
}:19005/LSO/...on?server=
https://{server}:19006
Please
login
to post a reply.