Name Server MasterServerOrAvailabilityGroup RpcClientAccessServer
-- - -
HA-Mailbox-01 EXMB-01 DAG-01 EXCAS-01.italy.local
HA-Mailbox-02 EXMB-01 DAG-01 EXCAS-02.italy.local
Joseph,
Thanks for testing this, but it only shows that you
I expect I'm being premature. It's now using 12+GB of memory.. I'll give it
until Monday before drawing any conclusions.
From: bounce-9494865-8066...@lyris.sunbelt-software.com
[mailto:bounce-9494865-8066...@lyris.sunbelt-software.com] On Behalf Of Sobey,
Richard A
Sent: 08 March 2012 08:45
You can only have one RPCClientAccessServer on a database. That can be a single
CAS, or multiple CASes referenced by the name of a CAS Array.
-Original Message-
From: bounce-9494884-8066...@lyris.sunbelt-software.com
[mailto:bounce-9494884-8066...@lyris.sunbelt-software.com] On Behalf
Yes that is fine. The CAS or CAS array is specified at a Database level, not a
DAG level. You could have 2 CAS arrays access 1 DAG that spans multiple sites.
You could have 1 CAS server for each database if you wanted to.. You could have
lots of DAGs and one CAS array.
Steve
-Original
It seems 2010 OWA is picking up the default domain policy on passwords rather
than the fine grained. So users are getting the banner saying it is about to
expire. We have no real need for people to change their password via OWA, so if
I just turn all of that off with the below does that also
Are you certain that your DFL and FFL have been bumped?
-Original Message-
From: Kennedy, Jim [mailto:kennedy...@elyriaschools.org]
Sent: Thursday, March 08, 2012 9:51 AM
To: MS-Exchange Admin Issues
Subject: 2010 OWA Change Password
It seems 2010 OWA is picking up the default domain
Domain was, Forest was not but it is now. It was just OWA that was popping the
users that it was going to expire yesterday. But when they log in today
directly to a desktop it is not expired, nor should it be. This hit this batch
of users as soon as I moved their mailbox off 07 to 10. However,
I am faced with a similar issue and found the below. However I am not ready to
go there. I am going to continue looking at it. My issue is a bit different
though, Mine have replicated and only the 2007 server thinks it has a
replication for it. No 2010 server thinks that.
I don't care how much Microsoft documentation recommends it, I have never had
anything but trouble with MoveAllReplicas.
I recommend using AddReplicaToPFRecursive, waiting until the replicas have
sync'ed, and then use RemoveReplicaFromPFRecursive.
There have been one or two times when I've HAD
Of course,
How could they allow such a config if the moment you failed one db over it
would error?
That would be total breakage.
From: Jay Kulsh [jayku...@csi.com]
Sent: Thursday, March 08, 2012 3:33 AM
To: MS-Exchange Admin Issues
Subject: RE: DAG and
I got tired of googling and ADSI deleted the offending database and then
decommissioned the server. So far after 30 minutes no problems.
From: Kennedy, Jim [mailto:kennedy...@elyriaschools.org]
Sent: Thursday, March 08, 2012 12:45 PM
To: MS-Exchange Admin Issues
Subject: RE: Exchange 2010
Does the below also apply to getting rid of 2003 replicas after migrating
to 2010?
Thx in advance
On Thu, Mar 8, 2012 at 12:50 PM, Michael B. Smith mich...@smithcons.comwrote:
I don’t care how much Microsoft documentation recommends it, I have
never had anything but trouble with
Are you certain that you are running the most recent release of BES? And I'd
recommend an update to 2010 SP2 UR1.
From: Binner, Lori A [mailto:lbin...@jjkeller.com]
Sent: Thursday, March 08, 2012 2:00 PM
To: MS-Exchange Admin Issues
Subject: BB's keep hard deleting Outlook Contacts
Hello-
We
They can be another kettle of fish.
Compared to Exchange 2010, Exchange 2003 was stupid. It allowed invalid values.
This can cause PF replication to fail and on the Exchange 2010 message for PF
repl messages to end up as poison message. So... you may have to turn off
poison message detection
Michael,
A while back you posted on your blog how to install SP2 for Exchange 2010.
With the addition of UR1, how does that fall into the procedure?
From: Michael B. Smith [mailto:mich...@smithcons.com]
Sent: Thursday, March 08, 2012 2:08 PM
To: MS-Exchange Admin Issues
Subject: RE: BB's keep
Put the update here, replacing the setup.com or setup.exe.
Finally, apply the service pack.
From a cmd.exe prompt:
setup.com /m:upgrade
From setup.exe, simply double-click the setup.exe executable and follow the
bouncing ball.
Next, I recommend a reboot of the server. Just because I'm old
16 matches
Mail list logo
