Following symlinks?

[splinterededge]

I use symlinks to bridge together the resources for the system images that I make with NTLite and Powershell. This saves me the trouble from making multiple copies, having out-of-date items or breaking a configuration or scripts because the filenames may have changed. Sometimes I symlink apps, drivers and registry files depending on how I am scripting that particular image to be built.

I rely on NTlite for most of it customization features which has been a breeze with the exception of one little quirk. Following symlinks, in this case I am attempting to use symlinks to refer to my repository of drivers. By having unchanging names for the symlinks I can update the drivers in my repo without breaking my ntlite configs, or so I thought.

TLDR: I noticed that ntlite will not follow the symlinks when I select a parent folder of 'drivers' containing symlinks to subfolders containing infs.

I would like to humbly request that ntlite follow symlinks when adding a folder of drivers, or registry items.

Thanks Nuhi, stay gold.

 

[splinterededge]

Bump.

It would be a nice improvement if I could subscribe the parent directory containing these symlinks to my repository of drivers.

 

[splinterededge]

Notably, the I do get the desired behavior with registry files, but these symlinks point to a file and instead of a folder.

 

[splinterededge]

Any thoughts?

 

[splinterededge]

Bump.