jaybird283 wrote:
Well.. I thought about the same thing. first of all. Seeding it in the default user profile wouldn't help in this situation since it would only apply to new users who log into the computers, not users that have already logged on before.
I am well aware of that hence it was the second part of my previous reply as I emphatically stated "and also while you're at it seed it under the Default User's Account so any newly created Accounts will automatically have the file present! "! 
I could create a startup script or a user based domain policy that applies the preferences.ini each time a user logs on. but I decided that it wasn't worth the time. Users are familiar with EULA's and I am not worried that they will screw that step up.
Yes I would not do a login script for this either however during to process of the initial install there is no good reason why a scripted solution cannot be implemented that enumerates the existing User Accounts on that system and copy/create the preferences.ini file under each existing account. Well I guess a good reason would be you don't know how to do it however depending on how many systems you need to install the product on it may not be worth you're time to implement the additional coding especially if you have to learn it on the fly.