How to add Key Software in th .ini file

[Wingpat]

Hello:
I have all my software installed on a partition on my server. The plan would
be to be able to click on setup.exe to start the installation without being
prompted for the key. I tried to add "PIDKEY"1234567890" to the "Setup.ini"
file but it didn't work.
Any suggestion?
Thank you in advance for your reply.

 

[Lanwench [MVP - Exchange]]

Hello:
I have all my software installed on a partition on my server. The
plan would be to be able to click on setup.exe to start the
installation without being prompted for the key. I tried to add
"PIDKEY"1234567890" to the "Setup.ini" file but it didn't work.
Any suggestion?
Thank you in advance for your reply.

You haven't mentioned your version of Office, but if it isn't an OEM copy,
you can do an administrative install to the server once, while logged in as
an administrator, and then run setup for users from there.

Start | Run | <full path to Office CD's setup.exe file> /a <enter>

 

[Lanwench [MVP - Exchange]]

Hello:
I have all my software installed on a partition on my server. The
plan would be to be able to click on setup.exe to start the
installation without being prompted for the key. I tried to add
"PIDKEY"1234567890" to the "Setup.ini" file but it didn't work.
Any suggestion?
Thank you in advance for your reply.

You haven't mentioned your version of Office, but if it isn't an OEM copy,
you can do an administrative install to the server once, while logged in as
an administrator, and then run setup for users from there.

Start | Run | <full path to Office CD's setup.exe file> /a <enter>

 

[Lanwench [MVP - Exchange]]

Hello:
I have all my software installed on a partition on my server. The
plan would be to be able to click on setup.exe to start the
installation without being prompted for the key. I tried to add
"PIDKEY"1234567890" to the "Setup.ini" file but it didn't work.
Any suggestion?
Thank you in advance for your reply.

You haven't mentioned your version of Office, but if it isn't an OEM copy,
you can do an administrative install to the server once, while logged in as
an administrator, and then run setup for users from there.

Start | Run | <full path to Office CD's setup.exe file> /a <enter>

 

[Lanwench [MVP - Exchange]]

Hello:
I have all my software installed on a partition on my server. The
plan would be to be able to click on setup.exe to start the
installation without being prompted for the key. I tried to add
"PIDKEY"1234567890" to the "Setup.ini" file but it didn't work.
Any suggestion?
Thank you in advance for your reply.

You haven't mentioned your version of Office, but if it isn't an OEM copy,
you can do an administrative install to the server once, while logged in as
an administrator, and then run setup for users from there.

Start | Run | <full path to Office CD's setup.exe file> /a <enter>

 

[Lanwench [MVP - Exchange]]

Hello:
I have all my software installed on a partition on my server. The
plan would be to be able to click on setup.exe to start the
installation without being prompted for the key. I tried to add
"PIDKEY"1234567890" to the "Setup.ini" file but it didn't work.
Any suggestion?
Thank you in advance for your reply.

You haven't mentioned your version of Office, but if it isn't an OEM copy,
you can do an administrative install to the server once, while logged in as
an administrator, and then run setup for users from there.

Start | Run | <full path to Office CD's setup.exe file> /a <enter>

 

[Lanwench [MVP - Exchange]]

Hello:
I have all my software installed on a partition on my server. The
plan would be to be able to click on setup.exe to start the
installation without being prompted for the key. I tried to add
"PIDKEY"1234567890" to the "Setup.ini" file but it didn't work.
Any suggestion?
Thank you in advance for your reply.

You haven't mentioned your version of Office, but if it isn't an OEM copy,
you can do an administrative install to the server once, while logged in as
an administrator, and then run setup for users from there.

Start | Run | <full path to Office CD's setup.exe file> /a <enter>

 

[Lanwench [MVP - Exchange]]

Hello:
I have all my software installed on a partition on my server. The
plan would be to be able to click on setup.exe to start the
installation without being prompted for the key. I tried to add
"PIDKEY"1234567890" to the "Setup.ini" file but it didn't work.
Any suggestion?
Thank you in advance for your reply.

You haven't mentioned your version of Office, but if it isn't an OEM copy,
you can do an administrative install to the server once, while logged in as
an administrator, and then run setup for users from there.

Start | Run | <full path to Office CD's setup.exe file> /a <enter>

 

[Lanwench [MVP - Exchange]]

Hello:
I have all my software installed on a partition on my server. The
plan would be to be able to click on setup.exe to start the
installation without being prompted for the key. I tried to add
"PIDKEY"1234567890" to the "Setup.ini" file but it didn't work.
Any suggestion?
Thank you in advance for your reply.

You haven't mentioned your version of Office, but if it isn't an OEM copy,
you can do an administrative install to the server once, while logged in as
an administrator, and then run setup for users from there.

Start | Run | <full path to Office CD's setup.exe file> /a <enter>

 

[Lanwench [MVP - Exchange]]

Hello:
I have all my software installed on a partition on my server. The
plan would be to be able to click on setup.exe to start the
installation without being prompted for the key. I tried to add
"PIDKEY"1234567890" to the "Setup.ini" file but it didn't work.
Any suggestion?
Thank you in advance for your reply.

You haven't mentioned your version of Office, but if it isn't an OEM copy,
you can do an administrative install to the server once, while logged in as
an administrator, and then run setup for users from there.

Start | Run | <full path to Office CD's setup.exe file> /a <enter>

 

[Michael Bednarek]

You haven't mentioned your version of Office, but if it isn't an OEM copy,
you can do an administrative install to the server once, while logged in as
an administrator, and then run setup for users from there.

Start | Run | <full path to Office CD's setup.exe file> /a <enter>

I think you'll find that this works only for VLK versions; from
<http://office.microsoft.com/en-us/assistance/HA011401931033.aspx>:
Note Only editions of Office 2003 acquired through a
Volume License agreement or other non-retail channel allow you
to create an administrative installation point. You cannot run
Setup.exe in administrative mode (/a) with an Office 2003 retail
edition.

If the OP does have a VLK, that link provides information on how
to create an Administrative Installation Point.

However, this will work for retail versions:
SETUP COMPANYNAME="company" USERNAME="user" PIDKEY=pidkey

 

[Michael Bednarek]

You haven't mentioned your version of Office, but if it isn't an OEM copy,
you can do an administrative install to the server once, while logged in as
an administrator, and then run setup for users from there.

Start | Run | <full path to Office CD's setup.exe file> /a <enter>

I think you'll find that this works only for VLK versions; from
<http://office.microsoft.com/en-us/assistance/HA011401931033.aspx>:
Note Only editions of Office 2003 acquired through a
Volume License agreement or other non-retail channel allow you
to create an administrative installation point. You cannot run
Setup.exe in administrative mode (/a) with an Office 2003 retail
edition.

If the OP does have a VLK, that link provides information on how
to create an Administrative Installation Point.

However, this will work for retail versions:
SETUP COMPANYNAME="company" USERNAME="user" PIDKEY=pidkey

 

[Michael Bednarek]

You haven't mentioned your version of Office, but if it isn't an OEM copy,
you can do an administrative install to the server once, while logged in as
an administrator, and then run setup for users from there.

Start | Run | <full path to Office CD's setup.exe file> /a <enter>

I think you'll find that this works only for VLK versions; from
<http://office.microsoft.com/en-us/assistance/HA011401931033.aspx>:
Note Only editions of Office 2003 acquired through a
Volume License agreement or other non-retail channel allow you
to create an administrative installation point. You cannot run
Setup.exe in administrative mode (/a) with an Office 2003 retail
edition.

If the OP does have a VLK, that link provides information on how
to create an Administrative Installation Point.

However, this will work for retail versions:
SETUP COMPANYNAME="company" USERNAME="user" PIDKEY=pidkey

 

[Michael Bednarek]

You haven't mentioned your version of Office, but if it isn't an OEM copy,
you can do an administrative install to the server once, while logged in as
an administrator, and then run setup for users from there.

Start | Run | <full path to Office CD's setup.exe file> /a <enter>

I think you'll find that this works only for VLK versions; from
<http://office.microsoft.com/en-us/assistance/HA011401931033.aspx>:
Note Only editions of Office 2003 acquired through a
Volume License agreement or other non-retail channel allow you
to create an administrative installation point. You cannot run
Setup.exe in administrative mode (/a) with an Office 2003 retail
edition.

If the OP does have a VLK, that link provides information on how
to create an Administrative Installation Point.

However, this will work for retail versions:
SETUP COMPANYNAME="company" USERNAME="user" PIDKEY=pidkey

 

[Michael Bednarek]

You haven't mentioned your version of Office, but if it isn't an OEM copy,
you can do an administrative install to the server once, while logged in as
an administrator, and then run setup for users from there.

Start | Run | <full path to Office CD's setup.exe file> /a <enter>

I think you'll find that this works only for VLK versions; from
<http://office.microsoft.com/en-us/assistance/HA011401931033.aspx>:
Note Only editions of Office 2003 acquired through a
Volume License agreement or other non-retail channel allow you
to create an administrative installation point. You cannot run
Setup.exe in administrative mode (/a) with an Office 2003 retail
edition.

If the OP does have a VLK, that link provides information on how
to create an Administrative Installation Point.

However, this will work for retail versions:
SETUP COMPANYNAME="company" USERNAME="user" PIDKEY=pidkey

 

[Michael Bednarek]

You haven't mentioned your version of Office, but if it isn't an OEM copy,
you can do an administrative install to the server once, while logged in as
an administrator, and then run setup for users from there.

Start | Run | <full path to Office CD's setup.exe file> /a <enter>

I think you'll find that this works only for VLK versions; from
<http://office.microsoft.com/en-us/assistance/HA011401931033.aspx>:
Note Only editions of Office 2003 acquired through a
Volume License agreement or other non-retail channel allow you
to create an administrative installation point. You cannot run
Setup.exe in administrative mode (/a) with an Office 2003 retail
edition.

If the OP does have a VLK, that link provides information on how
to create an Administrative Installation Point.

However, this will work for retail versions:
SETUP COMPANYNAME="company" USERNAME="user" PIDKEY=pidkey

 

[Michael Bednarek]

You haven't mentioned your version of Office, but if it isn't an OEM copy,
you can do an administrative install to the server once, while logged in as
an administrator, and then run setup for users from there.

Start | Run | <full path to Office CD's setup.exe file> /a <enter>

I think you'll find that this works only for VLK versions; from
<http://office.microsoft.com/en-us/assistance/HA011401931033.aspx>:
Note Only editions of Office 2003 acquired through a
Volume License agreement or other non-retail channel allow you
to create an administrative installation point. You cannot run
Setup.exe in administrative mode (/a) with an Office 2003 retail
edition.

If the OP does have a VLK, that link provides information on how
to create an Administrative Installation Point.

However, this will work for retail versions:
SETUP COMPANYNAME="company" USERNAME="user" PIDKEY=pidkey

 

[Michael Bednarek]

You haven't mentioned your version of Office, but if it isn't an OEM copy,
you can do an administrative install to the server once, while logged in as
an administrator, and then run setup for users from there.

Start | Run | <full path to Office CD's setup.exe file> /a <enter>

I think you'll find that this works only for VLK versions; from
<http://office.microsoft.com/en-us/assistance/HA011401931033.aspx>:
Note Only editions of Office 2003 acquired through a
Volume License agreement or other non-retail channel allow you
to create an administrative installation point. You cannot run
Setup.exe in administrative mode (/a) with an Office 2003 retail
edition.

If the OP does have a VLK, that link provides information on how
to create an Administrative Installation Point.

However, this will work for retail versions:
SETUP COMPANYNAME="company" USERNAME="user" PIDKEY=pidkey

 

[Michael Bednarek]

You haven't mentioned your version of Office, but if it isn't an OEM copy,
you can do an administrative install to the server once, while logged in as
an administrator, and then run setup for users from there.

Start | Run | <full path to Office CD's setup.exe file> /a <enter>

I think you'll find that this works only for VLK versions; from
<http://office.microsoft.com/en-us/assistance/HA011401931033.aspx>:
Note Only editions of Office 2003 acquired through a
Volume License agreement or other non-retail channel allow you
to create an administrative installation point. You cannot run
Setup.exe in administrative mode (/a) with an Office 2003 retail
edition.

If the OP does have a VLK, that link provides information on how
to create an Administrative Installation Point.

However, this will work for retail versions:
SETUP COMPANYNAME="company" USERNAME="user" PIDKEY=pidkey

 

[Lanwench [MVP - Exchange]]

I think you'll find that this works only for VLK versions; from
<http://office.microsoft.com/en-us/assistance/HA011401931033.aspx>:
Note Only editions of Office 2003 acquired through a
Volume License agreement or other non-retail channel allow you
to create an administrative installation point. You cannot run
Setup.exe in administrative mode (/a) with an Office 2003 retail
edition.

If the OP does have a VLK, that link provides information on how
to create an Administrative Installation Point.

However, this will work for retail versions:
SETUP COMPANYNAME="company" USERNAME="user" PIDKEY=pidkey

I'll trust you on this one - I've never tried it with anything but a volume
license version. It makes sense - if you want to have Office on multiple
PCs, you have to have enough licenses - so why would one *not* have a volume
license copy at that point?