Windows Authentication & Publishing

[Ann Keast]

This relates to the following post:
Subject: Windows Authenication
From: "Randy" <[email protected]> Sent: 6/12/2003
1:57:56 PM

Trying to find some help with the window authenication.
Virtual users that do not login to a domain (using local
windows accounts) can use the windows account to access
the web site and import a project. When they try to
collaborate by publishing they get spooler error
0x8c040028. I can see in the collaboration option that it
is pulling their machine name. How do you specify the
correct windows account you setup on the server or fix
this problem?
--------------------------------------------------

If SQL and Project Server are on the same machine, you
should be able to do
this if you use Project Server accounts for the people who
don't log on to
the domain.
---------------------------------------------------

Thanks for the comment. Yes, SQL and Project are on the
same machine. Aware the virtual staff who do not login
to the domain can access using Project Server login. My
understanding (which could be wrong) is the users must
authenicate with the windows account for using the
issues, documents and team services componets. Isn't
there a way to modify their machine names, etc to enable
windows authenication?

---------------------------------------------------
Our implementation has the same arhictecture. Able to use
Windows authentication to access the PWA. However, the
same user is able access Project Professional, but upon
publishing recieves the 0x8C040028 error.

We are wondering the same thing:
Is there a way to modify their machine names, etc to
enable windows authenication from the client software?