I thought about that... using an ini file or similar as the host and then just let the clients "go fetch", but how much resources will 1500 PC polling for a file across a WAN use, when they check every 15 minutes for an updated message.
I was thinking that it would be less resource intensive to push the text file to the machine... when installing the client, create a hidden share. Then the admin tool could ping, check for share, then copy. The client would look every 5 minutes for a file, read it then delete it.
Personally, I wouldn't worry as much if I could use a DFS share, but the netadmin refuse to do set one up.
