Reputation
700
Top tag
Next privilege 1,000 Rep.
See votes, expandable usercard
Badges
4 22
Newest
 Caucus
Impact
~14k people reached

Aug
28
comment SCCM application deployment shows as fail
What do AppDiscovery, AppEnforce, and AppIntentEval logs say about your application? Have you confirmed that the SCCM client sees a successful exit code when it runs the installer?
Aug
26
comment How to lock out normal (non-admin) users during software installs?
+1 I always wondered whether there were real-world uses for non-OSD task sequences.
Aug
21
comment SCCM App Catalog won't install applications if started as user other than the one logged in
You'd be relying on the application catalog automation to take care of that. I haven't confirmed it, but IIRC when a user selects install of a brand new app from the app catalog it kicks off the appropriate user and/or machine policy updates. Basically, if its installation is initiated from the app catalog I'm pretty sure it'll install without delay.
Aug
19
comment Configuration Manager (SCCM) Clients not updating their status
@BigHomie Have you resolved this before? I'm seeing basically the same thing occur here.
Aug
12
comment SCCM Collection Query- FullName
Yep. You have to curate that list of names somewhere. An AD security group is the natural place to do that and has the benefit that other applications can use that same curated list.
Aug
7
comment What, exactly, is the SCCM client doing when it installs an .msi for a system?
@Bin Duly noted.
Jul
28
comment What, exactly, is the SCCM client doing when it installs an .msi for a system?
@BigHomie I'm fairly sure the msiexec error code was 0. I wouldn't call it "successful". I do know for certain the SCCM install did something permanent because (1) it shows up in the results of gwmi -Class Win32_Product and (2) subsequent attempts to (un)install the same msi result in some flavor of "already installed" errors.
Jul
28
comment What, exactly, is the SCCM client doing when it installs an .msi for a system?
No apology necessary. I suppose you're chatting elsewhere...I can't seem to find you or @kce on chat.se.
Jul
28
comment What, exactly, is the SCCM client doing when it installs an .msi for a system?
@kce That idea makes me sad.
Jul
28
comment What, exactly, is the SCCM client doing when it installs an .msi for a system?
@kce I only use psexec for testing package installs to system. This is so that package installation can be validated separately from SCCM.
Jul
28
comment SCCM - not a valid .wim file?
Both your admin workstation and the SCCM server need permission to access the path of your .wim. That means that unless you're deliberate about it, you can easily end up with your workstation having permission to access the file but the SCCM does not.
Jul
28
comment What, exactly, is the SCCM client doing when it installs an .msi for a system?
I agree with treating all packages equally. I am also skeptical of the MSI Deployment type. I don't follow your preference for Applications over Packages though. I have yet to encounter an issue whose root cause is a fundamental problem with the Application model. The script installer deployment type seems to work as I expect. Do you have some specific problems with Applications in mind that I should know about?
Jul
28
comment What, exactly, is the SCCM client doing when it installs an .msi for a system?
I suspect this has something to do with msiexec installing for a single user instead of all users. That decision depends on "access privileges of the user, whether elevated privileges are required to install the application, the value of the ALLUSERS property, the value of the MSIINSTALLPERUSER property and the version of the operating system." (ref). That list of variables combined with the inability to test separately from SCCM is reason enough for me to avoid the MSI Deployment Type altogether.
Jul
27
comment What, exactly, is the SCCM client doing when it installs an .msi for a system?
This confirms a lot of what I already understood, but it doesn't explain how SCCM manages to install the .msi without it showing up in Add or Remove Programs.
Jul
27
comment Does AppEnforce.log really log the context used for installation incorrectly?
@Colyn1337 I suppose it is for that particular circumstance. The nomenclature used in SCCM is that "system context" refers to execution by the computer's account, while "user context" refers to execution by some other user (i.e. non-computer) account in AD.
Jul
23
comment Use System Center Configuration Manager 2012 to remove existing InstallShield App
The only cleanup would be the SCCM client removing the content from its cache. That happens transparently and automatically by SCCM's algorithms in a reasonable way whether or not the deployment is removed. You might consider leaving it deployed so that uninstallation is enforced even if someone manually installs the wrong version or rolls back a VM or boots up an old computer. SCCM application (un)installs are meant to be idempotent so you shouldn't have to be concerned with timing the removal of deployments.
Jul
23
comment Use System Center Configuration Manager 2012 to remove existing InstallShield App
Yes. That application deployments predate SCCM deployment is normal and shouldn't in itself cause a problem. When the SCCM client uninstalls an application it first ensures the content is in its cache then runs the uninstall command you specified. There is only one content folder per application, so it just downloads the whole folder whether it's installing or uninstalling.
Jul
8
comment How to securely install Windows executables across the network using SCCM?
I just checked my own notes and can confirm that I did use a high-permission account for a few things during server setup (schema extension, PKI template creation, service account and group creation). I certainly haven't needed a high-permission account for software deployment.
Jul
2
comment Create SCCM device collection based on last logged on users who are members of an AD security group
What is you end goal? This seems rather close to what SCCM's User Device Affinity already implements. Is there a reason you can't use UDA to achieve your goal?
Jun
22
comment During times when a maintenance window overlaps with business hours does SCCM perform operations?
What are the "special conditions"?