Link to home
Start Free TrialLog in
Avatar of macdonaldchinyani
macdonaldchinyaniFlag for United Kingdom of Great Britain and Northern Ireland

asked on

GEDIT.MSC

l have a windows server 2003 domain controller.l want to edit default domin policy and its coming with error.The way l am doing it is select Active Directory users and computers,select the domain,right click the selected domain,click properties,highlight the default policy and click edit and this error comes up "Failed to start Group Policy.The gedit.msc file maybe missing,files with the .msc extention maynot be associated with mmc.exe"
Avatar of graye
graye
Flag of United States of America image

Let's try a test before we "go down that rabbit hole"...
From the Start Menu, click on Run, type GPEDIT.MSC....  and let's see what happens
Avatar of macdonaldchinyani

ASKER

l am logging onto Server 2003 as an Admin and when l type gpedit.msc what comes is local computer policy not domain security policy.
Yeah but... that was just a test to see if the association of the *.msc extension was properly connected to MMC.
By default, 64-bit OS lauch the 64-bit version of MMC (when launched from the command line, like it our test).   I would assume that would also be the case for launching "AD Users and Computers".   Did you do anything strange when launching "users and computers"?
Its a 64bit Server and l did not do anything strange when launching AD user and computers.
Next, do a search for GEDIT.MSC to see where is shows up
After that we'll check the registry entries
when l search for gedit.msc it cannot find it."There are no results to display"
I'm sorry, that was a typo...  you need to search for GPEDIT.MSC to see where is shows  up.   For example, I'd expect  you'd find it at:
  • C:\Windows\System32
  • C:\Windows\SysWOW64
  • C:\Windows\winsxs
l have searched for gpedit.msc and its in C:\Windows\system32
Hummm.... it appears as if the 32-bit version of GPEDIT.MSC is indeed missing from your system.   Could you verify that it really isn't in C:\WIndows\SysWOW64
I'd recommend that you run the File System Checker (SFC) to detect and repair the missing files
http://support.microsoft.com/kb/310747 
l hnave verified that gpedit.msc is in C:/windows/system32 and not in C:\WIndows\SysWOW64
Okey dokey... then I'd suggest that you run the SFC to repair your installation of windows
ASKER CERTIFIED SOLUTION
Avatar of graye
graye
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
OK, search your registy to see if gpedit.dll appears in the following locations:
Windows Registry Editor Version 5.00
 
[HKEY_CLASSES_ROOT\CLSID\{0FDE5092-AA2A-11D1-A7D4-0000F87571E3}\InProcServer32]
@=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\
  00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,47,00,50,00,\
  45,00,64,00,69,00,74,00,2e,00,64,00,6c,00,6c,00,00,00
"ThreadingModel"="Apartment"
 
Windows Registry Editor Version 5.00
 
[HKEY_CLASSES_ROOT\CLSID\{4F637904-2CAB-4F0E-8688-D3717EBD2975}\InProcServer32]
@=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\
  00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,47,00,50,00,\
  45,00,64,00,69,00,74,00,2e,00,64,00,6c,00,6c,00,00,00
"ThreadingModel"="Apartment"
 
Windows Registry Editor Version 5.00
 
[HKEY_CLASSES_ROOT\CLSID\{63E23168-BFF7-4E87-A246-EF024425E4EC}\InProcServer32]
@=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\
  00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,47,00,50,00,\
  45,00,64,00,69,00,74,00,2e,00,64,00,6c,00,6c,00,00,00
"ThreadingModel"="Apartment"
 
Windows Registry Editor Version 5.00
 
[HKEY_CLASSES_ROOT\CLSID\{6DC3804B-7212-458D-ADB0-9A07E2AE1FA2}\InProcServer32]
@=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\
  00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,47,00,50,00,\
  45,00,64,00,69,00,74,00,2e,00,64,00,6c,00,6c,00,00,00
"ThreadingModel"="Apartment"
 
Windows Registry Editor Version 5.00
 
[HKEY_CLASSES_ROOT\CLSID\{8FC0B734-A0E1-11D1-A7D3-0000F87571E3}\InProcServer32]
@=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\
  00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,47,00,50,00,\
  45,00,64,00,69,00,74,00,2e,00,64,00,6c,00,6c,00,00,00
"ThreadingModel"="Apartment"
 
Windows Registry Editor Version 5.00
 
[HKEY_CLASSES_ROOT\CLSID\{D70A2BEA-A63E-11D1-A7D4-0000F87571E3}\InProcServer32]
@=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\
  00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,47,00,50,00,\
  45,00,64,00,69,00,74,00,2e,00,64,00,6c,00,6c,00,00,00
"ThreadingModel"="Apartment"
 
Windows Registry Editor Version 5.00
 
[HKEY_CLASSES_ROOT\CLSID\{EA502722-A23D-11D1-A7D3-0000F87571E3}\InProcServer32]
@=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\
  00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,47,00,50,00,\
  45,00,64,00,69,00,74,00,2e,00,64,00,6c,00,6c,00,00,00
"ThreadingModel"="Apartment"
 
Windows Registry Editor Version 5.00
 
[HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{0FDE5092-AA2A-11D1-A7D4-0000F87571E3}\InProcServer32]
@=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\
  00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,47,00,50,00,\
  45,00,64,00,69,00,74,00,2e,00,64,00,6c,00,6c,00,00,00
"ThreadingModel"="Apartment"
 
Windows Registry Editor Version 5.00
 
[HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{4F637904-2CAB-4F0E-8688-D3717EBD2975}\InProcServer32]
@=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\
  00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,47,00,50,00,\
  45,00,64,00,69,00,74,00,2e,00,64,00,6c,00,6c,00,00,00
"ThreadingModel"="Apartment"
 
Windows Registry Editor Version 5.00
 
[HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{63E23168-BFF7-4E87-A246-EF024425E4EC}\InProcServer32]
@=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\
  00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,47,00,50,00,\
  45,00,64,00,69,00,74,00,2e,00,64,00,6c,00,6c,00,00,00
"ThreadingModel"="Apartment"
 
Windows Registry Editor Version 5.00
 
[HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{6DC3804B-7212-458D-ADB0-9A07E2AE1FA2}\InProcServer32]
@=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\
  00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,47,00,50,00,\
  45,00,64,00,69,00,74,00,2e,00,64,00,6c,00,6c,00,00,00
"ThreadingModel"="Apartment"
 
Windows Registry Editor Version 5.00
 
[HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{8FC0B734-A0E1-11D1-A7D3-0000F87571E3}\InProcServer32]
@=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\
  00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,47,00,50,00,\
  45,00,64,00,69,00,74,00,2e,00,64,00,6c,00,6c,00,00,00
"ThreadingModel"="Apartment"
 
Windows Registry Editor Version 5.00
 
[HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{D70A2BEA-A63E-11D1-A7D4-0000F87571E3}\InProcServer32]
@=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\
  00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,47,00,50,00,\
  45,00,64,00,69,00,74,00,2e,00,64,00,6c,00,6c,00,00,00
"ThreadingModel"="Apartment"
 
Windows Registry Editor Version 5.00
 
[HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{EA502722-A23D-11D1-A7D3-0000F87571E3}\InProcServer32]
@=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\
  00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,47,00,50,00,\
  45,00,64,00,69,00,74,00,2e,00,64,00,6c,00,6c,00,00,00
"ThreadingModel"="Apartment"

Open in new window

l have done a search for gpedit.dll and thats what l found:
gedit.dll         C:\WINDOWS\System32
gedit.dll         C:\WINDOWS\SysWOW64
gedit.dll         C:\WINDOWS\Servicepackfiles\amd64
wgedit.dll         C:\WINDOWS\Servicepackfiles\i386
...and the registry locations?