|
Rick-
Another option to consider is to use security group
filtering on that GPO instead of relying on moving machines around. In other
words, permission the GPO so that only machines that are part of the "O2K3
Install" group will process the policy. Then, getting Office installed is simply
a matter of adding a machine to a group rather than having to move machines back
and forth between OUs.
Darren From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gasper, Rick Sent: Tuesday, May 25, 2004 9:18 AM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] task pads We want to have the first level support person move the machine into an OU so that office 2003 can be installed via group policy.
Rick
Gasper
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Mulnick,
Al
? You want to give some sort of secretary a MMC? Sure, why not? Works out well. You'll want to give permissions over computer objects as well for both the current and destination OU's it sounds like.
Not sure why somebody would be moving a computer account though? Is that some sort of tracking mechanism for you?
Al
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Gasper,
Rick Hi all, I need to give a non admin IT user access to aduc. Our plan is to use gpo to push out office 2k3. The non admin IT user is to move the machine to the deployment OU. Is this possible? I am thinking creating a task pad will do this, but I have not ever done that. Manager Network Services King's College Wilkes-Barre PA 18711 PH: 570-208-5845 Fax: 570-208-6072 |
Title: task pads
- [ActiveDir] task pads Gasper, Rick
- RE: [ActiveDir] task pads Mulnick, Al
- RE: [ActiveDir] task pads Gasper, Rick
- RE: [ActiveDir] task pads Darren Mar-Elia
- RE: [ActiveDir] task pads Passo, Larry
- RE: [ActiveDir] task pads Gasper, Rick
