tag:blogger.com,1999:blog-8994561579739999989.post4738838429022137118..comments2024-02-28T10:15:50.335+02:00Comments on Lotus Evangelist: 8.5.3 Machine Specific Policy...Not in the DocsKeith Brookshttp://www.blogger.com/profile/11107190540208956954noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-8994561579739999989.post-36895711009742134402011-10-10T03:09:15.515+02:002011-10-10T03:09:15.515+02:00I have no insight on the API, I'm an admin, th...I have no insight on the API, I'm an admin, the dev talk goes right past me. I should have paid more attention last week on the call. Sorry.<br />Something we have waited for and IBM delivered.Keith Brookshttps://www.blogger.com/profile/11107190540208956954noreply@blogger.comtag:blogger.com,1999:blog-8994561579739999989.post-26319604367093010192011-10-09T20:40:30.800+02:002011-10-09T20:40:30.800+02:00Thank God, I always wondered why there were server...Thank God, I always wondered why there were server configuration documents but no exact PC/Client configuration documents, you never knew what was out there. The client details in the person document could also do with some improvement to help with asset tracking / recording the environment. It would be good to see if this can be used to allow a backend ID file being used by an API call can be locked down to only be used on the intended machineAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-8994561579739999989.post-53519644207620940702011-10-06T20:29:32.986+02:002011-10-06T20:29:32.986+02:00Wow - that's very cool and powerful.Wow - that's very cool and powerful.Anonymousnoreply@blogger.com