|
> who would even think of
ghosting a Server
Heh. Quite a few people actually.
:)
> I have yet to hear anything worth while on why I
should be running sysprep on a workstation in a Domain Environment
The main one in my mind is simply a support thing with
MS. I agree with how bad the info is out there on why people think it needs to
be done. It is easier to do it as you go then to actually really hit a real
problem that does impact you that has you running around your environment doing
it for all machines. So while I myself have mixed feelings on how much it is
needed you will NEVER hear me tell a customer or anyone else they shouldn't do
it.
joe
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Aaron Visser Sent: Friday, January 20, 2006 5:24 PM To: [email protected] Subject: RE: [ActiveDir] AD computer accounts being removed I was referring to
workstations not Servers, who would even think of ghosting a Server? And here is
the bottom line I have been ghosting workstations for several years now at this
site without using Sysprep or anything like it, and it has caused me no
problems, I have yet to hear anything worth while on why I should be running
sysprep on a workstation in a Domain Environment where local login is not
prohibited other than some BS stuff from Wininternals or some other mag like
that. So put your rolled up newspapers away ( unless of course your going to be
using it on yourself ) and give me something worth while or concrete as to why I
should be running Sysprep in the mentioned environment other than NO NO NO NO
BAD BAD BAD BAD you must run sysprep. From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Brian
Desmond Tell
me about it. We had a vendor roll a server into every site to do as they pleased
with. Didn’t get sysprep’ed. Many sites decided to dcpromo theirs up. Of course
every independent domain has to trust me, and you can’t trust more than one
domain with the same sid… From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Lee, Wook You can have collisions
between a domain controller Wook From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of joe Yep sorry, didn't
intend to say it wasn't a good idea. At some point the list will catch up and my
post that says that will show up. :) From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Dozen
other reasons to run it. Not running sysprep is just a bad idea.
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of joe Well not really. The
important If the accounts are
disappearing it is one of two things 1. Someone is deleting
it. 2. During the join
process something fails and the computer deletes the object out. I don't recall
the details of this but I do recall hearing it happen. It happens right after
the failed join though, you don't have to wait for it. I have also heard
other people who don't have enough rights report the account being disabled
instead of deleted. I never verified personally either.
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of NO
NO NO NO NO BAD BAD BAD You
have to use sysprep. You’re getting duplicate SIDs here – bad.
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Aaron
Visser Gary,
Brian, I do not use Sysprep on
my images and have yet to come across any problems, but there may be one big
difference with my images, before I ghost them or create the image I put the
said machine into a workgroup and then create image. After I have imaged a
computer I log on and change the Computer Name reboot and then join the domain
with the new computer name, should I be using Sysprep?
And Brenda I have
experienced your problem but I have never noticed the accounts actually being
out of AD, anyways most times for me a simple reboot works although I have had
to actually ghost computers in order to rejoin the domain because I do not have
any local accounts active on my computers in the school, makes it a little safer
J but with that comes
more work L From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Are
you implying you don’t sysprep your images? From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Garyphold Brenda, FWIW: It happens
to me when I clone a workstation then try to join that workstation to the domain
in order to change the computer name. AD sees 2 machines with the same
name, gives me a notification and lets the 2nd one in. Then when the
original machine with that name logs in next time, it isn't seen on the
network. Then I have to do the same thing you did - with the original
machine. Then all is well again. Don't know if that will
help, but it might narrow down the problem
some. Gary
Polvinale -----Original
Message----- Yes,
their computer account in AD is actually
gone. Thanks,
Brenda Brenda
Casey Billings
Public Schools 406-247-3792 From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Gil
Kirkpatrick When you say "lose
their account", do you mean the computer object in AD disappears? Or something
else? -g From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Brenda
Casey Occasionally
computers will lose their account in Active Directory for no apparent
reason. Sometimes it is a computer that has just joined the domain, while
other times the machine has been a member of the domain for 2 years. The
computer can only be logged on by a local account (not a domain account).
To remedy this, the computer has to be disjoined from the domain, join a
workgroup, then join the domain again. As I am sure you all are aware,
this is not only time consuming, but very inappropriate to have to
do. Has
anyone else had this experience and how have you fixed
it? Thanks,
Brenda |
Title: Message
