Can't Install MSI with active directory

  • Thread starter Thread starter Laurence Nuttall
  • Start date Start date
L

Laurence Nuttall

Using Win 2003 server,
using active directory,
I cannot get an assigned msi file to install
on a client (win XP) box.

I have been on the phone with microsoft support for
a couple of months now, they are about ready to tell
me that they cannot figure it out. That there is something wrong with
the MSI file.

If I call installshield, (I used install shield express to create the
msi file), they ask me if the application installs when I run setup
or double click on the msi file. When I say Yes, the conversation
is over. Install shield says that if the msi installs by double clicking
on the msi file, and doesn't work with active directory, then it is not
there problem, That it is an active directory problem.

Does anyone have any suggestions as to where I can go to get help?

Thanks in Advance,

Laurence Nuttall
Programmer Analyst III
UCLA - Division of Continuing Education
 
Laurence,

Quick question: if you use GPO to deploy software from an application that
makes use of a 'native' .msi file does that work? An example of a software
application that makes use of a 'native' .msi file would be Office 2000 /
Office XP / Office 2003 or perhaps Adobe Acrobat Reader 6.0? I ask because
there can be problems with 'home brewed' .msi packages. I am not
questioning your ability to do this correctly, please do not misunderstand
my question.

I would also check to make sure that all is well with DNS.

Have you run any utilities to verify that the GPO is indeed reaching the
client? Have you looked in the event logs for any confirmations / errors?

HTH,

Cary
 
Native applications are being installed using GPO.

Microsoft had me turn on verbose logging,
and I have send them the logs, (about a dozen). The logs
are quite complex and cryptic and I cannot completely
decipher them.

I am not sure what you mean by all is well with DNS.
Domain Name system?

It probably is the home grown msi file, but I have no clues
as to what could be wrong with it. As Installshield washes there
hands in the matter.

Thank You for your help,

Laurence Nuttall
Programmer Analyst III
UCLA - Division of Continuing Education
 
Laurence,

I was asking about DNS as so much in WIN2000 is DNS related that when there
is a problem like the one that you are experiencing I immediately think: DNS
could play a part in this problem. However, if 'native' applications are
working just fine then it just might be the 'home grown' msi file.

Laurence, take a look at WinInstall Lite, which is located on the WIN2000
Server CD. I know that I have used it a couple of times to create a 'home
grown' msi file ( about 18 months ago or so! ). It worked out just fine as
I remember. IIRC, you make a clean install of WIN2000, take that 'before'
snap shot, install the application(s) in question and then take an 'after'
snap shot.

It might be worth a look ( and does not require any cash outlay! ).

Hope that you get to the bottom of this.

Cary


Also, the 'native' msi application
 
Thank You for your suggestion

Larry
Laurence,

I was asking about DNS as so much in WIN2000 is DNS related that when there
is a problem like the one that you are experiencing I immediately think: DNS
could play a part in this problem. However, if 'native' applications are
working just fine then it just might be the 'home grown' msi file.

Laurence, take a look at WinInstall Lite, which is located on the WIN2000
Server CD. I know that I have used it a couple of times to create a 'home
grown' msi file ( about 18 months ago or so! ). It worked out just fine as
I remember. IIRC, you make a clean install of WIN2000, take that 'before'
snap shot, install the application(s) in question and then take an 'after'
snap shot.

It might be worth a look ( and does not require any cash outlay! ).

Hope that you get to the bottom of this.

Cary


Also, the 'native' msi application
Native applications are being installed using GPO.

Microsoft had me turn on verbose logging,
and I have send them the logs, (about a dozen). The logs
are quite complex and cryptic and I cannot completely
decipher them.

I am not sure what you mean by all is well with DNS.
Domain Name system?

It probably is the home grown msi file, but I have no clues
as to what could be wrong with it. As Installshield washes there
hands in the matter.

Thank You for your help,

Laurence Nuttall
Programmer Analyst III
UCLA - Division of Continuing Education



Cary Shultz [A.D. MVP] wrote:

Laurence,

Quick question: if you use GPO to deploy software from an application
that
makes use of a 'native' .msi file does that work? An example of a
software
application that makes use of a 'native' .msi file would be Office 2000
/
Office XP / Office 2003 or perhaps Adobe Acrobat Reader 6.0? I ask
because
there can be problems with 'home brewed' .msi packages. I am not
questioning your ability to do this correctly, please do not
misunderstand
my question.

I would also check to make sure that all is well with DNS.

Have you run any utilities to verify that the GPO is indeed reaching the
client? Have you looked in the event logs for any confirmations /
errors?
HTH,

Cary



Using Win 2003 server,
using active directory,
I cannot get an assigned msi file to install
on a client (win XP) box.

I have been on the phone with microsoft support for
a couple of months now, they are about ready to tell
me that they cannot figure it out. That there is something wrong with
the MSI file.

If I call installshield, (I used install shield express to create the
msi file), they ask me if the application installs when I run setup
or double click on the msi file. When I say Yes, the conversation
is over. Install shield says that if the msi installs by double clicking
on the msi file, and doesn't work with active directory, then it is not
there problem, That it is an active directory problem.

Does anyone have any suggestions as to where I can go to get help?

Thanks in Advance,

Laurence Nuttall
Programmer Analyst III
UCLA - Division of Continuing Education
 
Back
Top