Automating COM and DCOM setting adjustments
Currently using an AutoIT script to change some default COM and DCOM object permission settings for XP SP2 machines. Unfortunately, this script is hanging during the machine build process due to timing and hardware differences.
I'm looking for a better way to handle this so we're not so dependant on hardware speed and timing.
Is it possible to script in setting changes with a repackager (Wise, Admin Studio, etc.) or by registry merge file?
Specifically I'm trying to configure the default COM Security access permissions limits to allow Remote Access for Anonymous login. Additionally I'm also trying to grant the local USERS group Local and Remote Launch abilities for Launch and Activation Permissions on the Machine Debug Manager DCOM object.
Any thoughts or help is much appreciated.
I'm looking for a better way to handle this so we're not so dependant on hardware speed and timing.
Is it possible to script in setting changes with a repackager (Wise, Admin Studio, etc.) or by registry merge file?
Specifically I'm trying to configure the default COM Security access permissions limits to allow Remote Access for Anonymous login. Additionally I'm also trying to grant the local USERS group Local and Remote Launch abilities for Launch and Activation Permissions on the Machine Debug Manager DCOM object.
Any thoughts or help is much appreciated.
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
aogilmor
20 years ago
I definitely wouldn't use AutoIT to do that.
Look at Secedit. Isn't that MSFT's command line tool for editing security settings?
It would probably be possible to do this using Wise, or Installshield but not the best way.
If it's just a reg entry you could do it by merging a .REG file but you'd need to know exactly which entries to place in the file.
Look at Secedit. Isn't that MSFT's command line tool for editing security settings?
It would probably be possible to do this using Wise, or Installshield but not the best way.
If it's just a reg entry you could do it by merging a .REG file but you'd need to know exactly which entries to place in the file.
ORIGINAL: nbozovich
Currently using an AutoIT script to change some default COM and DCOM object permission settings for XP SP2 machines. Unfortunately, this script is hanging during the machine build process due to timing and hardware differences.
I'm looking for a better way to handle this so we're not so dependant on hardware speed and timing.
Is it possible to script in setting changes with a repackager (Wise, Admin Studio, etc.) or by registry merge file?
Specifically I'm trying to configure the default COM Security access permissions limits to allow Remote Access for Anonymous login. Additionally I'm also trying to grant the local USERS group Local and Remote Launch abilities for Launch and Activation Permissions on the Machine Debug Manager DCOM object.
Any thoughts or help is much appreciated.
Posted by:
kkaminsk
19 years ago
I used DCOMPERM.exe to do some settings changes. Seems like vendors are using that for their products that have SP2 issues. It might be worth checking out.
Posted by:
brenthunter2005
19 years ago
This can be done using VBScripting and WMI.
Google for: wmi Win32_DCOMApplicationSetting
Google for: wmi Win32_DCOMApplicationSetting
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
