Effective December 3, NetApp adopts Microsoft’s Business-to-Customer (B2C) identity management to simplify and provide secure access to NetApp resources.
For accounts that did not pre-register (prior to Dec 3), access to your NetApp data may take up to 1 hour as your legacy NSS ID is synchronized to the new B2C identity.
To learn more, read the FAQ and watch the video.
Need assistance? Complete this form and select “Registration Issue” as the Feedback Category.

ONTAP Discussions

cifs domain discovered-servers show, how to remove one of listed DC servers

netappmagic

When I run " cifs domain discovered-servers show", I got the list of DC servers, one of them is no longer available, and I want to remove it.

 

Can anybody please let me nkow what command to remove it?

 

It is on cDOT 8.2

 

Thank you!

 

 

4 REPLIES 4

mbeattie

Hi,

 

Have you performed a metadata cleanup on the domain controller to remove it from Active Directory? If not in the interim you can set the preferred DC to one in the AD site that is available. EG


cluster1> active-directory preferred-dc add -vserver vserver1 -domain testlab.local -preferred-dc 192.168.100.10
  (vserver active-directory preferred-dc add)

 

/matt

If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.

netappmagic

Hi there,

 

I already have had / added multiple DC servers, the issue is not how to add more.

 

I wanted to remove that one from the list on the storage, since it is no longer availbe.

 

What should AD admin exactly do to remove it from AD, I am not so familiar with AD.

 

Thanks a lot!

AdvUniMD

You probably need to remove it from WINS manually (if you have WINS configured), which is a bit of a PITA since you have to delete the domain's entry on all WINS servers at the same time and wait for the DCs to repopulate it with the correct list of DCs.

 

On the AD side your AD admin should have used dcpromo.exe (or the new, fancy GUI variant thereof) to remove the DC from the AD

mbeattie

Hi,

 

The suggestion to use preferred domain controllers is just to ensure your vserver doesn't attempt to contact the failed domain controller. EG

 

cluster1> active-directory preferred-dc add -vserver vserver1 -domain testlab.local -preferred-dc 192.168.100.10

 

To resolve your issues, first i would recommend you perform a metadata clean in Active Directory to remove the failed domain controller (if you haven't already done so):

 

https://technet.microsoft.com/en-us/library/cc816907%28WS.10%29.aspx

 

Then you can run the following command to rediscovered the domain controllers in the AD site for the vserver:

 

cluster1> active-directory discovered-servers reset-servers -vserver vserver1

Hope this helps?

 

/matt

If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.
Announcements
NetApp on Discord Image

We're on Discord, are you?

Live Chat, Watch Parties, and More!

Explore Banner

Meet Explore, NetApp’s digital sales platform

Engage digitally throughout the sales process, from product discovery to configuration, and handle all your post-purchase needs.

NetApp Insights to Action
I2A Banner
Public