Deploy Local Group Policy

[Guest]

We have 250 mobile users that do not connect to a domain yet. Our
infrastructure is migrating to AD, but we still are a year or so away. In
the meantime we need to deploy 250 laptops. We have 5 difference version of
the Panasonic CF-29 unit.

Every time we build a new image we need to run through all the GPEDIT.MSC
setting and a few SECPOL.MSC settings. Is it possible to back up all local
group policy and secpol settings that we enabled and deploy them onto another
system?

 

[Lanwench [MVP - Exchange]]

We have 250 mobile users that do not connect to a domain yet.
Youch.

Our
infrastructure is migrating to AD, but we still are a year or so
away.

Youch, again. What are they using now? NDS? Anything? Or just a big messy
workgroup config?

You might see whether http://www.scriptlogic.com/desktop_management.asp will
work without AD.

In the meantime we need to deploy 250 laptops. We have 5
difference version of the Panasonic CF-29 unit.

Every time we build a new image we need to run through all the
GPEDIT.MSC setting and a few SECPOL.MSC settings. Is it possible to
back up all local group policy and secpol settings that we enabled
and deploy them onto another system?

If I were deploying that many new computers, I'd be imaging them from a
good/customized image I created.

That said, you can create .adm files to import into the local policies on
your computers - one way I haven't tried (but have read about) involves a
third party freeware tool called NUTS, which has something that converts
..reg (registry file export files) to .adm files. Info is found here:
http://yizhar.mvps.org/

I'd probably post in m.p.windows.group policy for more help. I'd actually be
curious about what will happen to all of this when you do move to AD.

 

[Guest]

Well we created 5 base images with all of our customizations. Problem is
every so often we get a new model of the CF-29. So far we have an ET, CT,
HT, LT and recently an NT version. We are ordering a few hundred more, but
Panasonic appears to cycle through models frequently.

I will try the links you suggested...as far as the new group
m.p.windows.group policy I will take a look.