Returning employee
J Burford Fields
The previous account could not be used because the new company can't
be privy to the pricing information of the ole. So, I disabled the
old account. I set the Workgroup to "None" and cleared the e-mail
address and Active Directory account info. Then I set up a new
account and pointed it to the re-activated windows account and email
address.
What I'm discovering is that the returned employee cannot see tasks in
his timesheet view.
Thoughts?
Crook
You probably already checked the basics, but were tasks published to the new
resource?
FWIW (which may not be much! Grin!)
Crook
"J Burford Fields" <jbfi...@gmail.com> wrote in message
news:1190055463.8...@n39g2000hsh.googlegroups.com...
J Burford Fields
> Hi J Burford,
>
> You probably already checked the basics, but were tasks published to the new
> resource?
>
> FWIW (which may not be much! Grin!)
> Crook
>
>
>
>
> > We had a contractor who left then came back under another company.
> > The previous account could not be used because the new company can't
> > be privy to the pricing information of the ole. So, I disabled the
> > old account. I set the Workgroup to "None" and cleared the e-mail
> > address and Active Directory account info. Then I set up a new
> > account and pointed it to the re-activated windows account and email
> > address.
>
> > What I'm discovering is that the returned employee cannot see tasks in
> > his timesheet view.
>
>
> - Show quoted text -
Thanks. I've republished a few times, but your though prompts me to
try republishing the assignment using the resource usage view.
Sometimes that has given me different results, in times past.
My suspicion is that the task assignment database elements ascertain
their security parameters based upon the user principal name (UPN),
which is generally the same as their e-mail address. The new resource
is using the same UPN as it was previously. It seems to me that I've
seen errors in other situations, when I try to change an account from
Windows authentication to Server authentication or the other way,
where similar difficulties develop.
Bloody baffling.
J
Crook
That's a good point. Maybe a different name would help. I will be
interested in hearing how this turns out for you.
Good Luck,
Crook
"J Burford Fields" <jbfi...@gmail.com> wrote in message
news:1190115289.9...@d55g2000hsg.googlegroups.com...