Calling a VB Script from within an MST

[Adrian Moss]

Hello All

In a scripted deployment of Office 2003 I'm currently involved in, I want to
call a VB Script from within the MST file.

We will be deploying the CD image to a folder on the local hard drive (using
LANDesk) and the VB Script will also be held in this location.

I've been trying to use the Add Installations and Run Programs page of the
Custom Installation Wizard but can't seem to get it to work. I've tried just
calling the VB Script, and also calling cscript with the VBS as an argument,
with no luck.

Can anyone tell me whether what I'm trying to do is actually possible and,
if so, give any advice on using that part of the CIW?

As background, the VB Script is just a couple of lines that copies a
registry entry from one area to a new key.

Many thanks,

Adrian

 

[Susan Ramlet]

Hi, Adrian,

Can you use the installation chaining instructions here:

Microsoft Office Assistance: Deploying Office and Other Products Together:
http://office.microsoft.com/en-us/assistance/HA011402051033.aspx#sub_10

 

[Susan Ramlet]

Hi, Adrian,

Can you use the installation chaining instructions here:

Microsoft Office Assistance: Deploying Office and Other Products Together:
http://office.microsoft.com/en-us/assistance/HA011402051033.aspx#sub_10

 

[Susan Ramlet]

Hi, Adrian,

Can you use the installation chaining instructions here:

Microsoft Office Assistance: Deploying Office and Other Products Together:
http://office.microsoft.com/en-us/assistance/HA011402051033.aspx#sub_10

 

[Susan Ramlet]

Hi, Adrian,

Can you use the installation chaining instructions here:

Microsoft Office Assistance: Deploying Office and Other Products Together:
http://office.microsoft.com/en-us/assistance/HA011402051033.aspx#sub_10

 

[Susan Ramlet]

Hi, Adrian,

Can you use the installation chaining instructions here:

Microsoft Office Assistance: Deploying Office and Other Products Together:
http://office.microsoft.com/en-us/assistance/HA011402051033.aspx#sub_10

 

[Susan Ramlet]

Hi, Adrian,

Can you use the installation chaining instructions here:

Microsoft Office Assistance: Deploying Office and Other Products Together:
http://office.microsoft.com/en-us/assistance/HA011402051033.aspx#sub_10

 

[Susan Ramlet]

Hi, Adrian,

Can you use the installation chaining instructions here:

Microsoft Office Assistance: Deploying Office and Other Products Together:
http://office.microsoft.com/en-us/assistance/HA011402051033.aspx#sub_10

 

[Susan Ramlet]

Hi, Adrian,

Can you use the installation chaining instructions here:

Microsoft Office Assistance: Deploying Office and Other Products Together:
http://office.microsoft.com/en-us/assistance/HA011402051033.aspx#sub_10

 

[Susan Ramlet]

Hi, Adrian,

Can you use the installation chaining instructions here:

Microsoft Office Assistance: Deploying Office and Other Products Together:
http://office.microsoft.com/en-us/assistance/HA011402051033.aspx#sub_10

 

[Adrian Moss]

Hello Susan

Thanks for that. We may be able to do that (we're using that method for
something else).

However, I've sorted out my cscript problem. I turned on logging for the
Office installation and it pointed out the obvious error....it looks like you
have to add in the full path for both cscript and the vbscript e.g. [target]
c:\winnt\system32\cscript.exe [argument] c:\installs\office2003\grouptemp.vbs

In my initial testing I had assumed that Windows would be able to find
cscript itself, but I was wrong.

Many thanks for your help,

Adrian

 

[Adrian Moss]

Hello Susan

Thanks for that. We may be able to do that (we're using that method for
something else).

However, I've sorted out my cscript problem. I turned on logging for the
Office installation and it pointed out the obvious error....it looks like you
have to add in the full path for both cscript and the vbscript e.g. [target]
c:\winnt\system32\cscript.exe [argument] c:\installs\office2003\grouptemp.vbs

In my initial testing I had assumed that Windows would be able to find
cscript itself, but I was wrong.

Many thanks for your help,

Adrian

 

[Adrian Moss]

Hello Susan

Thanks for that. We may be able to do that (we're using that method for
something else).

However, I've sorted out my cscript problem. I turned on logging for the
Office installation and it pointed out the obvious error....it looks like you
have to add in the full path for both cscript and the vbscript e.g. [target]
c:\winnt\system32\cscript.exe [argument] c:\installs\office2003\grouptemp.vbs

In my initial testing I had assumed that Windows would be able to find
cscript itself, but I was wrong.

Many thanks for your help,

Adrian

 

[Adrian Moss]

Hello Susan

Thanks for that. We may be able to do that (we're using that method for
something else).

However, I've sorted out my cscript problem. I turned on logging for the
Office installation and it pointed out the obvious error....it looks like you
have to add in the full path for both cscript and the vbscript e.g. [target]
c:\winnt\system32\cscript.exe [argument] c:\installs\office2003\grouptemp.vbs

In my initial testing I had assumed that Windows would be able to find
cscript itself, but I was wrong.

Many thanks for your help,

Adrian

 

[Adrian Moss]

Hello Susan

Thanks for that. We may be able to do that (we're using that method for
something else).

However, I've sorted out my cscript problem. I turned on logging for the
Office installation and it pointed out the obvious error....it looks like you
have to add in the full path for both cscript and the vbscript e.g. [target]
c:\winnt\system32\cscript.exe [argument] c:\installs\office2003\grouptemp.vbs

In my initial testing I had assumed that Windows would be able to find
cscript itself, but I was wrong.

Many thanks for your help,

Adrian

 

[Adrian Moss]

Hello Susan

Thanks for that. We may be able to do that (we're using that method for
something else).

However, I've sorted out my cscript problem. I turned on logging for the
Office installation and it pointed out the obvious error....it looks like you
have to add in the full path for both cscript and the vbscript e.g. [target]
c:\winnt\system32\cscript.exe [argument] c:\installs\office2003\grouptemp.vbs

In my initial testing I had assumed that Windows would be able to find
cscript itself, but I was wrong.

Many thanks for your help,

Adrian

 

[Adrian Moss]

Hello Susan

Thanks for that. We may be able to do that (we're using that method for
something else).

However, I've sorted out my cscript problem. I turned on logging for the
Office installation and it pointed out the obvious error....it looks like you
have to add in the full path for both cscript and the vbscript e.g. [target]
c:\winnt\system32\cscript.exe [argument] c:\installs\office2003\grouptemp.vbs

In my initial testing I had assumed that Windows would be able to find
cscript itself, but I was wrong.

Many thanks for your help,

Adrian

 

[Adrian Moss]

Hello Susan

Thanks for that. We may be able to do that (we're using that method for
something else).

However, I've sorted out my cscript problem. I turned on logging for the
Office installation and it pointed out the obvious error....it looks like you
have to add in the full path for both cscript and the vbscript e.g. [target]
c:\winnt\system32\cscript.exe [argument] c:\installs\office2003\grouptemp.vbs

In my initial testing I had assumed that Windows would be able to find
cscript itself, but I was wrong.

Many thanks for your help,

Adrian

 

[Adrian Moss]

Hello Susan

Thanks for that. We may be able to do that (we're using that method for
something else).

However, I've sorted out my cscript problem. I turned on logging for the
Office installation and it pointed out the obvious error....it looks like you
have to add in the full path for both cscript and the vbscript e.g. [target]
c:\winnt\system32\cscript.exe [argument] c:\installs\office2003\grouptemp.vbs

In my initial testing I had assumed that Windows would be able to find
cscript itself, but I was wrong.

Many thanks for your help,

Adrian