Re: Exchange Mixed Mode ??

From: Susan Bradley, [SBS Community Member] (sbradcpa_at_pacbell.net)
Date: 09/29/04 

Date: Wed, 29 Sep 2004 11:59:42 -0700

But then you can also get the client that knows more about a SBS box
than the consultant they've hired ;-)

Actually the only reason mixed is there is to aid in migration up. If
you have no 2k/nt boxes of Exchange [we don't] Jeff [the other Jeff]
flips it to native all the time. It's just there for the migration
process [better security too]

I'm not saying that you want to do anything without thought, but in
reality if you have a good backup and image, you can get yourself back
to where you were. This is true in patching as well.

And this client documents and knows what she's changed on a system. ;-)
Used to tick me off no end when a consultant would come in, ask for the
admin password and then build themselves a backdoor admin account and
not tell me they did that. [Like I'm not going to notice a new account?
  Gimme a break] Educate the client but respect them too. Not all of
us are untrainable. ;-)

Jeff L wrote:
> KIK,
>
> The other mode is native mode. If you are a cautious administrator you would
> leave it because there are few advantages that you will ever notice. However
> since you do not have any Exchange 2000 machines there is no reason not to
> change it. Choice is yours.
>
> As an aside, generally I suggest you not click around and if you were my
> client I would give you a severe warning. Basically my clients who try to
> fix things on their own I counsel to look for new support. There is a reason
> a professional considers what they do and then document it as the go through
> the process. Clients do not document. They do not remember what they have
> done and they have probably clicked twenty or thirty features for no reason
> besides curiosity. Then they wonder why you can't figure out what is going
> on in five minutes. Your server is a shared business resource and not a
> testing ground for your curiosity.
>
> Do yourself a big favour and don't touch your server without a good reason.
> So all in all I would say you excercised good judgement in canceling out.
> Good move, congratulations.
>
> Regards,
> Jeff Loucks
> Available Technology ®
> Solutions For Professionals ®
> www.availabletechnology.com
>
>
>
> <anonymous@discussions.microsoft.com> wrote in message
> news:178b01c4a638$2667e920$a601280a@phx.gbl...
>
>>While poking around Exchange on a SBS2003 setup I found a
>>tab that indicated Exchange was in "Mixed Mode", and
>>allowed me to change it.
>>It indicated it is a one way change, so I canceled out.
>>
>>But briefly what is the difference between Mixed and ??
>>(Sorry I don't remember the other option) ??
>>
>>My network is SBS2003, on Win2003 Server and all XP Pro
>>workstations.
>>
>>Should I change it ?
>>
>>Does it really matter ?
>>
>>KlK, MCSE
>
>
> 

-- 
http://www.sbslinks.com/really.htm
http://www.msmvps.com/bradley
http://www.threatcode.com
[let's get vendors to step up to the plate too]
https://www.ecora.com/ecora/jump/pm99.asp

Relevant Pages

  • Re: Holub on getters/setters again
    ... There is, as far as I can see, no reason to have the ArrayList at ... >>before the client that uses it was written. ... And I knew I wanted to call foreach on it from the very beginning, ... whether the element already exists in that container. ...
    (comp.object)
  • Re: Holub on getters/setters again
    ... >before the client that uses it was written. ... When the servers implementation is running the show, ... And I knew I wanted to call foreach on it from the very beginning, ... The reason that I didn't implement foreach was that it is slightly tricky, ...
    (comp.object)
  • Re: Silly question of the day #2: Hosted e-mail vs. Exchange on SBS2003
    ... My second reason depends on the hosting company. ... When I last had hosted e-mail, the hosting company had an aggressive and undocumented spam control plan that caused me a lot of problems. ... why would it be a better idea to leave the e-mail with the current hosting company vs. moving to Exchange 2003 SP2 when we are moving a client to SBS2003? ... They are using various Clients (he does not know what they use...he *thinks* they use the web mail "client" provided by the Hosting Company) to access e-mail remotely. ...
    (microsoft.public.windows.server.sbs)
  • Re: Killing threads
    ... >>>the proces of serving a client for any reason, ... The server thread actually forks new ... > recover a thread that is taking too long for whatever reason. ...
    (comp.programming.threads)
  • Re: Exchange Mixed Mode ??
    ... the server unless I tell them to. ... >And this client documents and knows what she's changed ... >Jeff L wrote: ... is no reason not to ...
    (microsoft.public.windows.server.sbs)