We deploy office 2000 via metaframe. All documents (e.g. word documents) seem to take 'administrator' as the creator/owner, and not the domain user who creates/modifies them. This is obviously no good from an auditing point of view. Does anyone know a fix? Turning W2K auditing on for all documents is not an option, due to overheads.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations biv343 on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Office files always owned by administrator
- Thread starter wilsona
- Start date
When you install Office initially on the Citrix server, when it prompts you for the user name - just leave the field blank. Then when each user first starts Office it will prompt for their name.
There's probably a setting somewhere to change this at a later date other than by asking the user to change it via tools/options (perhaps you could use kix to do this), but frankly when I've come upon this I've simply uninstalled office & then installed it again and usually it fixes it....
Cheers
There's probably a setting somewhere to change this at a later date other than by asking the user to change it via tools/options (perhaps you could use kix to do this), but frankly when I've come upon this I've simply uninstalled office & then installed it again and usually it fixes it....
Cheers
- Thread starter
- #3
Thanks for your reply, but your solution only addresses the user details within the document, not its operating system attributes. i.e. file creator/owner. We use manadatory profiles where the user particulars are hardwired anyway. We want any *.doc files created or modified to be stamped with the domain user acount name of the person who created/modified them (not administrator), so that we have some form of audit info.
ok - the actual operating system attributes should be set by the current user, hence my assumption that you meant the User Info/Author in the application itself. You aren't by any chance using anonymous accounts to publish Office2k? Perhaps run tsadmin.exe and see exactly what account(s) are being used on the server..... otherwise perhaps there's an issue with the mandatory profile.....
Cheers
Cheers
- Thread starter
- #5
Users are logged in with their normal W2K domain user acounts, and the application is a published desktop, which includes office, etc. Metaframe XPa and WIndows 2000 SP3. I'll have a look at the profile - maybe this has indeed got soemthing to do with it. Thanks.
- Thread starter
- #7
ah well.... if I think of anything else..... otherwise maybe it's the profile.... good luck!
Cheers
P.S. As always, if something weird appears to be happening, I strongly recommend physically logging onto the terminal server with a normal user account and seeing what happens. For example, with your problem, I'd log on and create a text file (eg "echo hi > c:\temp\test.txt"
and then view the file properties. If it's owned by the user, then try creating an office file and see if that's also owned by the user. I'd then publish a full desktop and do the same thing again. This way you can potentially rule in/out whether Citrix is an issue or if it's something else.
Cheers
P.S. As always, if something weird appears to be happening, I strongly recommend physically logging onto the terminal server with a normal user account and seeing what happens. For example, with your problem, I'd log on and create a text file (eg "echo hi > c:\temp\test.txt"
and then view the file properties. If it's owned by the user, then try creating an office file and see if that's also owned by the user. I'd then publish a full desktop and do the same thing again. This way you can potentially rule in/out whether Citrix is an issue or if it's something else.- Status
Similar threads
- Locked
- Question