4/8/2023 0 Comments Remove a default list in anydoI'm somewhat new at this, but my understanding of what makes an App "Provisioned" is that it's installed per user profile- which is exactly how the Apps I've been trying to excise behave. The only real difference I see is that his Get and Remove commands (at least in the first two, working commands) make no mention of Provisioned Apps. It's throwing an -allusers switch (as I'd expected one would have to to accomplish this). I can't say what is qualitatively different about this approach here, though. Now- just like the user who responds to him in that thread, the third command goes borky- errors/doesn't work.īUT! Upon Logging in a new user, the apps are in fact missing after running at least the two first commands- which is the result I was looking for. Remove-AppXProvisionedPackage -online -PackageName %s -allUsers Get-AppXPackage %s -PackageTypeFilter bundle -allUsers | Remove-AppXPackage -allUsersģ. Get-AppXPackage %s -allUsers | Remove-AppXPackage -allUsersĢ. Anyone have a working method for finally expunging these things?ġ. each time I sign in a "new" user, up pop the shovelware office apps again, no matter what I've done.Ĭredits to Microsoft here for finally taking pre-installed software from just "mildly annoying" to "bedbug infestation"-levels of infuriating.īut I'd like to get off the merry-go round please. Powershell scripts, deprovision regedits, domain GPOs. Most my reading suggests there is a way to do this, but none I've come across so far have actually worked. I have scores of users I am setting up at present, and my memory isn't great.Ĭlearly I can't reverse the current nonsense trend of "lets foist crap people never asked for with every operating system/device", so I am looking for a way to remove these so they don't keep cropping up in new user profiles and tripping me up as I try to proceed through new systems deployment. This means I have to remember to manually remove them from each and every user profile I create. And that's where we come back to "they're provisioned". Indeed I can verify if they're not present when setting up a user, you have no issues. So the only ideal solution seems to be to not have those installs present when setting up a user in the first place. You basically have to recreate the user's profile from scratch. You can't set a signature- and no targeted solution I've tried will work. In two separate cases I've had users lose the ability to do specific things in Outlook- most notably, calling the signatures pane to define a signature for email. The real problem for me is that these shovelware installs are like a damn landmine, waiting to be stepped on. Installing my company's sanctioned version of Office 365 adds yet a third office "app", and if you're a perfectionist that would be enough to drive one batty all on its own. These seem to re-insert themselves for every new user account- which my reading tells me that makes them "provisioned". The problem I am trying to actually address here is that Microsoft has decided to insert a "default" install of Office in new installations of Windows- two, actually. Or they've proposed a solution that does not work. So, sorry if this is a duplicate topic, but quite frankly I've been crawling over numerous posts in this and other technical forums that take a stab at answering this question, but none of them actually have.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |