A
adidistyle
Hello All,
I have several independent installations of MSP2007std. They will be sharing
plans and resources, and viewing a master(consolidated) schedule file
comprising inserted projects.
I want the option settings for each installation to be universal, and that
views table etc are common throughout. I also need to take control of the
master settings to prevent damage and enforce standards. I think I need to do
this to prevent incorrect alendar and resource changes. As far as I can tell
some settings are in global.mpt (Options menu items), some are saved in each
project file (eg view print settings), and some can be replaced in the file
via organizer.
I have have noted Rod Gill's suggestion to place global.mpt in a central
location and have the MSP shortcuts setting redirect "Start in" to that
location. However, that allows the user to modify the original file (some
have admin rights).
As an alternative, I was considering a batch file that overwrites the local
global.mpt with a standardised version, retrieved from a central location.
This batch file would be placed in all users' Windows Startup so it would
occur each time Windows was started. Any inadvertant changes would then be
remedied each startup. Does the location of the local global.mpt vary with
updates etc?
Does this seem a feasible solution? Is there a better way? Server version is
not an option for us. Extra est AUD11000 for three users. Gulp.
Regards, Adam
I have several independent installations of MSP2007std. They will be sharing
plans and resources, and viewing a master(consolidated) schedule file
comprising inserted projects.
I want the option settings for each installation to be universal, and that
views table etc are common throughout. I also need to take control of the
master settings to prevent damage and enforce standards. I think I need to do
this to prevent incorrect alendar and resource changes. As far as I can tell
some settings are in global.mpt (Options menu items), some are saved in each
project file (eg view print settings), and some can be replaced in the file
via organizer.
I have have noted Rod Gill's suggestion to place global.mpt in a central
location and have the MSP shortcuts setting redirect "Start in" to that
location. However, that allows the user to modify the original file (some
have admin rights).
As an alternative, I was considering a batch file that overwrites the local
global.mpt with a standardised version, retrieved from a central location.
This batch file would be placed in all users' Windows Startup so it would
occur each time Windows was started. Any inadvertant changes would then be
remedied each startup. Does the location of the local global.mpt vary with
updates etc?
Does this seem a feasible solution? Is there a better way? Server version is
not an option for us. Extra est AUD11000 for three users. Gulp.
Regards, Adam