• Content Count

  • Joined

  • Last visited

Community Reputation

  1. I've deployed 4.6.1 to our enterprise via ConfigMgr. Here is a HOW TO, just change the 4.5.2 to 4.6.1. However using ConfigMgr 2012 R2 Application Model, have run into an issue deploying the software. The command works fine when using elevated command prompt, and even when installed via the Catalog (user context), but when trying to install via System Context, it fails. Same results using psexec.exe (Installing as System). Command Line: /auto CHECKFORBETAS=0 DESKTOPSHORTCUT=0 CHECKFORUPDATES=0 Thoughts as to why Paint.Net does not install when using the SYSTEM account? Update.... Using the CreateMsi Command ( /CreateMsi CHECKFORBETAS=0 DESKTOPSHORTCUT=0 CHECKFORUPDATES=0) I've been able to to create the MSI files that do install as system. This just means extra steps each time Paint.Net is released. It was nice just downloading the .exe file and deploying that, which worked on either x86 or x64 machines, now I have to extract the MSI, create different deployments for x86 or x64. But at least it works, and I can deploy with ConfigMgr.