Office 2003 OEM deployment

[Josh]

Hi all,

Just wondering if anyone has any information on deploying an OEM licensed
Office 2003 package. At the moment, it installs fine and asks for the serial
number when you first start office / word /excel, but we would like this part
to be automated much the same way that the windows install is done.

Is there like an answer file that can be checked that matches computer name
with serial number, and inputs this accordingly?

Thank in advance,
Josh

 

[Bob Buckland ?:-\)]

Hi Josh,

You may want to check with the folks at http://microsoft.com/oem
for their tools for deploying OEM editions of Microsoft Office 2003
as well as the information in the Office 2003 Resource Kit (ORK)
http://microsoft.com/office/ork/2003. The ORK is aimed primarily
at folks using a Microsoft Volume License for Office (minimum buy is
5 Microsoft product [not all need to be Office] products, which gives
you the ability to enter the volume key during creation of an Office
Admin (setup/deployment source) point. http://microsoft.com/licensing

========
Hi all,

Just wondering if anyone has any information on deploying an OEM licensed
Office 2003 package. At the moment, it installs fine and asks for the serial
number when you first start office / word /excel, but we would like this part
to be automated much the same way that the windows install is done.

Is there like an answer file that can be checked that matches computer name
with serial number, and inputs this accordingly?

Thank in advance,
Josh >>
--
Let us know if this helped you,

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

For Everyday MS Office tips to "use right away" -
http://microsoft.com/events/series/administrativetipsandtricks.mspx

 

[Bob Buckland ?:-\)]

Hi Josh,

You may want to check with the folks at http://microsoft.com/oem
for their tools for deploying OEM editions of Microsoft Office 2003
as well as the information in the Office 2003 Resource Kit (ORK)
http://microsoft.com/office/ork/2003. The ORK is aimed primarily
at folks using a Microsoft Volume License for Office (minimum buy is
5 Microsoft product [not all need to be Office] products, which gives
you the ability to enter the volume key during creation of an Office
Admin (setup/deployment source) point. http://microsoft.com/licensing

========
Hi all,

Just wondering if anyone has any information on deploying an OEM licensed
Office 2003 package. At the moment, it installs fine and asks for the serial
number when you first start office / word /excel, but we would like this part
to be automated much the same way that the windows install is done.

Is there like an answer file that can be checked that matches computer name
with serial number, and inputs this accordingly?

Thank in advance,
Josh >>
--
Let us know if this helped you,

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

For Everyday MS Office tips to "use right away" -
http://microsoft.com/events/series/administrativetipsandtricks.mspx

 

[Bob Buckland ?:-\)]

Hi Josh,

You may want to check with the folks at http://microsoft.com/oem
for their tools for deploying OEM editions of Microsoft Office 2003
as well as the information in the Office 2003 Resource Kit (ORK)
http://microsoft.com/office/ork/2003. The ORK is aimed primarily
at folks using a Microsoft Volume License for Office (minimum buy is
5 Microsoft product [not all need to be Office] products, which gives
you the ability to enter the volume key during creation of an Office
Admin (setup/deployment source) point. http://microsoft.com/licensing

========
Hi all,

Just wondering if anyone has any information on deploying an OEM licensed
Office 2003 package. At the moment, it installs fine and asks for the serial
number when you first start office / word /excel, but we would like this part
to be automated much the same way that the windows install is done.

Is there like an answer file that can be checked that matches computer name
with serial number, and inputs this accordingly?

Thank in advance,
Josh >>
--
Let us know if this helped you,

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

For Everyday MS Office tips to "use right away" -
http://microsoft.com/events/series/administrativetipsandtricks.mspx

 

[Bob Buckland ?:-\)]

Hi Josh,

You may want to check with the folks at http://microsoft.com/oem
for their tools for deploying OEM editions of Microsoft Office 2003
as well as the information in the Office 2003 Resource Kit (ORK)
http://microsoft.com/office/ork/2003. The ORK is aimed primarily
at folks using a Microsoft Volume License for Office (minimum buy is
5 Microsoft product [not all need to be Office] products, which gives
you the ability to enter the volume key during creation of an Office
Admin (setup/deployment source) point. http://microsoft.com/licensing

========
Hi all,

Just wondering if anyone has any information on deploying an OEM licensed
Office 2003 package. At the moment, it installs fine and asks for the serial
number when you first start office / word /excel, but we would like this part
to be automated much the same way that the windows install is done.

Is there like an answer file that can be checked that matches computer name
with serial number, and inputs this accordingly?

Thank in advance,
Josh >>
--
Let us know if this helped you,

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

For Everyday MS Office tips to "use right away" -
http://microsoft.com/events/series/administrativetipsandtricks.mspx

 

[Bob Buckland ?:-\)]

Hi Josh,

You may want to check with the folks at http://microsoft.com/oem
for their tools for deploying OEM editions of Microsoft Office 2003
as well as the information in the Office 2003 Resource Kit (ORK)
http://microsoft.com/office/ork/2003. The ORK is aimed primarily
at folks using a Microsoft Volume License for Office (minimum buy is
5 Microsoft product [not all need to be Office] products, which gives
you the ability to enter the volume key during creation of an Office
Admin (setup/deployment source) point. http://microsoft.com/licensing

========
Hi all,

Just wondering if anyone has any information on deploying an OEM licensed
Office 2003 package. At the moment, it installs fine and asks for the serial
number when you first start office / word /excel, but we would like this part
to be automated much the same way that the windows install is done.

Is there like an answer file that can be checked that matches computer name
with serial number, and inputs this accordingly?

Thank in advance,
Josh >>
--
Let us know if this helped you,

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

For Everyday MS Office tips to "use right away" -
http://microsoft.com/events/series/administrativetipsandtricks.mspx

 

[Bob Buckland ?:-\)]

Hi Josh,

You may want to check with the folks at http://microsoft.com/oem
for their tools for deploying OEM editions of Microsoft Office 2003
as well as the information in the Office 2003 Resource Kit (ORK)
http://microsoft.com/office/ork/2003. The ORK is aimed primarily
at folks using a Microsoft Volume License for Office (minimum buy is
5 Microsoft product [not all need to be Office] products, which gives
you the ability to enter the volume key during creation of an Office
Admin (setup/deployment source) point. http://microsoft.com/licensing

========
Hi all,

Just wondering if anyone has any information on deploying an OEM licensed
Office 2003 package. At the moment, it installs fine and asks for the serial
number when you first start office / word /excel, but we would like this part
to be automated much the same way that the windows install is done.

Is there like an answer file that can be checked that matches computer name
with serial number, and inputs this accordingly?

Thank in advance,
Josh >>
--
Let us know if this helped you,

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

For Everyday MS Office tips to "use right away" -
http://microsoft.com/events/series/administrativetipsandtricks.mspx

 

[Bob Buckland ?:-\)]

Hi Josh,

You may want to check with the folks at http://microsoft.com/oem
for their tools for deploying OEM editions of Microsoft Office 2003
as well as the information in the Office 2003 Resource Kit (ORK)
http://microsoft.com/office/ork/2003. The ORK is aimed primarily
at folks using a Microsoft Volume License for Office (minimum buy is
5 Microsoft product [not all need to be Office] products, which gives
you the ability to enter the volume key during creation of an Office
Admin (setup/deployment source) point. http://microsoft.com/licensing

========
Hi all,

Just wondering if anyone has any information on deploying an OEM licensed
Office 2003 package. At the moment, it installs fine and asks for the serial
number when you first start office / word /excel, but we would like this part
to be automated much the same way that the windows install is done.

Is there like an answer file that can be checked that matches computer name
with serial number, and inputs this accordingly?

Thank in advance,
Josh >>
--
Let us know if this helped you,

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

For Everyday MS Office tips to "use right away" -
http://microsoft.com/events/series/administrativetipsandtricks.mspx

 

[Bob Buckland ?:-\)]

Hi Josh,

You may want to check with the folks at http://microsoft.com/oem
for their tools for deploying OEM editions of Microsoft Office 2003
as well as the information in the Office 2003 Resource Kit (ORK)
http://microsoft.com/office/ork/2003. The ORK is aimed primarily
at folks using a Microsoft Volume License for Office (minimum buy is
5 Microsoft product [not all need to be Office] products, which gives
you the ability to enter the volume key during creation of an Office
Admin (setup/deployment source) point. http://microsoft.com/licensing

========
Hi all,

Just wondering if anyone has any information on deploying an OEM licensed
Office 2003 package. At the moment, it installs fine and asks for the serial
number when you first start office / word /excel, but we would like this part
to be automated much the same way that the windows install is done.

Is there like an answer file that can be checked that matches computer name
with serial number, and inputs this accordingly?

Thank in advance,
Josh >>
--
Let us know if this helped you,

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

For Everyday MS Office tips to "use right away" -
http://microsoft.com/events/series/administrativetipsandtricks.mspx

 

[Bob Buckland ?:-\)]

Hi Josh,

You may want to check with the folks at http://microsoft.com/oem
for their tools for deploying OEM editions of Microsoft Office 2003
as well as the information in the Office 2003 Resource Kit (ORK)
http://microsoft.com/office/ork/2003. The ORK is aimed primarily
at folks using a Microsoft Volume License for Office (minimum buy is
5 Microsoft product [not all need to be Office] products, which gives
you the ability to enter the volume key during creation of an Office
Admin (setup/deployment source) point. http://microsoft.com/licensing

========
Hi all,

Just wondering if anyone has any information on deploying an OEM licensed
Office 2003 package. At the moment, it installs fine and asks for the serial
number when you first start office / word /excel, but we would like this part
to be automated much the same way that the windows install is done.

Is there like an answer file that can be checked that matches computer name
with serial number, and inputs this accordingly?

Thank in advance,
Josh >>
--
Let us know if this helped you,

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

For Everyday MS Office tips to "use right away" -
http://microsoft.com/events/series/administrativetipsandtricks.mspx

 

[Josh]

Hey Bob,

Thanks for the reply - unfortunately it doesn't much help me.. The licensing
has already been done, so we can't change that, and the OEM site I need to be
a MS partner to get into it. I think I read somewhere that MS took out the
option of doing an OEM deployment after Office XP, but I can't be sure.

I'm sort of resigned to the fact that it's not possible now which imho is
completely ridiculous. Taking away a feature like this because we pay half
the price of an open license? How dare we save money!

 

[Josh]

Hey Bob,

Thanks for the reply - unfortunately it doesn't much help me.. The licensing
has already been done, so we can't change that, and the OEM site I need to be
a MS partner to get into it. I think I read somewhere that MS took out the
option of doing an OEM deployment after Office XP, but I can't be sure.

I'm sort of resigned to the fact that it's not possible now which imho is
completely ridiculous. Taking away a feature like this because we pay half
the price of an open license? How dare we save money!

 

[Josh]

Hey Bob,

Thanks for the reply - unfortunately it doesn't much help me.. The licensing
has already been done, so we can't change that, and the OEM site I need to be
a MS partner to get into it. I think I read somewhere that MS took out the
option of doing an OEM deployment after Office XP, but I can't be sure.

I'm sort of resigned to the fact that it's not possible now which imho is
completely ridiculous. Taking away a feature like this because we pay half
the price of an open license? How dare we save money!

 

[Josh]

Hey Bob,

Thanks for the reply - unfortunately it doesn't much help me.. The licensing
has already been done, so we can't change that, and the OEM site I need to be
a MS partner to get into it. I think I read somewhere that MS took out the
option of doing an OEM deployment after Office XP, but I can't be sure.

I'm sort of resigned to the fact that it's not possible now which imho is
completely ridiculous. Taking away a feature like this because we pay half
the price of an open license? How dare we save money!

 

[Josh]

Hey Bob,

Thanks for the reply - unfortunately it doesn't much help me.. The licensing
has already been done, so we can't change that, and the OEM site I need to be
a MS partner to get into it. I think I read somewhere that MS took out the
option of doing an OEM deployment after Office XP, but I can't be sure.

I'm sort of resigned to the fact that it's not possible now which imho is
completely ridiculous. Taking away a feature like this because we pay half
the price of an open license? How dare we save money!

 

[Josh]

Hey Bob,

Thanks for the reply - unfortunately it doesn't much help me.. The licensing
has already been done, so we can't change that, and the OEM site I need to be
a MS partner to get into it. I think I read somewhere that MS took out the
option of doing an OEM deployment after Office XP, but I can't be sure.

I'm sort of resigned to the fact that it's not possible now which imho is
completely ridiculous. Taking away a feature like this because we pay half
the price of an open license? How dare we save money!

 

[Josh]

Hey Bob,

Thanks for the reply - unfortunately it doesn't much help me.. The licensing
has already been done, so we can't change that, and the OEM site I need to be
a MS partner to get into it. I think I read somewhere that MS took out the
option of doing an OEM deployment after Office XP, but I can't be sure.

I'm sort of resigned to the fact that it's not possible now which imho is
completely ridiculous. Taking away a feature like this because we pay half
the price of an open license? How dare we save money!

 

[Josh]

Hey Bob,

Thanks for the reply - unfortunately it doesn't much help me.. The licensing
has already been done, so we can't change that, and the OEM site I need to be
a MS partner to get into it. I think I read somewhere that MS took out the
option of doing an OEM deployment after Office XP, but I can't be sure.

I'm sort of resigned to the fact that it's not possible now which imho is
completely ridiculous. Taking away a feature like this because we pay half
the price of an open license? How dare we save money!

 

[Josh]

Hey Bob,

Thanks for the reply - unfortunately it doesn't much help me.. The licensing
has already been done, so we can't change that, and the OEM site I need to be
a MS partner to get into it. I think I read somewhere that MS took out the
option of doing an OEM deployment after Office XP, but I can't be sure.

I'm sort of resigned to the fact that it's not possible now which imho is
completely ridiculous. Taking away a feature like this because we pay half
the price of an open license? How dare we save money!