Honored Contributor
Honored ContributorThanks for the reply - it had to be a silent installation because it is to be installed to a large number of computers on our network - we simply do not have the resources to manually install each application to each PC.
I think i have a work around though - it seems that it was the system account which was causing the problem, I changed the install script to create a local user account, used that account to install the software, then remove the account. It now seems ok, I assume that it doesn't like the system account as it may be trying to create folders in the users documents or application data folders. Finalising the testing at the moment but so far, it's looking much better than before :-)
