Installing a New Font Using A Startup Script
- From: "Bryan" <Bryan@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 28 Jul 2005 11:55:02 -0700
I've written a VBS script to copy a TTF font file to a client PC's Fonts
folder. The client PC is running either Win2k Pro or WinXP. The script is
set up to run as a startup script defined in a Windows Server 2003 Group
Policy Object.
When the client's PC starts up, the script successfully copies the font file
to the C:\WinNT\Fonts (or C:\Windows \Fonts) folder on the client PC.
If the first user to login to the client PC after the script runs has local
administrative rights, the font is successfully installed and both visible as
a file in the Fonts folder in Windows Explorer and accessible as a font in
applications like Wordpad, Word, etc.
However, if the first user to login to the client does not have local
administrative rights, the font is neither visible in the client's Fonts
folder using Windows Explorer nor accessible within any application capable
of utilizing the font (Word, Wordpad, etc.).
It's my understanding that a startup script runs under the credentials of
the local System account on the client PC. If this is the case, then why is
the font not fully installed and accessible right after the script has
finished running regardless of the rights of the user logging into the client
afterwards?
Also, is there anything that I can do within my script to complete the font
installation even before the first user logs into the client after the script
runs?
Thanks,
Bryan
.
- Follow-Ups:
- Re: Installing a New Font Using A Startup Script
- From: Torgeir Bakken \(MVP\)
- Re: Installing a New Font Using A Startup Script
- Prev by Date: Re: Error: Expected statement?
- Next by Date: Deleting User and Mailbox in AD
- Previous by thread: objFile.Copy making folder read only?
- Next by thread: Re: Installing a New Font Using A Startup Script
- Index(es):
Relevant Pages
|