Re: MMC error in snap-in. Cannot get into Microsoft Management Con

Tech-Archive recommends: Fix windows errors by optimizing your registry



"Lanwench [MVP - Exchange]" wrote:

Peggy Sue <PeggySue@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
"Jim Behning SBS MVP" wrote:

Does gpedit.msc work?

On Tue, 7 Oct 2008 07:38:12 -0700, Peggy Sue <Peggy
Sue@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

I am trying to manage our group policy, but am unable to get to
this area. I have programs which depend on the network and are
suddenly not accessible. Should I download MMC 3.0? We use Windows
Server 2003 SBS
Thank you for your time.
See what SBS support is working on
http://blogs.technet.com/sbs/default.aspx
Check your SBS with the SBS Best Practices Analyzer
http://blogs.technet.com/sbs/archive/tags/BPA/default.aspx

Thank you, When I go to gpedit.msc I find that NO items are
configured. Since I am just learning, any help with which items
should be configured and how to do this would be appreciated.

gpedit.msc is just going to open the local policy. You do not want to monkey
around in there, trust me. I think Jim was just asking whether you could use
an MMC to open it. You need gpmc.msc to be working if you have any hope of
managing your group policy, but the underlying problem with your MMCs may be
stopping you.

See my reply to your other msg in this thread?


Thanks for your help! gpmc.msc opens fine when I type in run.
In checking your other items I found:
DHCP when 1st opened showed "not running". When I clicked it showed "running".
Event Viewer opens with these noted errors:
MSExchangeDSAccess/ Topology Discovery Failed, error 0x80040a02

Microsoft ISA report generator/ failed error: 0000: 75 07 00 00

Yes, I have ISA...and have disabled Trend Micro firewall ONLY on server and
clients and thought I had the ISA firewall running, thinking that windows
firewall ICS was that. :( Tough...and your fears are correct. Have asked
repeatedly for tech help, but boss not doing this for me. SBS windows
firewall shows enabled in gpmc

With regard to program issues...they are installed on our tera station.
I will remember to use separate posts next time. New at this.
.

Relevant Pages

  • Re: DCOM 10009 errors on SBS2008 with NAS
    ... The DCOM event id 10009 will occur when a client workstation has a miss-configured firewall or other issues affecting its network communications within the domain, for example if the workstation is not managed by an SBS GPO. ... If the workstation is on a different subnet than the SBS server and it is running Windows XP SP2 or higher, the firewall exceptions provided by the SBS group policies will not properly allow the required connectivity. ... You should edit the Client XP GPO and change the scope of the rules to allow subnet + the internal IP of the server. ...
    (microsoft.public.windows.server.sbs)
  • Re: Trouble in Windows Firewall
    ... Error message when you expand "Publishing Points" in the Windows Media ... MMC has detected an error in a snap-in" ... When I Running ISA Server Management, and then click SBS Internet Access ...
    (microsoft.public.windows.server.sbs)
  • Re: Trouble in Windows Firewall
    ... I've installed SP2 on my Windows SBS 2003 R2. ... My question, If error happened in this MMC and then Ignoring that, would my ... Error message when you expand "Publishing Points" in the Windows Media ... I tried to uninstalling ISA Server and then installing again, ...
    (microsoft.public.windows.server.sbs)
  • RE: VPN Authentication problems (unable to connect to the network using the user name and password y
    ... VPN following the below steps or manually create VPN to SBS from My Network ... Communications and Remote Desktop Connection? ... Are they using Windows XP SP2? ... For managing the Windows XP SP2 firewall under SBS network, ...
    (microsoft.public.windows.server.sbs)
  • Re: Still cant connect to RWW or OWA remotely
    ... In the Services MMC, is the Windows ... Firewall/Internet Connection Sharing service 'Disabled'? ... "Windows Firewall cannot run because another ... it certainly appears to be something about the SBS configuration. ...
    (microsoft.public.windows.server.sbs)