• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 274
  • Last Modified:

PDC name change

I recently took over a very small network from a very shady individual.  Thusly, I have changed all usernames and passwords and changed all computer names except the PDC, which obviously doesn't want to have its name changed.  Anybody know of a way that I can change the name of our PDC (only DC)/file server????

windows 2k server with active directories running.
0
1cell
Asked:
1cell
1 Solution
 
1cellAuthor Commented:
i saw that but it seemed to brief to be helpful;-)

 DCPromo? means before it's promoted to domain controller ay?  any options now? lol, i'm ignorant.
0
 
stevenlewisCommented:
DCPromo? means before it's promoted to domain controller ay
yes. Only one option now, set up another w2k, have it join the domain, promote it, demote the other, and then you can change it's name
0
Configuration Guide and Best Practices

Read the guide to learn how to orchestrate Data ONTAP, create application-consistent backups and enable fast recovery from NetApp storage snapshots. Version 9.5 also contains performance and scalability enhancements to meet the needs of the largest enterprise environments.

 
1cellAuthor Commented:
not worth it I guess.  i'm just anal about security and this network is named far too logically, like the accounting/payroll computer being named ACCOUNTING.  I'll take care of the rest and have to be happy.  I've already shut down every opening to the outside world temporarily.  I'm the only one with internet and I'm sans network straight to the T1!!!  watch how fast this submits!
0
 
andyalderSaggar makers bottom knockerCommented:
It's a good name for the accounts server, why change it?

The more logical the naming convention the better. Obfuscating machine names doesn't improve security, just makes it harder to maintain. If you think it's safer to have silly machine names then advise Microsoft since you can see their naming convention is logical by talking to their mail server:

HELO
220 inet-imc-02.redmond.corp.microsoft.com Microsoft.com ESMTP Server Sat, 13 Jul 2002 06:09:33 -0700
0
 
pjknibbsCommented:
Agree with andyalder--there's a fine line between good security practices and needless paranoia, and giving the machines names which bear no relation to their function just makes it harder for LEGITIMATE users to access them.
0
 
stevenlewisCommented:
That is true, but as my link points out, can't be done
0
 
1cellAuthor Commented:
ok, at this point and for about the next two months, these systems ALL have static ip's to the internet and the management of this company is slightly concerned that the previous, disgruntled admin would feel vengeful.  I figured changing computer names and switching IP's would help to ease that concern.  it's not JUST paranoia;-)

regardless, it can't be done.  or I should say it's not worth the energy required to get it done.

i guess it's worth the fifty points to teach me the "read technet" lesson.
0
 
stevenlewisCommented:
1cell
Wish I had better news for you
Steve
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now