Solaris

Hi There

I am having trouble in solving a scenario. We have some test systems on the network where users can login as themselves. These systems are connected to the LDAP server and authentication happens without any issues. These systems are used to create flars which are used to jumpstart other systems which are standalone. When users login to the test systems and create the flars, the files under the flars are created so that the owner of the files are the individual users who create the flars. When this is used to jumpstart the standalone systems, the files are copied likewise. However, since the standalone machines are not connected to LDAP and have not remnants of the users in the /etc/shadow and /etc/passwd file, the ownership of the files are screwed.
Is there a way in which this can be avoided? I want the files in the standalone machines, when installed, to be owned by root as it would be for an installation from a CD/DVD. I can't give root access to the test machines to the users, as this is a network wide root account. I can alter the /etc/shadow and /etc/passwd files but this will be a long process as there are a large number of users and a large number of systems. The standalone systems are supposed to replicate customer environment and thus any change to that will not be feasible either. In the flarcreation process, which is managed by another team, I would have thought that there would be a tar and/or a cpio command which can be modified so that the files created have a pre specified ownership. But I am told that is not the case. One of the files where the problem is pronounced is the /etc/profile and apparently it is not created during the flarcreation.Btw, the flarcreation process happens through a shell script.I can create a user which all the users login as and then perform the flarcreate process and I can create the account also on the standalone machines. However, this will not solve the problem as the production customer sites will not have the new account. Is there a way to give users, belonging to a particular group, the same ownership privileges as root, for files, so that when they are transferred to the standalone systems, they have the ownership of root user and not that of the user who created those files.
I am a bit confused by this. Any help will be greatly appreciated.