Copy to system32 for restricted user with loginscript.

[PC_LOAD_LETTER]

yeah but (sorry to oppose you here GSM ) using the runas command means the password is in plain text.

what i think he really needs is a vb script that scans the network for hosts and if they exist copy the files to \\hostname\c$\windows\system32

that way he can just run it from a server with admin rights

http://robotronic.de/runasspc/

creates a cryptfile that store your password for the included runas utility (cryptfile is only good for the running the exe it was created for)

[Bly]

This was an interesting thread, but I have come up with a better/different solution for oeminfo.ini.

Machine startup script in the GPO:

@echo off

if '%COMPUTERNAME%' == 'SERVER_1' goto SkipUpdate

if '%COMPUTERNAME%' == 'SERVER_2' goto SkipUpdate

attrib -r -h -s %SystemRoot%\system32\oeminfo.ini

del /q %SystemRoot%\system32\oeminfo.ini

@echo [General] > %SystemRoot%\system32\oeminfo.ini

@echo Manufacturer=Tech Support >> %SystemRoot%\system32\oeminfo.ini

@echo Model=PC >> %SystemRoot%\system32\oeminfo.ini

@echo [support Information] >> %SystemRoot%\system32\oeminfo.ini

@echo line1=***** Tech Support Contact Information *****>> %SystemRoot%\system32\oeminfo.ini

@echo line2=Etc etc etc..>> %SystemRoot%\system32\oeminfo.ini

:SkipUpdate

/script

I'm making sure the oeminfo.ini isn't marked as read only or a system file etc

Delete the oeminfo.ini

Then echo in all the information I need right from the machine startup batch....

The BMP isn't copied but it isn't required, on our domain the above script works perfectly... I don't have to copy the OEMINFO.ini from anywhere, no network login issues, and by running it in the machine startup it's the local admin which always has rights to the system32 directory...

Edited December 14, 2007 by Bly