|
| |||||||||
| Tags: 2000, 2003ad, prewindows |
![]() |
| | Thread Tools | Search this Thread |
|
#1
| |||
| |||
| 2003AD server not in AD, "pre-windows 2000 name is already in use"
We are trying to set up Symantec Backup Express before the first of the year. We are stuck. Part of the installation process requires us to choose the machine we are installing the client, (remote agent) to, from the AD computer list. The computer we are installing on IS our AD server, and is not on that list. When we try to add "OURDC" to that list, we get an error: "Windows cannot create the new computer object because the pre-Windows 2000 computer name OURDC is already in use. Select another name, and try again." The computer name for this machine is OURDC. It sure as hell is not a pre-windows 2000 machine. The name DOES exist under Domain Controllers. Any ideas? Phil |
|
#2
| |||
| |||
| Re: 2003AD server not in AD, "pre-windows 2000 name is already in use"
Hello Phil, If i understand you correct you try to install the remote agent on the server where also BE is already installed or should be installed? 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 > We are trying to set up Symantec Backup Express before the first of > the year. > > We are stuck. Part of the installation process requires us to choose > the machine we are installing the client, (remote agent) to, from the > AD > computer list. The computer we are installing on IS our AD server, > and > is not on that list. When we try to add "OURDC" to that list, we get > an > error: > "Windows cannot create the new computer object because the pre-Windows > 2000 computer name OURDC is already in use. Select another name, and > try again." > The computer name for this machine is OURDC. It sure as hell is not a > pre-windows 2000 machine. The name DOES exist under Domain > Controllers. > > Any ideas? > > Phil > |
|
#3
| |||
| |||
| Re: 2003AD server not in AD, "pre-windows 2000 name is already in use"
Hello Phil, Forget to mention that this belongs to the Symantec forums and not Microsoft: http://www.symantec.com/connect/back...ms/backup-exec 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 > We are trying to set up Symantec Backup Express before the first of > the year. > > We are stuck. Part of the installation process requires us to choose > the machine we are installing the client, (remote agent) to, from the > AD > computer list. The computer we are installing on IS our AD server, > and > is not on that list. When we try to add "OURDC" to that list, we get > an > error: > "Windows cannot create the new computer object because the pre-Windows > 2000 computer name OURDC is already in use. Select another name, and > try again." > The computer name for this machine is OURDC. It sure as hell is not a > pre-windows 2000 machine. The name DOES exist under Domain > Controllers. > > Any ideas? > > Phil > |
|
#4
| |||
| |||
| Re: 2003AD server not in AD, "pre-windows 2000 name is already inuse"
You are correct. I will post something on the Symantec forums as well. On 12/30/2009 2:45 PM, Meinolf Weber [MVP-DS] wrote: > Hello Phil, > > If i understand you correct you try to install the remote agent on the > server where also BE is already installed or should be installed? > > 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 > >> We are trying to set up Symantec Backup Express before the first of >> the year. >> >> We are stuck. Part of the installation process requires us to choose >> the machine we are installing the client, (remote agent) to, from the >> AD >> computer list. The computer we are installing on IS our AD server, >> and >> is not on that list. When we try to add "OURDC" to that list, we get >> an >> error: >> "Windows cannot create the new computer object because the pre-Windows >> 2000 computer name OURDC is already in use. Select another name, and >> try again." >> The computer name for this machine is OURDC. It sure as hell is not a >> pre-windows 2000 machine. The name DOES exist under Domain >> Controllers. >> >> Any ideas? >> >> Phil >> > > |
|
#5
| |||
| |||
| Re: 2003AD server not in AD, "pre-windows 2000 name is already inuse"
Hello Phil, The remote agent should only be installed on servers where BE is not installed, if BE itself is installed there is no need for the remote agent. Basically the error says this machine has it installed. 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 > You are correct. I will post something on the Symantec forums as > well. > > On 12/30/2009 2:45 PM, Meinolf Weber [MVP-DS] wrote: > >> Hello Phil, >> >> If i understand you correct you try to install the remote agent on >> the server where also BE is already installed or should be installed? >> >> 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 >>> We are trying to set up Symantec Backup Express before the first of >>> the year. >>> >>> We are stuck. Part of the installation process requires us to choose >>> the machine we are installing the client, (remote agent) to, from >>> the >>> AD >>> computer list. The computer we are installing on IS our AD server, >>> and >>> is not on that list. When we try to add "OURDC" to that list, we get >>> an >>> error: >>> "Windows cannot create the new computer object because the >>> pre-Windows >>> 2000 computer name OURDC is already in use. Select another name, and >>> try again." >>> The computer name for this machine is OURDC. It sure as hell is not >>> a >>> pre-windows 2000 machine. The name DOES exist under Domain >>> Controllers. >>> Any ideas? >>> >>> Phil >>> |
![]() |
|
| Thread Tools | Search this Thread |
| |
Similar Threads for: "2003AD server not in AD, "pre-windows 2000 name is already in use"" | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Domain Controller "status"on new W2K8 server is "not available" | Wolfgang Schlicker | Active Directory | 4 | 13-12-2011 03:03 PM |
| <input type="button" value="Enregistrer" onclick="location.href=../asp/PRaces.asp"> | Luz | Software Development | 6 | 18-05-2010 01:27 AM |
| help: "loader error 3" when booting Windows 2000 | mmo | Window 2000 Help | 4 | 31-12-2009 02:12 PM |
| Has Microsoft recently introduced "Loopback check" functionality in Windows 2000? | Trust No OneŽ | Window 2000 Help | 2 | 22-12-2008 10:12 PM |
| "Easy Transfer" download difficulty (to Windows 2000)... | Nick Clegg | Vista Setup and Install | 6 | 01-03-2007 05:46 AM |