Prev: VBS 5.8 reference
Next: Runtime error 6068
From: Ratboy on 23 Feb 2010 15:02
I have several maintenance automation scripts in place for servers in our
domain. We have noticed that several of the scripts are incapable of reading
or writing to the Windows 2008 Server registry. Does anyone know of an easy
workaround or a solution to this issue?

From: mayayana on 23 Feb 2010 18:19
In addition to permissions issues and
32 vs 64 bit issues. I've had trouble with
WScrip.Shell on Win7. I don't know if that's
a known problem, but I found with one script
that WScript.shell simply didn't work, while the
same operation using WMI StdRegProv did work.
I can't explain it. I just switched to WMI for
Win7.


> I have several maintenance automation scripts in place for servers in our
> domain. We have noticed that several of the scripts are incapable of
reading
> or writing to the Windows 2008 Server registry. Does anyone know of an
easy
> workaround or a solution to this issue?
>


From: Ratboy on 24 Feb 2010 08:15
Thanks you, I will give that a shot

"mayayana" <mayayana(a)nospam.invalid> wrote in message
news:uGozu5NtKHA.3360(a)TK2MSFTNGP06.phx.gbl...
> In addition to permissions issues and
> 32 vs 64 bit issues. I've had trouble with
> WScrip.Shell on Win7. I don't know if that's
> a known problem, but I found with one script
> that WScript.shell simply didn't work, while the
> same operation using WMI StdRegProv did work.
> I can't explain it. I just switched to WMI for
> Win7.
>
>
>> I have several maintenance automation scripts in place for servers in our
>> domain. We have noticed that several of the scripts are incapable of
> reading
>> or writing to the Windows 2008 Server registry. Does anyone know of an
> easy
>> workaround or a solution to this issue?
>>
>
>
 | 
Pages: 1
Prev: VBS 5.8 reference
Next: Runtime error 6068