I.P.

happy new year paul
 
i knew you would say that, you missed my major point. of course you can bundle different products for marketing purposes, microsoft also sells powerpoint and access in a bundle wich has nothing to do with each other.
 
but there is an access development team not really interacting with the powerpoint development team and both creating a product where access could become an excellent product and powerpoint a very poor piece of software. if they create a poweraccesspoint it would be a poor product overall and the market for access is open for an other solution on the market that focusses it better.

i don't think so in general. pc monitor should not loose its focus and not try to become a "PC Everything" instead of pc monitor. don't get me wrong, a remote screen control would be a great feature to pc monitor but it is not what the original architecture of pc monitor provides, a data stream from client to agent.

but providing this it _must_ be more expensive and becomes less secure.

yes, but claiming a motto does not change the world

managing does not neccessarily mean full screen access. i do not only think but i am sure that "adding everything" can make a product lose its focus and simplicity. there are monitoring solutions out there that have a much bigger funcionality range than pc monitor but can be outperformed by pc monitor by simplicity and ease of use.

if remote access can be provided without losing the push-architecture and without making the whole product more expensive i will welcome it, i only have doubts that this is possible without negative impacts.

yes, a data stream is the only way to achieve a good remote control, i am sure with that. of course not direct, i didn't say that. but especially when managing a data stream over the enterprise server for instance causes many traffic issues and although this all can be solved it must make the product more expensive for the end user.

We will add an option in the PC Monitor Admin app to use your own salting parameter. It will then be combined with your server Url to make it unique for each Enterprise Server instance.

cloud api is definitely the key for integration with other monitoring systems or applications. for me it has much more potential than pc monitor plugins. i have not done much .NET development so far and nearly no C# but when i can get productive results on the first day it is a good sign

just finished my first .NET Cloud API application. a cloud instance named WorldAgent that is fired from a web-application which allows other monitoring systems like nagios creating http-calls that end as a pc monitor notification visible in all pc monitor clients

the nagios apps just call http:// {myenterpriseserver/wa/?message=the_message&priority={normal|elevated|critical}&code={auth-code} and the notification is fired. there is no need to wait for the http answer so it can be implemented nearly everywhere. an easy to use API to use and sell the excellent pc monitor clients to clients that already have set up other monitoring systems and do not want to throw them

i do not agree completely. yes, the hash represents my password but i can only use it with authentication api's that allow using the hash and not everywhere, for instance at the web app or in the mobile apps. but when someone has my real password he can use it everywhere.

my idea was to accept the hash as logon password only with machanisms where an automated login is required, not everywhere. the Cloud API is such a thing.

but the facts are clear now that marius explained so i will use an alternative.

by the way, paul, i have read many of your posts in here and i thought many times this guy is a genious in really understanding the things. keep on!

We plan to add it