I'm fairly new to here but I've found a few solutions to problems and now I'm really stuck and hoping for some help from the experts. I've got a vendor supplied msi called Nokia Intellisync Desktop Web Toolkit which has been bought and transformed by Oracle to become Oracle PIM Sync On Demand. The MSI and transform works absolutely fine when I run it under the local admin account but when I try to push it out through SMS it installs but misses out several key files and folders and doesn't run.

Having searched though both sets of logs I can only really see that the LogonUser property is SYSTEM under the SMS install and our local admin otherwise. I can also see that the problems lie in adding files and folders to the LocalApplicationData, Common Files folder etc. If it gets installed under the local account thoguh it can still be used by any other user who logs on subsequently.

I've tried various different things and tried using the SoftwareInstallation Account but stilll nothing.

Anyone seen anything like this before and found a solution? It's driving me nuts!!
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
In your transform:

- create a new 'CurrentUser' feature
- locate any feature which has an advertised entry point, such as a shortcut
- move that feature so that it becomes a child of the 'CurrentUser' feature
- move the component(s) which contain anything which is targeted at the user's profile, such as the LocalApplicationData folders and files. Don't forget stuff in HKCU

That way, when the advertised entry-point is first used (e.g. when the shortcut - if that's what you used - is clicked), the WI engine will see that the feature is "broken" and "repair" it.

One day, enterprise vendors will work out that no-one in their customer base actually walks the estate with a CD. One day.

Meanwhile, search AppDeploy for John McFadyen's blog URL on livespace. It has a ton of stuff about repair/self-healing.
Answered 04/28/2009 by: VBScab
Red Belt

Please log in to comment
0
Thanks, I'll give that a try jsut now and get back to you. I did try using ActiveSetup to force a reinstall for each user but it didn't solve the problem.

I'll give this a bash
Answered 04/28/2009 by: DavieH
Yellow Belt

Please log in to comment
0
I did try using ActiveSetup to force a reinstall for each user but it didn't solve the problem I originally had my standard 'here's how to do Active Setup' post in the clipboard, ready to add to my response but I prefer this way so didn't bother. So, what happened with AS?
Answered 04/28/2009 by: VBScab
Red Belt

Please log in to comment
0
Not a lot to be honest. It did rerun the msiexec on logon of other users and I tried using /fu and /fa but although it seemed to run, the missing files were still not added. I really don't understand it and it's driving me nuts. Might just be my imagination but I think it's a really badly built msi!!

I'm trying the approach you suggested but I'm not getting anywhere so far. Guess I need more practice.

I'm going to try installing through SMS, taking a snapshot, uninstall then install manually and take another snapshot to see exactly what files are missing.
Answered 04/28/2009 by: DavieH
Yellow Belt

Please log in to comment
0
Guys,

have you been able to find a resolution for this. for us this is a 3rd party solution, and your experience is very welcome.

cheers
sven
Answered 05/19/2009 by: svenheijnene
Yellow Belt

Please log in to comment
0
Sven, you having this same problem with this same application or a different one? VBScab's suggestion should be applicable to any MSI having this issue.
Answered 05/19/2009 by: jcarri06
Senior Purple Belt

Please log in to comment
0
it is indeed the same application.
Answered 05/20/2009 by: svenheijnene
Yellow Belt

Please log in to comment
0
Did you already try running active setup or creating the feature structure that VBS recommended and still failing?
Answered 05/20/2009 by: jcarri06
Senior Purple Belt

Please log in to comment
0
Below is an excerpt from .\Data\1033\Readme.txt in the expanded install files:

Distributed Installation No Longer Working
------------------------------
An issue exists in the current base client code from Nokia for PIM Sync
On Demand v2.0 which prevents the ability to distribute the client software
remotely. Oracle is awaiting a fix for this issue from Nokia which is
targeted for delivery in a future patch (currently 1080.0.03). Please note
this delivery date is subject to change.
Should your organization require remote installation capabilities and are
unable to wait for a fix to be delivered, you can contact customer care to
request a prior version of the PIM Sync On Demand client (v1.8) which does
provide the ability to distribute and install the PIM Sync client remotely.

Yeppers ... I've wasted about a week trying to get this one to work anyway, but no luck yet
Answered 02/16/2010 by: jdat747
Yellow Belt

Please log in to comment
0
Yeh, but the thing is, SMS\SCCM doesn't install remotely. Packages are copied to the client and then executed locally by the System account.
Answered 02/16/2010 by: VBScab
Red Belt

Please log in to comment
0
Indeed, but the problem w/ this software is that when you install it under the system account, it doesn't work for anyone else. I've tried to manually install under the local admin, and then get the app to work for a locked down user ... even another admin user, but it fails with a dialog that says: "This program was not installed for the current user." I can get it to self heal, but I haven't gotten it to fully reinstall for a new user.

I tried using process monitor to see what the *.exe was looking for on launch, but I never got anywhere w/ that.
Answered 02/23/2010 by: jdat747
Yellow Belt

Please log in to comment
0
Sounds to me like allusers is not explicitly set to 1. Try adding ALLUSERS=1 to your msiexec command line through SCCM, and see where that gets you. In many cases, depending on how the MSI is built, if ALLUSERS is not explicitly called out on the command line, it will attempt to install to the system user account, instead of the local system account.

EDIT: Oh, and if it's just an awful msi that must be installed to a user account, just have it install only while a user is logged in, and have it not run with administrative privileges, that will force it to install to the currently logged in users' account.
Answered 02/23/2010 by: Jsaylor
Second Degree Blue Belt

Please log in to comment
0
Thanks Jsaylor. I checked the vendor msi and they don't have allusers explicitly set to 1 in properties, so that may be something.
Answered 02/24/2010 by: jdat747
Yellow Belt

Please log in to comment
0
I added the ALLUSERS property to the MSI and set it to 2 and was then able to deploy this from SCCM using the extracted contents and the following command line: setup.exe /S /v/qn
Answered 05/12/2010 by: ultie3131
Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity