Jump to content


JerichoJones

Established Members
  • Posts

    6
  • Joined

  • Last visited

Profile Information

  • Gender
    Male

JerichoJones's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Technically correct however from a user perspective it is one place. They go to one place to get the software. I go to one place to update it. Simple. Unix & Mac? Really? I can deploy software to those? Is that new? Last I heard it could only do inventory. As for mobile we have something designed specifically for that. CM12 is not even close to being a robust solution yet. In any event I can get around the issue for now by using Packages which do use the domain account (Thanks go to REDDIT for that tidbit). Strangely MS does not view that as a security concern.
  2. #1, It would seem then that I have to have the same software in multiple places due to what appears to be a restrictive design choice by MS. Is there a sensible reason why SCCM does not use a domain account to do the installation? I don't get it. #2, Agreed. We cannot give Everyone access.
  3. OK. Why does does deploying an EXE work but not an MSI? This really confuses me.
  4. Answer to #1 - So I do not have to redo how we install software or maintain multiple repositories. Maybe I'm missing something though. Oddly I have a friend at another institution that uses DFS successfully (or so he claims). Others on the Interwebs indicate that they are using it as well. Unfortunately I have had no success in finding a document that covers how to set this up.
  5. Well pointing at the server directly fails as well. It does work if I give "Everyone" access. So something strange is going on with how the permissions are parsed (I guess). Does anyone have ideas or links on troubleshooting permissions parsing? I've never had to get that deep into it.
  6. Hello All, I have been struggling with this for the last few days. I have been trying to deploy Applications from a DFS share but cannot get it to work. It appears that the MSI cannot be found when MSIEXEC is invoked (error 1619). I have checked the paths and permissions and there does not appear to be an issue there (both the Site Server and installation user account have permissions). Under the Deployment Type I have the following: Content Tab - Empty Programs Tab Installation Program: msiexec /i "\\dfsroot\Software\Install\7zip\7z920x64.msi" Installation start in: \\dfsroot\Software\Install\7zip User Experience Tab Installation behavior: Install for system Logon requirement: Whether or not a user is logged on Installation program visibility: Hidden I checked the event log on the client and MSIEXEC is getting invoked under the SYSTEM account. That obviously won't work. What am I missing?
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.