MSI admin update for OfficXP_pro SP3 results 860mb directory

[neo [mvp outlook]]

I think you just mentioned what the problem is, you are trying to slipstream
a service pack to a cached CD copy and not an administrative install point.
I think the best you can do with a cached CD copy is chain the install of
the service pack.

 

[neo [mvp outlook]]

I think you just mentioned what the problem is, you are trying to slipstream
a service pack to a cached CD copy and not an administrative install point.
I think the best you can do with a cached CD copy is chain the install of
the service pack.

 

[neo [mvp outlook]]

I think you just mentioned what the problem is, you are trying to slipstream
a service pack to a cached CD copy and not an administrative install point.
I think the best you can do with a cached CD copy is chain the install of
the service pack.

 

[neo [mvp outlook]]

I think you just mentioned what the problem is, you are trying to slipstream
a service pack to a cached CD copy and not an administrative install point.
I think the best you can do with a cached CD copy is chain the install of
the service pack.

 

[neo [mvp outlook]]

I think you just mentioned what the problem is, you are trying to slipstream
a service pack to a cached CD copy and not an administrative install point.
I think the best you can do with a cached CD copy is chain the install of
the service pack.

 

[neo [mvp outlook]]

I think you just mentioned what the problem is, you are trying to slipstream
a service pack to a cached CD copy and not an administrative install point.
I think the best you can do with a cached CD copy is chain the install of
the service pack.

 

[neo [mvp outlook]]

I think you just mentioned what the problem is, you are trying to slipstream
a service pack to a cached CD copy and not an administrative install point.
I think the best you can do with a cached CD copy is chain the install of
the service pack.

 

[neo [mvp outlook]]

I think you just mentioned what the problem is, you are trying to slipstream
a service pack to a cached CD copy and not an administrative install point.
I think the best you can do with a cached CD copy is chain the install of
the service pack.

 

[Sean Mercer, MCSE]

yep, you are right. I think you replied to me in a different group, I
posted in serveral other groups and will now have to find those posts and
post finished replies. If I remember correctly, you posted in another group
to look at: http://www.petri.co.il/office_xp_sp_slipstreaming.htm This
website let me to know of the new command in OfficeXp setup /a. Odly enogh
this website states that it is uncertain if it is possible to slipstream the
service pack into office2000. The msiexec commands I mentioned in my post
worked perfectly for office2000 and windows 2000.

Anyway, I created the admin install point on my hard drive with setup /a and
applied the service pack and then used the resource kit to customize the
installation and profile, and I'm in business. I mailed off the CD to the
customer today. It did leave me with one problem though that I didn't have
with my word2000 cd. After completing the process for OfficeXP, the custom
CD no longer prompted for a keycode, as it used the product key I used with
the admin install but the Office2000 CD didn't do that. It prompted for the
keycode, which is good because the customer I gave the CD to could enter his
own valid licensed product key.

I am surprised it took so long for someone to tell me something so simple
that I have to apply the .msp to an admin point created from setup /a and
then it would work. Thank you for replying! I think that I will just paste
this post into the other newsgroups that I requested help from to simplify
my response. This response is originally written to
"microsoft.public.office" in reply to "neo[mvp outlook]"

 

[Sean Mercer, MCSE]

yep, you are right. I think you replied to me in a different group, I
posted in serveral other groups and will now have to find those posts and
post finished replies. If I remember correctly, you posted in another group
to look at: http://www.petri.co.il/office_xp_sp_slipstreaming.htm This
website let me to know of the new command in OfficeXp setup /a. Odly enogh
this website states that it is uncertain if it is possible to slipstream the
service pack into office2000. The msiexec commands I mentioned in my post
worked perfectly for office2000 and windows 2000.

Anyway, I created the admin install point on my hard drive with setup /a and
applied the service pack and then used the resource kit to customize the
installation and profile, and I'm in business. I mailed off the CD to the
customer today. It did leave me with one problem though that I didn't have
with my word2000 cd. After completing the process for OfficeXP, the custom
CD no longer prompted for a keycode, as it used the product key I used with
the admin install but the Office2000 CD didn't do that. It prompted for the
keycode, which is good because the customer I gave the CD to could enter his
own valid licensed product key.

I am surprised it took so long for someone to tell me something so simple
that I have to apply the .msp to an admin point created from setup /a and
then it would work. Thank you for replying! I think that I will just paste
this post into the other newsgroups that I requested help from to simplify
my response. This response is originally written to
"microsoft.public.office" in reply to "neo[mvp outlook]"

 

[Sean Mercer, MCSE]

yep, you are right. I think you replied to me in a different group, I
posted in serveral other groups and will now have to find those posts and
post finished replies. If I remember correctly, you posted in another group
to look at: http://www.petri.co.il/office_xp_sp_slipstreaming.htm This
website let me to know of the new command in OfficeXp setup /a. Odly enogh
this website states that it is uncertain if it is possible to slipstream the
service pack into office2000. The msiexec commands I mentioned in my post
worked perfectly for office2000 and windows 2000.

Anyway, I created the admin install point on my hard drive with setup /a and
applied the service pack and then used the resource kit to customize the
installation and profile, and I'm in business. I mailed off the CD to the
customer today. It did leave me with one problem though that I didn't have
with my word2000 cd. After completing the process for OfficeXP, the custom
CD no longer prompted for a keycode, as it used the product key I used with
the admin install but the Office2000 CD didn't do that. It prompted for the
keycode, which is good because the customer I gave the CD to could enter his
own valid licensed product key.

I am surprised it took so long for someone to tell me something so simple
that I have to apply the .msp to an admin point created from setup /a and
then it would work. Thank you for replying! I think that I will just paste
this post into the other newsgroups that I requested help from to simplify
my response. This response is originally written to
"microsoft.public.office" in reply to "neo[mvp outlook]"

 

[Sean Mercer, MCSE]

yep, you are right. I think you replied to me in a different group, I
posted in serveral other groups and will now have to find those posts and
post finished replies. If I remember correctly, you posted in another group
to look at: http://www.petri.co.il/office_xp_sp_slipstreaming.htm This
website let me to know of the new command in OfficeXp setup /a. Odly enogh
this website states that it is uncertain if it is possible to slipstream the
service pack into office2000. The msiexec commands I mentioned in my post
worked perfectly for office2000 and windows 2000.

Anyway, I created the admin install point on my hard drive with setup /a and
applied the service pack and then used the resource kit to customize the
installation and profile, and I'm in business. I mailed off the CD to the
customer today. It did leave me with one problem though that I didn't have
with my word2000 cd. After completing the process for OfficeXP, the custom
CD no longer prompted for a keycode, as it used the product key I used with
the admin install but the Office2000 CD didn't do that. It prompted for the
keycode, which is good because the customer I gave the CD to could enter his
own valid licensed product key.

I am surprised it took so long for someone to tell me something so simple
that I have to apply the .msp to an admin point created from setup /a and
then it would work. Thank you for replying! I think that I will just paste
this post into the other newsgroups that I requested help from to simplify
my response. This response is originally written to
"microsoft.public.office" in reply to "neo[mvp outlook]"

 

[Sean Mercer, MCSE]

yep, you are right. I think you replied to me in a different group, I
posted in serveral other groups and will now have to find those posts and
post finished replies. If I remember correctly, you posted in another group
to look at: http://www.petri.co.il/office_xp_sp_slipstreaming.htm This
website let me to know of the new command in OfficeXp setup /a. Odly enogh
this website states that it is uncertain if it is possible to slipstream the
service pack into office2000. The msiexec commands I mentioned in my post
worked perfectly for office2000 and windows 2000.

Anyway, I created the admin install point on my hard drive with setup /a and
applied the service pack and then used the resource kit to customize the
installation and profile, and I'm in business. I mailed off the CD to the
customer today. It did leave me with one problem though that I didn't have
with my word2000 cd. After completing the process for OfficeXP, the custom
CD no longer prompted for a keycode, as it used the product key I used with
the admin install but the Office2000 CD didn't do that. It prompted for the
keycode, which is good because the customer I gave the CD to could enter his
own valid licensed product key.

I am surprised it took so long for someone to tell me something so simple
that I have to apply the .msp to an admin point created from setup /a and
then it would work. Thank you for replying! I think that I will just paste
this post into the other newsgroups that I requested help from to simplify
my response. This response is originally written to
"microsoft.public.office" in reply to "neo[mvp outlook]"

 

[Sean Mercer, MCSE]

yep, you are right. I think you replied to me in a different group, I
posted in serveral other groups and will now have to find those posts and
post finished replies. If I remember correctly, you posted in another group
to look at: http://www.petri.co.il/office_xp_sp_slipstreaming.htm This
website let me to know of the new command in OfficeXp setup /a. Odly enogh
this website states that it is uncertain if it is possible to slipstream the
service pack into office2000. The msiexec commands I mentioned in my post
worked perfectly for office2000 and windows 2000.

Anyway, I created the admin install point on my hard drive with setup /a and
applied the service pack and then used the resource kit to customize the
installation and profile, and I'm in business. I mailed off the CD to the
customer today. It did leave me with one problem though that I didn't have
with my word2000 cd. After completing the process for OfficeXP, the custom
CD no longer prompted for a keycode, as it used the product key I used with
the admin install but the Office2000 CD didn't do that. It prompted for the
keycode, which is good because the customer I gave the CD to could enter his
own valid licensed product key.

I am surprised it took so long for someone to tell me something so simple
that I have to apply the .msp to an admin point created from setup /a and
then it would work. Thank you for replying! I think that I will just paste
this post into the other newsgroups that I requested help from to simplify
my response. This response is originally written to
"microsoft.public.office" in reply to "neo[mvp outlook]"

 

[Sean Mercer, MCSE]

yep, you are right. I think you replied to me in a different group, I
posted in serveral other groups and will now have to find those posts and
post finished replies. If I remember correctly, you posted in another group
to look at: http://www.petri.co.il/office_xp_sp_slipstreaming.htm This
website let me to know of the new command in OfficeXp setup /a. Odly enogh
this website states that it is uncertain if it is possible to slipstream the
service pack into office2000. The msiexec commands I mentioned in my post
worked perfectly for office2000 and windows 2000.

Anyway, I created the admin install point on my hard drive with setup /a and
applied the service pack and then used the resource kit to customize the
installation and profile, and I'm in business. I mailed off the CD to the
customer today. It did leave me with one problem though that I didn't have
with my word2000 cd. After completing the process for OfficeXP, the custom
CD no longer prompted for a keycode, as it used the product key I used with
the admin install but the Office2000 CD didn't do that. It prompted for the
keycode, which is good because the customer I gave the CD to could enter his
own valid licensed product key.

I am surprised it took so long for someone to tell me something so simple
that I have to apply the .msp to an admin point created from setup /a and
then it would work. Thank you for replying! I think that I will just paste
this post into the other newsgroups that I requested help from to simplify
my response. This response is originally written to
"microsoft.public.office" in reply to "neo[mvp outlook]"

 

[Sean Mercer, MCSE]

yep, you are right. I think you replied to me in a different group, I
posted in serveral other groups and will now have to find those posts and
post finished replies. If I remember correctly, you posted in another group
to look at: http://www.petri.co.il/office_xp_sp_slipstreaming.htm This
website let me to know of the new command in OfficeXp setup /a. Odly enogh
this website states that it is uncertain if it is possible to slipstream the
service pack into office2000. The msiexec commands I mentioned in my post
worked perfectly for office2000 and windows 2000.

Anyway, I created the admin install point on my hard drive with setup /a and
applied the service pack and then used the resource kit to customize the
installation and profile, and I'm in business. I mailed off the CD to the
customer today. It did leave me with one problem though that I didn't have
with my word2000 cd. After completing the process for OfficeXP, the custom
CD no longer prompted for a keycode, as it used the product key I used with
the admin install but the Office2000 CD didn't do that. It prompted for the
keycode, which is good because the customer I gave the CD to could enter his
own valid licensed product key.

I am surprised it took so long for someone to tell me something so simple
that I have to apply the .msp to an admin point created from setup /a and
then it would work. Thank you for replying! I think that I will just paste
this post into the other newsgroups that I requested help from to simplify
my response. This response is originally written to
"microsoft.public.office" in reply to "neo[mvp outlook]"

 

[Sean Mercer, MCSE]

yep, you are right. I think you replied to me in a different group, I
posted in serveral other groups and will now have to find those posts and
post finished replies. If I remember correctly, you posted in another group
to look at: http://www.petri.co.il/office_xp_sp_slipstreaming.htm This
website let me to know of the new command in OfficeXp setup /a. Odly enogh
this website states that it is uncertain if it is possible to slipstream the
service pack into office2000. The msiexec commands I mentioned in my post
worked perfectly for office2000 and windows 2000.

Anyway, I created the admin install point on my hard drive with setup /a and
applied the service pack and then used the resource kit to customize the
installation and profile, and I'm in business. I mailed off the CD to the
customer today. It did leave me with one problem though that I didn't have
with my word2000 cd. After completing the process for OfficeXP, the custom
CD no longer prompted for a keycode, as it used the product key I used with
the admin install but the Office2000 CD didn't do that. It prompted for the
keycode, which is good because the customer I gave the CD to could enter his
own valid licensed product key.

I am surprised it took so long for someone to tell me something so simple
that I have to apply the .msp to an admin point created from setup /a and
then it would work. Thank you for replying! I think that I will just paste
this post into the other newsgroups that I requested help from to simplify
my response. This response is originally written to
"microsoft.public.office" in reply to "neo[mvp outlook]"

 

[Sean Mercer, MCSE]

Bob Buckland referenced a web site that provided the answer to my problem
(A): which is to correct a file size problem so as to make it possible to
burn to CD. This website is:"
http://www.petri.co.il/office_xp_sp_slipstreaming.htm "This website let me
to know of the new command in OfficeXp called: "setup /a". Oddly enough
this website states that it is uncertain if it is possible to slipstream a
service pack into office2000. The msiexec commands I mentioned in my post
worked perfectly for office2000 and windows 2000.
Anyway, I created the admin install point on my hard drive with setup /a and
applied the service pack and then used the
resource kit to customize the installation and profile, and I'm in business.
I mailed off the CD to the customer today. It did leave me with one problem
though that I didn't have with my word2000 cd. (B) After completing the
process for OfficeXP, the custom CD no longer prompted for a keycode, as it
used the product key I used with the admin install (setup /a) but the
Office2000 CD didn't do that as it prompted for the keycode, which is good
because the customer I gave the CD to could enter his own valid licensed
product key. I am surprised it took so long for someone to tell me
something so simple that I have to apply the .msp to an admin point created
from setup /a and then it would work. Thank you for replying, Bob Buckland!
MS Office System Products MVP
Anyone reading these post can compare the original webpage from Microsoft
describing the procedure to the one that Bob referenced. Microsoft:
"http://office.microsoft.com/en-us/assistance/HA011525351033.aspx" Bob:
http://www.petri.co.il/office_xp_sp_slipstreaming.htm" Sorry for multiple
posts, I didn't do a good job of tracking myself. I posted in 5 news groups,
they should all be covered in this post.

 

[Sean Mercer, MCSE]

Bob Buckland referenced a web site that provided the answer to my problem
(A): which is to correct a file size problem so as to make it possible to
burn to CD. This website is:"
http://www.petri.co.il/office_xp_sp_slipstreaming.htm "This website let me
to know of the new command in OfficeXp called: "setup /a". Oddly enough
this website states that it is uncertain if it is possible to slipstream a
service pack into office2000. The msiexec commands I mentioned in my post
worked perfectly for office2000 and windows 2000.
Anyway, I created the admin install point on my hard drive with setup /a and
applied the service pack and then used the
resource kit to customize the installation and profile, and I'm in business.
I mailed off the CD to the customer today. It did leave me with one problem
though that I didn't have with my word2000 cd. (B) After completing the
process for OfficeXP, the custom CD no longer prompted for a keycode, as it
used the product key I used with the admin install (setup /a) but the
Office2000 CD didn't do that as it prompted for the keycode, which is good
because the customer I gave the CD to could enter his own valid licensed
product key. I am surprised it took so long for someone to tell me
something so simple that I have to apply the .msp to an admin point created
from setup /a and then it would work. Thank you for replying, Bob Buckland!
MS Office System Products MVP
Anyone reading these post can compare the original webpage from Microsoft
describing the procedure to the one that Bob referenced. Microsoft:
"http://office.microsoft.com/en-us/assistance/HA011525351033.aspx" Bob:
http://www.petri.co.il/office_xp_sp_slipstreaming.htm" Sorry for multiple
posts, I didn't do a good job of tracking myself. I posted in 5 news groups,
they should all be covered in this post.

 

[Sean Mercer, MCSE]

Bob Buckland referenced a web site that provided the answer to my problem
(A): which is to correct a file size problem so as to make it possible to
burn to CD. This website is:"
http://www.petri.co.il/office_xp_sp_slipstreaming.htm "This website let me
to know of the new command in OfficeXp called: "setup /a". Oddly enough
this website states that it is uncertain if it is possible to slipstream a
service pack into office2000. The msiexec commands I mentioned in my post
worked perfectly for office2000 and windows 2000.
Anyway, I created the admin install point on my hard drive with setup /a and
applied the service pack and then used the
resource kit to customize the installation and profile, and I'm in business.
I mailed off the CD to the customer today. It did leave me with one problem
though that I didn't have with my word2000 cd. (B) After completing the
process for OfficeXP, the custom CD no longer prompted for a keycode, as it
used the product key I used with the admin install (setup /a) but the
Office2000 CD didn't do that as it prompted for the keycode, which is good
because the customer I gave the CD to could enter his own valid licensed
product key. I am surprised it took so long for someone to tell me
something so simple that I have to apply the .msp to an admin point created
from setup /a and then it would work. Thank you for replying, Bob Buckland!
MS Office System Products MVP
Anyone reading these post can compare the original webpage from Microsoft
describing the procedure to the one that Bob referenced. Microsoft:
"http://office.microsoft.com/en-us/assistance/HA011525351033.aspx" Bob:
http://www.petri.co.il/office_xp_sp_slipstreaming.htm" Sorry for multiple
posts, I didn't do a good job of tracking myself. I posted in 5 news groups,
they should all be covered in this post.