J
Jim
Hi,
We have a situation where we have three domians within our organisation, let's call them Dm1, Dm2 and Dm3.
We have installed Project Server 2003, WSS, Analysis Services and SQl on Dm1. Users all have accounts on Dm2. Dm1 and Dm2 have a trust relationship. We cannot set-up a trust relationship with Dm3, but we have users who have to use their Dm3 accounts for day to day stuff and we do not want them to log out and in everytime they use Project. We are going to look into transferring all users to Dm2 in the Medium term but it is not realistic in the short term.
Terminal Services is not an Option because of the cost involved.
We do not want to have to create identical local accounts on Dm1 so that Dm3 users can login across a non trusted domain, because the Admin would be a nightmare.
We do not have the Budget to set up a VPM.
So what if we ensured that all users had an Account on Dm2, but they only used it for Project Pro or PWA access. i.e. they logged onto their PC's Email etc with their Dm3 account? Could we use basic SSL connection and then get users to specify the Dm2\Username and Password when they logged in through PWA or Project Pro?
Is this possible using just SSL?
Will Project Managers still be able to publish projects using the Dm2 windows accounts?
Will users be able to view WSS and Porfolio Analyzer using the Dm2 windows accounts?
I know with 2002 this would have caused problems as highlighted in "Deploy Microsoft Project Server 2002 Across Non-Trusted Domains" article, but do these same issues apply in 2003 and with IIS6?
Thanks
We have a situation where we have three domians within our organisation, let's call them Dm1, Dm2 and Dm3.
We have installed Project Server 2003, WSS, Analysis Services and SQl on Dm1. Users all have accounts on Dm2. Dm1 and Dm2 have a trust relationship. We cannot set-up a trust relationship with Dm3, but we have users who have to use their Dm3 accounts for day to day stuff and we do not want them to log out and in everytime they use Project. We are going to look into transferring all users to Dm2 in the Medium term but it is not realistic in the short term.
Terminal Services is not an Option because of the cost involved.
We do not want to have to create identical local accounts on Dm1 so that Dm3 users can login across a non trusted domain, because the Admin would be a nightmare.
We do not have the Budget to set up a VPM.
So what if we ensured that all users had an Account on Dm2, but they only used it for Project Pro or PWA access. i.e. they logged onto their PC's Email etc with their Dm3 account? Could we use basic SSL connection and then get users to specify the Dm2\Username and Password when they logged in through PWA or Project Pro?
Is this possible using just SSL?
Will Project Managers still be able to publish projects using the Dm2 windows accounts?
Will users be able to view WSS and Porfolio Analyzer using the Dm2 windows accounts?
I know with 2002 this would have caused problems as highlighted in "Deploy Microsoft Project Server 2002 Across Non-Trusted Domains" article, but do these same issues apply in 2003 and with IIS6?
Thanks