setting default global.mpt location without Policy

[Pat Dotbat]

I really hope someone can help - this has got me stumped.

I'm trying to apply a setting to a large number of machines to dictate the
global.mpt that each uses.
The file is bing copied to the path specified in
[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\11.0\MS
Project\GlobalSearch]
"RootKey"="C:\\Program Files\\Microsoft Office\\Office11\\1033"
yet the success of applying this registry setting is barely 50% of machines
- it seems that security on that key is such that a non-admin user cannot
change it.
I've search the proj11.adm and can't locate any reference to that location,
either.
My questions are:
1. is there some other 'overriding' setting which dictates where any machine
will look for global.mpt?
2. how is the 'Policies' key set, if not via GPO, and if I (for example)
modify the hku\.default value, how can I force this to apply to any logged on
user.

 

[Rob Schneider]

I really hope someone can help - this has got me stumped.

I'm trying to apply a setting to a large number of machines to dictate the
global.mpt that each uses.
The file is bing copied to the path specified in
[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\11.0\MS
Project\GlobalSearch]
"RootKey"="C:\\Program Files\\Microsoft Office\\Office11\\1033"
yet the success of applying this registry setting is barely 50% of machines
- it seems that security on that key is such that a non-admin user cannot
change it.
I've search the proj11.adm and can't locate any reference to that location,
either.
My questions are:
1. is there some other 'overriding' setting which dictates where any machine
will look for global.mpt?
2. how is the 'Policies' key set, if not via GPO, and if I (for example)
modify the hku\.default value, how can I force this to apply to any logged on
user.

I'm curious the reason why you want a standard and single global.mpt
location for everyone? I don't think that a good idea unless absolutely
everyone needs to use one shared global.mpt. If everyone useing same
(and if that works) I can imaging chaos with everyone wanting their own
stuff in the "global" global.mpt and of courase no everyone will want that.

Project has rules for how it looks for global.mpt. I, or example, work
with a special global.mpt with each project I'm working on. Each project
has it's own. To use a specific global.mpt, it's only necessary to
start Project with the "startup folder" to be where that specific
global.mpt to be and used.

If someone *told" me as a Project Manager which global.mpt I *had* to
use, I would not be a happy camper!

So, before we explore this further, why do you want this?

 

[Pat Dotbat]

I really hope someone can help - this has got me stumped.

I'm trying to apply a setting to a large number of machines to dictate the
global.mpt that each uses.
The file is bing copied to the path specified in
[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\11.0\MS
Project\GlobalSearch]
"RootKey"="C:\\Program Files\\Microsoft Office\\Office11\\1033"
yet the success of applying this registry setting is barely 50% of machines
- it seems that security on that key is such that a non-admin user cannot
change it.
I've search the proj11.adm and can't locate any reference to that location,
either.
My questions are:
1. is there some other 'overriding' setting which dictates where any machine
will look for global.mpt?
2. how is the 'Policies' key set, if not via GPO, and if I (for example)
modify the hku\.default value, how can I force this to apply to any logged on
user.

I'm curious the reason why you want a standard and single global.mpt
location for everyone? I don't think that a good idea unless absolutely
everyone needs to use one shared global.mpt. If everyone useing same
(and if that works) I can imaging chaos with everyone wanting their own
stuff in the "global" global.mpt and of courase no everyone will want that.

Project has rules for how it looks for global.mpt. I, or example, work
with a special global.mpt with each project I'm working on. Each project
has it's own. To use a specific global.mpt, it's only necessary to
start Project with the "startup folder" to be where that specific
global.mpt to be and used.

If someone *told" me as a Project Manager which global.mpt I *had* to
use, I would not be a happy camper!

So, before we explore this further, why do you want this?

sorry, I should have been more specific ...
our corporate global.mpt includes views and macros which support integration
with two other business systems (financial and document management) and in
future we may have to modify and redploy this template, so every machine
needs the same one (at least to start with, we don't prevent users making
their own based on it).
I've done some reserch on those search rules you mention and it seems that
most start at this pesky globalsearch key which is awkward to set.
I need to either find a reliable and programmatic way to set that key, or
perhaps the 'startup folder' (the Office one?) would be useful - if I can set
the 'working directoy' for Project to that 1033 folder, then would it use the
global.mpt therein, in preference to any other on the machine, irrespective
of registry settings?