Windows Thread, MSi Installation Failure Problem in Technical; I created an MSi to install 2Simple French and another for 2DIY, The DIY is fine but the french one ...
17th June 2009, 03:04 PM #1
MSi Installation Failure Problem
I created an MSi to install 2Simple French and another for 2DIY, The DIY is fine but the french one is now running at every user login on the laptops. I have been messing around for ages and have lost the original entry in the GPO (the folder and Msi are still in place)
The installation fails because it tries to create an icon on the desktop. I have changed all permissions on that folder and no difference!!!
The MSI package will install on each laptop when logged in as the manager.
I have cleared the local profile even renamed the NTUSER file on the server.
I guess my question is can I cancel a msi install once it has been created?
As I said the entry in the GGP has been deleted but it is still trying to install.
17th June 2009, 03:17 PM #2
Hi you can cancel the msi install by removing the msi file from the group policy that is being used to apply it.
find the msi in the gpo right click I think of the top of my head it is All-tasks chose the top option.
In regards to 2simple. I have installed quite a bit of this most of it these days comes with an msi file that can be used to install the program through group policy. if not try concacting the software vendor and see if they have an MSI for that piece of software. the y may or may not be able to help.
this would be the easiest way.
17th June 2009, 03:23 PM #3
You may have some GPO setting that disables users to add or change items on the desktop rather than it just being permissions. The easiest way round is to recreate the MSI and delete the desktop item it creates while in the middle of the snapshot. I don't know what sotwware you used but generally they are before and after snapshots so in the middle delete the icon.
17th June 2009, 04:02 PM #4
How is the software being deployed is it being deployed at the user level or at the computer level?
17th June 2009, 05:48 PM #5
unfortunately it is user level. I have tried again with a new msi from 2simple and got that right installed at computer level as the laptop booted. The problem I have would appear to be the original msi that I set at user level (never again) It keeps trying to install the 2french even though the later msi has already installed it successfully.
18th June 2009, 09:29 AM #6
Have you removed this user level msi deployment from the gpo. Remove the file from the gpo and then gpo. also have you done a gpudate /force on one of the computers.
18th June 2009, 09:50 AM #7
I have the same sort of problems with some MSI's My desktops come from the server so I don't want the MSI to install any shortcuts .... I use Orca to edit out the line that puts the shortcut onto the desktop so that when the MSI runs it just installs the programme but no shortcuts ... I then add the shortcut to my redirected desktops ...
Just out of interest .. I always install via the computer side of the GPO ... and just add the PC's that I want the gpo to effect ... Is there an advantage in doing it from the user side?
18th June 2009, 09:58 AM #8
we advertise software for laptops as all depts do not require the same sort of level of software distro that the curriculm PC's need. But obviously other schools have differing requirements for use of laptops.
Is there an advantage in doing it from the user side?
16th July 2009, 02:41 PM #9
- Rep Power
Just to confirm that yes, we do provide MSIs for all our programs. We have also created a set of MSIs without shortcuts because of the problems described below
29th July 2009, 10:22 AM #10
- Rep Power
The following may help. I spotted it in a web manual I'm reading:
You can enable 'verbose' MSI logging. This can be enabled on the client by creating the following Registry value:
Key: HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Win dows\Installer
This will create log files in the %temp% folder (\Windows\Temp for standard Group Policy MSI deployment. The users’ own temporary folder for manual MSI deployment). This following document explains this in detail:
How to enable Windows Installer logging
After this setting has been enabled, reboot the PC, and allow Windows to attempt to MSI installation again. When this process has completed (or nothing has happened) log into the machine and check the log files created in the \Windows\Temp folder.
If this technique does not reveal the cause of the problem it may also be useful to enable ‘verbose’ logging for the Windows Group Policy engine. Please remember that this is an advanced technique and it may take some time to decipher the log files. You can enable this logging by creating the following registry value. It may also be necessary to create the Diagnostics key if one is not already present.
Key: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Diagnostics
After this setting has been enabled, reboot the PC, and repeat the installation process described above. The Group Policy engine will create a file called Appmgmt.log in the C:\Windows\Debug\Usermode folder. This is further explained here:
Troubleshooting Program Deployment By Using Verbose Logging
NB: You may also need to create the Usermode folder if it does not already exist.
By steveo2000 in forum Windows
Last Post: 20th February 2009, 08:43 PM
By TheFopp in forum Windows
Last Post: 19th November 2008, 10:05 AM
By HMCTech in forum EduGeek Joomla 1.0 Package
Last Post: 10th April 2008, 08:59 PM
By WithoutMotive in forum Windows
Last Post: 7th February 2008, 03:19 PM
By WithoutMotive in forum Windows
Last Post: 23rd September 2007, 07:27 PM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)