Jump to content


OSD failing when "Start In" field is populated in program

Recommended Posts

My OSD fails on any program in the task sequence that has the "Start in" field populated. If i remove the network location from the start in field the program will install and the task sequence will continue.


The execmgr log seems to be telling me that it is getting an access denied error, so i gave everyone read/write to a specific folder for testing and the program still fails.


Any ideas?



Share this post

Link to post
Share on other sites

Why do you need the Start in at all, if the app installs correctly when you remove it?

We use "Start In" in the event the program needs to be repaired. If you leave it blank and then try to repair a program which needs it's source files the directory will be incorrect. I believe it points to _smstasksequence folder which gets deleted after the build.

Share this post

Link to post
Share on other sites

Sorry, I must've misunderstood completely.


Ok, what about importing the MSI product code instead of using Start in?



I currently do use that feature but not all of our software we install have MSI's. I just find it strange that the TS will execute just fine if the field is empty. It almost seems like SCCM has read rights but not read/execute?

Share this post

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Create New...