Software Deployment

Does this have anything to do with the AppDeploy Repackager or its recipe files or should this post be moved to Package Development?

May be i dont know exactly where it should be.

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.

Hi krishna,
has this file to go to each user on a machine or only to one particular profile?
Regards, Nick

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.

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.

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

Hi nheim,

All the users who logon to the machine.

Hi VBScab,

In my company only XP work stations.

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.

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.