TWIMC,
1. I have a client who is running mixed release for Project Professional
2003 and Project Server 2003.
Example: Project Professional SP3 accessing Project Server SP1.
2. What issues can this cause if known?
3. I remember reading, years ago that Project Professional 2003 should match
the SP releases on the Project Server 2003. Is that correct?
Example:
- Project Professional 2003 SP1 to Project Server 2003 SP1.
- Project Professional 2003 SP2 to Project Server 2003 SP2A.
- Project Professional 2003 SP3 to Project Server 2003 SP3.
David.

There's no specific guidance on what issues it could cause. However,
there is a very significant potential for unpredictable behavior, data
corruption, and data loss. It is also possible that nothing will go
awry. However, it is better to err on the side of caution in this case.
EPM is not the place to live dangerously :o)



One should always match versions between Pro and Server in situations
where there are corresponding updates for both.

--

Stephen Sanderlin

Principal Consultant

MSProjectExperts



For Project Server Consulting: http://www.msprojectexperts.com

For Project Server Training: http://www.projectservertraining.com



Read my blog at: http://www.projectserverhelp.com/

Join the community at: http://forums.epmfaq.com





"David326x" <David326x@discussions.microsoft.com> wrote in message
news:2BA655BC-84D7-460C-A764-BF2BCB155B02@microsoft.com:

> TWIMC,
> 1. I have a client who is running mixed release for Project Professional
> 2003 and Project Server 2003.
> Example: Project Professional SP3 accessing Project Server SP1.
> 2. What issues can this cause if known?
> 3. I remember reading, years ago that Project Professional 2003 should match
> the SP releases on the Project Server 2003. Is that correct?
> Example:
> - Project Professional 2003 SP1 to Project Server 2003 SP1.
> - Project Professional 2003 SP2 to Project Server 2003 SP2A.
> - Project Professional 2003 SP3 to Project Server 2003 SP3.
> David.

Thank you Stephen. I expected as much. I now have a new deliverable in my
project plan to address this issue.

Thanks again for the tips!
David.


"Stephen Sanderlin" wrote:

> There's no specific guidance on what issues it could cause. However,
> there is a very significant potential for unpredictable behavior, data
> corruption, and data loss. It is also possible that nothing will go
> awry. However, it is better to err on the side of caution in this case.
> EPM is not the place to live dangerously :o)
>
>
>
> One should always match versions between Pro and Server in situations
> where there are corresponding updates for both.
>
> --
>
> Stephen Sanderlin
>
> Principal Consultant
>
> MSProjectExperts
>
>
>
> For Project Server Consulting: http://www.msprojectexperts.com
>
> For Project Server Training: http://www.projectservertraining.com
>
>
>
> Read my blog at: http://www.projectserverhelp.com/
>
> Join the community at: http://forums.epmfaq.com
>
>
>
>
>
> "David326x" <David326x@discussions.microsoft.com> wrote in message
> news:2BA655BC-84D7-460C-A764-BF2BCB155B02@microsoft.com:
>
> > TWIMC,
> > 1. I have a client who is running mixed release for Project Professional
> > 2003 and Project Server 2003.
> > Example: Project Professional SP3 accessing Project Server SP1.
> > 2. What issues can this cause if known?
> > 3. I remember reading, years ago that Project Professional 2003 should match
> > the SP releases on the Project Server 2003. Is that correct?
> > Example:
> > - Project Professional 2003 SP1 to Project Server 2003 SP1.
> > - Project Professional 2003 SP2 to Project Server 2003 SP2A.
> > - Project Professional 2003 SP3 to Project Server 2003 SP3.
> > David

No problem - glad to help!

--

Stephen Sanderlin

Principal Consultant

MSProjectExperts



For Project Server Consulting: http://www.msprojectexperts.com

For Project Server Training: http://www.projectservertraining.com



Read my blog at: http://www.projectserverhelp.com/

Join the community at: http://forums.epmfaq.com





"David326x" <David326x@discussions.microsoft.com> wrote in message
news:2FD917B5-9B33-406F-98BB-5FA138B57BAB@microsoft.com:

> Thank you Stephen. I expected as much. I now have a new deliverable in my
> project plan to address this issue.
>
> Thanks again for the tips!
> David.
>
>
> "Stephen Sanderlin" wrote:
>
>
> > There's no specific guidance on what issues it could cause. However,
> > there is a very significant potential for unpredictable behavior, data
> > corruption, and data loss. It is also possible that nothing will go
> > awry. However, it is better to err on the side of caution in this case.
> > EPM is not the place to live dangerously :o)
> >
> >
> >
> > One should always match versions between Pro and Server in situations
> > where there are corresponding updates for both.
> >
> > --
> >
> > Stephen Sanderlin
> >
> > Principal Consultant
> >
> > MSProjectExperts
> >
> >
> >
> > For Project Server Consulting: http://www.msprojectexperts.com
> >
> > For Project Server Training: http://www.projectservertraining.com
> >
> >
> >
> > Read my blog at: http://www.projectserverhelp.com/
> >
> > Join the community at: http://forums.epmfaq.com
> >
> >
> >
> >
> >
> > "David326x" <David326x@discussions.microsoft.com> wrote in message
> > news:2BA655BC-84D7-460C-A764-BF2BCB155B02@microsoft.com:
> >
>
> > > TWIMC,
> > > 1. I have a client who is running mixed release for Project Professional
> > > 2003 and Project Server 2003.
> > > Example: Project Professional SP3 accessing Project Server SP1.
> > > 2. What issues can this cause if known?
> > > 3. I remember reading, years ago that Project Professional 2003 should match
> > > the SP releases on the Project Server 2003. Is that correct?
> > > Example:
> > > - Project Professional 2003 SP1 to Project Server 2003 SP1.
> > > - Project Professional 2003 SP2 to Project Server 2003 SP2A.
> > > - Project Professional 2003 SP3 to Project Server 2003 SP3.
> > > David