[gptalk] Re: gpedit.msc

  • From: "Cruz, Jerome L" <jerome.l.cruz@xxxxxxxxxx>
  • To: "gptalk@xxxxxxxxxxxxx" <gptalk@xxxxxxxxxxxxx>
  • Date: Wed, 29 Oct 2008 13:25:22 -0700

There is another aspect to this that relates to usability. It regards the GPMC 
scripts. Some of them depend upon the 'Lib_CommonGPMCFunctions.js' resource 
file to function correctly. My experience is that any of the sample scripts 
that rely upon that resource fail to work. I have yet to find an exception to 
this or to develop any type of work-around on 64-bit systems. GPMC scripts that 
do not depend upon that file seem to work just fine. My testing is NOT 
exhaustive.

In short, you really need to have a "very" good reason to be installing and 
using it on a 64-bit device...and did I mention that it's "NOT" supported by 
Microsoft? :-)

Use Vista or W2KOCHO 64-bit devices where it's supported natively (with all the 
new features as well)!

Jerry


-----Original Message-----
From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] On 
Behalf Of Cruz, Jerome L
Sent: Tuesday, October 28, 2008 12:11 PM
To: gptalk@xxxxxxxxxxxxx
Subject: [gptalk] Re: gpedit.msc

As noted: It's not supported by Microsoft. I have all 64 bit DCs and I do 
sometimes need to edit from there. Example: to get the SID of an account 
correctly into a User Rights Assignment setting...if not done on a DC, you can 
get an account's "text" name added to the GPO instead of its SID... if the 
account is ever renamed...you break the GPO for the account.

I can say it has worked just fine for specific Security settings I've used it 
on (Account Policies, User Rights Assignments, and Security Options only) and 
for Admin Template (registry) items. I have not tested other client extensions. 
Always test in the lab first to make sure it works.

You're on your own with this one....

Jerry

-----Original Message-----
From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] On 
Behalf Of Aaron Rabinowitz
Sent: Tuesday, October 28, 2008 11:03 AM
To: gptalk@xxxxxxxxxxxxx
Subject: [gptalk] Re: gpedit.msc

-woops i read that wrong -

- it is 64bit 2003 R2 server

- copying the gpedit from system32 to the syswow64 folder has fixed
the problem - is this soemthing I can leave and not have to worry
about or is this a temp solution I should delete and not keep?

thanks for all of your help btw!! you've all been quite helpful

Aaron


On Tue, Oct 28, 2008 at 12:54 PM, Cruz, Jerome L
<jerome.l.cruz@xxxxxxxxxx> wrote:
> Actually "SystemRoot=C:\WINDOWS" is correct as Jamie already noted in his 
> message...
>
>  > Also make sure your SYSTEMROOT and WINDIR variables are correctly
>  > pointing to 'C:\WINDOWS'
>
> Jerry Cruz | Group Policies Product Manager | Windows Infrastructure 
> Architecture | Boeing IT
>
>
> -----Original Message-----
> From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] On 
> Behalf Of Aaron Rabinowitz
> Sent: Tuesday, October 28, 2008 9:43 AM
> To: gptalk@xxxxxxxxxxxxx
> Subject: [gptalk] Re: gpedit.msc
>
> I think thats the problem  it looks like its specifying the root as
> SystemRoot=C:\WINDOWS instead of system32.... how should I got about
> changing it?
>
> On Tue, Oct 28, 2008 at 11:51 AM, Nelson, Jamie <Jamie.Nelson@xxxxxxx> wrote:
>> Easiest way is to go to a command prompt and type 'set', then hit enter.
>> This will list all your environment variables.
>>
>> Look for the PATH variable, which will be a long string of directories
>> separated by semicolons. Make sure the 'C:\WINDOWS\System32' directory
>> is in there.
>>
>> Also make sure your SYSTEMROOT and WINDIR variables are correctly
>> pointing to 'C:\WINDOWS'
>>
>> Jamie Nelson | Operations Consultant | BI&T Infrastructure-Intel | Devon
>> Energy Corporation | Work: 405.552.8054 | Mobile: 405.200.8088 |
>> http://www.dvn.com
>>
>>
>> -----Original Message-----
>> From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx]
>> On Behalf Of Aaron Rabinowitz
>> Sent: Tuesday, October 28, 2008 10:34 AM
>> To: gptalk@xxxxxxxxxxxxx
>> Subject: [gptalk] Re: gpedit.msc
>>
>> how do I check that? sorry im not that knowledgeable
>>
>> On Tue, Oct 28, 2008 at 11:32 AM, Nelson, Jamie <Jamie.Nelson@xxxxxxx>
>> wrote:
>>> Check your path environment variable and make sure it didn't get
>> messed
>>> up somehow.
>>>
>>> Jamie Nelson | Operations Consultant | BI&T Infrastructure-Intel |
>> Devon
>>> Energy Corporation | Work: 405.552.8054 | Mobile: 405.200.8088 |
>>> http://www.dvn.com
>>>
>>>
>>> -----Original Message-----
>>> From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx]
>>> On Behalf Of Aaron Rabinowitz
>>> Sent: Tuesday, October 28, 2008 10:30 AM
>>> To: gptalk@xxxxxxxxxxxxx
>>> Subject: [gptalk] Re: gpedit.msc
>>>
>>> it actually exists there - and works when I click it... gpmc just
>>> doesnt find it?
>>>
>>> On Tue, Oct 28, 2008 at 11:26 AM, Darren Mar-Elia <darren@xxxxxxxxxx>
>>> wrote:
>>>> Perhaps gpedit.msc got deleted? Check in c:\windows\system32 to make
>>> sure
>>>> that's it. You can create a new version by saving the MMC tool with
>> GP
>>>> Editor loaded as that name in c:\windows\system32.
>>>>
>>>> Darren
>>>>
>>>> -----Original Message-----
>>>> From: gptalk-bounce@xxxxxxxxxxxxx
>> [mailto:gptalk-bounce@xxxxxxxxxxxxx]
>>> On
>>>> Behalf Of Aaron Rabinowitz
>>>> Sent: Tuesday, October 28, 2008 8:22 AM
>>>> To: gptalk@xxxxxxxxxxxxx
>>>> Subject: [gptalk] gpedit.msc
>>>>
>>>> When I try to edit a policy from the gpmc (right clicking gpo and
>>>> selecting 'edit') it says gpedit.msc not found - any thoughts? I can
>>>> access it though mmc and adding in the group policy snap in but I
>>>> would like to be able toa ccess it through the gpmc.
>>>> ***********************
>>>> You can unsubscribe from gptalk by sending email to
>>>> gptalk-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field
>>> OR by
>>>> logging into the freelists.org Web interface. Archives for the list
>>> are
>>>> available at http://www.freelists.org/archives/gptalk/
>>>> ************************
>>>>
>>>> ***********************
>>>> You can unsubscribe from gptalk by sending email to
>>> gptalk-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field
>> OR
>>> by logging into the freelists.org Web interface. Archives for the list
>>> are available at http://www.freelists.org/archives/gptalk/
>>>
>>>> ************************
>>>>
>>> ***********************
>>> You can unsubscribe from gptalk by sending email to
>>> gptalk-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field
>> OR
>>> by logging into the freelists.org Web interface. Archives for the list
>>> are available at http://www.freelists.org/archives/gptalk/
>>> ************************
>>> Confidentiality Warning: This message and any attachments are intended
>> only for the use of the intended recipient(s), are confidential, and may
>> be privileged.
>>> If you are not the intended recipient, you are hereby notified that
>> any review, retransmission, conversion to hard copy, copying,
>> circulation or other use of all or any portion of this message and any
>> attachments is strictly prohibited. If you are not the intended
>> recipient, please notify the sender immediately by return e-mail, and
>> delete this message and any attachments from your system.
>>> ***********************
>>> You can unsubscribe from gptalk by sending email to
>> gptalk-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field OR
>> by logging into the freelists.org Web interface. Archives for the list
>> are available at http://www.freelists.org/archives/gptalk/
>>
>>> ************************
>>>
>> ***********************
>> You can unsubscribe from gptalk by sending email to
>> gptalk-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field OR
>> by logging into the freelists.org Web interface. Archives for the list
>> are available at http://www.freelists.org/archives/gptalk/
>> ************************
>> ***********************
>> You can unsubscribe from gptalk by sending email to 
>> gptalk-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field OR by 
>> logging into the freelists.org Web interface. Archives for the list are 
>> available at http://www.freelists.org/archives/gptalk/
>
>> ************************
>>
> ***********************
> You can unsubscribe from gptalk by sending email to 
> gptalk-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field OR by 
> logging into the freelists.org Web interface. Archives for the list are 
> available at http://www.freelists.org/archives/gptalk/


> ************************
> ***********************
> You can unsubscribe from gptalk by sending email to 
> gptalk-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field OR by 
> logging into the freelists.org Web interface. Archives for the list are 
> available at http://www.freelists.org/archives/gptalk/


> ************************
>
***********************
You can unsubscribe from gptalk by sending email to 
gptalk-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field OR by 
logging into the freelists.org Web interface. Archives for the list are 
available at http://www.freelists.org/archives/gptalk/
************************
***********************
You can unsubscribe from gptalk by sending email to 
gptalk-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field OR by 
logging into the freelists.org Web interface. Archives for the list are 
available at http://www.freelists.org/archives/gptalk/
************************
***********************
You can unsubscribe from gptalk by sending email to 
gptalk-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field OR by 
logging into the freelists.org Web interface. Archives for the list are 
available at http://www.freelists.org/archives/gptalk/
************************

Other related posts: