Re: Assigning software via Group Policy
- From: "zenner" <zenner@xxxxxxxxxxx>
- Date: Wed, 13 Jul 2005 22:42:25 GMT
Yes, I use it in production environments. Once you define the group
classifications, it is basically self-maintaining. Start out with Admin
users, work out the bug then move to users, with what you learn.
Sometimes posting upgrades can be a bit tricky. In the way of a caveat; it
is easy to run into licensing problems, so a quarterly...minimum of yearly,
installed software review of installed vs. licensed copies is important.
Once properly setup, you eliminate the majority of helpdesk calls related to
application problems. Worse case, just delete the app and let it reinstall.
Slipstreaming upgrades to the base application can keep ".msi" apps
up-to-date, without Ops or user intervention. Home-grown, custom
applications can be deployed...it just takes a little imagination, effort
and a pristine system to stage the install. Really useful if you suffer a
lot of employee turn-over.
"Daniel Wilson" <d.wilson@xxxxxxxxxxx> wrote in message
news:ua3uBJ$hFHA.1204@xxxxxxxxxxxxxxxxxxxxxxx
> One of the things I'm studying for 296 is assigning/publishing software
> via
> Group Policy. I'm also preparing to help some of our customers implement
> it
> for our software.
>
> Does anybody use this outside the labratory? Our customers' admins don't
> use it & most seem not to have heard of it.
>
> Do any of you have personal experience with it? If so, would you recomend
> it?
>
> Thanks.
>
>
> --
> Daniel Wilson
>
>
.
- References:
- Assigning software via Group Policy
- From: Daniel Wilson
- Assigning software via Group Policy
- Prev by Date: Re: High Score on 70-218
- Next by Date: Re: High Score on 70-218
- Previous by thread: Assigning software via Group Policy
- Next by thread: Re: Assigning software via Group Policy
- Index(es):
Relevant Pages
|