Administrative Installation of Office 2000 Pro Problems in a locked down environment

[David Fritz]

In this case, I have an administrative installation point of Office 2000
Pro, updated to SP3 and all the latest patches. I applied a Transform file
to not include Outlook and Access in the installation. I have installed
this to a pristine Windows 2000 Professional machine as administrator, run
Word as administrator (to allow completion of setup) and then used the ORK's
Profiles Wizard to save off the settings (OPS) file. I have rerun the
Custom Installation Wizard to include the OPS file into the Transform.

Now when I install this setup on pristine Windows 2000 machines, Office 2000
installs fine, but it insists on completing the setup (installation) for
every user that logs on. In this environment, this cannot be allowed (users
are not allowed to invoke the MSI installer for any reason). This includes
domain users who logon to a machine and attempt to run any Office product.
The user cannot complete the installation, and all file associations for
Office are not set, there is an error message on starting the Office
Assistant and requests to reinstall it.

I am looking for a way to build an administrative installation of Office
2000, that, when installed on a workstation, will be ready for use without
having to finish an installation for each user.

Any ideas? I have searched without avail.

Thanks,
Dave Fritz

 

[Bob Buckland ?:-\)]

Hi Dave,

For travelling users the first time a new user logs on
Office creates registry and folders related to that user.
You may be able to prepoplulate the registry with the
needed entries for all of your users if the information
for the linked white paper here doesn't have an alternative
that will work for you.
http://office.microsoft.com/en-us/assistance/HA011384831033.aspx

========
In this case, I have an administrative installation point of Office 2000
Pro, updated to SP3 and all the latest patches. I applied a Transform file
to not include Outlook and Access in the installation. I have installed
this to a pristine Windows 2000 Professional machine as administrator, run
Word as administrator (to allow completion of setup) and then used the ORK's
Profiles Wizard to save off the settings (OPS) file. I have rerun the
Custom Installation Wizard to include the OPS file into the Transform.

Now when I install this setup on pristine Windows 2000 machines, Office 2000
installs fine, but it insists on completing the setup (installation) for
every user that logs on. In this environment, this cannot be allowed (users
are not allowed to invoke the MSI installer for any reason). This includes
domain users who logon to a machine and attempt to run any Office product.
The user cannot complete the installation, and all file associations for
Office are not set, there is an error message on starting the Office
Assistant and requests to reinstall it.

I am looking for a way to build an administrative installation of Office
2000, that, when installed on a workstation, will be ready for use without
having to finish an installation for each user.

Any ideas? I have searched without avail.

Thanks,
Dave Fritz>>
--
Let us know if this helped you,

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

Office 2003 Editions explained
http://www.microsoft.com/uk/office/editions.mspx

 

[Bob Buckland ?:-\)]

Hi Dave,

For travelling users the first time a new user logs on
Office creates registry and folders related to that user.
You may be able to prepoplulate the registry with the
needed entries for all of your users if the information
for the linked white paper here doesn't have an alternative
that will work for you.
http://office.microsoft.com/en-us/assistance/HA011384831033.aspx

========
In this case, I have an administrative installation point of Office 2000
Pro, updated to SP3 and all the latest patches. I applied a Transform file
to not include Outlook and Access in the installation. I have installed
this to a pristine Windows 2000 Professional machine as administrator, run
Word as administrator (to allow completion of setup) and then used the ORK's
Profiles Wizard to save off the settings (OPS) file. I have rerun the
Custom Installation Wizard to include the OPS file into the Transform.

Now when I install this setup on pristine Windows 2000 machines, Office 2000
installs fine, but it insists on completing the setup (installation) for
every user that logs on. In this environment, this cannot be allowed (users
are not allowed to invoke the MSI installer for any reason). This includes
domain users who logon to a machine and attempt to run any Office product.
The user cannot complete the installation, and all file associations for
Office are not set, there is an error message on starting the Office
Assistant and requests to reinstall it.

I am looking for a way to build an administrative installation of Office
2000, that, when installed on a workstation, will be ready for use without
having to finish an installation for each user.

Any ideas? I have searched without avail.

Thanks,
Dave Fritz>>
--
Let us know if this helped you,

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

Office 2003 Editions explained
http://www.microsoft.com/uk/office/editions.mspx

 

[Bob Buckland ?:-\)]

Hi Dave,

For travelling users the first time a new user logs on
Office creates registry and folders related to that user.
You may be able to prepoplulate the registry with the
needed entries for all of your users if the information
for the linked white paper here doesn't have an alternative
that will work for you.
http://office.microsoft.com/en-us/assistance/HA011384831033.aspx

========
In this case, I have an administrative installation point of Office 2000
Pro, updated to SP3 and all the latest patches. I applied a Transform file
to not include Outlook and Access in the installation. I have installed
this to a pristine Windows 2000 Professional machine as administrator, run
Word as administrator (to allow completion of setup) and then used the ORK's
Profiles Wizard to save off the settings (OPS) file. I have rerun the
Custom Installation Wizard to include the OPS file into the Transform.

Now when I install this setup on pristine Windows 2000 machines, Office 2000
installs fine, but it insists on completing the setup (installation) for
every user that logs on. In this environment, this cannot be allowed (users
are not allowed to invoke the MSI installer for any reason). This includes
domain users who logon to a machine and attempt to run any Office product.
The user cannot complete the installation, and all file associations for
Office are not set, there is an error message on starting the Office
Assistant and requests to reinstall it.

I am looking for a way to build an administrative installation of Office
2000, that, when installed on a workstation, will be ready for use without
having to finish an installation for each user.

Any ideas? I have searched without avail.

Thanks,
Dave Fritz>>
--
Let us know if this helped you,

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

Office 2003 Editions explained
http://www.microsoft.com/uk/office/editions.mspx

 

[Bob Buckland ?:-\)]

Hi Dave,

For travelling users the first time a new user logs on
Office creates registry and folders related to that user.
You may be able to prepoplulate the registry with the
needed entries for all of your users if the information
for the linked white paper here doesn't have an alternative
that will work for you.
http://office.microsoft.com/en-us/assistance/HA011384831033.aspx

========
In this case, I have an administrative installation point of Office 2000
Pro, updated to SP3 and all the latest patches. I applied a Transform file
to not include Outlook and Access in the installation. I have installed
this to a pristine Windows 2000 Professional machine as administrator, run
Word as administrator (to allow completion of setup) and then used the ORK's
Profiles Wizard to save off the settings (OPS) file. I have rerun the
Custom Installation Wizard to include the OPS file into the Transform.

Now when I install this setup on pristine Windows 2000 machines, Office 2000
installs fine, but it insists on completing the setup (installation) for
every user that logs on. In this environment, this cannot be allowed (users
are not allowed to invoke the MSI installer for any reason). This includes
domain users who logon to a machine and attempt to run any Office product.
The user cannot complete the installation, and all file associations for
Office are not set, there is an error message on starting the Office
Assistant and requests to reinstall it.

I am looking for a way to build an administrative installation of Office
2000, that, when installed on a workstation, will be ready for use without
having to finish an installation for each user.

Any ideas? I have searched without avail.

Thanks,
Dave Fritz>>
--
Let us know if this helped you,

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

Office 2003 Editions explained
http://www.microsoft.com/uk/office/editions.mspx

 

[Bob Buckland ?:-\)]

Hi Dave,

For travelling users the first time a new user logs on
Office creates registry and folders related to that user.
You may be able to prepoplulate the registry with the
needed entries for all of your users if the information
for the linked white paper here doesn't have an alternative
that will work for you.
http://office.microsoft.com/en-us/assistance/HA011384831033.aspx

========
In this case, I have an administrative installation point of Office 2000
Pro, updated to SP3 and all the latest patches. I applied a Transform file
to not include Outlook and Access in the installation. I have installed
this to a pristine Windows 2000 Professional machine as administrator, run
Word as administrator (to allow completion of setup) and then used the ORK's
Profiles Wizard to save off the settings (OPS) file. I have rerun the
Custom Installation Wizard to include the OPS file into the Transform.

Now when I install this setup on pristine Windows 2000 machines, Office 2000
installs fine, but it insists on completing the setup (installation) for
every user that logs on. In this environment, this cannot be allowed (users
are not allowed to invoke the MSI installer for any reason). This includes
domain users who logon to a machine and attempt to run any Office product.
The user cannot complete the installation, and all file associations for
Office are not set, there is an error message on starting the Office
Assistant and requests to reinstall it.

I am looking for a way to build an administrative installation of Office
2000, that, when installed on a workstation, will be ready for use without
having to finish an installation for each user.

Any ideas? I have searched without avail.

Thanks,
Dave Fritz>>
--
Let us know if this helped you,

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

Office 2003 Editions explained
http://www.microsoft.com/uk/office/editions.mspx

 

[Bob Buckland ?:-\)]

Hi Dave,

For travelling users the first time a new user logs on
Office creates registry and folders related to that user.
You may be able to prepoplulate the registry with the
needed entries for all of your users if the information
for the linked white paper here doesn't have an alternative
that will work for you.
http://office.microsoft.com/en-us/assistance/HA011384831033.aspx

========
In this case, I have an administrative installation point of Office 2000
Pro, updated to SP3 and all the latest patches. I applied a Transform file
to not include Outlook and Access in the installation. I have installed
this to a pristine Windows 2000 Professional machine as administrator, run
Word as administrator (to allow completion of setup) and then used the ORK's
Profiles Wizard to save off the settings (OPS) file. I have rerun the
Custom Installation Wizard to include the OPS file into the Transform.

Now when I install this setup on pristine Windows 2000 machines, Office 2000
installs fine, but it insists on completing the setup (installation) for
every user that logs on. In this environment, this cannot be allowed (users
are not allowed to invoke the MSI installer for any reason). This includes
domain users who logon to a machine and attempt to run any Office product.
The user cannot complete the installation, and all file associations for
Office are not set, there is an error message on starting the Office
Assistant and requests to reinstall it.

I am looking for a way to build an administrative installation of Office
2000, that, when installed on a workstation, will be ready for use without
having to finish an installation for each user.

Any ideas? I have searched without avail.

Thanks,
Dave Fritz>>
--
Let us know if this helped you,

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

Office 2003 Editions explained
http://www.microsoft.com/uk/office/editions.mspx

 

[Bob Buckland ?:-\)]

Hi Dave,

For travelling users the first time a new user logs on
Office creates registry and folders related to that user.
You may be able to prepoplulate the registry with the
needed entries for all of your users if the information
for the linked white paper here doesn't have an alternative
that will work for you.
http://office.microsoft.com/en-us/assistance/HA011384831033.aspx

========
In this case, I have an administrative installation point of Office 2000
Pro, updated to SP3 and all the latest patches. I applied a Transform file
to not include Outlook and Access in the installation. I have installed
this to a pristine Windows 2000 Professional machine as administrator, run
Word as administrator (to allow completion of setup) and then used the ORK's
Profiles Wizard to save off the settings (OPS) file. I have rerun the
Custom Installation Wizard to include the OPS file into the Transform.

Now when I install this setup on pristine Windows 2000 machines, Office 2000
installs fine, but it insists on completing the setup (installation) for
every user that logs on. In this environment, this cannot be allowed (users
are not allowed to invoke the MSI installer for any reason). This includes
domain users who logon to a machine and attempt to run any Office product.
The user cannot complete the installation, and all file associations for
Office are not set, there is an error message on starting the Office
Assistant and requests to reinstall it.

I am looking for a way to build an administrative installation of Office
2000, that, when installed on a workstation, will be ready for use without
having to finish an installation for each user.

Any ideas? I have searched without avail.

Thanks,
Dave Fritz>>
--
Let us know if this helped you,

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

Office 2003 Editions explained
http://www.microsoft.com/uk/office/editions.mspx

 

[Bob Buckland ?:-\)]

Hi Dave,

For travelling users the first time a new user logs on
Office creates registry and folders related to that user.
You may be able to prepoplulate the registry with the
needed entries for all of your users if the information
for the linked white paper here doesn't have an alternative
that will work for you.
http://office.microsoft.com/en-us/assistance/HA011384831033.aspx

========
In this case, I have an administrative installation point of Office 2000
Pro, updated to SP3 and all the latest patches. I applied a Transform file
to not include Outlook and Access in the installation. I have installed
this to a pristine Windows 2000 Professional machine as administrator, run
Word as administrator (to allow completion of setup) and then used the ORK's
Profiles Wizard to save off the settings (OPS) file. I have rerun the
Custom Installation Wizard to include the OPS file into the Transform.

Now when I install this setup on pristine Windows 2000 machines, Office 2000
installs fine, but it insists on completing the setup (installation) for
every user that logs on. In this environment, this cannot be allowed (users
are not allowed to invoke the MSI installer for any reason). This includes
domain users who logon to a machine and attempt to run any Office product.
The user cannot complete the installation, and all file associations for
Office are not set, there is an error message on starting the Office
Assistant and requests to reinstall it.

I am looking for a way to build an administrative installation of Office
2000, that, when installed on a workstation, will be ready for use without
having to finish an installation for each user.

Any ideas? I have searched without avail.

Thanks,
Dave Fritz>>
--
Let us know if this helped you,

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

Office 2003 Editions explained
http://www.microsoft.com/uk/office/editions.mspx

 

[Bob Buckland ?:-\)]

Hi Dave,

For travelling users the first time a new user logs on
Office creates registry and folders related to that user.
You may be able to prepoplulate the registry with the
needed entries for all of your users if the information
for the linked white paper here doesn't have an alternative
that will work for you.
http://office.microsoft.com/en-us/assistance/HA011384831033.aspx

========
In this case, I have an administrative installation point of Office 2000
Pro, updated to SP3 and all the latest patches. I applied a Transform file
to not include Outlook and Access in the installation. I have installed
this to a pristine Windows 2000 Professional machine as administrator, run
Word as administrator (to allow completion of setup) and then used the ORK's
Profiles Wizard to save off the settings (OPS) file. I have rerun the
Custom Installation Wizard to include the OPS file into the Transform.

Now when I install this setup on pristine Windows 2000 machines, Office 2000
installs fine, but it insists on completing the setup (installation) for
every user that logs on. In this environment, this cannot be allowed (users
are not allowed to invoke the MSI installer for any reason). This includes
domain users who logon to a machine and attempt to run any Office product.
The user cannot complete the installation, and all file associations for
Office are not set, there is an error message on starting the Office
Assistant and requests to reinstall it.

I am looking for a way to build an administrative installation of Office
2000, that, when installed on a workstation, will be ready for use without
having to finish an installation for each user.

Any ideas? I have searched without avail.

Thanks,
Dave Fritz>>
--
Let us know if this helped you,

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

Office 2003 Editions explained
http://www.microsoft.com/uk/office/editions.mspx

 

[David Fritz]

Thanks Bob. It took awhile to find the document as it is no longer where
the link points to in the page you gave me. A brute force find on the title
found it in
http://www.microsoft.com/technet/prodtechnol/office/office2000/maintain/operate/travwppr.mspx

Dave Fritz

 

[David Fritz]

Thanks Bob. It took awhile to find the document as it is no longer where
the link points to in the page you gave me. A brute force find on the title
found it in
http://www.microsoft.com/technet/prodtechnol/office/office2000/maintain/operate/travwppr.mspx

Dave Fritz

 

[David Fritz]

Thanks Bob. It took awhile to find the document as it is no longer where
the link points to in the page you gave me. A brute force find on the title
found it in
http://www.microsoft.com/technet/prodtechnol/office/office2000/maintain/operate/travwppr.mspx

Dave Fritz

 

[David Fritz]

Thanks Bob. It took awhile to find the document as it is no longer where
the link points to in the page you gave me. A brute force find on the title
found it in
http://www.microsoft.com/technet/prodtechnol/office/office2000/maintain/operate/travwppr.mspx

Dave Fritz

 

[David Fritz]

Thanks Bob. It took awhile to find the document as it is no longer where
the link points to in the page you gave me. A brute force find on the title
found it in
http://www.microsoft.com/technet/prodtechnol/office/office2000/maintain/operate/travwppr.mspx

Dave Fritz

 

[David Fritz]

Thanks Bob. It took awhile to find the document as it is no longer where
the link points to in the page you gave me. A brute force find on the title
found it in
http://www.microsoft.com/technet/prodtechnol/office/office2000/maintain/operate/travwppr.mspx

Dave Fritz

 

[David Fritz]

Thanks Bob. It took awhile to find the document as it is no longer where
the link points to in the page you gave me. A brute force find on the title
found it in
http://www.microsoft.com/technet/prodtechnol/office/office2000/maintain/operate/travwppr.mspx

Dave Fritz

 

[David Fritz]

Thanks Bob. It took awhile to find the document as it is no longer where
the link points to in the page you gave me. A brute force find on the title
found it in
http://www.microsoft.com/technet/prodtechnol/office/office2000/maintain/operate/travwppr.mspx

Dave Fritz

 

[David Fritz]

Thanks Bob. It took awhile to find the document as it is no longer where
the link points to in the page you gave me. A brute force find on the title
found it in
http://www.microsoft.com/technet/prodtechnol/office/office2000/maintain/operate/travwppr.mspx

Dave Fritz