Bleedin Microsoft !!!!!!!!!

  • Thread starter Thread starter andy
  • Start date Start date
A

andy

All DNS AD errors have now been fixed.

Service pack 4 will not allow a DC to talk to a domain
with a single name, ie mydomain.

WHY??????

Two weeks and two server builds because Microsoft
downgraded a service and didn't put big warning signs on
it.

Talk about a tad upset!!!!!!!

Now we have to figure out how to delete a DC from the AD
that was forcibly removed and is no longer present.
 
-----Original Message-----
All DNS AD errors have now been fixed.

Service pack 4 will not allow a DC to talk to a domain
with a single name, ie mydomain.

WHY??????

Two weeks and two server builds because Microsoft
downgraded a service and didn't put big warning signs on
it.

Talk about a tad upset!!!!!!!

Now we have to figure out how to delete a DC from the AD
that was forcibly removed and is no longer present.
.
Click to expand...

Andy,

While I can not speak Microsoft adding / removing
a 'feature' ( it is their perrogative - they write this
stuff! ) I do know that there has been a lot of activity
lately concerning a so-called "single-label" domain, i.e,
MICROSOFT instead or MICROSOFT.COM ( or MICROSOFT.NET or
whatever ).

As to removing a DC from AD that was forceable removed I
can help there. It *should* be somewhat easy. I just
played with this at home in my test lab where I simply
turned off a DC and removed the network cable from the
switch. Simply use NTDSUtil and ADSIEdit and that DC will
be removed from AD. You will also need to get rid of it
from the ADSS MMC ( but I am pretty sure that you can do
that in ADSIEdit as well ) and manually remove some DNS
entries. Furthermore, if you have Exchange 2000 you might
need to change the DC that the RUS reference ( as it
*could* be the DC that was forceable removed! ).

If you would like some assistance I would be happy to
oblige. I can either go from memory or provide you with
some links from the MSKB.

HTH,

Cary

PS...You might want to e-mail me as I might get busy and
forget.....
 
Thanks for all your help Cary,

I managed to remove the server using NTDSutil metadata
cleanup, then a simple delete from AD sites and services.

Just think that when you go to windows update and select
service pack 4 as a automatic course of action, Microsoft
should give a little more warning that it will screw your
network up if you have a single name domain. To think when
we built this third server we nearly updated all to SP4.
The thing is now how do we change the domain without re-
imaging 2000 workstations so we can stay up to date with
sp's, will domain.local work?
 
-----Original Message-----
Thanks for all your help Cary,

I managed to remove the server using NTDSutil metadata
cleanup, then a simple delete from AD sites and services.

Just think that when you go to windows update and select
service pack 4 as a automatic course of action, Microsoft
should give a little more warning that it will screw your
network up if you have a single name domain. To think when
we built this third server we nearly updated all to SP4.
The thing is now how do we change the domain without re-
imaging 2000 workstations so we can stay up to date with
sp's, will domain.local work?

.
Click to expand...

Andy,


I just might have an answer for you on that question as
well!

We have one client for whom we do everything workstation
related with Ghost. My boss creates an image with all of
the applications as well as Service Packs and Critical
Updates and Recommended Updates. As the Updates are
released I then go around and manually update the 35 or so
workstations. Not really the best of solutions. And as
new clients are added to the network ( over time )that
image really proves to be old. Choice is to take that PC
that was used for the original image and update it and
then to update the image on the server! However, that is
a bit tedious and will help only the new workstations.

In short, the answer is SUS! I believe that SUS stands
for Software Update Service. I have not yet had time to
play with it but am going to really soon. The client I
mentioned does not really appreciate me spending five
hours going machine to machine and manually doing this (
it costs them a good chunk of change! ).

Take a look at SUS. If you need some links I can provide
you with some. However, you should be able to go to
http://www.microsoft.com and find sufficient information.
Or, you can do a search in this NG. Herb Martin and I
just had a tiny conversation about SUS a few days ago....

HTH,

Cary
 
Back
Top