Re: disabled in gpedit, but shutdown tracker still tracking
- From: "Evan" <eurkofsky@xxxxxxxxxxxxxxx>
- Date: Fri, 9 Sep 2005 12:36:08 -0700
oh, hey. thx for not giving up! i'm reasonably certain that it's a corrupted
install (scandisk, sfc, etc. were no help) so i already blew away the
partition and am re-installing now, WITHOUT the dell management disk. i'm
gonna chalk this up to a flukey install and get on with my life. :-) but, if
i run into the same problem, i'll post back.
again, i do appreciate your time.
thx,
evan
"Miha Pihler [MVP]" <mihap-news@xxxxxxxxxxx> wrote in message
news:%23At3qLXtFHA.1472@xxxxxxxxxxxxxxxxxxxxxxx
> OK. Sorry. My mistake. So if I understand it correctly you have NT domain?
>
> --
> Mike
> Microsoft MVP - Windows Security
>
>
> "Evan" <eurkofsky@xxxxxxxxxxxxxxx> wrote in message
> news:u$0s41WtFHA.460@xxxxxxxxxxxxxxxxxxxxxxx
>> thx for the help, mike. i had a feeling you were gonna say that. as i
>> stated previously, this particular domain is not ad'd, and i have no
>> intentions of making it so. (unless, of course, you're willing to call my
>> boss and convince her to do so!) i think i'm gonna reinstall and get dell
>> on the phone if i have any more problems. (i still suspect it might be
>> their damn server setup software).
>>
>> thx again!
>>
>> "Miha Pihler [MVP]" <mihap-news@xxxxxxxxxxx> wrote in message
>> news:eef4NxWtFHA.3720@xxxxxxxxxxxxxxxxxxxxxxx
>>> Install DNS service on Active Directory Server and create appropriate
>>> Forward Zones (DNS name of your Active Directory domain).
>>> Once it is installed change the preferred DNS setting (under TCP/IP) on
>>> the Active Directory Server to point back to its own IP address (or loop
>>> back IP address of 127.0.0.1). Once this is done, restart the NetLogon
>>> service on Active Directory Server.
>>>
>>> Now we can move to the File Server. Change the preferred DNS settings on
>>> the file server to point to IP address of your DNS server (I guess your
>>> Active Directory server now). Restart Netlogon service on this server or
>>> reboot the whole server if you can/want.
>>> See how server behaves now and we will take it from here if there are
>>> any problems (or what's left of the problems...)
>>>
>>> --
>>> Mike
>>> Microsoft MVP - Windows Security
>>>
>>>
>>> "Evan" <eurkofsky@xxxxxxxxxxxxxxx> wrote in message
>>> news:O6lwOoWtFHA.3328@xxxxxxxxxxxxxxxxxxxxxxx
>>>> yes, this box is a member of a domain. (something else i have not
>>>> mentioned before: this w2k3 box is replacing a w2k server box). so...
>>>>
>>>> sure let's fix the dns!! what do you have in mind?
>>>>
>>>> thx again,
>>>>
>>>> evan
>>>>
>>>>
>>>> "Miha Pihler [MVP]" <mihap-news@xxxxxxxxxxx> wrote in message
>>>> news:%23t7L7KWtFHA.3908@xxxxxxxxxxxxxxxxxxxxxxx
>>>>> Hi,
>>>>>
>>>>> Ok another question just to make sure -- this file server is a member
>>>>> of domain? If yes, then you will _have_ to fix the DNS thing first
>>>>> before we can go on. Even if you do the fdisk (and I don't think you
>>>>> will have to once you fix DNS) it will only fix the problem for short
>>>>> period of time (days, maybe a week...)...
>>>>>
>>>>> --
>>>>> Mike
>>>>> Microsoft MVP - Windows Security
>>>>>
>>>>> "Evan" <Evan@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>>>>> news:8B8E5807-44E3-4F2A-AF55-84C235FBC437@xxxxxxxxxxxxxxxx
>>>>>> hi mike. i'm sorry if i have not been clear in my previous posts: we
>>>>>> are not
>>>>>> using ad. the dc does not have the dns server role installed. (don't
>>>>>> ask me
>>>>>> why. it was like that when i got here and my boss wants/likes it that
>>>>>> way).
>>>>>>
>>>>>> so, with that in mind, let's recap: this is a w2k3 box set up as a
>>>>>> file
>>>>>> server only; *NO* ad; the system log is corrupted; event tracker
>>>>>> disabled in
>>>>>> gpo but still tracking; red X on computer configuration in rsop
>>>>>> (prolly cuz
>>>>>> no ad, right?); red X on "administrator on ourserver - rsop" in rsop;
>>>>>> also -
>>>>>> not previously mentioned - i have disables ie enhanced secrity and
>>>>>> can surf
>>>>>> just fine, but the homepage is stuck on the enhanced security
>>>>>> message.
>>>>>>
>>>>>> what do you think? fdisk?
>>>>>>
>>>>>> thx again.
>>>>>>
>>>>>> "Miha Pihler [MVP]" wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> My suggestion it to try and solve one problem at the time :-). I
>>>>>>> will help
>>>>>>> you as much as I can.
>>>>>>>
>>>>>>> One of requirements for setting up Active Directory is DNS server.
>>>>>>> You can't
>>>>>>> have (healthy, working) Active Directory without DNS server.
>>>>>>>
>>>>>>> In most cases Active Directory server will also be DNS server...
>>>>>>>
>>>>>>> Since your server is member of your Active Directory domain it needs
>>>>>>> to talk
>>>>>>> to domain controller. The only way for your server to find domain
>>>>>>> controller
>>>>>>> is by DNS. So this is something your will have to check and fix.
>>>>>>>
>>>>>>> If you run
>>>>>>>
>>>>>>> ipconfig /all
>>>>>>>
>>>>>>> on your server. What is the result that you get?
>>>>>>>
>>>>>>> Can you check your Active Directory server to see if DNS Server is
>>>>>>> installed
>>>>>>> on it?
>>>>>>>
>>>>>>> --
>>>>>>> Mike
>>>>>>> Microsoft MVP - Windows Security
>>>>>>>
>>>>>>> "Evan" <eurkofsky@xxxxxxxxxxxxxxx> wrote in message
>>>>>>> news:e4F67eVtFHA.1372@xxxxxxxxxxxxxxxxxxxxxxx
>>>>>>> > okay, we don't have a dns server so it's set to obtain
>>>>>>> > automatically. the
>>>>>>> > system event viewer...
>>>>>>> >
>>>>>>> > okay, obviously something got f'ed up here. i got a red X on the
>>>>>>> > system
>>>>>>> > event viewer (application and security are okay) and a dialog
>>>>>>> > stating that
>>>>>>> > the system log is corrupted. as you're an mvp, i'll take your
>>>>>>> > advice here,
>>>>>>> > but this is a brand new box with no data yet, so i'm thinkin' "do
>>>>>>> > over".
>>>>>>> > what do you think?
>>>>>>> >
>>>>>>> > thx again for your help on this.
>>>>>>> >
>>>>>>> > evan
>>>>>>> >
>>>>>>> > "Miha Pihler [MVP]" <mihap-news@xxxxxxxxxxx> wrote in message
>>>>>>> > news:%23DC7RKRtFHA.4080@xxxxxxxxxxxxxxxxxxxxxxx
>>>>>>> >> Hi,
>>>>>>> >>
>>>>>>> >> Can you check few things on this server?
>>>>>>> >> - Are there any errors on this server in Application or System
>>>>>>> >> Event log?
>>>>>>> >> - Where does preferred DNS point to on this server (configuration
>>>>>>> >> under
>>>>>>> >> TCP/IP properties)
>>>>>>> >>
>>>>>>> >> --
>>>>>>> >> Mike
>>>>>>> >> Microsoft MVP - Windows Security
>>>>>>> >>
>>>>>>> >> "Evan" <eurkofsky@xxxxxxxxxxxxxxx> wrote in message
>>>>>>> >> news:eTd2WKNtFHA.2892@xxxxxxxxxxxxxxxxxxxxxxx
>>>>>>> >>> yup. i did just what you did: start|run|gpedit.msc|CC|AT|system.
>>>>>>> >>> and by
>>>>>>> >>> gum, it's set to 'disable'. via rsop: well now, that's
>>>>>>> >>> interesting. i've
>>>>>>> >>> got a red X thru computer configuration. hmmm, there's even a
>>>>>>> >>> red X
>>>>>>> >>> above that on the root of "administrator on ourservername -
>>>>>>> >>> rsop"
>>>>>>> >>>
>>>>>>> >>> okay, wtf?
>>>>>>> >>>
>>>>>>> >>>
>>>>>>> >>> "Miha Pihler [MVP]" <mihap-news@xxxxxxxxxxx> wrote in message
>>>>>>> >>> news:%236a4VnKtFHA.3596@xxxxxxxxxxxxxxxxxxxxxxx
>>>>>>> >>>> Hi,
>>>>>>> >>>>
>>>>>>> >>>> How did you set the policy?
>>>>>>> >>>>
>>>>>>> >>>> I just tested this on one of mine computers and it worked.
>>>>>>> >>>>
>>>>>>> >>>> I open group policy editor and drilled down under Computer
>>>>>>> >>>> Configuration\Administrative Templates\System. Here I doubled
>>>>>>> >>>> clicked
>>>>>>> >>>> on the policy called "Shut Down Event Tracker" and selected
>>>>>>> >>>> Disable. I
>>>>>>> >>>> closed the policy and the server did not show the Tracker any
>>>>>>> >>>> more...
>>>>>>> >>>>
>>>>>>> >>>> Can you run RSOP.msc from Start -> Run menu on the server? What
>>>>>>> >>>> do you
>>>>>>> >>>> see set for "Shut Down Event Tracker" policy?
>>>>>>> >>>>
>>>>>>> >>>> --
>>>>>>> >>>> Mike
>>>>>>> >>>> Microsoft MVP - Windows Security
>>>>>>> >>>>
>>>>>>> >>>> "Evan" <eurkofsky@xxxxxxxxxxxxxxx> wrote in message
>>>>>>> >>>> news:%238HqwlItFHA.616@xxxxxxxxxxxxxxxxxxxxxxx
>>>>>>> >>>>> hey mike.
>>>>>>> >>>>>
>>>>>>> >>>>> yes, this is a file server only and is on a domain. i edited
>>>>>>> >>>>> the
>>>>>>> >>>>> policy locally. please note, though, that we are not using ad
>>>>>>> >>>>> so
>>>>>>> >>>>> nothing is getting pushed down via gpo. i'm wondering if this
>>>>>>> >>>>> has
>>>>>>> >>>>> something to do with the fact that i used dell's 'installation
>>>>>>> >>>>> and
>>>>>>> >>>>> server management' cd to do the install. it's the first time
>>>>>>> >>>>> i've used
>>>>>>> >>>>> that method and it's the first time i've had this problem.
>>>>>>> >>>>> doesn't
>>>>>>> >>>>> seem likely, but my spidey senses are definitely tingling!
>>>>>>> >>>>>
>>>>>>> >>>>> thx,
>>>>>>> >>>>>
>>>>>>> >>>>> evan
>>>>>>> >>>>>
>>>>>>> >>>>>
>>>>>>> >>>>> "Miha Pihler [MVP]" <mihap-news@xxxxxxxxxxx> wrote in message
>>>>>>> >>>>> news:u8yJvzDtFHA.1216@xxxxxxxxxxxxxxxxxxxxxxx
>>>>>>> >>>>>> Hi,
>>>>>>> >>>>>>
>>>>>>> >>>>>> Is computer member of domain? Did you edit local policy or
>>>>>>> >>>>>> group
>>>>>>> >>>>>> policy?
>>>>>>> >>>>>>
>>>>>>> >>>>>> --
>>>>>>> >>>>>> Mike
>>>>>>> >>>>>> Microsoft MVP - Windows Security
>>>>>>> >>>>>>
>>>>>>> >>>>>> "Evan" <eurkofsky@xxxxxxxxxxxxxxx> wrote in message
>>>>>>> >>>>>> news:uWhKYFAtFHA.1444@xxxxxxxxxxxxxxxxxxxxxxx
>>>>>>> >>>>>>> i think the title says it all. brand new install of w2k3
>>>>>>> >>>>>>> sp1. i'm
>>>>>>> >>>>>>> still getting the tracking box even though it's disabled via
>>>>>>> >>>>>>> gpedit.
>>>>>>> >>>>>>> ideas?
>>>>>>> >>>>>>>
>>>>>>> >>>>>>> thx!
>>>>>>> >>>>>>>
>>>>>>> >>>>>>
>>>>>>> >>>>>>
>>>>>>> >>>>>
>>>>>>> >>>>>
>>>>>>> >>>>
>>>>>>> >>>>
>>>>>>> >>>
>>>>>>> >>>
>>>>>>> >>
>>>>>>> >>
>>>>>>> >
>>>>>>> >
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
.
- Follow-Ups:
- References:
- disabled in gpedit, but shutdown tracker still tracking
- From: Evan
- Re: disabled in gpedit, but shutdown tracker still tracking
- From: Miha Pihler [MVP]
- Re: disabled in gpedit, but shutdown tracker still tracking
- From: Evan
- Re: disabled in gpedit, but shutdown tracker still tracking
- From: Miha Pihler [MVP]
- Re: disabled in gpedit, but shutdown tracker still tracking
- From: Evan
- Re: disabled in gpedit, but shutdown tracker still tracking
- From: Miha Pihler [MVP]
- Re: disabled in gpedit, but shutdown tracker still tracking
- From: Evan
- Re: disabled in gpedit, but shutdown tracker still tracking
- From: Miha Pihler [MVP]
- Re: disabled in gpedit, but shutdown tracker still tracking
- From: Evan
- Re: disabled in gpedit, but shutdown tracker still tracking
- From: Miha Pihler [MVP]
- Re: disabled in gpedit, but shutdown tracker still tracking
- From: Evan
- Re: disabled in gpedit, but shutdown tracker still tracking
- From: Miha Pihler [MVP]
- Re: disabled in gpedit, but shutdown tracker still tracking
- From: Evan
- Re: disabled in gpedit, but shutdown tracker still tracking
- From: Miha Pihler [MVP]
- disabled in gpedit, but shutdown tracker still tracking
- Prev by Date: Re: disabled in gpedit, but shutdown tracker still tracking
- Next by Date: Re: disabled in gpedit, but shutdown tracker still tracking
- Previous by thread: Re: disabled in gpedit, but shutdown tracker still tracking
- Next by thread: Re: disabled in gpedit, but shutdown tracker still tracking
- Index(es):
Relevant Pages
|
Loading