small network deployment of Office2003?

[LYoung]

I'm getting started in upgrading our school's computers from Office2K to
2003. I want to do it remotely, or blindly, or whatever - just so I don't
have to sit at each computer to install. I've been investigating and am
totally confused -- do I use Custom Installation Wizard? Administration
Installation Point? Office Profile Wizard? Remote Installation Services?
Group Policy Software Deployment?

Is there a how-to basics for a small network (<200 computers) deployment of
Office2003?

Thanks.
Lynda Young

 

[Will Butler]

-You can Create an administrative install point.
-Use the Custom Installation Wizard to create a transform that will have
the setup information (which components to install, EULA acceptance, and
Product Key). Save the resulting transform (.mst file) to your install
point.
-If you have a Active Directory domain you can then use Group policy to
assign the software to Users or Computers. Make sure to use the
"advanced" option and include your transform.

 

[Will Butler]

-You can Create an administrative install point.
-Use the Custom Installation Wizard to create a transform that will have
the setup information (which components to install, EULA acceptance, and
Product Key). Save the resulting transform (.mst file) to your install
point.
-If you have a Active Directory domain you can then use Group policy to
assign the software to Users or Computers. Make sure to use the
"advanced" option and include your transform.

 

[Will Butler]

-You can Create an administrative install point.
-Use the Custom Installation Wizard to create a transform that will have
the setup information (which components to install, EULA acceptance, and
Product Key). Save the resulting transform (.mst file) to your install
point.
-If you have a Active Directory domain you can then use Group policy to
assign the software to Users or Computers. Make sure to use the
"advanced" option and include your transform.

 

[Will Butler]

-You can Create an administrative install point.
-Use the Custom Installation Wizard to create a transform that will have
the setup information (which components to install, EULA acceptance, and
Product Key). Save the resulting transform (.mst file) to your install
point.
-If you have a Active Directory domain you can then use Group policy to
assign the software to Users or Computers. Make sure to use the
"advanced" option and include your transform.

 

[LYoung]

Thanks, Will - this gives me a starting point!

-You can Create an administrative install point.
-Use the Custom Installation Wizard to create a transform that will have
the setup information (which components to install, EULA acceptance, and
Product Key). Save the resulting transform (.mst file) to your install
point.
-If you have a Active Directory domain you can then use Group policy to
assign the software to Users or Computers. Make sure to use the
"advanced" option and include your transform.

 

[LYoung]

Thanks, Will - this gives me a starting point!

-You can Create an administrative install point.
-Use the Custom Installation Wizard to create a transform that will have
the setup information (which components to install, EULA acceptance, and
Product Key). Save the resulting transform (.mst file) to your install
point.
-If you have a Active Directory domain you can then use Group policy to
assign the software to Users or Computers. Make sure to use the
"advanced" option and include your transform.

 

[LYoung]

Thanks, Will - this gives me a starting point!

-You can Create an administrative install point.
-Use the Custom Installation Wizard to create a transform that will have
the setup information (which components to install, EULA acceptance, and
Product Key). Save the resulting transform (.mst file) to your install
point.
-If you have a Active Directory domain you can then use Group policy to
assign the software to Users or Computers. Make sure to use the
"advanced" option and include your transform.

 

[LYoung]

Thanks, Will - this gives me a starting point!

-You can Create an administrative install point.
-Use the Custom Installation Wizard to create a transform that will have
the setup information (which components to install, EULA acceptance, and
Product Key). Save the resulting transform (.mst file) to your install
point.
-If you have a Active Directory domain you can then use Group policy to
assign the software to Users or Computers. Make sure to use the
"advanced" option and include your transform.

 

[Bob Buckland ?:-\)]

Hi Lynda,

To add one bit to Will's reply, you may want to review the information in the Office 2003 Resource Kit (ORK) through
http://microsoft.com/office/ork/2003 on the Office Admin Point and the Customization tools that were mentioned.

You need a volume license key with the Office product to be able to create the Office Admin point.

==============
Thanks, Will - this gives me a starting point! >>
--

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

 

[Bob Buckland ?:-\)]

Hi Lynda,

To add one bit to Will's reply, you may want to review the information in the Office 2003 Resource Kit (ORK) through
http://microsoft.com/office/ork/2003 on the Office Admin Point and the Customization tools that were mentioned.

You need a volume license key with the Office product to be able to create the Office Admin point.

==============
Thanks, Will - this gives me a starting point! >>
--

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

 

[Bob Buckland ?:-\)]

Hi Lynda,

To add one bit to Will's reply, you may want to review the information in the Office 2003 Resource Kit (ORK) through
http://microsoft.com/office/ork/2003 on the Office Admin Point and the Customization tools that were mentioned.

You need a volume license key with the Office product to be able to create the Office Admin point.

==============
Thanks, Will - this gives me a starting point! >>
--

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

 

[Bob Buckland ?:-\)]

Hi Lynda,

To add one bit to Will's reply, you may want to review the information in the Office 2003 Resource Kit (ORK) through
http://microsoft.com/office/ork/2003 on the Office Admin Point and the Customization tools that were mentioned.

You need a volume license key with the Office product to be able to create the Office Admin point.

==============
Thanks, Will - this gives me a starting point! >>
--

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*