Page 1 of 1

Protecting Configuration files in V6

Posted: Fri Dec 21, 2012 5:15 pm
by DSantos

We have TS 2012 deployed in several PCs in our network (Local install) but both the folders Group and Config are stored in a network path (A UNC path).

I want to make sure that TS core configuration files can't be changed. I mean, TopProcess forms, UI settings, parameter files, and everything that could change the UI or the behavior of the software in the workstations running it. The system variables TOPCONFIG and TOPGROUP are configured in each of these PCs to point these UNC paths, however if I set any of these folders as read-only, TS fails to launch.

What's the best practice to protect configuration files against changes made by curious users, changes that could be spread inadvertently to other users, or in the worst cases, files being deleted accidentally.

How can I protect the configuration files stored in Group / Config when these folders are stored in a network drive? :?:

Posted: Fri Dec 21, 2012 7:12 pm
by Bill
I am checking into this with Missler. I will let you know what I find.