/build/static/layout/Breadcrumb_cap_w.png

Not able to deploy

Hi guys,

I have a word document which should be deployed on this path C:\Documents and Settings\<username>\Application Data\Microsoft\Templates.

I have created a msi which has word document on the specified path. when i install manually it is working good. But when i deploy through SCCM i can see the msi file in add remove programs not the word document file in the specified path.

Can any one provide me a solution.

0 Comments   [ + ] Show comments

Answers (11)

Posted by: bkelly 15 years ago
Red Belt
0
Does this have anything to do with the AppDeploy Repackager or its recipe files or should this post be moved to Package Development?
Posted by: rvkc831 15 years ago
Senior Yellow Belt
0
May be i dont know exactly where it should be.
Posted by: michaelnowell 15 years ago
Second Degree Blue Belt
0
I suspect that when you're deploying it via SCCM it is installing under the local system account and not the user account. This would result in the document being installed under a different location.

To check to see how your application is installing. Expand you application in SCCM, select Programs, right click the Program that you are installing (e.g. Per-user attended) and select properties. Look on the Environment tab and I suspect that it's set to run as 'Run with administrative rights'.

If you change this to 'Run with user's rights' then your document should install to the desired path.
Posted by: nheim 15 years ago
10th Degree Black Belt
0
Hi krishna,
has this file to go to each user on a machine or only to one particular profile?
Regards, Nick
Posted by: djain3 15 years ago
Second Degree Blue Belt
0
ORIGINAL: rvkc831

Hi guys,

I have a word document which should be deployed on this path C:\Documents and Settings\<username>\Application Data\Microsoft\Templates.

I have created a msi which has word document on the specified path. when i install manually it is working good. But when i deploy through SCCM i can see the msi file in add remove programs not the word document file in the specified path.

Can any one provide me a solution.



Probably you may try to put this in your msi:

C:\Documents and Settings\[LogonUser]\Application Data\Microsoft\Templates.
Posted by: anonymous_9363 15 years ago
Red Belt
0
Probably you may try to put this in your msi:

C:\Documents and Settings\[LogonUser]\Application Data\Microsoft\Templates.
...which will mean your package will only install on XP. NT uses a different profile path as do Vista and Windows v7. I would regard that as sub-optimal, wouldn't you? :)

Far and away the easiest route is to do as Michael says.
Posted by: jmcfadyen 15 years ago
5th Degree Black Belt
0
put an HKCU entry in the component that houses the word template file.

mark the HKCU key as the keypath.

I would suggest something along the lines of

HKCU\Software\[CompanyName]\Packages\[ProductName]\ValidationFix_ComponentName = true
Posted by: rvkc831 15 years ago
Senior Yellow Belt
0
Hi nheim,

All the users who logon to the machine.
Posted by: rvkc831 15 years ago
Senior Yellow Belt
0
Hi VBScab,

In my company only XP work stations.
Posted by: anonymous_9363 15 years ago
Red Belt
0
Oh, I see. You work at a company which never upgrades. Cool. It probably never UATs new OS releases, either, eh?

Make your packages future-proof, as far as you can. It's a pain to re-visit them.
Posted by: rvkc831 15 years ago
Senior Yellow Belt
0
When i changed the Administrative Rights to User Rights in the SCCM Program properties it is working.
Thanks to all of you guys and michaelnowell too.
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