My transform file to change the Office2003 & add the license faile

[hrjohn]

I set up a group policy to assign office 2003 to computers and that seems to
work. However, I also wrote a transform using the Custon Installation Wizard
but I do not know how to get the MST to work? when I open MS Word it asks me
for the license key still. Do I have to change the setup.ini file and add the
transform??

 

[neo [mvp outlook]]

When you created the group policy object in active directory to deploy
Office 2003 is when you specify the MSI and MST file.

For the other part, are you using a retail or oem version of Office 2003 to
do this deployment? The reason that i ask is that retail or oem versions of
Office 2003 cannot be used to do rollouts this way. You have to use a
volume license version of Office 2003 and the bypass product key Microsoft
supplies for it.

If you are using the volume license version, you place the bypass product
key in the MST via the CIW like you are doing. The setup.ini file is not
read or used when deploying to computers via a group policy object.

 

[neo [mvp outlook]]

When you created the group policy object in active directory to deploy
Office 2003 is when you specify the MSI and MST file.

For the other part, are you using a retail or oem version of Office 2003 to
do this deployment? The reason that i ask is that retail or oem versions of
Office 2003 cannot be used to do rollouts this way. You have to use a
volume license version of Office 2003 and the bypass product key Microsoft
supplies for it.

If you are using the volume license version, you place the bypass product
key in the MST via the CIW like you are doing. The setup.ini file is not
read or used when deploying to computers via a group policy object.

 

[neo [mvp outlook]]

When you created the group policy object in active directory to deploy
Office 2003 is when you specify the MSI and MST file.

For the other part, are you using a retail or oem version of Office 2003 to
do this deployment? The reason that i ask is that retail or oem versions of
Office 2003 cannot be used to do rollouts this way. You have to use a
volume license version of Office 2003 and the bypass product key Microsoft
supplies for it.

If you are using the volume license version, you place the bypass product
key in the MST via the CIW like you are doing. The setup.ini file is not
read or used when deploying to computers via a group policy object.

 

[neo [mvp outlook]]

When you created the group policy object in active directory to deploy
Office 2003 is when you specify the MSI and MST file.

For the other part, are you using a retail or oem version of Office 2003 to
do this deployment? The reason that i ask is that retail or oem versions of
Office 2003 cannot be used to do rollouts this way. You have to use a
volume license version of Office 2003 and the bypass product key Microsoft
supplies for it.

If you are using the volume license version, you place the bypass product
key in the MST via the CIW like you are doing. The setup.ini file is not
read or used when deploying to computers via a group policy object.

 

[neo [mvp outlook]]

When you created the group policy object in active directory to deploy
Office 2003 is when you specify the MSI and MST file.

For the other part, are you using a retail or oem version of Office 2003 to
do this deployment? The reason that i ask is that retail or oem versions of
Office 2003 cannot be used to do rollouts this way. You have to use a
volume license version of Office 2003 and the bypass product key Microsoft
supplies for it.

If you are using the volume license version, you place the bypass product
key in the MST via the CIW like you are doing. The setup.ini file is not
read or used when deploying to computers via a group policy object.

 

[neo [mvp outlook]]

When you created the group policy object in active directory to deploy
Office 2003 is when you specify the MSI and MST file.

For the other part, are you using a retail or oem version of Office 2003 to
do this deployment? The reason that i ask is that retail or oem versions of
Office 2003 cannot be used to do rollouts this way. You have to use a
volume license version of Office 2003 and the bypass product key Microsoft
supplies for it.

If you are using the volume license version, you place the bypass product
key in the MST via the CIW like you are doing. The setup.ini file is not
read or used when deploying to computers via a group policy object.

 

[neo [mvp outlook]]

When you created the group policy object in active directory to deploy
Office 2003 is when you specify the MSI and MST file.

For the other part, are you using a retail or oem version of Office 2003 to
do this deployment? The reason that i ask is that retail or oem versions of
Office 2003 cannot be used to do rollouts this way. You have to use a
volume license version of Office 2003 and the bypass product key Microsoft
supplies for it.

If you are using the volume license version, you place the bypass product
key in the MST via the CIW like you are doing. The setup.ini file is not
read or used when deploying to computers via a group policy object.

 

[neo [mvp outlook]]

When you created the group policy object in active directory to deploy
Office 2003 is when you specify the MSI and MST file.

For the other part, are you using a retail or oem version of Office 2003 to
do this deployment? The reason that i ask is that retail or oem versions of
Office 2003 cannot be used to do rollouts this way. You have to use a
volume license version of Office 2003 and the bypass product key Microsoft
supplies for it.

If you are using the volume license version, you place the bypass product
key in the MST via the CIW like you are doing. The setup.ini file is not
read or used when deploying to computers via a group policy object.

 

[neo [mvp outlook]]

When you created the group policy object in active directory to deploy
Office 2003 is when you specify the MSI and MST file.

For the other part, are you using a retail or oem version of Office 2003 to
do this deployment? The reason that i ask is that retail or oem versions of
Office 2003 cannot be used to do rollouts this way. You have to use a
volume license version of Office 2003 and the bypass product key Microsoft
supplies for it.

If you are using the volume license version, you place the bypass product
key in the MST via the CIW like you are doing. The setup.ini file is not
read or used when deploying to computers via a group policy object.

 

[hrjohn]

I am using a volume license version. When I setup the group policy the
Modifications tab had the "Add" tab grayed out and I could not add any
transforms??

 

[hrjohn]

I am using a volume license version. When I setup the group policy the
Modifications tab had the "Add" tab grayed out and I could not add any
transforms??

 

[hrjohn]

I am using a volume license version. When I setup the group policy the
Modifications tab had the "Add" tab grayed out and I could not add any
transforms??

 

[hrjohn]

I am using a volume license version. When I setup the group policy the
Modifications tab had the "Add" tab grayed out and I could not add any
transforms??

 

[hrjohn]

I am using a volume license version. When I setup the group policy the
Modifications tab had the "Add" tab grayed out and I could not add any
transforms??

 

[hrjohn]

I am using a volume license version. When I setup the group policy the
Modifications tab had the "Add" tab grayed out and I could not add any
transforms??

 

[hrjohn]

I am using a volume license version. When I setup the group policy the
Modifications tab had the "Add" tab grayed out and I could not add any
transforms??

 

[hrjohn]

I am using a volume license version. When I setup the group policy the
Modifications tab had the "Add" tab grayed out and I could not add any
transforms??

 

[hrjohn]

I am using a volume license version. When I setup the group policy the
Modifications tab had the "Add" tab grayed out and I could not add any
transforms??

 

[neo [mvp outlook]]

When creating the software install package in the GPO, did you select
Assigned or Advanced? (You need to pick Advanced in order to define MSI and
MST.)


I should ask this now in order to save you headaches later, are you
planning on patching Office 2003 later with WSUS? The reason that I ask is
that WSUS can't update a client workstation under certain circumstances and
I want you to be aware at this stage rather than later.