/build/static/layout/Breadcrumb_cap_w.png

Exceed 2008 - SMS Deployment

Hello all,

I'm currently working on upgrading a large number of Exceed v9 installations to Exceed 2008 (v13).

All working fine, except when the package deploys via SMS - existing user connection settings aren't migrating.

If I install the same package from the SMS distribution point, with the same SMS command line but with my admin account, then logon as an end user, the settings migrate perfectly.

Anyone come acrross this ever? I'm scratching my head with what to try next - I guess comparing verbose windows installer logs from the 2 installations but that is not going to be fun so I though I'd post this in the meantime [;)]

Cheers,
Rob.

0 Comments   [ + ] Show comments

Answers (3)

Posted by: pjgeutjens 14 years ago
Red Belt
0
My first instinct would be to check any properties / paths being set in custom actions based on the executing user's environment. The package being pushed with LocalSystem, maybe this is causing some strange effects...

Good luck with it in any case [;)]

PJ
Posted by: anonymous_9363 14 years ago
Red Belt
0
Comparing WI logs not fun? Are you MAD?
Posted by: MSIPackager 14 years ago
3rd Degree Black Belt
0
Yes there are differences in the paths resolved in the WI logs - my first (and obvious solution) was to use the SMS software installation account (this is a domain service account) to install the package rather than the local sysem account.. however in the SMS execmgr.log it still says; UserContext = "NT AUTHORITY\\SYSTEM" (I'd expect to see domain\serviceaccount) so maybe there's an issue with the SMS config...?

If I install the package with the local PC administrator account I get the same result as the SMS distribution suggesting it does need domain access in some way. However there is a section on SMS deployment in the Exceed documentation - and nothing is suggested along these lines.

And Ian, yes trawling the logs is tremendous fun.. thank that lord for Excel and Beyond Compare [:)]
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ