SCCM unable to do "required" remove of Project 2016
We're trying to reclaim licenses of Project 2016 from Windows 10 SCCM clients. We're running SCCM CB 2006. I've tried two different methods of using a SCCM application to run the removal command and create a log file that I can use to track progress.
This is more complicated than it should be because we have a standing "Available" deployment to all users to install Project. But this is a "Required Approval" deploy.
I can't use the same application to uninstall from targeted devices b/c SCCM recognizes the conflict.
We've tried separate applications with a .cmd file with the msiexec command and a self contained executable created with PsADT. Both work when you try them manually. Both work when tried in "Available" deployments. When I try a "Required" deployment, they fail with a "0x1 (1)" error code (Incorrect function).
We like having the "Available for all users (approval required)" in software center b/c it's convenient for users and the service desk. Is there a better way to solve this riddle?
Is there a log file that can give me a better idea of where the breakdown is really taking place?
This is more complicated than it should be because we have a standing "Available" deployment to all users to install Project. But this is a "Required Approval" deploy.
I can't use the same application to uninstall from targeted devices b/c SCCM recognizes the conflict.
We've tried separate applications with a .cmd file with the msiexec command and a self contained executable created with PsADT. Both work when you try them manually. Both work when tried in "Available" deployments. When I try a "Required" deployment, they fail with a "0x1 (1)" error code (Incorrect function).
We like having the "Available for all users (approval required)" in software center b/c it's convenient for users and the service desk. Is there a better way to solve this riddle?
Is there a log file that can give me a better idea of where the breakdown is really taking place?
Last Comment
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Hello,
Communication between the clients and the SCCM server is job based. You even can configure some of them in the SCCM GUI. That means, the SCCM database can only show you, what the client jobs pushed to the server.
As office programs are usually writing into the HKCU regitry hive, I can imagine that you need a logon (what may be the case for other applications as well).
I just would try to avoid creating overlapping deployments as this is a conflict as it.
So either you separate the by group memberships mapping to SCCM device or user groups, or you put the deployment into one package (removing / reinstalling).
According to your removal job. possibly the SCCM client first recognized the conflict and reported an error state, but this do not neccessary mean, that another deployment package is not deployed. But you see the result first after the client reported it.
Communication between the clients and the SCCM server is job based. You even can configure some of them in the SCCM GUI. That means, the SCCM database can only show you, what the client jobs pushed to the server.
As office programs are usually writing into the HKCU regitry hive, I can imagine that you need a logon (what may be the case for other applications as well).
I just would try to avoid creating overlapping deployments as this is a conflict as it.
So either you separate the by group memberships mapping to SCCM device or user groups, or you put the deployment into one package (removing / reinstalling).
According to your removal job. possibly the SCCM client first recognized the conflict and reported an error state, but this do not neccessary mean, that another deployment package is not deployed. But you see the result first after the client reported it.
ASKER
Bembi,
I think you're correct in that I need to have disparate groups of "licensed users" and "revoked licensed users". Even though the PsADT executable is working reliably (with the "user logged on" restriction), I agree it's best NOT to have overlapping deployments. We will find an alternate way for users to request software.
I think you're correct in that I need to have disparate groups of "licensed users" and "revoked licensed users". Even though the PsADT executable is working reliably (with the "user logged on" restriction), I agree it's best NOT to have overlapping deployments. We will find an alternate way for users to request software.
Microsoft Applications
Microsoft applications include a variety of software programs, including development and digital authoring programs (Expression and Media Center), educational programs, Internet software, including Essentials, Skype and the Live family, anti-virus, productivity applications and suites like Office, Excel, Word, Outlook, Access and PowerPoint, video games and server applications such as Exchange, SharePoint, IIS and Virtual Server.
45K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
ASKER
The self-contained PsADT executable appears to work if I restrict the deployed SCCM application to only run when a user is logged in. The funny thing is that it initially returns the "Error Code 0x1 (1) (Incorrect function)" error to the SCCM monitor initially. If you wait a 5-10 minutes and re-run the summarization, the status for the targeted computer will change from "Error" to "Success".
I've tested three different computers and seen the same result now. Is this just a feature that I shouldn't be concerned with, or should I investigate further?