F
Freddy C.
We're in the process of moving to Project Server 2k3 with web access. We work
in a managed desktop scenario, so some of the people who will use PWA won't
be able to accept the EULA. Microsoft has provided the ActiveX files to
download, so we took them and created a package that registered the files and
put them in the System32 directory. This worked fine in our test enviornment,
but when we created a UAT enviornment with a new server, the PC's with the
ActiveX files installed are being prompted to accept the EULA again. Even if
we reinstall the files, the users are being prompted. What's REALLY strange
is if we accept the EULA from the test PWA server, it downloads the files and
we can access PWA on the test server, but not the UAT server; it still
prompts to accept the agreement. If we accept the EULA on the UAT server, we
can access PWA on the test server as well as the UAT server. We can't change
the rights of the users, and logging into 300+ machines to accept the EULA
for them isn't something we want to do. Any ideas?
in a managed desktop scenario, so some of the people who will use PWA won't
be able to accept the EULA. Microsoft has provided the ActiveX files to
download, so we took them and created a package that registered the files and
put them in the System32 directory. This worked fine in our test enviornment,
but when we created a UAT enviornment with a new server, the PC's with the
ActiveX files installed are being prompted to accept the EULA again. Even if
we reinstall the files, the users are being prompted. What's REALLY strange
is if we accept the EULA from the test PWA server, it downloads the files and
we can access PWA on the test server, but not the UAT server; it still
prompts to accept the agreement. If we accept the EULA on the UAT server, we
can access PWA on the test server as well as the UAT server. We can't change
the rights of the users, and logging into 300+ machines to accept the EULA
for them isn't something we want to do. Any ideas?