Slipstream Project 2003 with SP2

F

FRCarters

I know how to slipstream SP2 into Project 2003. The problem I'm having is
after I do so it no longer caches the source files on the PC anymore. I would
like to be able to send out a CD to my offsite employees that includes SP2
and still cache's the source files on the PC. Is this possible? This would
really help me.
Thanks in advance!
Vince
 
G

Goose[MS]

What method are you using to "slipstream" SP2? If you're chaining the
installation of SP2 after you install Project, then you should be able to set
the local cache as active by suing the CDCACHE=2 on the installation command.
If you're using an Admin Installation Point, the local caching of files known
as the Local Installation Source (LIS) is not available.

--
Gustavo
Software Test Engineer
Microsoft

Legal Disclaimer: This posting is provided "AS IS" with no warranties, and
confers no rights.
 
F

FRCarters

Thanks for the reply. I believe I am using an admin installation point. This
way it is all inclusive when I burn my CD. Do you have any advice on using
"chaining"

Again,
I appreciate your response.
Thanks,
Vince
 
F

FRCarters

You have been a Great help. I have one further question. I have edit my
setup.ini file to do a basic install (Display) so the user doesn't have to
put in the product key. It runs through the setup fine. Then it goes to
install SP2 but it stops and prompts me to select yes or no to install the
update. Then prompts to accept the license agreement. Once I select yes, it
goes through fine and is complete. How can I get the service pack not to
prompt me for those questions? Your help is greatly appreciated.

Thanks,
Vince
 
G

Goose[MS]

I guess I need some more info to answer your question.
From your post I assume you're using the executable (.exe) file to install
the patch, you can also extract the .MSP file inside to install that directly
by editing these fields in the setup.ini file for the chained install

[ChainedInstall_1]
TASKTYPE=exe
PATH=C:\Windows\System32\MSIExec.exe
CmdLine=\\server\share\admin_install_point\1234\[MSP file] /qb /lpiwaeo
[path\name of log file]

The "/qb" command line switch is what avoids all UI when installing patches.
I haven't tried chaining the executable in this fashion, but if you did, you
should try passing the "/q" command line switch for a quiet installation.
Lemme know if this works.

--
Gustavo
Software Test Engineer
Microsoft

Legal Disclaimer: This posting is provided "AS IS" with no warranties, and
confers no rights.
 
F

FRCarters

Here is some more information. I am using the executable (.exe). I'm willing
to do it anyway I can to make this work. I am curious about the command line.
In the example of the command line you gave me it is showing the path of a
server. This install will come from a CD. Will that work? Do I just change
the path somehow to reflect that it is installing from a CD? If I use the
command line then maybe the /q switch will work? What do you think? Here is
what I have in my setup.ini:

[Options]
PIDKEY=R3WHV6MVCH73X2W7C6YDYG9VM

[Display]
Display=basic

[ChainedInstall_1]
TaskType=exe
Path=\SP2\Visio2003SP2-KB887622-FullFile-ENU.exe
Display=none
CompletionNotice=Yes
EXE=Visio2003SP2-KB887622-FullFile-ENU.exe /q

These modifications has allowed me to install Office 2003 without user
interaction up to the point of the service pack install.

I hope this gives you better insight to what I'm trying to accomplish.
You've got me so close to this point. I'm very excited about getting this.

Thanks,
Vince

Goose said:
I guess I need some more info to answer your question.
From your post I assume you're using the executable (.exe) file to install
the patch, you can also extract the .MSP file inside to install that directly
by editing these fields in the setup.ini file for the chained install

[ChainedInstall_1]
TASKTYPE=exe
PATH=C:\Windows\System32\MSIExec.exe
CmdLine=\\server\share\admin_install_point\1234\[MSP file] /qb /lpiwaeo
[path\name of log file]

The "/qb" command line switch is what avoids all UI when installing patches.
I haven't tried chaining the executable in this fashion, but if you did, you
should try passing the "/q" command line switch for a quiet installation.
Lemme know if this works.

--
Gustavo
Software Test Engineer
Microsoft

Legal Disclaimer: This posting is provided "AS IS" with no warranties, and
confers no rights.


FRCarters said:
You have been a Great help. I have one further question. I have edit my
setup.ini file to do a basic install (Display) so the user doesn't have to
put in the product key. It runs through the setup fine. Then it goes to
install SP2 but it stops and prompts me to select yes or no to install the
update. Then prompts to accept the license agreement. Once I select yes, it
goes through fine and is complete. How can I get the service pack not to
prompt me for those questions? Your help is greatly appreciated.

Thanks,
Vince
 
G

Goose[MS]

The path to the exe you're pointing to can be pretty much anywhere. In your
case it isn't a server, but a CD dirve letter (in the example below I used
D:\). Just make sure the machine's you'll be running this on all have the CD
drive mapped to the same drive.
Give this command line a try, it should work:
[ChainedInstall_1]
TaskType=exe
Path=D:\SP2\Visio2003SP2-KB887622-FullFile-ENU.exe
Display=none
CompletionNotice=Yes
CmdLine=/q

Let me know if this works for you.

--
Gustavo
Software Test Engineer
Microsoft

Legal Disclaimer: This posting is provided "AS IS" with no warranties, and
confers no rights.


FRCarters said:
Here is some more information. I am using the executable (.exe). I'm willing
to do it anyway I can to make this work. I am curious about the command line.
In the example of the command line you gave me it is showing the path of a
server. This install will come from a CD. Will that work? Do I just change
the path somehow to reflect that it is installing from a CD? If I use the
command line then maybe the /q switch will work? What do you think? Here is
what I have in my setup.ini:

[Options]
PIDKEY=R3WHV6MVCH73X2W7C6YDYG9VM

[Display]
Display=basic

[ChainedInstall_1]
TaskType=exe
Path=\SP2\Visio2003SP2-KB887622-FullFile-ENU.exe
Display=none
CompletionNotice=Yes
EXE=Visio2003SP2-KB887622-FullFile-ENU.exe /q

These modifications has allowed me to install Office 2003 without user
interaction up to the point of the service pack install.

I hope this gives you better insight to what I'm trying to accomplish.
You've got me so close to this point. I'm very excited about getting this.

Thanks,
Vince

Goose said:
I guess I need some more info to answer your question.
From your post I assume you're using the executable (.exe) file to install
the patch, you can also extract the .MSP file inside to install that directly
by editing these fields in the setup.ini file for the chained install

[ChainedInstall_1]
TASKTYPE=exe
PATH=C:\Windows\System32\MSIExec.exe
CmdLine=\\server\share\admin_install_point\1234\[MSP file] /qb /lpiwaeo
[path\name of log file]

The "/qb" command line switch is what avoids all UI when installing patches.
I haven't tried chaining the executable in this fashion, but if you did, you
should try passing the "/q" command line switch for a quiet installation.
Lemme know if this works.

--
Gustavo
Software Test Engineer
Microsoft

Legal Disclaimer: This posting is provided "AS IS" with no warranties, and
confers no rights.


FRCarters said:
You have been a Great help. I have one further question. I have edit my
setup.ini file to do a basic install (Display) so the user doesn't have to
put in the product key. It runs through the setup fine. Then it goes to
install SP2 but it stops and prompts me to select yes or no to install the
update. Then prompts to accept the license agreement. Once I select yes, it
goes through fine and is complete. How can I get the service pack not to
prompt me for those questions? Your help is greatly appreciated.

Thanks,
Vince

:

I sure do. Check out this article on deploying Office updates
http://office.microsoft.com/en-us/assistance/HA011402381033.aspx
it should have all the info you need.

--
Gustavo
Software Test Engineer
Microsoft

Legal Disclaimer: This posting is provided "AS IS" with no warranties, and
confers no rights.


:

Thanks for the reply. I believe I am using an admin installation point. This
way it is all inclusive when I burn my CD. Do you have any advice on using
"chaining"

Again,
I appreciate your response.
Thanks,
Vince

:

What method are you using to "slipstream" SP2? If you're chaining the
installation of SP2 after you install Project, then you should be able to set
the local cache as active by suing the CDCACHE=2 on the installation command.
If you're using an Admin Installation Point, the local caching of files known
as the Local Installation Source (LIS) is not available.

--
Gustavo
Software Test Engineer
Microsoft

Legal Disclaimer: This posting is provided "AS IS" with no warranties, and
confers no rights.


:

I know how to slipstream SP2 into Project 2003. The problem I'm having is
after I do so it no longer caches the source files on the PC anymore. I would
like to be able to send out a CD to my offsite employees that includes SP2
and still cache's the source files on the PC. Is this possible? This would
really help me.
Thanks in advance!
Vince
 
F

FRCarters

FYI. I just wanted to let you know that Friday I went in a different
direction. I used the "ohotfix" to achieve what I was trying to accomplish. I
was able to hide the product key, cache the source files and give completion
notice. Thank so much for your help. I consider this to be closed.
Vince

Goose said:
The path to the exe you're pointing to can be pretty much anywhere. In your
case it isn't a server, but a CD dirve letter (in the example below I used
D:\). Just make sure the machine's you'll be running this on all have the CD
drive mapped to the same drive.
Give this command line a try, it should work:
[ChainedInstall_1]
TaskType=exe
Path=D:\SP2\Visio2003SP2-KB887622-FullFile-ENU.exe
Display=none
CompletionNotice=Yes
CmdLine=/q

Let me know if this works for you.

--
Gustavo
Software Test Engineer
Microsoft

Legal Disclaimer: This posting is provided "AS IS" with no warranties, and
confers no rights.


FRCarters said:
Here is some more information. I am using the executable (.exe). I'm willing
to do it anyway I can to make this work. I am curious about the command line.
In the example of the command line you gave me it is showing the path of a
server. This install will come from a CD. Will that work? Do I just change
the path somehow to reflect that it is installing from a CD? If I use the
command line then maybe the /q switch will work? What do you think? Here is
what I have in my setup.ini:

[Options]
PIDKEY=R3WHV6MVCH73X2W7C6YDYG9VM

[Display]
Display=basic

[ChainedInstall_1]
TaskType=exe
Path=\SP2\Visio2003SP2-KB887622-FullFile-ENU.exe
Display=none
CompletionNotice=Yes
EXE=Visio2003SP2-KB887622-FullFile-ENU.exe /q

These modifications has allowed me to install Office 2003 without user
interaction up to the point of the service pack install.

I hope this gives you better insight to what I'm trying to accomplish.
You've got me so close to this point. I'm very excited about getting this.

Thanks,
Vince

Goose said:
I guess I need some more info to answer your question.
From your post I assume you're using the executable (.exe) file to install
the patch, you can also extract the .MSP file inside to install that directly
by editing these fields in the setup.ini file for the chained install

[ChainedInstall_1]
TASKTYPE=exe
PATH=C:\Windows\System32\MSIExec.exe
CmdLine=\\server\share\admin_install_point\1234\[MSP file] /qb /lpiwaeo
[path\name of log file]

The "/qb" command line switch is what avoids all UI when installing patches.
I haven't tried chaining the executable in this fashion, but if you did, you
should try passing the "/q" command line switch for a quiet installation.
Lemme know if this works.

--
Gustavo
Software Test Engineer
Microsoft

Legal Disclaimer: This posting is provided "AS IS" with no warranties, and
confers no rights.


:

You have been a Great help. I have one further question. I have edit my
setup.ini file to do a basic install (Display) so the user doesn't have to
put in the product key. It runs through the setup fine. Then it goes to
install SP2 but it stops and prompts me to select yes or no to install the
update. Then prompts to accept the license agreement. Once I select yes, it
goes through fine and is complete. How can I get the service pack not to
prompt me for those questions? Your help is greatly appreciated.

Thanks,
Vince

:

I sure do. Check out this article on deploying Office updates
http://office.microsoft.com/en-us/assistance/HA011402381033.aspx
it should have all the info you need.

--
Gustavo
Software Test Engineer
Microsoft

Legal Disclaimer: This posting is provided "AS IS" with no warranties, and
confers no rights.


:

Thanks for the reply. I believe I am using an admin installation point. This
way it is all inclusive when I burn my CD. Do you have any advice on using
"chaining"

Again,
I appreciate your response.
Thanks,
Vince

:

What method are you using to "slipstream" SP2? If you're chaining the
installation of SP2 after you install Project, then you should be able to set
the local cache as active by suing the CDCACHE=2 on the installation command.
If you're using an Admin Installation Point, the local caching of files known
as the Local Installation Source (LIS) is not available.

--
Gustavo
Software Test Engineer
Microsoft

Legal Disclaimer: This posting is provided "AS IS" with no warranties, and
confers no rights.


:

I know how to slipstream SP2 into Project 2003. The problem I'm having is
after I do so it no longer caches the source files on the PC anymore. I would
like to be able to send out a CD to my offsite employees that includes SP2
and still cache's the source files on the PC. Is this possible? This would
really help me.
Thanks in advance!
Vince
 
G

Goose[MS]

Thanks for posting back with the resolution.
Glad I could help.

--
Gustavo
Software Test Engineer
Microsoft

Legal Disclaimer: This posting is provided "AS IS" with no warranties, and
confers no rights.


FRCarters said:
FYI. I just wanted to let you know that Friday I went in a different
direction. I used the "ohotfix" to achieve what I was trying to accomplish. I
was able to hide the product key, cache the source files and give completion
notice. Thank so much for your help. I consider this to be closed.
Vince

Goose said:
The path to the exe you're pointing to can be pretty much anywhere. In your
case it isn't a server, but a CD dirve letter (in the example below I used
D:\). Just make sure the machine's you'll be running this on all have the CD
drive mapped to the same drive.
Give this command line a try, it should work:
[ChainedInstall_1]
TaskType=exe
Path=D:\SP2\Visio2003SP2-KB887622-FullFile-ENU.exe
Display=none
CompletionNotice=Yes
CmdLine=/q

Let me know if this works for you.

--
Gustavo
Software Test Engineer
Microsoft

Legal Disclaimer: This posting is provided "AS IS" with no warranties, and
confers no rights.


FRCarters said:
Here is some more information. I am using the executable (.exe). I'm willing
to do it anyway I can to make this work. I am curious about the command line.
In the example of the command line you gave me it is showing the path of a
server. This install will come from a CD. Will that work? Do I just change
the path somehow to reflect that it is installing from a CD? If I use the
command line then maybe the /q switch will work? What do you think? Here is
what I have in my setup.ini:

[Options]
PIDKEY=R3WHV6MVCH73X2W7C6YDYG9VM

[Display]
Display=basic

[ChainedInstall_1]
TaskType=exe
Path=\SP2\Visio2003SP2-KB887622-FullFile-ENU.exe
Display=none
CompletionNotice=Yes
EXE=Visio2003SP2-KB887622-FullFile-ENU.exe /q

These modifications has allowed me to install Office 2003 without user
interaction up to the point of the service pack install.

I hope this gives you better insight to what I'm trying to accomplish.
You've got me so close to this point. I'm very excited about getting this.

Thanks,
Vince

:

I guess I need some more info to answer your question.
From your post I assume you're using the executable (.exe) file to install
the patch, you can also extract the .MSP file inside to install that directly
by editing these fields in the setup.ini file for the chained install

[ChainedInstall_1]
TASKTYPE=exe
PATH=C:\Windows\System32\MSIExec.exe
CmdLine=\\server\share\admin_install_point\1234\[MSP file] /qb /lpiwaeo
[path\name of log file]

The "/qb" command line switch is what avoids all UI when installing patches.
I haven't tried chaining the executable in this fashion, but if you did, you
should try passing the "/q" command line switch for a quiet installation.
Lemme know if this works.

--
Gustavo
Software Test Engineer
Microsoft

Legal Disclaimer: This posting is provided "AS IS" with no warranties, and
confers no rights.


:

You have been a Great help. I have one further question. I have edit my
setup.ini file to do a basic install (Display) so the user doesn't have to
put in the product key. It runs through the setup fine. Then it goes to
install SP2 but it stops and prompts me to select yes or no to install the
update. Then prompts to accept the license agreement. Once I select yes, it
goes through fine and is complete. How can I get the service pack not to
prompt me for those questions? Your help is greatly appreciated.

Thanks,
Vince

:

I sure do. Check out this article on deploying Office updates
http://office.microsoft.com/en-us/assistance/HA011402381033.aspx
it should have all the info you need.

--
Gustavo
Software Test Engineer
Microsoft

Legal Disclaimer: This posting is provided "AS IS" with no warranties, and
confers no rights.


:

Thanks for the reply. I believe I am using an admin installation point. This
way it is all inclusive when I burn my CD. Do you have any advice on using
"chaining"

Again,
I appreciate your response.
Thanks,
Vince

:

What method are you using to "slipstream" SP2? If you're chaining the
installation of SP2 after you install Project, then you should be able to set
the local cache as active by suing the CDCACHE=2 on the installation command.
If you're using an Admin Installation Point, the local caching of files known
as the Local Installation Source (LIS) is not available.

--
Gustavo
Software Test Engineer
Microsoft

Legal Disclaimer: This posting is provided "AS IS" with no warranties, and
confers no rights.


:

I know how to slipstream SP2 into Project 2003. The problem I'm having is
after I do so it no longer caches the source files on the PC anymore. I would
like to be able to send out a CD to my offsite employees that includes SP2
and still cache's the source files on the PC. Is this possible? This would
really help me.
Thanks in advance!
Vince
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top