Hi,

I'm trying to use a computer startup script to replace the windows
vista logon screen across an entire domain, in a fashion similar to
the manual process documented here:
http://spikex.net/blog/2007/07/18/ch...windows-vista/

I have my basic script below that works through several steps to
replace a key dll, changing the owner of the file to SYSTEM, renaming
it and copying in a replacement file, which all looks sound and has
worked in a roundabout way for me manually.

This script runs via group policy through the computer configuration
startup script section. I understand from a little searching that
these scripts run under the context of the SYSTEM account which should
be privileged enough to perform the commands I call.

I was hoping someone might be able to help me debug and tune this code
as I'm at a loss as to what to try with it.

Many thanks in advance!!

---------------------
Option Explicit
On Error Resume Next

Dim strCommandLine
Dim objFSO

strCommandLine = "\\server\logonreplace\XCACLS.vbs C:\Windows
\System32\imageres.dll /G SID#S-1-5-18:f /E"
ExecuteThis(strCommandLine)



objFSO = CreateObject("Scripting.FileSystemObject")
objFSO.MoveFile "C:\Windows\System32\imageres.dll" , " C:\Windows
\System32\imageres.dll~"
objFSO.CopyFile "\\server\logonreplace\imageres.new.dll", "C:\Windows
\System32\imageres.dll"
Set objFSO = Nothing

Function ExecuteThis(FULLSTRING)
Dim objShell : Set objShell = CreateObject("Wscript.Shell")
ExecuteThis = objShell.Run(FULLSTRING,,1)
Set objShell = Nothing
End Function

You should not have bought into Vista in the first place.



<cerebral.hunger@xxxxxx> wrote in message
news:90649dd3-ed31-4cfe-825e-0cde69816aec@xxxxxx

> Hi,
>
> I'm trying to use a computer startup script to replace the windows
> vista logon screen across an entire domain, in a fashion similar to
> the manual process documented here:
> http://spikex.net/blog/2007/07/18/ch...windows-vista/
>
> I have my basic script below that works through several steps to
> replace a key dll, changing the owner of the file to SYSTEM, renaming
> it and copying in a replacement file, which all looks sound and has
> worked in a roundabout way for me manually.
>
> This script runs via group policy through the computer configuration
> startup script section. I understand from a little searching that
> these scripts run under the context of the SYSTEM account which should
> be privileged enough to perform the commands I call.
>
> I was hoping someone might be able to help me debug and tune this code
> as I'm at a loss as to what to try with it.
>
> Many thanks in advance!!
>
> ---------------------
> Option Explicit
> On Error Resume Next
>
> Dim strCommandLine
> Dim objFSO
>
> strCommandLine = "\\server\logonreplace\XCACLS.vbs C:\Windows
> \System32\imageres.dll /G SID#S-1-5-18:f /E"
> ExecuteThis(strCommandLine)
>
> objFSO = CreateObject("Scripting.FileSystemObject")
> objFSO.MoveFile "C:\Windows\System32\imageres.dll" , " C:\Windows
> \System32\imageres.dll~"
> objFSO.CopyFile "\\server\logonreplace\imageres.new.dll", "C:\Windows
> \System32\imageres.dll"
> Set objFSO = Nothing
>
> Function ExecuteThis(FULLSTRING)
> Dim objShell : Set objShell = CreateObject("Wscript.Shell")
> ExecuteThis = objShell.Run(FULLSTRING,,1)
> Set objShell = Nothing
> End Function