Consequences of deleting DEFAULTIPSITELINK?

[NATD]

Hi,

To date, we have only had AD at a single site, and the
NTDS connections were created automatically.

While putting in our first server at a remote site, we
accidentally deleted the DEFAULTIPSITELINK but after
creating a new IP site link everything seems to work, and
replica monitor shows things as healthy. NTDS connections
still automatically created.

We are debating whether it is fine to leave things as it
is (my feeling) or that we MUST restore from backup that
old object (which I'm arguing is unnecessary).

Is the inter-site transport link that I created manually
any different than the default one?

I'm happy to manually create site links (we aren't very
big and topology changes will be rare). If we had the
DEFAULT one back, would it automate anything and save us
some admin down the track?

I'm REALLY hoping to get some firm guidance one way or the
other!

Thanks for reading,

NATD.

 

[Mark Renoden [MSFT]]

Hi

To my knowledge, there's no reason to restore the DEFAULTIPSITELINK. As
long as you have a Site Link, you should be OK.

Kind regards
--
Mark Renoden [MSFT]
Windows Platform Support Team
Email: (e-mail address removed)

Please note you'll need to strip ".online" from my email address to email
me; I'll post a response back to the group.

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[NATD]

Thanks for the reply. That is what I wanted to hear but
can I just ask you to address one specific point;

Is the DEFAULTIPSITELINK and different to a link I create
myself (assuming I set the same properties of course)? Ie
does it have any magic powers that once deleted stop some
automatic functionality?

One of us here is concerned that that DEFAULT object was
critical to the KCC doing it's job properly - hence the
insistance that we must restore that particular object.

Can you say that is not the case with some certainty? That
in turn gives me the confidence to say 'we aren't
restoring it!'

I'm an eDir guy - I have to be careful when insisting on
actions or inactions on AD!!!!

-----Original Message-----
Hi

To my knowledge, there's no reason to restore the DEFAULTIPSITELINK. As
long as you have a Site Link, you should be OK.

Kind regards
--
Mark Renoden [MSFT]
Windows Platform Support Team
Email: (e-mail address removed)

Please note you'll need to strip ".online" from my email address to email
me; I'll post a response back to the group.

This posting is provided "AS IS" with no warranties, and confers no rights.

Hi,

To date, we have only had AD at a single site, and the
NTDS connections were created automatically.

While putting in our first server at a remote site, we
accidentally deleted the DEFAULTIPSITELINK but after
creating a new IP site link everything seems to work, and
replica monitor shows things as healthy. NTDS connections
still automatically created.

We are debating whether it is fine to leave things as it
is (my feeling) or that we MUST restore from backup that
old object (which I'm arguing is unnecessary).

Is the inter-site transport link that I created manually
any different than the default one?

I'm happy to manually create site links (we aren't very
big and topology changes will be rare). If we had the
DEFAULT one back, would it automate anything and save us
some admin down the track?

I'm REALLY hoping to get some firm guidance one way or the
other!

Thanks for reading,

NATD.

.

 

[Mark Renoden [MSFT]]

Hi

I'm pretty sure (not totally confident) that there's nothing special about
this. As long as each Site in your AD is associated with a Site Link
object, the KCC should be able to do it's thing.

Kind regards
--
Mark Renoden [MSFT]
Windows Platform Support Team
Email: (e-mail address removed)

Please note you'll need to strip ".online" from my email address to email
me; I'll post a response back to the group.

This posting is provided "AS IS" with no warranties, and confers no rights.

Thanks for the reply. That is what I wanted to hear but
can I just ask you to address one specific point;

Is the DEFAULTIPSITELINK and different to a link I create
myself (assuming I set the same properties of course)? Ie
does it have any magic powers that once deleted stop some
automatic functionality?

One of us here is concerned that that DEFAULT object was
critical to the KCC doing it's job properly - hence the
insistance that we must restore that particular object.

Can you say that is not the case with some certainty? That
in turn gives me the confidence to say 'we aren't
restoring it!'

I'm an eDir guy - I have to be careful when insisting on
actions or inactions on AD!!!!

-----Original Message-----
Hi

To my knowledge, there's no reason to restore the DEFAULTIPSITELINK. As
long as you have a Site Link, you should be OK.

Kind regards
--
Mark Renoden [MSFT]
Windows Platform Support Team
Email: (e-mail address removed)

Please note you'll need to strip ".online" from my email address to email
me; I'll post a response back to the group.

This posting is provided "AS IS" with no warranties, and confers no rights.

Hi,

To date, we have only had AD at a single site, and the
NTDS connections were created automatically.

While putting in our first server at a remote site, we
accidentally deleted the DEFAULTIPSITELINK but after
creating a new IP site link everything seems to work, and
replica monitor shows things as healthy. NTDS connections
still automatically created.

We are debating whether it is fine to leave things as it
is (my feeling) or that we MUST restore from backup that
old object (which I'm arguing is unnecessary).

Is the inter-site transport link that I created manually
any different than the default one?

I'm happy to manually create site links (we aren't very
big and topology changes will be rare). If we had the
DEFAULT one back, would it automate anything and save us
some admin down the track?

I'm REALLY hoping to get some firm guidance one way or the
other!

Thanks for reading,

NATD.

.