This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Sysnative
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
May 16, 2016
11:27 AM
Editing XML \ Config Files in C:\Windows\System32
I've been trying to edit a config file – applicationhost.config in C:\Windows\System32\inetsrv\config folder. I’m using the inherent InstallShield functionality of 'XML File Changes' for this. Whenever I try to make this change the system redirects the change to C:\Windows\Syswow64\inetsrv\config.
Now, I’ve ensured that the template I’m working on is 64 bit and all components in there are 64 bit as well. But there seems to be no way to make the change happen in the right folder.
The strange part is a change to the same file when placed in C:\Program Files folder – a 64 bit folder works! It is only in C:\Windows\System32 folder that I’m unable to make changes in.
Any help would be much appreciated. Thanks in advance.
Now, I’ve ensured that the template I’m working on is 64 bit and all components in there are 64 bit as well. But there seems to be no way to make the change happen in the right folder.
The strange part is a change to the same file when placed in C:\Program Files folder – a 64 bit folder works! It is only in C:\Windows\System32 folder that I’m unable to make changes in.
Any help would be much appreciated. Thanks in advance.
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
May 17, 2016
05:54 AM
Using Sysnative in ism template i.e. [WindowsFolder]\Sysnative\inetsrv\config instead of [System64folder]\inetsrv\config seems to be working. I'm trying to ascertain the implications of using Sysnative in the template. Using Sysnative seems to create a C:\windows\Sysnative folder when it is actually supposed to be a virtual folder.