Trying to deploy SP1 for Office 2003?!?

Z

Zack

Just thought I'd chime in and say that I'm in the same boat. I have
Office 2003 deployed to my users via a compressed CD image on the network,
assigned to computers via GP along with a custom MST file created with the
CIW. Since we only have .msp files from the SP1 patch, I can't just
upgrade the application via GP, if I understand the situation correctly.

Given that installing via compressed CD image with local source caching is
Microsoft's recommended method of deployment for Office, why is it now a
headache to update to SP1? Unless I'm misunderstanding the instructions,
it seems the only methods of updating our installed base is having
everyone run the patch on their machines. Obviously this is unacceptable,
so I hope that I'm misunderstanding something. Isn't there at the least a
way to apply the .msp file to the .msi on the network, then modify the
original GPO to redeploy the application?

Thanks for any help!

-Zack-, who is relatively new to Group Policy Software Installation
 
Z

Zack

Just thought I'd chime in and say that I'm in the same boat. I have
Office 2003 deployed to my users via a compressed CD image on the network,
assigned to computers via GP along with a custom MST file created with the
CIW. Since we only have .msp files from the SP1 patch, I can't just
upgrade the application via GP, if I understand the situation correctly.

Given that installing via compressed CD image with local source caching is
Microsoft's recommended method of deployment for Office, why is it now a
headache to update to SP1? Unless I'm misunderstanding the instructions,
it seems the only methods of updating our installed base is having
everyone run the patch on their machines. Obviously this is unacceptable,
so I hope that I'm misunderstanding something. Isn't there at the least a
way to apply the .msp file to the .msi on the network, then modify the
original GPO to redeploy the application?

Thanks for any help!

-Zack-, who is relatively new to Group Policy Software Installation
 
Z

Zack

Just thought I'd chime in and say that I'm in the same boat. I have
Office 2003 deployed to my users via a compressed CD image on the network,
assigned to computers via GP along with a custom MST file created with the
CIW. Since we only have .msp files from the SP1 patch, I can't just
upgrade the application via GP, if I understand the situation correctly.

Given that installing via compressed CD image with local source caching is
Microsoft's recommended method of deployment for Office, why is it now a
headache to update to SP1? Unless I'm misunderstanding the instructions,
it seems the only methods of updating our installed base is having
everyone run the patch on their machines. Obviously this is unacceptable,
so I hope that I'm misunderstanding something. Isn't there at the least a
way to apply the .msp file to the .msi on the network, then modify the
original GPO to redeploy the application?

Thanks for any help!

-Zack-, who is relatively new to Group Policy Software Installation
 
Z

Zack

Just thought I'd chime in and say that I'm in the same boat. I have
Office 2003 deployed to my users via a compressed CD image on the network,
assigned to computers via GP along with a custom MST file created with the
CIW. Since we only have .msp files from the SP1 patch, I can't just
upgrade the application via GP, if I understand the situation correctly.

Given that installing via compressed CD image with local source caching is
Microsoft's recommended method of deployment for Office, why is it now a
headache to update to SP1? Unless I'm misunderstanding the instructions,
it seems the only methods of updating our installed base is having
everyone run the patch on their machines. Obviously this is unacceptable,
so I hope that I'm misunderstanding something. Isn't there at the least a
way to apply the .msp file to the .msi on the network, then modify the
original GPO to redeploy the application?

Thanks for any help!

-Zack-, who is relatively new to Group Policy Software Installation
 
Z

Zack

Just thought I'd chime in and say that I'm in the same boat. I have
Office 2003 deployed to my users via a compressed CD image on the network,
assigned to computers via GP along with a custom MST file created with the
CIW. Since we only have .msp files from the SP1 patch, I can't just
upgrade the application via GP, if I understand the situation correctly.

Given that installing via compressed CD image with local source caching is
Microsoft's recommended method of deployment for Office, why is it now a
headache to update to SP1? Unless I'm misunderstanding the instructions,
it seems the only methods of updating our installed base is having
everyone run the patch on their machines. Obviously this is unacceptable,
so I hope that I'm misunderstanding something. Isn't there at the least a
way to apply the .msp file to the .msi on the network, then modify the
original GPO to redeploy the application?

Thanks for any help!

-Zack-, who is relatively new to Group Policy Software Installation
 
Z

Zack

Just thought I'd chime in and say that I'm in the same boat. I have
Office 2003 deployed to my users via a compressed CD image on the network,
assigned to computers via GP along with a custom MST file created with the
CIW. Since we only have .msp files from the SP1 patch, I can't just
upgrade the application via GP, if I understand the situation correctly.

Given that installing via compressed CD image with local source caching is
Microsoft's recommended method of deployment for Office, why is it now a
headache to update to SP1? Unless I'm misunderstanding the instructions,
it seems the only methods of updating our installed base is having
everyone run the patch on their machines. Obviously this is unacceptable,
so I hope that I'm misunderstanding something. Isn't there at the least a
way to apply the .msp file to the .msi on the network, then modify the
original GPO to redeploy the application?

Thanks for any help!

-Zack-, who is relatively new to Group Policy Software Installation
 
Z

Zack

Just thought I'd chime in and say that I'm in the same boat. I have
Office 2003 deployed to my users via a compressed CD image on the network,
assigned to computers via GP along with a custom MST file created with the
CIW. Since we only have .msp files from the SP1 patch, I can't just
upgrade the application via GP, if I understand the situation correctly.

Given that installing via compressed CD image with local source caching is
Microsoft's recommended method of deployment for Office, why is it now a
headache to update to SP1? Unless I'm misunderstanding the instructions,
it seems the only methods of updating our installed base is having
everyone run the patch on their machines. Obviously this is unacceptable,
so I hope that I'm misunderstanding something. Isn't there at the least a
way to apply the .msp file to the .msi on the network, then modify the
original GPO to redeploy the application?

Thanks for any help!

-Zack-, who is relatively new to Group Policy Software Installation
 
Z

Zack

Just thought I'd chime in and say that I'm in the same boat. I have
Office 2003 deployed to my users via a compressed CD image on the network,
assigned to computers via GP along with a custom MST file created with the
CIW. Since we only have .msp files from the SP1 patch, I can't just
upgrade the application via GP, if I understand the situation correctly.

Given that installing via compressed CD image with local source caching is
Microsoft's recommended method of deployment for Office, why is it now a
headache to update to SP1? Unless I'm misunderstanding the instructions,
it seems the only methods of updating our installed base is having
everyone run the patch on their machines. Obviously this is unacceptable,
so I hope that I'm misunderstanding something. Isn't there at the least a
way to apply the .msp file to the .msi on the network, then modify the
original GPO to redeploy the application?

Thanks for any help!

-Zack-, who is relatively new to Group Policy Software Installation
 
Z

Zack

Arie,

As Joseph mentioned, when running this step on a compressed CD image, we
receive 'You have not entered a valid Product Key', and Setup fails. Even
when trying without the /qb option, the same error is given without any
option to actually *enter* a product key for the update.

Any other ideas? :(

Thanks,

-Zack-
 
Z

Zack

Arie,

As Joseph mentioned, when running this step on a compressed CD image, we
receive 'You have not entered a valid Product Key', and Setup fails. Even
when trying without the /qb option, the same error is given without any
option to actually *enter* a product key for the update.

Any other ideas? :(

Thanks,

-Zack-
 
Z

Zack

Arie,

As Joseph mentioned, when running this step on a compressed CD image, we
receive 'You have not entered a valid Product Key', and Setup fails. Even
when trying without the /qb option, the same error is given without any
option to actually *enter* a product key for the update.

Any other ideas? :(

Thanks,

-Zack-
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

deploy office 2003 0
Deply Compatibility Pack with SP1 0
Deploying Office 2007 Compatibility Pack with SP1 0
Office 2007 SP1 Application failure 0
Changing a setting in already-deployed Office 2007 0
Deploying PerUser settings via OCT created MSP files 0
Office 2007 SP1 1
Microsoft Update says Office SP1 needs to be installed. 0

Top