Alan's Blog

"Yeah. I wrote a script that will do that."

Fixing SCCM 1603 Errors

Posted on September 3rd, 2010

I was recently forwarded a link from Richard Balsley’s blog about 1603 Errors in SCCM, see  He characterizes the problem like this: “When a local administrator was logged on during runtime, the application would install fine. It would also install fine if no one was logged on. However if a user was logged on without admin rights, we’d get the 1603 error.”

Richard shows how to look up the AppID in DCOM and provides a script to delete the RunAs key, which resets launch permissions to The Launching User.

I decided to further automate this process.  InstallShieldDCOMFix.vbs uses WMI to enumerate the AppID, and then delete the associated RunAs key.

If you run this with no arguments the local machine will be fixed.  Use cscript.exe //b InstallShieldDcomFix.vbs or comment out Wscript.Echo to avoid popups from messages.  You can also run this against remote computers using the computername as an argument, such as cscript.exe //b //nologo  InstallShieldDcomFix.vbs computername

Rename file from _vbs.txt to .vbs.



Filed under VbScript, Windows Administration |

Leave a Reply

You must be logged in to post a comment.

Please Note

All the scripts are saved as .txt files. Newer files have a "View Script" button which will let you save or open a script in notepad. For earlier posts, the easiest way to download with IE is to right click on the link and use "Save Target As". Rename file from Name_ext.txt to Name.ext.

To see a full post after searching, please click on the title.

PowerShell Scripts were written with Version 3 or 4.

https connections are supported.

All new users accounts must be approved, as are comments. Please be patient. It is pretty easy to figure out my email address from the scripts, and you are welcome to contact me that way.

Site Search



SQL Site

Bad Behavior has blocked 262 access attempts in the last 7 days.