Trying to deploy SP1 for Office 2003?!?

[Zack]

Thanks Joseph. That was actually the next thing on my list to try,
believe it or not. I was just trying to avoid a 'normal' admin install
point, as using one disables the local source caching I believe.

Let me know how it goes, and I'll do the same!

-Z-

Zack, here is how far I have now gotten with it:

First though, I got the info from the latest issue of this mag:

http://www.winnetmag.com/

I highly reccommend a subscription!

1. Create an Admin Install Point copy the Office CD Image local
2. Drop to CMD Prompt and goto the office folder, type: setup /a

This will create an admin image wherever you specify (for me it was on a
DFS
Share), you also put in your CD Key there...

3. Hit GO! This took me about 3 hours to get an uncompressed Admin Point
and its over gigE.

The next 2 steps I am in process of doing now, dunno which order though,
I
ASSUME it will be:

4. Run the patch on the admin point:

(Here is the EXACT command I ran minus my domain in x's)
msiexec.exe /p "c:\Office 2003 SP1\MAINSP1op.msp" /a
"\\xxx\ddmainroot\Deployment\Applications\Microsoft\Microsoft Office
2003\Office 2003\PRO11.MSI" /qb /lv* c:\log.txt

5. Create an MST for the overall installer to tell it where your
templates
are and all that...



Right now I am running the patch so I will post back when its through the
GPO and tell you if its installed properly.

Joe

Just to clarify--I'm talking about a *compressed CD image* (ie copy of
the
CD), *not* an administrative installation point (created with setup.exe
/a). With your method here I still get an error message relating to the
key... Hmm.

-Z-

A workaround I've found for this is to do the patch this way:

msiexec.exe /p [path\name of MSP file] /a [path\name of MSI file]
PIDKEY=[your-25-digit-CD-KEY] /qb

If you don't know your PIDKEY, use the MST viewer to examine your MST
file
and you will find it there. Of course, you don't include the "[" or "]"
in
the syntax above

 

[Zack]

Thanks Joseph. That was actually the next thing on my list to try,
believe it or not. I was just trying to avoid a 'normal' admin install
point, as using one disables the local source caching I believe.

Let me know how it goes, and I'll do the same!

-Z-

Zack, here is how far I have now gotten with it:

First though, I got the info from the latest issue of this mag:

http://www.winnetmag.com/

I highly reccommend a subscription!

1. Create an Admin Install Point copy the Office CD Image local
2. Drop to CMD Prompt and goto the office folder, type: setup /a

This will create an admin image wherever you specify (for me it was on a
DFS
Share), you also put in your CD Key there...

3. Hit GO! This took me about 3 hours to get an uncompressed Admin Point
and its over gigE.

The next 2 steps I am in process of doing now, dunno which order though,
I
ASSUME it will be:

4. Run the patch on the admin point:

(Here is the EXACT command I ran minus my domain in x's)
msiexec.exe /p "c:\Office 2003 SP1\MAINSP1op.msp" /a
"\\xxx\ddmainroot\Deployment\Applications\Microsoft\Microsoft Office
2003\Office 2003\PRO11.MSI" /qb /lv* c:\log.txt

5. Create an MST for the overall installer to tell it where your
templates
are and all that...



Right now I am running the patch so I will post back when its through the
GPO and tell you if its installed properly.

Joe

Just to clarify--I'm talking about a *compressed CD image* (ie copy of
the
CD), *not* an administrative installation point (created with setup.exe
/a). With your method here I still get an error message relating to the
key... Hmm.

-Z-

A workaround I've found for this is to do the patch this way:

msiexec.exe /p [path\name of MSP file] /a [path\name of MSI file]
PIDKEY=[your-25-digit-CD-KEY] /qb

If you don't know your PIDKEY, use the MST viewer to examine your MST
file
and you will find it there. Of course, you don't include the "[" or "]"
in
the syntax above

 

[Joseph Boswell]

So far so good Zack,

When you create the MST I think it has options in there for local source
cacheing, though for me that is not that much of an issue, I just need it to
get deployed...

I am getting an error on the DC I am deploying from (the one thats hosting
the GPO) but I think its probably because of my MST file, I am going to
recreate it and see. Its still deploying properly though so...

Joe

Thanks Joseph. That was actually the next thing on my list to try,
believe it or not. I was just trying to avoid a 'normal' admin install
point, as using one disables the local source caching I believe.

Let me know how it goes, and I'll do the same!

-Z-

Zack, here is how far I have now gotten with it:

First though, I got the info from the latest issue of this mag:

http://www.winnetmag.com/

I highly reccommend a subscription!

1. Create an Admin Install Point copy the Office CD Image local
2. Drop to CMD Prompt and goto the office folder, type: setup /a

This will create an admin image wherever you specify (for me it was on a
DFS
Share), you also put in your CD Key there...

3. Hit GO! This took me about 3 hours to get an uncompressed Admin Point
and its over gigE.

The next 2 steps I am in process of doing now, dunno which order though,
I
ASSUME it will be:

4. Run the patch on the admin point:

(Here is the EXACT command I ran minus my domain in x's)
msiexec.exe /p "c:\Office 2003 SP1\MAINSP1op.msp" /a
"\\xxx\ddmainroot\Deployment\Applications\Microsoft\Microsoft Office
2003\Office 2003\PRO11.MSI" /qb /lv* c:\log.txt

5. Create an MST for the overall installer to tell it where your
templates
are and all that...



Right now I am running the patch so I will post back when its through the
GPO and tell you if its installed properly.

Joe

Just to clarify--I'm talking about a *compressed CD image* (ie copy of
the
CD), *not* an administrative installation point (created with setup.exe
/a). With your method here I still get an error message relating to the
key... Hmm.

-Z-

On Fri, 27 Aug 2004 13:28:23 -0700, Deji Akomolafe
<[email protected]>
wrote:

A workaround I've found for this is to do the patch this way:

msiexec.exe /p [path\name of MSP file] /a [path\name of MSI file]
PIDKEY=[your-25-digit-CD-KEY] /qb

If you don't know your PIDKEY, use the MST viewer to examine your MST
file
and you will find it there. Of course, you don't include the "[" or
"]"
in
the syntax above

 

[Joseph Boswell]

So far so good Zack,

When you create the MST I think it has options in there for local source
cacheing, though for me that is not that much of an issue, I just need it to
get deployed...

I am getting an error on the DC I am deploying from (the one thats hosting
the GPO) but I think its probably because of my MST file, I am going to
recreate it and see. Its still deploying properly though so...

Joe

Thanks Joseph. That was actually the next thing on my list to try,
believe it or not. I was just trying to avoid a 'normal' admin install
point, as using one disables the local source caching I believe.

Let me know how it goes, and I'll do the same!

-Z-

Zack, here is how far I have now gotten with it:

First though, I got the info from the latest issue of this mag:

http://www.winnetmag.com/

I highly reccommend a subscription!

1. Create an Admin Install Point copy the Office CD Image local
2. Drop to CMD Prompt and goto the office folder, type: setup /a

This will create an admin image wherever you specify (for me it was on a
DFS
Share), you also put in your CD Key there...

3. Hit GO! This took me about 3 hours to get an uncompressed Admin Point
and its over gigE.

The next 2 steps I am in process of doing now, dunno which order though,
I
ASSUME it will be:

4. Run the patch on the admin point:

(Here is the EXACT command I ran minus my domain in x's)
msiexec.exe /p "c:\Office 2003 SP1\MAINSP1op.msp" /a
"\\xxx\ddmainroot\Deployment\Applications\Microsoft\Microsoft Office
2003\Office 2003\PRO11.MSI" /qb /lv* c:\log.txt

5. Create an MST for the overall installer to tell it where your
templates
are and all that...



Right now I am running the patch so I will post back when its through the
GPO and tell you if its installed properly.

Joe

Just to clarify--I'm talking about a *compressed CD image* (ie copy of
the
CD), *not* an administrative installation point (created with setup.exe
/a). With your method here I still get an error message relating to the
key... Hmm.

-Z-

On Fri, 27 Aug 2004 13:28:23 -0700, Deji Akomolafe
<[email protected]>
wrote:

A workaround I've found for this is to do the patch this way:

msiexec.exe /p [path\name of MSP file] /a [path\name of MSI file]
PIDKEY=[your-25-digit-CD-KEY] /qb

If you don't know your PIDKEY, use the MST viewer to examine your MST
file
and you will find it there. Of course, you don't include the "[" or
"]"
in
the syntax above

 

[Joseph Boswell]

So far so good Zack,

When you create the MST I think it has options in there for local source
cacheing, though for me that is not that much of an issue, I just need it to
get deployed...

I am getting an error on the DC I am deploying from (the one thats hosting
the GPO) but I think its probably because of my MST file, I am going to
recreate it and see. Its still deploying properly though so...

Joe

Thanks Joseph. That was actually the next thing on my list to try,
believe it or not. I was just trying to avoid a 'normal' admin install
point, as using one disables the local source caching I believe.

Let me know how it goes, and I'll do the same!

-Z-

Zack, here is how far I have now gotten with it:

First though, I got the info from the latest issue of this mag:

http://www.winnetmag.com/

I highly reccommend a subscription!

1. Create an Admin Install Point copy the Office CD Image local
2. Drop to CMD Prompt and goto the office folder, type: setup /a

This will create an admin image wherever you specify (for me it was on a
DFS
Share), you also put in your CD Key there...

3. Hit GO! This took me about 3 hours to get an uncompressed Admin Point
and its over gigE.

The next 2 steps I am in process of doing now, dunno which order though,
I
ASSUME it will be:

4. Run the patch on the admin point:

(Here is the EXACT command I ran minus my domain in x's)
msiexec.exe /p "c:\Office 2003 SP1\MAINSP1op.msp" /a
"\\xxx\ddmainroot\Deployment\Applications\Microsoft\Microsoft Office
2003\Office 2003\PRO11.MSI" /qb /lv* c:\log.txt

5. Create an MST for the overall installer to tell it where your
templates
are and all that...



Right now I am running the patch so I will post back when its through the
GPO and tell you if its installed properly.

Joe

Just to clarify--I'm talking about a *compressed CD image* (ie copy of
the
CD), *not* an administrative installation point (created with setup.exe
/a). With your method here I still get an error message relating to the
key... Hmm.

-Z-

On Fri, 27 Aug 2004 13:28:23 -0700, Deji Akomolafe
<[email protected]>
wrote:

A workaround I've found for this is to do the patch this way:

msiexec.exe /p [path\name of MSP file] /a [path\name of MSI file]
PIDKEY=[your-25-digit-CD-KEY] /qb

If you don't know your PIDKEY, use the MST viewer to examine your MST
file
and you will find it there. Of course, you don't include the "[" or
"]"
in
the syntax above

 

[Joseph Boswell]

So far so good Zack,

When you create the MST I think it has options in there for local source
cacheing, though for me that is not that much of an issue, I just need it to
get deployed...

I am getting an error on the DC I am deploying from (the one thats hosting
the GPO) but I think its probably because of my MST file, I am going to
recreate it and see. Its still deploying properly though so...

Joe

Thanks Joseph. That was actually the next thing on my list to try,
believe it or not. I was just trying to avoid a 'normal' admin install
point, as using one disables the local source caching I believe.

Let me know how it goes, and I'll do the same!

-Z-

Zack, here is how far I have now gotten with it:

First though, I got the info from the latest issue of this mag:

http://www.winnetmag.com/

I highly reccommend a subscription!

1. Create an Admin Install Point copy the Office CD Image local
2. Drop to CMD Prompt and goto the office folder, type: setup /a

This will create an admin image wherever you specify (for me it was on a
DFS
Share), you also put in your CD Key there...

3. Hit GO! This took me about 3 hours to get an uncompressed Admin Point
and its over gigE.

The next 2 steps I am in process of doing now, dunno which order though,
I
ASSUME it will be:

4. Run the patch on the admin point:

(Here is the EXACT command I ran minus my domain in x's)
msiexec.exe /p "c:\Office 2003 SP1\MAINSP1op.msp" /a
"\\xxx\ddmainroot\Deployment\Applications\Microsoft\Microsoft Office
2003\Office 2003\PRO11.MSI" /qb /lv* c:\log.txt

5. Create an MST for the overall installer to tell it where your
templates
are and all that...



Right now I am running the patch so I will post back when its through the
GPO and tell you if its installed properly.

Joe

Just to clarify--I'm talking about a *compressed CD image* (ie copy of
the
CD), *not* an administrative installation point (created with setup.exe
/a). With your method here I still get an error message relating to the
key... Hmm.

-Z-

On Fri, 27 Aug 2004 13:28:23 -0700, Deji Akomolafe
<[email protected]>
wrote:

A workaround I've found for this is to do the patch this way:

msiexec.exe /p [path\name of MSP file] /a [path\name of MSI file]
PIDKEY=[your-25-digit-CD-KEY] /qb

If you don't know your PIDKEY, use the MST viewer to examine your MST
file
and you will find it there. Of course, you don't include the "[" or
"]"
in
the syntax above

 

[Joseph Boswell]

So far so good Zack,

When you create the MST I think it has options in there for local source
cacheing, though for me that is not that much of an issue, I just need it to
get deployed...

I am getting an error on the DC I am deploying from (the one thats hosting
the GPO) but I think its probably because of my MST file, I am going to
recreate it and see. Its still deploying properly though so...

Joe

Thanks Joseph. That was actually the next thing on my list to try,
believe it or not. I was just trying to avoid a 'normal' admin install
point, as using one disables the local source caching I believe.

Let me know how it goes, and I'll do the same!

-Z-

Zack, here is how far I have now gotten with it:

First though, I got the info from the latest issue of this mag:

http://www.winnetmag.com/

I highly reccommend a subscription!

1. Create an Admin Install Point copy the Office CD Image local
2. Drop to CMD Prompt and goto the office folder, type: setup /a

This will create an admin image wherever you specify (for me it was on a
DFS
Share), you also put in your CD Key there...

3. Hit GO! This took me about 3 hours to get an uncompressed Admin Point
and its over gigE.

The next 2 steps I am in process of doing now, dunno which order though,
I
ASSUME it will be:

4. Run the patch on the admin point:

(Here is the EXACT command I ran minus my domain in x's)
msiexec.exe /p "c:\Office 2003 SP1\MAINSP1op.msp" /a
"\\xxx\ddmainroot\Deployment\Applications\Microsoft\Microsoft Office
2003\Office 2003\PRO11.MSI" /qb /lv* c:\log.txt

5. Create an MST for the overall installer to tell it where your
templates
are and all that...



Right now I am running the patch so I will post back when its through the
GPO and tell you if its installed properly.

Joe

Just to clarify--I'm talking about a *compressed CD image* (ie copy of
the
CD), *not* an administrative installation point (created with setup.exe
/a). With your method here I still get an error message relating to the
key... Hmm.

-Z-

On Fri, 27 Aug 2004 13:28:23 -0700, Deji Akomolafe
<[email protected]>
wrote:

A workaround I've found for this is to do the patch this way:

msiexec.exe /p [path\name of MSP file] /a [path\name of MSI file]
PIDKEY=[your-25-digit-CD-KEY] /qb

If you don't know your PIDKEY, use the MST viewer to examine your MST
file
and you will find it there. Of course, you don't include the "[" or
"]"
in
the syntax above

 

[Joseph Boswell]

So far so good Zack,

When you create the MST I think it has options in there for local source
cacheing, though for me that is not that much of an issue, I just need it to
get deployed...

I am getting an error on the DC I am deploying from (the one thats hosting
the GPO) but I think its probably because of my MST file, I am going to
recreate it and see. Its still deploying properly though so...

Joe

Thanks Joseph. That was actually the next thing on my list to try,
believe it or not. I was just trying to avoid a 'normal' admin install
point, as using one disables the local source caching I believe.

Let me know how it goes, and I'll do the same!

-Z-

Zack, here is how far I have now gotten with it:

First though, I got the info from the latest issue of this mag:

http://www.winnetmag.com/

I highly reccommend a subscription!

1. Create an Admin Install Point copy the Office CD Image local
2. Drop to CMD Prompt and goto the office folder, type: setup /a

This will create an admin image wherever you specify (for me it was on a
DFS
Share), you also put in your CD Key there...

3. Hit GO! This took me about 3 hours to get an uncompressed Admin Point
and its over gigE.

The next 2 steps I am in process of doing now, dunno which order though,
I
ASSUME it will be:

4. Run the patch on the admin point:

(Here is the EXACT command I ran minus my domain in x's)
msiexec.exe /p "c:\Office 2003 SP1\MAINSP1op.msp" /a
"\\xxx\ddmainroot\Deployment\Applications\Microsoft\Microsoft Office
2003\Office 2003\PRO11.MSI" /qb /lv* c:\log.txt

5. Create an MST for the overall installer to tell it where your
templates
are and all that...



Right now I am running the patch so I will post back when its through the
GPO and tell you if its installed properly.

Joe

Just to clarify--I'm talking about a *compressed CD image* (ie copy of
the
CD), *not* an administrative installation point (created with setup.exe
/a). With your method here I still get an error message relating to the
key... Hmm.

-Z-

On Fri, 27 Aug 2004 13:28:23 -0700, Deji Akomolafe
<[email protected]>
wrote:

A workaround I've found for this is to do the patch this way:

msiexec.exe /p [path\name of MSP file] /a [path\name of MSI file]
PIDKEY=[your-25-digit-CD-KEY] /qb

If you don't know your PIDKEY, use the MST viewer to examine your MST
file
and you will find it there. Of course, you don't include the "[" or
"]"
in
the syntax above

 

[Joseph Boswell]

So far so good Zack,

When you create the MST I think it has options in there for local source
cacheing, though for me that is not that much of an issue, I just need it to
get deployed...

I am getting an error on the DC I am deploying from (the one thats hosting
the GPO) but I think its probably because of my MST file, I am going to
recreate it and see. Its still deploying properly though so...

Joe

Thanks Joseph. That was actually the next thing on my list to try,
believe it or not. I was just trying to avoid a 'normal' admin install
point, as using one disables the local source caching I believe.

Let me know how it goes, and I'll do the same!

-Z-

Zack, here is how far I have now gotten with it:

First though, I got the info from the latest issue of this mag:

http://www.winnetmag.com/

I highly reccommend a subscription!

1. Create an Admin Install Point copy the Office CD Image local
2. Drop to CMD Prompt and goto the office folder, type: setup /a

This will create an admin image wherever you specify (for me it was on a
DFS
Share), you also put in your CD Key there...

3. Hit GO! This took me about 3 hours to get an uncompressed Admin Point
and its over gigE.

The next 2 steps I am in process of doing now, dunno which order though,
I
ASSUME it will be:

4. Run the patch on the admin point:

(Here is the EXACT command I ran minus my domain in x's)
msiexec.exe /p "c:\Office 2003 SP1\MAINSP1op.msp" /a
"\\xxx\ddmainroot\Deployment\Applications\Microsoft\Microsoft Office
2003\Office 2003\PRO11.MSI" /qb /lv* c:\log.txt

5. Create an MST for the overall installer to tell it where your
templates
are and all that...



Right now I am running the patch so I will post back when its through the
GPO and tell you if its installed properly.

Joe

Just to clarify--I'm talking about a *compressed CD image* (ie copy of
the
CD), *not* an administrative installation point (created with setup.exe
/a). With your method here I still get an error message relating to the
key... Hmm.

-Z-

On Fri, 27 Aug 2004 13:28:23 -0700, Deji Akomolafe
<[email protected]>
wrote:

A workaround I've found for this is to do the patch this way:

msiexec.exe /p [path\name of MSP file] /a [path\name of MSI file]
PIDKEY=[your-25-digit-CD-KEY] /qb

If you don't know your PIDKEY, use the MST viewer to examine your MST
file
and you will find it there. Of course, you don't include the "[" or
"]"
in
the syntax above

 

[Joseph Boswell]

So far so good Zack,

When you create the MST I think it has options in there for local source
cacheing, though for me that is not that much of an issue, I just need it to
get deployed...

I am getting an error on the DC I am deploying from (the one thats hosting
the GPO) but I think its probably because of my MST file, I am going to
recreate it and see. Its still deploying properly though so...

Joe

Thanks Joseph. That was actually the next thing on my list to try,
believe it or not. I was just trying to avoid a 'normal' admin install
point, as using one disables the local source caching I believe.

Let me know how it goes, and I'll do the same!

-Z-

Zack, here is how far I have now gotten with it:

First though, I got the info from the latest issue of this mag:

http://www.winnetmag.com/

I highly reccommend a subscription!

1. Create an Admin Install Point copy the Office CD Image local
2. Drop to CMD Prompt and goto the office folder, type: setup /a

This will create an admin image wherever you specify (for me it was on a
DFS
Share), you also put in your CD Key there...

3. Hit GO! This took me about 3 hours to get an uncompressed Admin Point
and its over gigE.

The next 2 steps I am in process of doing now, dunno which order though,
I
ASSUME it will be:

4. Run the patch on the admin point:

(Here is the EXACT command I ran minus my domain in x's)
msiexec.exe /p "c:\Office 2003 SP1\MAINSP1op.msp" /a
"\\xxx\ddmainroot\Deployment\Applications\Microsoft\Microsoft Office
2003\Office 2003\PRO11.MSI" /qb /lv* c:\log.txt

5. Create an MST for the overall installer to tell it where your
templates
are and all that...



Right now I am running the patch so I will post back when its through the
GPO and tell you if its installed properly.

Joe

Just to clarify--I'm talking about a *compressed CD image* (ie copy of
the
CD), *not* an administrative installation point (created with setup.exe
/a). With your method here I still get an error message relating to the
key... Hmm.

-Z-

On Fri, 27 Aug 2004 13:28:23 -0700, Deji Akomolafe
<[email protected]>
wrote:

A workaround I've found for this is to do the patch this way:

msiexec.exe /p [path\name of MSP file] /a [path\name of MSI file]
PIDKEY=[your-25-digit-CD-KEY] /qb

If you don't know your PIDKEY, use the MST viewer to examine your MST
file
and you will find it there. Of course, you don't include the "[" or
"]"
in
the syntax above

 

[Joseph Boswell]

So far so good Zack,

When you create the MST I think it has options in there for local source
cacheing, though for me that is not that much of an issue, I just need it to
get deployed...

I am getting an error on the DC I am deploying from (the one thats hosting
the GPO) but I think its probably because of my MST file, I am going to
recreate it and see. Its still deploying properly though so...

Joe

Thanks Joseph. That was actually the next thing on my list to try,
believe it or not. I was just trying to avoid a 'normal' admin install
point, as using one disables the local source caching I believe.

Let me know how it goes, and I'll do the same!

-Z-

Zack, here is how far I have now gotten with it:

First though, I got the info from the latest issue of this mag:

http://www.winnetmag.com/

I highly reccommend a subscription!

1. Create an Admin Install Point copy the Office CD Image local
2. Drop to CMD Prompt and goto the office folder, type: setup /a

This will create an admin image wherever you specify (for me it was on a
DFS
Share), you also put in your CD Key there...

3. Hit GO! This took me about 3 hours to get an uncompressed Admin Point
and its over gigE.

The next 2 steps I am in process of doing now, dunno which order though,
I
ASSUME it will be:

4. Run the patch on the admin point:

(Here is the EXACT command I ran minus my domain in x's)
msiexec.exe /p "c:\Office 2003 SP1\MAINSP1op.msp" /a
"\\xxx\ddmainroot\Deployment\Applications\Microsoft\Microsoft Office
2003\Office 2003\PRO11.MSI" /qb /lv* c:\log.txt

5. Create an MST for the overall installer to tell it where your
templates
are and all that...



Right now I am running the patch so I will post back when its through the
GPO and tell you if its installed properly.

Joe

Just to clarify--I'm talking about a *compressed CD image* (ie copy of
the
CD), *not* an administrative installation point (created with setup.exe
/a). With your method here I still get an error message relating to the
key... Hmm.

-Z-

On Fri, 27 Aug 2004 13:28:23 -0700, Deji Akomolafe
<[email protected]>
wrote:

A workaround I've found for this is to do the patch this way:

msiexec.exe /p [path\name of MSP file] /a [path\name of MSI file]
PIDKEY=[your-25-digit-CD-KEY] /qb

If you don't know your PIDKEY, use the MST viewer to examine your MST
file
and you will find it there. Of course, you don't include the "[" or
"]"
in
the syntax above

 

[Joseph Boswell]

Found the answer to that error also, apparently it was caused in some
fashion by the language of the app? If that makes any sense? It is in
english anyway but the Fix (more importantly) is to set (in the GPO) to
ignore language settings and you wont see the error on your DC anymore.

It was a pain in the ass I dont understand but its all finished and deployed
and working now so I only hope this can help others in this situation, I
just hope SMS has a solution to deploy stuff like this, I am really trying
to get away from going to command line as possible.

Joe

So far so good Zack,

When you create the MST I think it has options in there for local source
cacheing, though for me that is not that much of an issue, I just need it to
get deployed...

I am getting an error on the DC I am deploying from (the one thats hosting
the GPO) but I think its probably because of my MST file, I am going to
recreate it and see. Its still deploying properly though so...

Joe

Thanks Joseph. That was actually the next thing on my list to try,
believe it or not. I was just trying to avoid a 'normal' admin install
point, as using one disables the local source caching I believe.

Let me know how it goes, and I'll do the same!

-Z-

Zack, here is how far I have now gotten with it:

First though, I got the info from the latest issue of this mag:

http://www.winnetmag.com/

I highly reccommend a subscription!

1. Create an Admin Install Point copy the Office CD Image local
2. Drop to CMD Prompt and goto the office folder, type: setup /a

This will create an admin image wherever you specify (for me it was on a
DFS
Share), you also put in your CD Key there...

3. Hit GO! This took me about 3 hours to get an uncompressed Admin Point
and its over gigE.

The next 2 steps I am in process of doing now, dunno which order though,
I
ASSUME it will be:

4. Run the patch on the admin point:

(Here is the EXACT command I ran minus my domain in x's)
msiexec.exe /p "c:\Office 2003 SP1\MAINSP1op.msp" /a
"\\xxx\ddmainroot\Deployment\Applications\Microsoft\Microsoft Office
2003\Office 2003\PRO11.MSI" /qb /lv* c:\log.txt

5. Create an MST for the overall installer to tell it where your
templates
are and all that...



Right now I am running the patch so I will post back when its through the
GPO and tell you if its installed properly.

Joe
Just to clarify--I'm talking about a *compressed CD image* (ie copy of
the
CD), *not* an administrative installation point (created with setup.exe
/a). With your method here I still get an error message relating to the
key... Hmm.

-Z-

On Fri, 27 Aug 2004 13:28:23 -0700, Deji Akomolafe
<[email protected]>
wrote:

A workaround I've found for this is to do the patch this way:

msiexec.exe /p [path\name of MSP file] /a [path\name of MSI file]
PIDKEY=[your-25-digit-CD-KEY] /qb

If you don't know your PIDKEY, use the MST viewer to examine your MST
file
and you will find it there. Of course, you don't include the "[" or
"]"
in
the syntax above

 

[Joseph Boswell]

Found the answer to that error also, apparently it was caused in some
fashion by the language of the app? If that makes any sense? It is in
english anyway but the Fix (more importantly) is to set (in the GPO) to
ignore language settings and you wont see the error on your DC anymore.

It was a pain in the ass I dont understand but its all finished and deployed
and working now so I only hope this can help others in this situation, I
just hope SMS has a solution to deploy stuff like this, I am really trying
to get away from going to command line as possible.

Joe

So far so good Zack,

When you create the MST I think it has options in there for local source
cacheing, though for me that is not that much of an issue, I just need it to
get deployed...

I am getting an error on the DC I am deploying from (the one thats hosting
the GPO) but I think its probably because of my MST file, I am going to
recreate it and see. Its still deploying properly though so...

Joe

Thanks Joseph. That was actually the next thing on my list to try,
believe it or not. I was just trying to avoid a 'normal' admin install
point, as using one disables the local source caching I believe.

Let me know how it goes, and I'll do the same!

-Z-

Zack, here is how far I have now gotten with it:

First though, I got the info from the latest issue of this mag:

http://www.winnetmag.com/

I highly reccommend a subscription!

1. Create an Admin Install Point copy the Office CD Image local
2. Drop to CMD Prompt and goto the office folder, type: setup /a

This will create an admin image wherever you specify (for me it was on a
DFS
Share), you also put in your CD Key there...

3. Hit GO! This took me about 3 hours to get an uncompressed Admin Point
and its over gigE.

The next 2 steps I am in process of doing now, dunno which order though,
I
ASSUME it will be:

4. Run the patch on the admin point:

(Here is the EXACT command I ran minus my domain in x's)
msiexec.exe /p "c:\Office 2003 SP1\MAINSP1op.msp" /a
"\\xxx\ddmainroot\Deployment\Applications\Microsoft\Microsoft Office
2003\Office 2003\PRO11.MSI" /qb /lv* c:\log.txt

5. Create an MST for the overall installer to tell it where your
templates
are and all that...



Right now I am running the patch so I will post back when its through the
GPO and tell you if its installed properly.

Joe
Just to clarify--I'm talking about a *compressed CD image* (ie copy of
the
CD), *not* an administrative installation point (created with setup.exe
/a). With your method here I still get an error message relating to the
key... Hmm.

-Z-

On Fri, 27 Aug 2004 13:28:23 -0700, Deji Akomolafe
<[email protected]>
wrote:

A workaround I've found for this is to do the patch this way:

msiexec.exe /p [path\name of MSP file] /a [path\name of MSI file]
PIDKEY=[your-25-digit-CD-KEY] /qb

If you don't know your PIDKEY, use the MST viewer to examine your MST
file
and you will find it there. Of course, you don't include the "[" or
"]"
in
the syntax above

 

[Joseph Boswell]

Found the answer to that error also, apparently it was caused in some
fashion by the language of the app? If that makes any sense? It is in
english anyway but the Fix (more importantly) is to set (in the GPO) to
ignore language settings and you wont see the error on your DC anymore.

It was a pain in the ass I dont understand but its all finished and deployed
and working now so I only hope this can help others in this situation, I
just hope SMS has a solution to deploy stuff like this, I am really trying
to get away from going to command line as possible.

Joe

So far so good Zack,

When you create the MST I think it has options in there for local source
cacheing, though for me that is not that much of an issue, I just need it to
get deployed...

I am getting an error on the DC I am deploying from (the one thats hosting
the GPO) but I think its probably because of my MST file, I am going to
recreate it and see. Its still deploying properly though so...

Joe

Thanks Joseph. That was actually the next thing on my list to try,
believe it or not. I was just trying to avoid a 'normal' admin install
point, as using one disables the local source caching I believe.

Let me know how it goes, and I'll do the same!

-Z-

Zack, here is how far I have now gotten with it:

First though, I got the info from the latest issue of this mag:

http://www.winnetmag.com/

I highly reccommend a subscription!

1. Create an Admin Install Point copy the Office CD Image local
2. Drop to CMD Prompt and goto the office folder, type: setup /a

This will create an admin image wherever you specify (for me it was on a
DFS
Share), you also put in your CD Key there...

3. Hit GO! This took me about 3 hours to get an uncompressed Admin Point
and its over gigE.

The next 2 steps I am in process of doing now, dunno which order though,
I
ASSUME it will be:

4. Run the patch on the admin point:

(Here is the EXACT command I ran minus my domain in x's)
msiexec.exe /p "c:\Office 2003 SP1\MAINSP1op.msp" /a
"\\xxx\ddmainroot\Deployment\Applications\Microsoft\Microsoft Office
2003\Office 2003\PRO11.MSI" /qb /lv* c:\log.txt

5. Create an MST for the overall installer to tell it where your
templates
are and all that...



Right now I am running the patch so I will post back when its through the
GPO and tell you if its installed properly.

Joe
Just to clarify--I'm talking about a *compressed CD image* (ie copy of
the
CD), *not* an administrative installation point (created with setup.exe
/a). With your method here I still get an error message relating to the
key... Hmm.

-Z-

On Fri, 27 Aug 2004 13:28:23 -0700, Deji Akomolafe
<[email protected]>
wrote:

A workaround I've found for this is to do the patch this way:

msiexec.exe /p [path\name of MSP file] /a [path\name of MSI file]
PIDKEY=[your-25-digit-CD-KEY] /qb

If you don't know your PIDKEY, use the MST viewer to examine your MST
file
and you will find it there. Of course, you don't include the "[" or
"]"
in
the syntax above

 

[Joseph Boswell]

Found the answer to that error also, apparently it was caused in some
fashion by the language of the app? If that makes any sense? It is in
english anyway but the Fix (more importantly) is to set (in the GPO) to
ignore language settings and you wont see the error on your DC anymore.

It was a pain in the ass I dont understand but its all finished and deployed
and working now so I only hope this can help others in this situation, I
just hope SMS has a solution to deploy stuff like this, I am really trying
to get away from going to command line as possible.

Joe

So far so good Zack,

When you create the MST I think it has options in there for local source
cacheing, though for me that is not that much of an issue, I just need it to
get deployed...

I am getting an error on the DC I am deploying from (the one thats hosting
the GPO) but I think its probably because of my MST file, I am going to
recreate it and see. Its still deploying properly though so...

Joe

Thanks Joseph. That was actually the next thing on my list to try,
believe it or not. I was just trying to avoid a 'normal' admin install
point, as using one disables the local source caching I believe.

Let me know how it goes, and I'll do the same!

-Z-

Zack, here is how far I have now gotten with it:

First though, I got the info from the latest issue of this mag:

http://www.winnetmag.com/

I highly reccommend a subscription!

1. Create an Admin Install Point copy the Office CD Image local
2. Drop to CMD Prompt and goto the office folder, type: setup /a

This will create an admin image wherever you specify (for me it was on a
DFS
Share), you also put in your CD Key there...

3. Hit GO! This took me about 3 hours to get an uncompressed Admin Point
and its over gigE.

The next 2 steps I am in process of doing now, dunno which order though,
I
ASSUME it will be:

4. Run the patch on the admin point:

(Here is the EXACT command I ran minus my domain in x's)
msiexec.exe /p "c:\Office 2003 SP1\MAINSP1op.msp" /a
"\\xxx\ddmainroot\Deployment\Applications\Microsoft\Microsoft Office
2003\Office 2003\PRO11.MSI" /qb /lv* c:\log.txt

5. Create an MST for the overall installer to tell it where your
templates
are and all that...



Right now I am running the patch so I will post back when its through the
GPO and tell you if its installed properly.

Joe
Just to clarify--I'm talking about a *compressed CD image* (ie copy of
the
CD), *not* an administrative installation point (created with setup.exe
/a). With your method here I still get an error message relating to the
key... Hmm.

-Z-

On Fri, 27 Aug 2004 13:28:23 -0700, Deji Akomolafe
<[email protected]>
wrote:

A workaround I've found for this is to do the patch this way:

msiexec.exe /p [path\name of MSP file] /a [path\name of MSI file]
PIDKEY=[your-25-digit-CD-KEY] /qb

If you don't know your PIDKEY, use the MST viewer to examine your MST
file
and you will find it there. Of course, you don't include the "[" or
"]"
in
the syntax above

 

[Joseph Boswell]

Found the answer to that error also, apparently it was caused in some
fashion by the language of the app? If that makes any sense? It is in
english anyway but the Fix (more importantly) is to set (in the GPO) to
ignore language settings and you wont see the error on your DC anymore.

It was a pain in the ass I dont understand but its all finished and deployed
and working now so I only hope this can help others in this situation, I
just hope SMS has a solution to deploy stuff like this, I am really trying
to get away from going to command line as possible.

Joe

So far so good Zack,

When you create the MST I think it has options in there for local source
cacheing, though for me that is not that much of an issue, I just need it to
get deployed...

I am getting an error on the DC I am deploying from (the one thats hosting
the GPO) but I think its probably because of my MST file, I am going to
recreate it and see. Its still deploying properly though so...

Joe

Thanks Joseph. That was actually the next thing on my list to try,
believe it or not. I was just trying to avoid a 'normal' admin install
point, as using one disables the local source caching I believe.

Let me know how it goes, and I'll do the same!

-Z-

Zack, here is how far I have now gotten with it:

First though, I got the info from the latest issue of this mag:

http://www.winnetmag.com/

I highly reccommend a subscription!

1. Create an Admin Install Point copy the Office CD Image local
2. Drop to CMD Prompt and goto the office folder, type: setup /a

This will create an admin image wherever you specify (for me it was on a
DFS
Share), you also put in your CD Key there...

3. Hit GO! This took me about 3 hours to get an uncompressed Admin Point
and its over gigE.

The next 2 steps I am in process of doing now, dunno which order though,
I
ASSUME it will be:

4. Run the patch on the admin point:

(Here is the EXACT command I ran minus my domain in x's)
msiexec.exe /p "c:\Office 2003 SP1\MAINSP1op.msp" /a
"\\xxx\ddmainroot\Deployment\Applications\Microsoft\Microsoft Office
2003\Office 2003\PRO11.MSI" /qb /lv* c:\log.txt

5. Create an MST for the overall installer to tell it where your
templates
are and all that...



Right now I am running the patch so I will post back when its through the
GPO and tell you if its installed properly.

Joe
Just to clarify--I'm talking about a *compressed CD image* (ie copy of
the
CD), *not* an administrative installation point (created with setup.exe
/a). With your method here I still get an error message relating to the
key... Hmm.

-Z-

On Fri, 27 Aug 2004 13:28:23 -0700, Deji Akomolafe
<[email protected]>
wrote:

A workaround I've found for this is to do the patch this way:

msiexec.exe /p [path\name of MSP file] /a [path\name of MSI file]
PIDKEY=[your-25-digit-CD-KEY] /qb

If you don't know your PIDKEY, use the MST viewer to examine your MST
file
and you will find it there. Of course, you don't include the "[" or
"]"
in
the syntax above

 

[Joseph Boswell]

Found the answer to that error also, apparently it was caused in some
fashion by the language of the app? If that makes any sense? It is in
english anyway but the Fix (more importantly) is to set (in the GPO) to
ignore language settings and you wont see the error on your DC anymore.

It was a pain in the ass I dont understand but its all finished and deployed
and working now so I only hope this can help others in this situation, I
just hope SMS has a solution to deploy stuff like this, I am really trying
to get away from going to command line as possible.

Joe

So far so good Zack,

When you create the MST I think it has options in there for local source
cacheing, though for me that is not that much of an issue, I just need it to
get deployed...

I am getting an error on the DC I am deploying from (the one thats hosting
the GPO) but I think its probably because of my MST file, I am going to
recreate it and see. Its still deploying properly though so...

Joe

Thanks Joseph. That was actually the next thing on my list to try,
believe it or not. I was just trying to avoid a 'normal' admin install
point, as using one disables the local source caching I believe.

Let me know how it goes, and I'll do the same!

-Z-

Zack, here is how far I have now gotten with it:

First though, I got the info from the latest issue of this mag:

http://www.winnetmag.com/

I highly reccommend a subscription!

1. Create an Admin Install Point copy the Office CD Image local
2. Drop to CMD Prompt and goto the office folder, type: setup /a

This will create an admin image wherever you specify (for me it was on a
DFS
Share), you also put in your CD Key there...

3. Hit GO! This took me about 3 hours to get an uncompressed Admin Point
and its over gigE.

The next 2 steps I am in process of doing now, dunno which order though,
I
ASSUME it will be:

4. Run the patch on the admin point:

(Here is the EXACT command I ran minus my domain in x's)
msiexec.exe /p "c:\Office 2003 SP1\MAINSP1op.msp" /a
"\\xxx\ddmainroot\Deployment\Applications\Microsoft\Microsoft Office
2003\Office 2003\PRO11.MSI" /qb /lv* c:\log.txt

5. Create an MST for the overall installer to tell it where your
templates
are and all that...



Right now I am running the patch so I will post back when its through the
GPO and tell you if its installed properly.

Joe
Just to clarify--I'm talking about a *compressed CD image* (ie copy of
the
CD), *not* an administrative installation point (created with setup.exe
/a). With your method here I still get an error message relating to the
key... Hmm.

-Z-

On Fri, 27 Aug 2004 13:28:23 -0700, Deji Akomolafe
<[email protected]>
wrote:

A workaround I've found for this is to do the patch this way:

msiexec.exe /p [path\name of MSP file] /a [path\name of MSI file]
PIDKEY=[your-25-digit-CD-KEY] /qb

If you don't know your PIDKEY, use the MST viewer to examine your MST
file
and you will find it there. Of course, you don't include the "[" or
"]"
in
the syntax above

 

[Joseph Boswell]

Found the answer to that error also, apparently it was caused in some
fashion by the language of the app? If that makes any sense? It is in
english anyway but the Fix (more importantly) is to set (in the GPO) to
ignore language settings and you wont see the error on your DC anymore.

It was a pain in the ass I dont understand but its all finished and deployed
and working now so I only hope this can help others in this situation, I
just hope SMS has a solution to deploy stuff like this, I am really trying
to get away from going to command line as possible.

Joe

So far so good Zack,

When you create the MST I think it has options in there for local source
cacheing, though for me that is not that much of an issue, I just need it to
get deployed...

I am getting an error on the DC I am deploying from (the one thats hosting
the GPO) but I think its probably because of my MST file, I am going to
recreate it and see. Its still deploying properly though so...

Joe

Thanks Joseph. That was actually the next thing on my list to try,
believe it or not. I was just trying to avoid a 'normal' admin install
point, as using one disables the local source caching I believe.

Let me know how it goes, and I'll do the same!

-Z-

Zack, here is how far I have now gotten with it:

First though, I got the info from the latest issue of this mag:

http://www.winnetmag.com/

I highly reccommend a subscription!

1. Create an Admin Install Point copy the Office CD Image local
2. Drop to CMD Prompt and goto the office folder, type: setup /a

This will create an admin image wherever you specify (for me it was on a
DFS
Share), you also put in your CD Key there...

3. Hit GO! This took me about 3 hours to get an uncompressed Admin Point
and its over gigE.

The next 2 steps I am in process of doing now, dunno which order though,
I
ASSUME it will be:

4. Run the patch on the admin point:

(Here is the EXACT command I ran minus my domain in x's)
msiexec.exe /p "c:\Office 2003 SP1\MAINSP1op.msp" /a
"\\xxx\ddmainroot\Deployment\Applications\Microsoft\Microsoft Office
2003\Office 2003\PRO11.MSI" /qb /lv* c:\log.txt

5. Create an MST for the overall installer to tell it where your
templates
are and all that...



Right now I am running the patch so I will post back when its through the
GPO and tell you if its installed properly.

Joe
Just to clarify--I'm talking about a *compressed CD image* (ie copy of
the
CD), *not* an administrative installation point (created with setup.exe
/a). With your method here I still get an error message relating to the
key... Hmm.

-Z-

On Fri, 27 Aug 2004 13:28:23 -0700, Deji Akomolafe
<[email protected]>
wrote:

A workaround I've found for this is to do the patch this way:

msiexec.exe /p [path\name of MSP file] /a [path\name of MSI file]
PIDKEY=[your-25-digit-CD-KEY] /qb

If you don't know your PIDKEY, use the MST viewer to examine your MST
file
and you will find it there. Of course, you don't include the "[" or
"]"
in
the syntax above

 

[Joseph Boswell]

Found the answer to that error also, apparently it was caused in some
fashion by the language of the app? If that makes any sense? It is in
english anyway but the Fix (more importantly) is to set (in the GPO) to
ignore language settings and you wont see the error on your DC anymore.

It was a pain in the ass I dont understand but its all finished and deployed
and working now so I only hope this can help others in this situation, I
just hope SMS has a solution to deploy stuff like this, I am really trying
to get away from going to command line as possible.

Joe

So far so good Zack,

When you create the MST I think it has options in there for local source
cacheing, though for me that is not that much of an issue, I just need it to
get deployed...

I am getting an error on the DC I am deploying from (the one thats hosting
the GPO) but I think its probably because of my MST file, I am going to
recreate it and see. Its still deploying properly though so...

Joe

Thanks Joseph. That was actually the next thing on my list to try,
believe it or not. I was just trying to avoid a 'normal' admin install
point, as using one disables the local source caching I believe.

Let me know how it goes, and I'll do the same!

-Z-

Zack, here is how far I have now gotten with it:

First though, I got the info from the latest issue of this mag:

http://www.winnetmag.com/

I highly reccommend a subscription!

1. Create an Admin Install Point copy the Office CD Image local
2. Drop to CMD Prompt and goto the office folder, type: setup /a

This will create an admin image wherever you specify (for me it was on a
DFS
Share), you also put in your CD Key there...

3. Hit GO! This took me about 3 hours to get an uncompressed Admin Point
and its over gigE.

The next 2 steps I am in process of doing now, dunno which order though,
I
ASSUME it will be:

4. Run the patch on the admin point:

(Here is the EXACT command I ran minus my domain in x's)
msiexec.exe /p "c:\Office 2003 SP1\MAINSP1op.msp" /a
"\\xxx\ddmainroot\Deployment\Applications\Microsoft\Microsoft Office
2003\Office 2003\PRO11.MSI" /qb /lv* c:\log.txt

5. Create an MST for the overall installer to tell it where your
templates
are and all that...



Right now I am running the patch so I will post back when its through the
GPO and tell you if its installed properly.

Joe
Just to clarify--I'm talking about a *compressed CD image* (ie copy of
the
CD), *not* an administrative installation point (created with setup.exe
/a). With your method here I still get an error message relating to the
key... Hmm.

-Z-

On Fri, 27 Aug 2004 13:28:23 -0700, Deji Akomolafe
<[email protected]>
wrote:

A workaround I've found for this is to do the patch this way:

msiexec.exe /p [path\name of MSP file] /a [path\name of MSI file]
PIDKEY=[your-25-digit-CD-KEY] /qb

If you don't know your PIDKEY, use the MST viewer to examine your MST
file
and you will find it there. Of course, you don't include the "[" or
"]"
in
the syntax above

 

[Joseph Boswell]

Found the answer to that error also, apparently it was caused in some
fashion by the language of the app? If that makes any sense? It is in
english anyway but the Fix (more importantly) is to set (in the GPO) to
ignore language settings and you wont see the error on your DC anymore.

It was a pain in the ass I dont understand but its all finished and deployed
and working now so I only hope this can help others in this situation, I
just hope SMS has a solution to deploy stuff like this, I am really trying
to get away from going to command line as possible.

Joe

So far so good Zack,

When you create the MST I think it has options in there for local source
cacheing, though for me that is not that much of an issue, I just need it to
get deployed...

I am getting an error on the DC I am deploying from (the one thats hosting
the GPO) but I think its probably because of my MST file, I am going to
recreate it and see. Its still deploying properly though so...

Joe

Thanks Joseph. That was actually the next thing on my list to try,
believe it or not. I was just trying to avoid a 'normal' admin install
point, as using one disables the local source caching I believe.

Let me know how it goes, and I'll do the same!

-Z-

Zack, here is how far I have now gotten with it:

First though, I got the info from the latest issue of this mag:

http://www.winnetmag.com/

I highly reccommend a subscription!

1. Create an Admin Install Point copy the Office CD Image local
2. Drop to CMD Prompt and goto the office folder, type: setup /a

This will create an admin image wherever you specify (for me it was on a
DFS
Share), you also put in your CD Key there...

3. Hit GO! This took me about 3 hours to get an uncompressed Admin Point
and its over gigE.

The next 2 steps I am in process of doing now, dunno which order though,
I
ASSUME it will be:

4. Run the patch on the admin point:

(Here is the EXACT command I ran minus my domain in x's)
msiexec.exe /p "c:\Office 2003 SP1\MAINSP1op.msp" /a
"\\xxx\ddmainroot\Deployment\Applications\Microsoft\Microsoft Office
2003\Office 2003\PRO11.MSI" /qb /lv* c:\log.txt

5. Create an MST for the overall installer to tell it where your
templates
are and all that...



Right now I am running the patch so I will post back when its through the
GPO and tell you if its installed properly.

Joe
Just to clarify--I'm talking about a *compressed CD image* (ie copy of
the
CD), *not* an administrative installation point (created with setup.exe
/a). With your method here I still get an error message relating to the
key... Hmm.

-Z-

On Fri, 27 Aug 2004 13:28:23 -0700, Deji Akomolafe
<[email protected]>
wrote:

A workaround I've found for this is to do the patch this way:

msiexec.exe /p [path\name of MSP file] /a [path\name of MSI file]
PIDKEY=[your-25-digit-CD-KEY] /qb

If you don't know your PIDKEY, use the MST viewer to examine your MST
file
and you will find it there. Of course, you don't include the "[" or
"]"
in
the syntax above