Hi. I know this thread is several months old, but the topic is very current to me, as I'm wrestling with the same design choices now. And, a thought occurred to me that may allow the initial asker of this question to achieve the desired results. (And, if my idea is flawed, then at least I will learn something :-)...
My idea is this: On each of the clients, you create a "one-time" app that has the deploymentclient.conf, which allows the client to make the initial contact with the Deployment Server. However, the key idea is this: The Deployment Server does know about this app - this app is always on the Deployment Server, and it is always EMPTY. Thus, the first time the deployment client phones home, that "one-time" app is deleted because it doesn't match the deployment server's version of this app. Of course, the deployment server must give the client a new app which provides a new version of deploymentclient.conf, that now is managed by the deployment server.
Would this give the asker what is desired? If not, where have I fallen down?
Thx!
mfeeny1
... View more