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
X
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
Jeffin Joy
Past 24 Hours:
0
Prev. 24 Hours:
1
Overall:
4988
People Online:
Visitors:
78
Members:
0
Total:
78
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
X
Please
login
to post a reply.
1 Replies
0
Subscribed to this topic
13 Subscribed to this forum
Sort:
Oldest First
Most Recent First
Author
Messages
R. Ahern
New Member
Posts: 2
10/26/2012 7:57 PM
X
Roger French
Veteran Member
Posts: 549
New Poster
Congrats on posting!
10/29/2012 4:08 AM
Split
You say you installed it using your existing LDAP Tivoli? On Windows?
I don't think that is correct. When you mention Tivoli, do you really mean the S3 applications that LSO will ultimately connect to? When you finally install LSO, you can 'connect' LSO with your S3 applications using the Grid Extensions, and it sounds like it's those S3 applications which use Tivoli. So ultimately, when you log on to LSO, you use the same ID and password you use to log on to your S3 applications.
When you install LCM on a Windows server, you should install LCM and LSO with an account that has full administrative privileges and rights. You should also ensure that the account that you use for the LCM Service has the security policy to Log on as a Service.
Please
login
to post a reply.