saving locally as a default

N

Not-a-nerd-Naomi

I've seen the posts on choosing to save locally or to the server. My
question is if saving locally can be set as the default. Our users
tend not to look at details and as a result save directly to the server
because that's the default that seems to be built into project.

Thanks
Naomi
 
K

Kevin W Flanagan

Naomi-

Your best solution is to train your team members not to be so hasty in their
work. However, your administrator can set up the connection to be Manual
instead of Automatic and train them to choose My Computer to work and save
locally in the Tools -> Enterprise Options -> Microsoft Office Project Server
Accounts. I am assumoing that eventually you do want them to be able to save
onto the Server at a later date.

Hope this helps
 
N

Not-a-nerd-Naomi

Hi Kevin, thanks for the response. I tried out what you said.

My inference just from my workstation is that everyone has access to
Tools -> Enterprise Options -> Microsoft Office Project Server
Accounts and a manager is not needed. Is this true?

Also, while we're at it, what's the difference between saving to the
server and importing using the wizard? Both seemed to put my projects
online. But someone has said not to save...

Thanks,

Naomi
 
K

Kevin W Flanagan

Sorry. Yes a user can set up their account to connect manually and you do
not need an admin to do so.

Saving the project allows task and resource potential errors to be saved out
in project server. During the Import process, the wizard checks for
mispelled or local resources and gives you the chance to map them to an
enterprise resource. It is generally safer to import rather than to just
save as the rrors will not show up until the user attempts to publish the
project schedule and the sppoler will throw an error.
 
N

Not-a-nerd-Naomi

Thanks Kevin. That makes sense. I'm now getting totally screwed up on
whether you open locally, go online and open, etc. etc. Is there an
online tutorial or some project for dummies (maybe there is!)? As I
unravel this I'll just have more questions that I'd rather not take up
posting space with.

Thanks
Naomi
 
K

Kevin W Flanagan

Let me share how we do things where I am a consultant currently.

1. First we(PMO) create a project workspace for the project manager with a
skeleton template based on the work of the project
2. This allows the PM to have a workspace to start storing documents like a
project charter, communications plan, RAM, etc.
3. We coach the PM to get their project into the shape before we allow it
to be published: complete line or predecessors or successors throghout the
project, actual resources assigned (no generic reource assignments), baseline
set, etc. This makes for more valid information in our reporting to upper
management
4. We have established a weekly update process for PMs to follow to make
sure the shceudloe are updated on a regular basis.

Hope this helps.
 
Top