I am having some difficulty pushing out a .reg file in a startup script. It
seems to only work sporatically, or not at all. Can someone help me with
troubleshooting ideas?

thanks.

Chris Markus schrieb:
> I am having some difficulty pushing out a .reg file in a startup script. It
> seems to only work sporatically, or not at all. Can someone help me with
> troubleshooting ideas?

convert it to an ADM template.

common problems with .reg files:
- no permissions to add a HKLM entry as a user
- script runs async. the import happens too late, e.g. if
you manipulate the explorer, the program starts prior
script finishes.

Solutions:
- make users local admins ... argh, don´t do that! Just kidding.
- compconf\admtmepl\system\scripts
"Run Scrpts synchronously"

Or just use an ADM template.

Mark
--
Mark Heitbrink - MVP Windows Server
Homepage: www.gruppenrichtlinien.de
extend GPO: www.desktopstandard.com
PM: Vorname@Homepage, Versende-Adresse wird nicht abgerufen.

thanks for the suggestion with the ADM template. If I am trying to update
the registry HKLM\software\microsoft\office\11.0\outlook with a new dword,
what is the syntax for the adm?

"Mark Heitbrink [MVP]" wrote:

> Chris Markus schrieb:
> > I am having some difficulty pushing out a .reg file in a startup script. It
> > seems to only work sporatically, or not at all. Can someone help me with
> > troubleshooting ideas?
>
> convert it to an ADM template.
>
> common problems with .reg files:
> - no permissions to add a HKLM entry as a user
> - script runs async. the import happens too late, e.g. if
> you manipulate the explorer, the program starts prior
> script finishes.
>
> Solutions:
> - make users local admins ... argh, don´t do that! Just kidding.
> - compconf\admtmepl\system\scripts
> "Run Scrpts synchronously"
>
> Or just use an ADM template.
>
> Mark
> --
> Mark Heitbrink - MVP Windows Server
> Homepage: www.gruppenrichtlinien.de
> extend GPO: www.desktopstandard.com
> PM: Vorname@Homepage, Versende-Adresse wird nicht abgerufen.
>

Hi,

Chris Markus schrieb:
> thanks for the suggestion with the ADM template. If I am trying to update
> the registry HKLM\software\microsoft\office\11.0\outlook with a new dword,
> what is the syntax for the adm?

http://www.oreilly.de/catalog/winsys...pter/ch08.html

can look like this:

CLASS MACHINE

CATEGORY "Outlook Configuration"
KEYNAME "software\microsoft\office\11.0\outlook"
POLICY "What ever you want to do, with this policy"
VALUENAME "yourDWord"
VALUEON NUMERIC 1 VALUEOFF NUMERIC 0
; or: on=0 and off=1, or: off=DELETE
END POLICY
END CATEGORY

Mark
--
Mark Heitbrink - MVP Windows Server
Homepage: www.gruppenrichtlinien.de
extend GPO: www.desktopstandard.com
PM: Vorname@Homepage, Versende-Adresse wird nicht abgerufen.

If you would rather just push the registry entries, see
tip 9808 » PolicyMaker™ Registry Extension freeware.
in the 'Tips & Tricks' at http://www.jsifaq.com


On Thu, 15 Jun 2006 11:29:02 -0700, Chris Markus <(E-Mail Removed)> wrote:

>thanks for the suggestion with the ADM template. If I am trying to update
>the registry HKLM\software\microsoft\office\11.0\outlook with a new dword,
>what is the syntax for the adm?
>
>"Mark Heitbrink [MVP]" wrote:
>
>> Chris Markus schrieb:
>> > I am having some difficulty pushing out a .reg file in a startup script. It
>> > seems to only work sporatically, or not at all. Can someone help me with
>> > troubleshooting ideas?
>>
>> convert it to an ADM template.
>>
>> common problems with .reg files:
>> - no permissions to add a HKLM entry as a user
>> - script runs async. the import happens too late, e.g. if
>> you manipulate the explorer, the program starts prior
>> script finishes.
>>
>> Solutions:
>> - make users local admins ... argh, don´t do that! Just kidding.
>> - compconf\admtmepl\system\scripts
>> "Run Scrpts synchronously"
>>
>> Or just use an ADM template.
>>
>> Mark
>> --
>> Mark Heitbrink - MVP Windows Server
>> Homepage: www.gruppenrichtlinien.de
>> extend GPO: www.desktopstandard.com
>> PM: Vorname@Homepage, Versende-Adresse wird nicht abgerufen.
>>

Jerold Schulman
Windows Server MVP
JSI, Inc.
http://www.jsiinc.com
http://www.jsifaq.com

Hi,

I do this all the time. Works like a Charm.

Put the .reg file in the NETLOGON share. Have a Batch File as a Startup
Script. In the batch file type

regedit /s \\server\netlogon\file.reg

I have about 50 that always work.

Cheers,
Lara

"Chris Markus" wrote:

> I am having some difficulty pushing out a .reg file in a startup script. It
> seems to only work sporatically, or not at all. Can someone help me with
> troubleshooting ideas?
>
> thanks.

Hi,

lforbes schrieb:
> I do this all the time. Works like a Charm.
> Put the .reg file in the NETLOGON share. Have a Batch File as a Startup
> Script. In the batch file type
> regedit /s \\server\netlogon\file.reg
> I have about 50 that always work.

Because:
- non is editing the HKLM Hive
or
- every user in your network ahs the permission to write to
HKLM (Power User or local Admin) or manual define permissions
vie GPO -> Registry
- the User is allowed to edit the registry in general

Deploying *.reg files in a login script or startup script
can cause failures, there is no general way to say "it always work".

Thats why I recomend to avoid them.

Mark
--
Mark Heitbrink - MVP Windows Server
Homepage: www.gruppenrichtlinien.de
extend GPO: www.desktopstandard.com
PM: Vorname@Homepage, Versende-Adresse wird nicht abgerufen.

Hi

> I do this all the time. Works like a Charm.
>
> Put the .reg file in the NETLOGON share. Have a Batch File as a Startup
> Script. In the batch file type
>
> regedit /s \\server\netlogon\file.reg
>
> I have about 50 that always work.

Your network security probably isn't very good in that case - note he
says he wants to deploy HKLM.

--
Gerry Hickman (London UK)

Hi,

If I'm doing HKLM, I usually just do it overnight using WMI as I don't
like Machine policies, but there's one advantage to Machine policies -
they will also be applied to newly built machines automatically.

Jerold Schulman wrote:
> If you would rather just push the registry entries, see
> tip 9808 » PolicyMaker™ Registry Extension freeware.
> in the 'Tips & Tricks' at http://www.jsifaq.com
>
>
> On Thu, 15 Jun 2006 11:29:02 -0700, Chris Markus <(E-Mail Removed)> wrote:
>
>> thanks for the suggestion with the ADM template. If I am trying to update
>> the registry HKLM\software\microsoft\office\11.0\outlook with a new dword,
>> what is the syntax for the adm?
>>
>> "Mark Heitbrink [MVP]" wrote:
>>
>>> Chris Markus schrieb:
>>>> I am having some difficulty pushing out a .reg file in a startup script. It
>>>> seems to only work sporatically, or not at all. Can someone help me with
>>>> troubleshooting ideas?
>>> convert it to an ADM template.
>>>
>>> common problems with .reg files:
>>> - no permissions to add a HKLM entry as a user
>>> - script runs async. the import happens too late, e.g. if
>>> you manipulate the explorer, the program starts prior
>>> script finishes.
>>>
>>> Solutions:
>>> - make users local admins ... argh, don´t do that! Just kidding.
>>> - compconf\admtmepl\system\scripts
>>> "Run Scrpts synchronously"
>>>
>>> Or just use an ADM template.
>>>
>>> Mark
>>> --
>>> Mark Heitbrink - MVP Windows Server
>>> Homepage: www.gruppenrichtlinien.de
>>> extend GPO: www.desktopstandard.com
>>> PM: Vorname@Homepage, Versende-Adresse wird nicht abgerufen.
>>>
>
> Jerold Schulman
> Windows Server MVP
> JSI, Inc.
> http://www.jsiinc.com
> http://www.jsifaq.com


--
Gerry Hickman (London UK)

Hi,

Actually, IF you are deploying it as a Logon Script, it will only work with
the HKLUser Key. IF you deploy it as a Startup Script it WILL modify the
HKLMachine key with absolutely no problems because it uses the SYSTEM account
and not a local user account. I again have about these batch files-reg files
that do everything from turning the Numlock Key on to setting the Desktop
behind the CTRL-ALT-Del sign to adding registry keys for Applications that
need specific keys modified.

I also use VBScript files to Modify the Registry but they won't work
reliably as Start-up Scripts. The reason that VBScript won't work is simply
because the VBScript engine doesn't load until after the startup scripts.
That is why VBScript Startup scripts are unreliable. I use VBScripts soley
for logon scripts.

I have been a network Admin since Windows NT 3.x Back in those days there
was no such thing as Group Policy and everything had to be done manually so I
scripted pretty much everything with BATCH files.

There is a way to "hack" the registry of local computers using Group Policy.
I use it rarely though. It is in the Local Settings - Registry. Currently I
only use it to set permissions on the Security Tab so my users cannot see the
Security Tab in the properties and set file permissions.

Cheers,
Lara

"Mark Heitbrink [MVP]" wrote:

> Hi,
>
> lforbes schrieb:
> > I do this all the time. Works like a Charm.
> > Put the .reg file in the NETLOGON share. Have a Batch File as a Startup
> > Script. In the batch file type
> > regedit /s \\server\netlogon\file.reg
> > I have about 50 that always work.
>
> Because:
> - non is editing the HKLM Hive
> or
> - every user in your network ahs the permission to write to
> HKLM (Power User or local Admin) or manual define permissions
> vie GPO -> Registry
> - the User is allowed to edit the registry in general
>
> Deploying *.reg files in a login script or startup script
> can cause failures, there is no general way to say "it always work".
>
> Thats why I recomend to avoid them.
>
> Mark
> --
> Mark Heitbrink - MVP Windows Server
> Homepage: www.gruppenrichtlinien.de
> extend GPO: www.desktopstandard.com
> PM: Vorname@Homepage, Versende-Adresse wird nicht abgerufen.
>