• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 296
  • Last Modified:

GPO Software installs, installing at every boot and login

We use both Computer side and user side installs via GPO.  Seeing recently where both are re-installing at every reboot or login, rather than recognizing the software is already installed.  Not occuring with every install, but most.  Each GPO is configured exactly the same way, just pointing to different .msi installs.  Server 2008 SR2; occuring on both WinXP Pro SP3 systems and Windows 7 Enterprise SP1.
0
sloth10k
Asked:
sloth10k
1 Solution
 
McKnifeCommented:
Hi.

You should be familiar with the event log, I suppose. Look for reasons, why the Installation Fails (I suppose it's failing to reinstall and retries and retries).
0
 
Will SzymkowskiSenior Solution ArchitectCommented:
Are you using the software installation GPO to install the software or are you using a script to call an MSI? If you are using a script this is probably the issue as it cannot determine if the software has been installed and will continue to run each time the machine reboots.

If you are using the Software Installation then I would run rsop.msc and see if the policy is failing somewhere. You can also check the event viewer to get more information on the Group Policies that have been applied.

I would start there.
0
 
sloth10kAuthor Commented:
No errors in the log as it successfuly installs every time. Using Software Installation to point to an MSI that is in abn open share.
0
 [eBook] Windows Nano Server

Download this FREE eBook and learn all you need to get started with Windows Nano Server, including deployment options, remote management
and troubleshooting tips and tricks

 
nappy_dCommented:
So you have this set to run at logon?  If that is the case, it will always run and install.

If you want it to run at login you should create a script to do the following:

check for a file in "%programfiles%\application directory\<fileName.txt>"
If the file exists stop install process
else if the file does not exist, start installation
after installation completes, create file <fileName.txt>

The above should run everytime a user logs on or the computer boots, if the application is not smart enough to be aware that the installation has already run.

Hope this helps.
0
 
sloth10kAuthor Commented:
I think that's going to create a problem for version updates of these applications.  We could change the .txt file and the script each time, but that could get a bit tedious.
0
 
nappy_dCommented:
Yes and no. I had a similar issue a year or so back. There's much you can do. And yes that's what I had to do was to create. Versioned text file name.

If you are only updating every few month instead of every week this should not be that big an issue. In the end, it's only one script and one line you have to update for your GPO deployment. ...just a thought.
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Tackle projects and never again get stuck behind a technical roadblock.
Join Now