I have a package with some HKCU-keys. The package is distributed with SMS.
When the pckage is started, the HKCU is repaired for the current user (sofar so good!)

However at the same time, the SAME repair is triggerd for the NT AUTHORITY\NETWORKSERVICE.
This happens every time, the package is started (probably because the NETWORKSERVICE doesn't have a user-profile).

Does anyone know how starting a package could trigger a repair from the NETWORKSERVICE-user or better how I can get rid of these repairs?
0 Comments   [ - ] Hide 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.
Answer this question or Comment on this question for clarity


Hmm, that's odd. When the repair is kicked off, what's listed in the application event viewer for that event? The problem component should be highlighted.
Does it do this when SMS is taken out of the picture?
Answered 04/16/2007 by: turbokitty
Sixth Degree Black Belt

Please log in to comment
You could run a repair with verbose logging to work out what is happening..
Answered 04/16/2007 by: Tone
Second Degree Blue Belt

Please log in to comment
check to see you haven't captured any registry such as

HKU\S-1-5-215-xxxx-xxxxx-xxxx these strings are SIDS and relate to specific users. When this happens its often due to capturing these reg entries for other users.

also the event log will give you the component guid for the offending component that will narrow it down to whatever is the keypath for that component
Answered 04/18/2007 by: jmcfadyen
Fifth Degree Black Belt

Please log in to comment