System Attendant

27 Jun 2009 2:15 PM

Andreas

In a new installation of Exchange 2007 x64, the system Attendant does not
auto-start but it can be started later manually. I found many articles and I
followed Microsoft's recommendations which was:
- Make dependency on the Netlogon service
- Configure it to restart if it fails
- Properly add the server into the Exchange domain servers group
- etc.

Nothing of those makes it start automatically.

I also found that I should disable STP on the switch. Will that help?

btw, one of MS recommendations is to start it manually. It sounds stupid to
me.

27 Jun 2009 4:08 PM

Ed Crowley [MVP]

Although I've never seen that behavior, I fail to understand what the big
deal is. How often do you boot the server? I wouldn't think you'd be doing
that very often? Can't you just make sure that all services are running on
the rare occasions you reboot the server?

Are you running Exchange on a domain controller?

--
Ed Crowley MVP
"There are seldom good technological solutions to behavioral problems."
..

Show quoteHide quote

"Andreas" <ayiangoul***@hotmail.com> wrote in message
news:OqBQRHz9JHA.1492@TK2MSFTNGP03.phx.gbl...
> In a new installation of Exchange 2007 x64, the system Attendant does not
> auto-start but it can be started later manually. I found many articles and
> I followed Microsoft's recommendations which was:
> - Make dependency on the Netlogon service
> - Configure it to restart if it fails
> - Properly add the server into the Exchange domain servers group
> - etc.
>
> Nothing of those makes it start automatically.
>
> I also found that I should disable STP on the switch. Will that help?
>
> btw, one of MS recommendations is to start it manually. It sounds stupid
> to me.

27 Jun 2009 4:30 PM

Andreas

Yes the server is also a dc but only temporarily.It is planned to be
demoted. Could this be the problem?

As far as rebooting is concerned, you have to consider that there are
networks at customer sites were there is no administrator to monitor this
and it is better that all services are started normally.

Show quoteHide quote

"Ed Crowley [MVP]" <curspice@nospam.net> wrote in message
news:eM$OAG09JHA.1252@TK2MSFTNGP04.phx.gbl...
> Although I've never seen that behavior, I fail to understand what the big
> deal is. How often do you boot the server? I wouldn't think you'd be
> doing that very often? Can't you just make sure that all services are
> running on the rare occasions you reboot the server?
>
> Are you running Exchange on a domain controller?
> --
> Ed Crowley MVP
> "There are seldom good technological solutions to behavioral problems."
> .
>
> "Andreas" <ayiangoul***@hotmail.com> wrote in message
> news:OqBQRHz9JHA.1492@TK2MSFTNGP03.phx.gbl...
>> In a new installation of Exchange 2007 x64, the system Attendant does not
>> auto-start but it can be started later manually. I found many articles
>> and I followed Microsoft's recommendations which was:
>> - Make dependency on the Netlogon service
>> - Configure it to restart if it fails
>> - Properly add the server into the Exchange domain servers group
>> - etc.
>>
>> Nothing of those makes it start automatically.
>>
>> I also found that I should disable STP on the switch. Will that help?
>>
>> btw, one of MS recommendations is to start it manually. It sounds stupid
>> to me.
>

28 Jun 2009 4:37 AM

Ed Crowley [MVP]

Yes that's a problem on two fronts. Apparently the Exchange services are
coming up before the DC components are able to service them. Perhaps your
idea of setting a service dependency might solve your problem. But a better
solution is to simply leave the server running and quit shutting it down.

The second problem is that it's unsupported to promote or demote a domain
controller on which Exchange is installed. You will break it, so you can't
demote it. Instead, what you'd need to do is move all the mailboxes, public
folders and connectors to a new Exchange server on a member server.

--
Ed Crowley MVP
"There are seldom good technological solutions to behavioral problems."
..

Show quoteHide quote

"Andreas" <ayiangoul***@hotmail.com> wrote in message
news:ejwVqS09JHA.1488@TK2MSFTNGP03.phx.gbl...
> Yes the server is also a dc but only temporarily.It is planned to be
> demoted. Could this be the problem?
>
> As far as rebooting is concerned, you have to consider that there are
> networks at customer sites were there is no administrator to monitor this
> and it is better that all services are started normally.
>
>
>
> "Ed Crowley [MVP]" <curspice@nospam.net> wrote in message
> news:eM$OAG09JHA.1252@TK2MSFTNGP04.phx.gbl...
>> Although I've never seen that behavior, I fail to understand what the big
>> deal is. How often do you boot the server? I wouldn't think you'd be
>> doing that very often? Can't you just make sure that all services are
>> running on the rare occasions you reboot the server?
>>
>> Are you running Exchange on a domain controller?
>> --
>> Ed Crowley MVP
>> "There are seldom good technological solutions to behavioral problems."
>> .
>>
>> "Andreas" <ayiangoul***@hotmail.com> wrote in message
>> news:OqBQRHz9JHA.1492@TK2MSFTNGP03.phx.gbl...
>>> In a new installation of Exchange 2007 x64, the system Attendant does
>>> not auto-start but it can be started later manually. I found many
>>> articles and I followed Microsoft's recommendations which was:
>>> - Make dependency on the Netlogon service
>>> - Configure it to restart if it fails
>>> - Properly add the server into the Exchange domain servers group
>>> - etc.
>>>
>>> Nothing of those makes it start automatically.
>>>
>>> I also found that I should disable STP on the switch. Will that help?
>>>
>>> btw, one of MS recommendations is to start it manually. It sounds stupid
>>> to me.
>>
>