# Scripted install with preconfigured configuration

**URL:** <https://techcommunity.softwareag.com/t/scripted-install-with-preconfigured-configuration/62255>\
**Category:** Forum\
**Tags:** Adabas-Natural, Natural, Natural-Single-Point-of-Development-SPoD\
**Created:** [May 30, 2007, 2:22pm UTC](https://techcommunity.softwareag.com/t/scripted-install-with-preconfigured-configuration/62255 "2007-05-30T14:22:42Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![jose\_de\_vogelaere](https://avatars.discourse-cdn.com/v4/letter/j/ac8455/32.png) [@jose\_de\_vogelaere](https://techcommunity.softwareag.com/u/jose_de_vogelaere)\
**Post date:** [May 30, 2007, 2:22pm UTC](https://techcommunity.softwareag.com/t/scripted-install-with-preconfigured-configuration/62255/1 "2007-05-30T14:22:42Z")

</div>

We want to install SPoD (natural workstation) automatically on developers pc via an automated script. So far no problem.  
However we would like that some customisations that are normally done by the developer himself once he logs on for the first time are part of the automated script as well.  
Example: the activation of NDV plugins, the definitions of the NDV server connections, some predefined user commands, etc.

Who has a good idea ?

---

<div class="post-metadata">

**Author:** ![Klaus\_Sponagel](https://avatars.discourse-cdn.com/v4/letter/k/3bc359/32.png) [@Klaus\_Sponagel](https://techcommunity.softwareag.com/u/Klaus_Sponagel)\
**Post date:** [May 31, 2007, 4:35pm UTC](https://techcommunity.softwareag.com/t/scripted-install-with-preconfigured-configuration/62255/2 "2007-05-31T16:35:18Z")

</div>

The mappings are in user dependent profile on Natural Prof directory. Maybe you can copy a standard .PRU file to the Prof directory during installation.  
I’m not sure if the Usercommands and Plugins are defined within the .PRU file as well.

---

<div class="post-metadata">

**Author:** ![Mark\_Barnard](https://avatars.discourse-cdn.com/v4/letter/m/bc8723/32.png) [@Mark\_Barnard](https://techcommunity.softwareag.com/u/Mark_Barnard)\
**Post date:** [May 31, 2007, 10:54pm UTC](https://techcommunity.softwareag.com/t/scripted-install-with-preconfigured-configuration/62255/3 "2007-05-31T22:54:47Z")

</div>

The user commands are actually stored in the registry. Look at this key (for example):  
HKEY\_CURRENT\_USER\Software\Software AG\Natural\6.2\Commands\User Commands

---

<div class="post-metadata">

**Author:** ![Mark\_Barnard](https://avatars.discourse-cdn.com/v4/letter/m/bc8723/32.png) [@Mark\_Barnard](https://techcommunity.softwareag.com/u/Mark_Barnard)\
**Post date:** [May 31, 2007, 11:05pm UTC](https://techcommunity.softwareag.com/t/scripted-install-with-preconfigured-configuration/62255/4 "2007-05-31T23:05:59Z")

</div>

And to indicate which plug-ins should be started automatically, you also need to add some data to the registry. Look at:

HKEY\_CURRENT\_USER\Software\Software AG\Natural\6.2\Plug-ins

Then add the Plug-in GUID as a child key to this node for each plug-in you want to start automatically. For example, here is a example registry file (.reg) contents to make sure the plug-in manager and object compare are started automatically:

```auto
Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Software AG\Natural\6.2\Plug-ins]

[HKEY_CURRENT_USER\Software\Software AG\Natural\6.2\Plug-ins\{9B22E72B-7913-493C-A4FB-6B00A007D5FD}]
@="Plug-in Manager"

[HKEY_CURRENT_USER\Software\Software AG\Natural\6.2\Plug-ins\{D3503545-4F8F-4F60-8166-4EDB5C2FEA96}]
@="Object Compare"

```

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/techcommunity/original/3X/c/d/cd19967bb605d28a72d77eb83a1cae22f3df2eb8.svg) [@system](https://techcommunity.softwareag.com/u/system)\
**Post date:** [April 2, 2021, 2:41pm UTC](https://techcommunity.softwareag.com/t/scripted-install-with-preconfigured-configuration/62255/5 "2021-04-02T14:41:13Z")

</div>