...maybe a little late in the day...
I'm assuming that the users are in the Active Directory in which case this
isn't an issue it's by design. Otherwise you'd be having users circumventing
desktop restrictions by finding a machine in another trusted domain.
Perhaps what you should actually be
Hmm maybe I will go check out this joeware stuff you are talking about.
Thanks. :o)
Glad to know I have some positive impact.
Now to figure out how to put a web link on my resume in the section for
references pointing at this list...
joe
-
http://www.joeware.net (download
I wanted to document some stuff I learned this week. We finally have a K3
load with all of the stuff the company wants in it and tested, etc so we
started deploying some K3 domain controllers.
I tested this all out in our Exchange lab of course and it all worked well,
in fact K3 DCs running in
Thanks for the info. As for your second item, I agree whole heartedly on a
need for some more AD data verification tools. That's a nice thing about
Novell's NDS as a dsrepair will show you these types of things and even fix
them most of the time.
-Original Message-
From: [EMAIL
In our environment (60+ sites, 130 DCs, 25k+ users) I've not yet chosen a
bridegehead, and am successful at controlling where my replication takes
place by carefully choosing through AD Sites and Services the site that a
specific set of servers can talk to - or, a server to server by defining the
thanks Joe for the heads up - haven't had this one myself, however, I wonder
what you're using to day to monitor replication of your AD? I suspect you'd
have had similar replication issues with the european partition all along -
no?
Or was the bad data on a multivalued attribute of a printer
I forgot to mention the two KBs pointing out the issue with E2K and LVR:
http://support.microsoft.com/default.aspx?scid=kb;en-us;831809
(Exchange 2000 Recipient Update Service does not replicate changes
successfully in forest functional level 1 or 2 in Windows Server 2003 Active
Directory)
and
