J
Jack Kohn
Situation: We have MS Project Pro on our MetaFrame server so our PM's
can access their projects remotely.
We have a number of external sites in the Trusted Zone for which we do
*not* want to use the setting "Automatically logon using current
username and password".
Unfortunately, MS Project forces the Project server to be in the
"Trusted Zone." So our PM's windows credentials don't get
automatically passed through to the Project Server.
Our workarounds for this seem to be:
A) relax security settings for the "Trusted zone" to allow
automatic login;
B) force users to login separately to the Project Server; or
C) ask users to modify their zone security settings when they
want to use Project.
None of these seem acceptable:
A) is not acceptable: we do not want to pass our internal
network credentials to any trusted site that happens to ask for them.
B) is no good: PM's are complaining about the extra login.
C) is not acceptable: We don't *want* users to modify zone
security settings, for obvious reasons.
It seems like it would solve our problems if we could just have our MS
Project server in the Intranet zone, but the system doesn't work that
way.
We do not want to set up Project server for external access via the
Internet. We don't need that feature / exposure, and it brings
additional administration overhead.
Anyone have any ideas?
Thanks.
-jmk
Jack Kohn
can access their projects remotely.
We have a number of external sites in the Trusted Zone for which we do
*not* want to use the setting "Automatically logon using current
username and password".
Unfortunately, MS Project forces the Project server to be in the
"Trusted Zone." So our PM's windows credentials don't get
automatically passed through to the Project Server.
Our workarounds for this seem to be:
A) relax security settings for the "Trusted zone" to allow
automatic login;
B) force users to login separately to the Project Server; or
C) ask users to modify their zone security settings when they
want to use Project.
None of these seem acceptable:
A) is not acceptable: we do not want to pass our internal
network credentials to any trusted site that happens to ask for them.
B) is no good: PM's are complaining about the extra login.
C) is not acceptable: We don't *want* users to modify zone
security settings, for obvious reasons.
It seems like it would solve our problems if we could just have our MS
Project server in the Intranet zone, but the system doesn't work that
way.
We do not want to set up Project server for external access via the
Internet. We don't need that feature / exposure, and it brings
additional administration overhead.
Anyone have any ideas?
Thanks.
-jmk
Jack Kohn