B
Bob Buckland ?:-\)
Hi Rob,
In earlier versions of Office there was a method for
doing that, but for Office 2003 you'll need to use
the System Builder (OEM) tools, Office Preinstall kit
from the website I mentioned previously,
http://microsoft.com/oem
========
In response to your last paragraph, I'm trying to do just the opposite. I
want to have one installation point, whether it is Admin or local set up, for
all our office to use, but I want the user to input the key that way they are
using their departments key, not one that is in the MST. I'm not sure If I
am being clear as to what I am looking for. With Office XP, my predessor
created one deployment package that any depart could use. Office would be
deployed to the machine and install with only a progress indicator. When the
installation was complete and the machine rebooted, the user would click on
Any of the applications, say Word. When they did, the Product Key dialog box
would open and the user would not be able to continue without inserting a
valid license key. My predessor is gone and I don't know how he did it and
there is no documentation. It would seem that I should be able to do the
same thing with Office 2k3. However, no matter how I create the deployment,
whether from CD image, or Administrative Installation point, the install will
not complete if I do not insert the product key in either of the MST's. It
will fail with the error "invalid key." If I do input the key, the app
installs and never asks for the key, so I would definitely be out of
compliace the application installed with only the key that was in the MST.
Barring any other way to complete this, I will end up creating a large
number of MST's for each department and each configuration, which is not
necessarily a big deal, just time consuming in the beginning and we run the
risk of users or technicians selecting the wrong MST for the wrong department
user, making determining compliance more difficult.
Thanks again Gentlemen.
Rob >>
--
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
In earlier versions of Office there was a method for
doing that, but for Office 2003 you'll need to use
the System Builder (OEM) tools, Office Preinstall kit
from the website I mentioned previously,
http://microsoft.com/oem
========
In response to your last paragraph, I'm trying to do just the opposite. I
want to have one installation point, whether it is Admin or local set up, for
all our office to use, but I want the user to input the key that way they are
using their departments key, not one that is in the MST. I'm not sure If I
am being clear as to what I am looking for. With Office XP, my predessor
created one deployment package that any depart could use. Office would be
deployed to the machine and install with only a progress indicator. When the
installation was complete and the machine rebooted, the user would click on
Any of the applications, say Word. When they did, the Product Key dialog box
would open and the user would not be able to continue without inserting a
valid license key. My predessor is gone and I don't know how he did it and
there is no documentation. It would seem that I should be able to do the
same thing with Office 2k3. However, no matter how I create the deployment,
whether from CD image, or Administrative Installation point, the install will
not complete if I do not insert the product key in either of the MST's. It
will fail with the error "invalid key." If I do input the key, the app
installs and never asks for the key, so I would definitely be out of
compliace the application installed with only the key that was in the MST.
Barring any other way to complete this, I will end up creating a large
number of MST's for each department and each configuration, which is not
necessarily a big deal, just time consuming in the beginning and we run the
risk of users or technicians selecting the wrong MST for the wrong department
user, making determining compliance more difficult.
Thanks again Gentlemen.
Rob >>
--
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