In order to provide support for the widest range of Windows® versions the Export-It application keeps "INI" files and print spool files in a nominal “Windows” folder. Although this is a legacy of the time when each user had their own Windows® PC, it remains a Microsoft supported practice in the latest software versions. However, in today's environments when multiple users may be executing the application on the same platform [computer] it is best to think of a “Windows” folder as a repository for things that are at system level, but related to a specific user of the system (i.e. a hybrid in the hierarchy).
Every user should have a separate “Windows” directory for their settings and printing. It may be the actual “%systemroot%” folder when they are the only user of a PC, an arbitrary location defined by a user's “windir” environment variable (which can differ for each user), the “home” directory specified in a user “profile” or (for terminal service users) a private “Windows” directory defined in setting up the user. Note that, for security reasons, it is not necessary for the Export-It user to have access to the physical Windows directory—a user only needs access to a user Windows folder. In fact, for server-based installations it is recommended by Syscob that the user not be given access to the “real” Windows directory. And for centrally administered workstations in a domain the company policy may also deny access to a machine’s Windows folder (in such a case define a user “windir” environment variable to override the system environment variable and point it to a user “Windows” folder).
Each user must have "Full" file access permissions to their “Windows” directory. However, only the folder itself is used, not any subfolders which exist in the “real” Windows directory.
Should more than one user share the same “Windows” directory—whether the actual “%systemroot%” or not—then their printing may conflict. This is why separate user “Windows” folders are recommended by Syscob.