Office 2003 Admin Install

[AtvFun67]

I have created an admin install with our VL Office 2003 product.

However, my users cannot install it because they are not
administrators.
Therefore, If I "RUN AS" to install it as administrator it installs
fine, but the first time any "user" runs any of the office apps, it
starts "Installing" again (not the full product, just what I believe is
the user config for the package). Then it fails because they are not an
administrator.

If I temporarially make them a member of the administrators group, run
each of the office apps once, then remove them from the administrators
group it works forever. However, I do not want to do that for 400
machines and 1000 users.

 

[neo [mvp outlook]]

If these workstations are in an Active Directory domain, why not use a
domain based group policy object to distribute the software to the
workstation? (When you configure the GPO, you attach to the computer
portion and not the user)

If Active Directory is not an option, any 3rd party software distribution
tools? (e.g. Microsoft's SMS, Novell's Zenworks, Diskeeper's SiteKeeper,
..etc)

 

[neo [mvp outlook]]

If these workstations are in an Active Directory domain, why not use a
domain based group policy object to distribute the software to the
workstation? (When you configure the GPO, you attach to the computer
portion and not the user)

If Active Directory is not an option, any 3rd party software distribution
tools? (e.g. Microsoft's SMS, Novell's Zenworks, Diskeeper's SiteKeeper,
..etc)

 

[neo [mvp outlook]]

If these workstations are in an Active Directory domain, why not use a
domain based group policy object to distribute the software to the
workstation? (When you configure the GPO, you attach to the computer
portion and not the user)

If Active Directory is not an option, any 3rd party software distribution
tools? (e.g. Microsoft's SMS, Novell's Zenworks, Diskeeper's SiteKeeper,
..etc)

 

[neo [mvp outlook]]

If these workstations are in an Active Directory domain, why not use a
domain based group policy object to distribute the software to the
workstation? (When you configure the GPO, you attach to the computer
portion and not the user)

If Active Directory is not an option, any 3rd party software distribution
tools? (e.g. Microsoft's SMS, Novell's Zenworks, Diskeeper's SiteKeeper,
..etc)

 

[neo [mvp outlook]]

If these workstations are in an Active Directory domain, why not use a
domain based group policy object to distribute the software to the
workstation? (When you configure the GPO, you attach to the computer
portion and not the user)

If Active Directory is not an option, any 3rd party software distribution
tools? (e.g. Microsoft's SMS, Novell's Zenworks, Diskeeper's SiteKeeper,
..etc)

 

[AtvFun67]

The machines are in AD however we use ScriptLogic to deploy our
applications (I inherited it when I took this job). I create the
packages with Ghost Enterprise AI Builder. Wouldn't I run into the
same issue I am having no matter what product I use to deploy? After
all, the problem is not with the deployment (using the Ghost AI
package), it is the "First Run" when each user tries to run word,
excel, powerpoint and outlook.

Any other thought would be appreciated.

 

[AtvFun67]

The machines are in AD however we use ScriptLogic to deploy our
applications (I inherited it when I took this job). I create the
packages with Ghost Enterprise AI Builder. Wouldn't I run into the
same issue I am having no matter what product I use to deploy? After
all, the problem is not with the deployment (using the Ghost AI
package), it is the "First Run" when each user tries to run word,
excel, powerpoint and outlook.

Any other thought would be appreciated.

 

[AtvFun67]

The machines are in AD however we use ScriptLogic to deploy our
applications (I inherited it when I took this job). I create the
packages with Ghost Enterprise AI Builder. Wouldn't I run into the
same issue I am having no matter what product I use to deploy? After
all, the problem is not with the deployment (using the Ghost AI
package), it is the "First Run" when each user tries to run word,
excel, powerpoint and outlook.

Any other thought would be appreciated.

 

[AtvFun67]

The machines are in AD however we use ScriptLogic to deploy our
applications (I inherited it when I took this job). I create the
packages with Ghost Enterprise AI Builder. Wouldn't I run into the
same issue I am having no matter what product I use to deploy? After
all, the problem is not with the deployment (using the Ghost AI
package), it is the "First Run" when each user tries to run word,
excel, powerpoint and outlook.

Any other thought would be appreciated.

 

[AtvFun67]

The machines are in AD however we use ScriptLogic to deploy our
applications (I inherited it when I took this job). I create the
packages with Ghost Enterprise AI Builder. Wouldn't I run into the
same issue I am having no matter what product I use to deploy? After
all, the problem is not with the deployment (using the Ghost AI
package), it is the "First Run" when each user tries to run word,
excel, powerpoint and outlook.

Any other thought would be appreciated.

 

[Ricki_DK]

If Ghost Console is a part the AI Builder - you should consider using
it to deploy the AI packages. Works fine for me - although I prefer
deploying Office through AD/Software installation.

Ricki

 

[Ricki_DK]

If Ghost Console is a part the AI Builder - you should consider using
it to deploy the AI packages. Works fine for me - although I prefer
deploying Office through AD/Software installation.

Ricki

 

[Ricki_DK]

If Ghost Console is a part the AI Builder - you should consider using
it to deploy the AI packages. Works fine for me - although I prefer
deploying Office through AD/Software installation.

Ricki

 

[Ricki_DK]

If Ghost Console is a part the AI Builder - you should consider using
it to deploy the AI packages. Works fine for me - although I prefer
deploying Office through AD/Software installation.

Ricki

 

[Ricki_DK]

If Ghost Console is a part the AI Builder - you should consider using
it to deploy the AI packages. Works fine for me - although I prefer
deploying Office through AD/Software installation.

Ricki

 

[neo [mvp outlook]]

You shouldn't since the kick off of the installer is nothing more than
ensuring that the files and registry key are intact. It is normal for it to
happen when a first time user logs on and launches an Office app, but not at
every logon. Sounds like something is fishy in workstation\app deployment.

I wonder if ScriptLogic is actually working under the user context and not
system. What happens if you enable the "Always install with elevated
privileges" policy. (it is found under User Configuration > Administrative
Templates > Windows Components > Windows Installer.)

 

[neo [mvp outlook]]

You shouldn't since the kick off of the installer is nothing more than
ensuring that the files and registry key are intact. It is normal for it to
happen when a first time user logs on and launches an Office app, but not at
every logon. Sounds like something is fishy in workstation\app deployment.

I wonder if ScriptLogic is actually working under the user context and not
system. What happens if you enable the "Always install with elevated
privileges" policy. (it is found under User Configuration > Administrative
Templates > Windows Components > Windows Installer.)

 

[neo [mvp outlook]]

You shouldn't since the kick off of the installer is nothing more than
ensuring that the files and registry key are intact. It is normal for it to
happen when a first time user logs on and launches an Office app, but not at
every logon. Sounds like something is fishy in workstation\app deployment.

I wonder if ScriptLogic is actually working under the user context and not
system. What happens if you enable the "Always install with elevated
privileges" policy. (it is found under User Configuration > Administrative
Templates > Windows Components > Windows Installer.)

 

[neo [mvp outlook]]

You shouldn't since the kick off of the installer is nothing more than
ensuring that the files and registry key are intact. It is normal for it to
happen when a first time user logs on and launches an Office app, but not at
every logon. Sounds like something is fishy in workstation\app deployment.

I wonder if ScriptLogic is actually working under the user context and not
system. What happens if you enable the "Always install with elevated
privileges" policy. (it is found under User Configuration > Administrative
Templates > Windows Components > Windows Installer.)