The default configuration for ColdFusion on a Windows server
is to run
as a service under the 'localsystem' account. This account,
by default,
has *NO* permissions to any network resources.
Your choices are:
To modify the permissions of the localsystem account, but
this is not a
good idea.
OR
You could run the ColdFusion service under an existing
account that has
the required permission, still not a great idea, but ok for
testing
purposes.
OR
The best practice is to create a domain account specifically
for the
ColdFusion service and give it exactly what permissions your
ColdFusion
applications need and then set the ColdFusion service to run
under this
account in the Windows Services Panel.
This is done by accessing the properties of the ColdFusion
service(s) in
the Windows Services panel and chaning the 'Log On' tab to
run a
specific account instead of the default 'Local System
account'.