Unable to Merge registry files using script in Altiris
Hi,
I have a registry file which have a IE security settings for trusted sites (HKCU registry). I'm trying to merge the registry using the command
regedit /s trust.reg
but it is not working. the registry file is in C drive. I have tried another option to import registry
reg.exe import trust.reg - not working.
tried running the batch file placed in the c drive from altris
c:
cd\
trust.bat (batch file have regedit /s trust.reg command)
still not working.
I can run the same command and batch file on the local computer without any issues. I try to package and it doesn't seems to work, all the job are running fine but the changes are not happened.
My goal is to copy the reg files to user computer and run the batch file to merge the registry files.
Please help me!
I have a registry file which have a IE security settings for trusted sites (HKCU registry). I'm trying to merge the registry using the command
regedit /s trust.reg
but it is not working. the registry file is in C drive. I have tried another option to import registry
reg.exe import trust.reg - not working.
tried running the batch file placed in the c drive from altris
c:
cd\
trust.bat (batch file have regedit /s trust.reg command)
still not working.
I can run the same command and batch file on the local computer without any issues. I try to package and it doesn't seems to work, all the job are running fine but the changes are not happened.
My goal is to copy the reg files to user computer and run the batch file to merge the registry files.
Please help me!
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
anonymous_9363
16 years ago
You've built an MSI simply to run a batch file which runs RegEdit to merge in a .REG file?
There is a much simpler way to achieve what you want using native Windows Installer technology. Can I politely suggest that you do some reading about Windows Installer (see the post earlier this week - or last week? - in the 'Package Development' forum about packaging books) and/or use MSDN to read up about the Registry table?
BTW, I presume your .REG file has the correct header and is in the correct format? NT-compatible .REG files needs to be in ASCII and have the first line as 'REGEDIT4' with a carriage return/line-feed pair following that and for XP and above they are generally in Unicode with the first line as 'Windows Registry Editor Version 5.00'. XP will read and process NT-compatible .REG files (I normally use this format as a common denominator).
It's a common error to load XP .REG files into a text editor, make changes and save them. If the editor doesn't save in Unicode, the resulting file won't work. In these instances, I normally copy-and-paste the content of the file, i.e. everything except the header, into a new file, add the NT-style header and save this new file.
There is a much simpler way to achieve what you want using native Windows Installer technology. Can I politely suggest that you do some reading about Windows Installer (see the post earlier this week - or last week? - in the 'Package Development' forum about packaging books) and/or use MSDN to read up about the Registry table?
BTW, I presume your .REG file has the correct header and is in the correct format? NT-compatible .REG files needs to be in ASCII and have the first line as 'REGEDIT4' with a carriage return/line-feed pair following that and for XP and above they are generally in Unicode with the first line as 'Windows Registry Editor Version 5.00'. XP will read and process NT-compatible .REG files (I normally use this format as a common denominator).
It's a common error to load XP .REG files into a text editor, make changes and save them. If the editor doesn't save in Unicode, the resulting file won't work. In these instances, I normally copy-and-paste the content of the file, i.e. everything except the header, into a new file, add the NT-style header and save this new file.
Posted by:
snddoud
16 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.