Profile Wizard Switches - Office 2K3

[Ken]

I am attempting to rollout office 2003 via network /a
install.
I have the MST call the OPS in step 16/24 with the /r /d
switches.

I would like everyone who logs into that computer to have
the same profile (OPS) initially.

The problem I am running into is; the initial install and
profile installs alright. When I log in as new user, the
new OPS does not run until I open Word. Then asking me to
Close Office Program to finish OPS. I've tried all
switches and combinations.

Is there a way to get the OPS to run once a user logs in
and not around this; or have it run once and apply to all
current and future windows 2000 user accounts?
WE have also pointed the MST file to an ops file in step
9/24 as another possibility. Again, the specific user
settings in the ops file are applied to the installing
user always, other user accounts seldom. We need it to
apply to all users all the time. ???

Thanks in advance.
Ken

 

[Arie Heinrich]

Hi Ken,

You should add the OPS file at step 9.
Not as a file to be run at step 16.

Generally, I don't use OPS files in my installs.
All the settings are found in the MST, and the very few that
are not, I use the equivalent reg key import to make sure they
are set as I wish.

Basically an OPS file isn't different then a ZIP file. It gathers
files and registry and later unzips them to the same place from
where they were taken.

Creating a good OPS is not an easy job. Simple point and click
may cause problems with the results, as the default settings for
an OPS file gather too many keys that should not be used for a
Wide-deployment of Office, rather for cases where you want to
reinstall office to a user and want him/her to have same
personalization he/she had before, especially in cases where you
are changing the computer/OS.

If you have specific settings you want your users to have and have
scanned the options in the MST and still cant find them..were here to help


Take care,

Arie H.
MS MVP

 

[Arie Heinrich]

Hi Ken,

You should add the OPS file at step 9.
Not as a file to be run at step 16.

Generally, I don't use OPS files in my installs.
All the settings are found in the MST, and the very few that
are not, I use the equivalent reg key import to make sure they
are set as I wish.

Basically an OPS file isn't different then a ZIP file. It gathers
files and registry and later unzips them to the same place from
where they were taken.

Creating a good OPS is not an easy job. Simple point and click
may cause problems with the results, as the default settings for
an OPS file gather too many keys that should not be used for a
Wide-deployment of Office, rather for cases where you want to
reinstall office to a user and want him/her to have same
personalization he/she had before, especially in cases where you
are changing the computer/OS.

If you have specific settings you want your users to have and have
scanned the options in the MST and still cant find them..were here to help


Take care,

Arie H.
MS MVP

 

[Arie Heinrich]

Hi Ken,

You should add the OPS file at step 9.
Not as a file to be run at step 16.

Generally, I don't use OPS files in my installs.
All the settings are found in the MST, and the very few that
are not, I use the equivalent reg key import to make sure they
are set as I wish.

Basically an OPS file isn't different then a ZIP file. It gathers
files and registry and later unzips them to the same place from
where they were taken.

Creating a good OPS is not an easy job. Simple point and click
may cause problems with the results, as the default settings for
an OPS file gather too many keys that should not be used for a
Wide-deployment of Office, rather for cases where you want to
reinstall office to a user and want him/her to have same
personalization he/she had before, especially in cases where you
are changing the computer/OS.

If you have specific settings you want your users to have and have
scanned the options in the MST and still cant find them..were here to help


Take care,

Arie H.
MS MVP

 

[Arie Heinrich]

Hi Ken,

You should add the OPS file at step 9.
Not as a file to be run at step 16.

Generally, I don't use OPS files in my installs.
All the settings are found in the MST, and the very few that
are not, I use the equivalent reg key import to make sure they
are set as I wish.

Basically an OPS file isn't different then a ZIP file. It gathers
files and registry and later unzips them to the same place from
where they were taken.

Creating a good OPS is not an easy job. Simple point and click
may cause problems with the results, as the default settings for
an OPS file gather too many keys that should not be used for a
Wide-deployment of Office, rather for cases where you want to
reinstall office to a user and want him/her to have same
personalization he/she had before, especially in cases where you
are changing the computer/OS.

If you have specific settings you want your users to have and have
scanned the options in the MST and still cant find them..were here to help


Take care,

Arie H.
MS MVP

 

[Arie Heinrich]

Hi Ken,

You should add the OPS file at step 9.
Not as a file to be run at step 16.

Generally, I don't use OPS files in my installs.
All the settings are found in the MST, and the very few that
are not, I use the equivalent reg key import to make sure they
are set as I wish.

Basically an OPS file isn't different then a ZIP file. It gathers
files and registry and later unzips them to the same place from
where they were taken.

Creating a good OPS is not an easy job. Simple point and click
may cause problems with the results, as the default settings for
an OPS file gather too many keys that should not be used for a
Wide-deployment of Office, rather for cases where you want to
reinstall office to a user and want him/her to have same
personalization he/she had before, especially in cases where you
are changing the computer/OS.

If you have specific settings you want your users to have and have
scanned the options in the MST and still cant find them..were here to help


Take care,

Arie H.
MS MVP

 

[Arie Heinrich]

Hi Ken,

You should add the OPS file at step 9.
Not as a file to be run at step 16.

Generally, I don't use OPS files in my installs.
All the settings are found in the MST, and the very few that
are not, I use the equivalent reg key import to make sure they
are set as I wish.

Basically an OPS file isn't different then a ZIP file. It gathers
files and registry and later unzips them to the same place from
where they were taken.

Creating a good OPS is not an easy job. Simple point and click
may cause problems with the results, as the default settings for
an OPS file gather too many keys that should not be used for a
Wide-deployment of Office, rather for cases where you want to
reinstall office to a user and want him/her to have same
personalization he/she had before, especially in cases where you
are changing the computer/OS.

If you have specific settings you want your users to have and have
scanned the options in the MST and still cant find them..were here to help


Take care,

Arie H.
MS MVP

 

[Arie Heinrich]

Hi Ken,

You should add the OPS file at step 9.
Not as a file to be run at step 16.

Generally, I don't use OPS files in my installs.
All the settings are found in the MST, and the very few that
are not, I use the equivalent reg key import to make sure they
are set as I wish.

Basically an OPS file isn't different then a ZIP file. It gathers
files and registry and later unzips them to the same place from
where they were taken.

Creating a good OPS is not an easy job. Simple point and click
may cause problems with the results, as the default settings for
an OPS file gather too many keys that should not be used for a
Wide-deployment of Office, rather for cases where you want to
reinstall office to a user and want him/her to have same
personalization he/she had before, especially in cases where you
are changing the computer/OS.

If you have specific settings you want your users to have and have
scanned the options in the MST and still cant find them..were here to help


Take care,

Arie H.
MS MVP

 

[Arie Heinrich]

Hi Ken,

You should add the OPS file at step 9.
Not as a file to be run at step 16.

Generally, I don't use OPS files in my installs.
All the settings are found in the MST, and the very few that
are not, I use the equivalent reg key import to make sure they
are set as I wish.

Basically an OPS file isn't different then a ZIP file. It gathers
files and registry and later unzips them to the same place from
where they were taken.

Creating a good OPS is not an easy job. Simple point and click
may cause problems with the results, as the default settings for
an OPS file gather too many keys that should not be used for a
Wide-deployment of Office, rather for cases where you want to
reinstall office to a user and want him/her to have same
personalization he/she had before, especially in cases where you
are changing the computer/OS.

If you have specific settings you want your users to have and have
scanned the options in the MST and still cant find them..were here to help


Take care,

Arie H.
MS MVP

 

[Arie Heinrich]

Hi Ken,

You should add the OPS file at step 9.
Not as a file to be run at step 16.

Generally, I don't use OPS files in my installs.
All the settings are found in the MST, and the very few that
are not, I use the equivalent reg key import to make sure they
are set as I wish.

Basically an OPS file isn't different then a ZIP file. It gathers
files and registry and later unzips them to the same place from
where they were taken.

Creating a good OPS is not an easy job. Simple point and click
may cause problems with the results, as the default settings for
an OPS file gather too many keys that should not be used for a
Wide-deployment of Office, rather for cases where you want to
reinstall office to a user and want him/her to have same
personalization he/she had before, especially in cases where you
are changing the computer/OS.

If you have specific settings you want your users to have and have
scanned the options in the MST and still cant find them..were here to help


Take care,

Arie H.
MS MVP