Re: Where are our computers?

Tech-Archive recommends: Fix windows errors by optimizing your registry

It looks to be an AD Replication problem, not sure at this point but you can
you provide some additional info here:
1.Are the two DCs in the same AD Site?
2.Do you see any errors on either of DCs with respect to AD replication?
3. Can you try creating a user object on DC1 and check if you can see that
on DC2

On the additional exchange tabs that you see, it might be likely that you
either have exchange installed on DC1 or just the exchange snap-in installed
on DC1 and not on DC2.
"Tcs" <someone@xxxxxxxxxxxxx> wrote in message
news:2srh14t0adp7nbq3idppioiohkl5bia5fb@xxxxxxxxxx
I found the computers. They're on DC1. And they're all under
"computers". Not one is on DC2. And I *did* do a lot of looking,
just to be sure.

So now I have a question:

Why wouldn't the computers be replicated to DC2, since all the users
and OUs have been replicated? What's the difference?

Also...this may or may not be related...

My co-worker and I have noticed a difference between DC1 & DC2. If we
pull up the properties of a user on either DC, there is a definite
difference. On DC2, there are three (3) rows of tabs in the property
window. On DC1 there are five (5). The extra two (2) are:

Exchange General, E-mail Addresses
Exchange Features, Exchange Advanced

( We have an Exchange 2003 server. )

When we create a user who will also get an email address, we have to
do so on DC1. I found this out the hard way by having done so on DC2,
and consequently no mailbox.

Is this difference normal? Or have we managed to get it "not quite
right"?

Thanks,

Tom

On Sun, 27 Apr 2008 17:48:03 +0000 (UTC), Meinolf Weber
<meiweb(nospam)@gmx.de> wrote:

Hello Tcs,

On the second DC you can open ADUC and can see the DC, where you are at
the
moment(behind the domain name). If you rightclick it you can switch to the
other DC, no need for logging on to the other DC.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and
confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

I only searched the second DC. I can connect to the first one, but my
co-workers usually connect to that one, when they have a need.
Consequently, I get knocked off. So I just connect to the second one
and don't get knocked off by them.

They're both in the same place. We do have mulitple office locations
around town, but both DCs are in the main office.

I'll try your suggestion tomorrow.

Thanks.

On Sun, 27 Apr 2008 15:04:29 +0000 (UTC), Meinolf Weber
<meiweb(nospam)@gmx.de> wrote:

Hello Tcs,

If you have added computers to AD, you can find them via ADUC and
computername on domain level, if you rightclick and choose find,
change to search for computers, default is users, groups etc. Did you
search on all DC's in your domain?

If you can not them this way, please desscribe your setup, how many
DC's and sites. Maybe there is a replication problem in your domain.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and
confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
This may sound silly, but...I can't find our computers anywhere in
AD. While we did create OUs for keeping track of where they are, we
never created/moved any computers into these OUs as yet. That's
what I'd like to do now but can't. Why not? Because I can't find
them. And I know they're there...SOMEWHERE. I have a script that
reads thru AD and logs what computers exist. But I can't find any
computers anywhere.

Could I impose someone to...enlighten me?

Thanks in advance,

Tom




.

Relevant Pages

  • Re: AD replication
    ... Assuming DC1 for the Root Domain, and DC2 for the child domain: ... NtdsSettings -> all tasks and choose check replication topology, ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD replication not working
    ... If replication is missing over the tombstone lifetime, between 60 and 180 days, it can require a reinstall of one DC. ... At the moment my goal it to try to get DC1 ... DC2; meaning it shows up in AD UC, but is not available to add to NTFS ... The target name used was DOMAIN\DC2$. ...
    (microsoft.public.windows.server.active_directory)
  • AD Replication Questions
    ... to DC2. ... the connection objects. ... Computer: DC1 ... established to ensure that replication continues. ...
    (microsoft.public.win2000.active_directory)
  • Re: Where are our computers?
    ... Are DC1 and DC2 in one domain with the same domain name or different domain names? ... The account problem belongs to the replication problem and you should better stop creating new accounts before not all problems are solved. ... Why wouldn't the computers be replicated to DC2, ...
    (microsoft.public.windows.server.active_directory)
  • Re: Where are our computers?
    ... DC2 "magically" appear...by adjusting the filter. ... Are DC1 and DC2 in one domain with the same domain name or different domain ... The account problem belongs to the replication problem and you should better ... Why wouldn't the computers be replicated to DC2, ...
    (microsoft.public.windows.server.active_directory)