Re: How to remove old Domain

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



Non in either network.

"Mathieu CHATEAU" wrote:

Hello,

any left trust relationship ?

--
Cordialement,
Mathieu CHATEAU
http://lordoftheping.blogspot.com


"Dan" <Dan@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3F15CEB3-4ABF-4D0E-A28F-7A27F865D3A4@xxxxxxxxxxxxxxxx
I am 99% sure they are not tied into our current system. In the beging
they
tried to tie the 2 system into our current AD, however they failed to do
so,
which is why I am stuck with this error. Basically they were new to VOIP
and
couldnt tie into our system so instead of making it work they keep their
system seperate from ours. Currently the unity server is on a domain
called
MICSVM. Basically the domain MICSUNITY doesnt have and DC... they are
long
gone, I was looking for a way to remove it without the DCs.


"Ryan Hanisco" wrote:

Dan,

Before you end up there, you will want to make sure that the phone system
isn't tied to it. If this is Cisco, Unity and Call Manager can be tied
to
it and you might not have a way to pull the domain out of there.

Otherwise, you should be able to just use DCPROMO to demote each DC and
then
turn them off. I would highly suggest that you, get someone to review
your
environment in person and verify that there is nothing tied to it and no
other services that the organization is using.
--
Ryan Hanisco
MCSE, MCTS: SQL 2005, Project+
Chicago, IL

Remember: Marking helpful answers helps everyone find the info they need
quickly.


"Dan" wrote:

I get the following error in all my domain controllers. The MICSUNITY
domain
was a temporary domain some consultants used when implementing out VOIP
system 3-4 years ago. How would I go about removing this domain from
my
network.

----------- Error Message ----------------

This computer was not able to set up a secure session with a domain
controller in domain MICSUNITY due to the following:
There are currently no logon servers available to service the logon
request.
This may lead to authentication problems. Make sure that this computer
is
connected to the network. If the problem persists, please contact your
domain
administrator.

ADDITIONAL INFO
If this computer is a domain controller for the specified domain, it
sets up
the secure session to the primary domain controller emulator in the
specified
domain. Otherwise, this computer sets up the secure session to any
domain
controller in the specified domain.


.



Relevant Pages

  • RE: Strange Irregular DNS/Networking Problems
    ... My network is not a complicated set up and only has one domain controller. ... problems with DNS resolving after changing DNS servers. ... I was already using the server for DHCP. ...
    (microsoft.public.windows.server.dns)
  • Re: IPSec / domain isolation: confusing MS documents
    ... workstation, he is able to attach to server ressources again, but for our ... The user right for access this computer from the network ... will not work for computer accounts unless ipsec is being used. ... securing a domain controller. ...
    (microsoft.public.windows.server.security)
  • RE: Strange Irregular DNS/Networking Problems
    ... Disable offloading in the network adapter properties ... After doing this on the server and the client it seems to have fixed ... Tested with just one client and the domain controller on the ... "Meinolf Weber" wrote: ...
    (microsoft.public.windows.server.dns)
  • RE: Strange Irregular DNS/Networking Problems
    ... "Meinolf Weber" wrote: ... Disable offloading in the network adapter properties ... worse than vista was because chimney offloading was on by default ... Tested with just one client and the domain controller on the ...
    (microsoft.public.windows.server.dns)
  • RE: Strange Irregular DNS/Networking Problems
    ... Disable offloading in the network adapter properties ... After disabling all these things file transfers across the network are a lot ... My network is not a complicated set up and only has one domain controller. ... I tried doing a net stop server after the network stalled as from an article ...
    (microsoft.public.windows.server.dns)