Hi, Tim,
In regard to your reply: "Supposing each install of
Windows had all named the
same name for the machine. If he were to boot into
Windows and join each to
the same domain this would reset the machine account each
time. Once that was done if you booted back into the
first install to be joined to
the domain, the secure channel session setup would have
failed as an access
denied. A reset would be required (or a disjoin or
rejoin)."
Why will I get access denied when trying to boot back into
the first install of Windows, after having joined the
second install of Windows to the domain? Is it because AD
notices a a computer with the same PC name but a different
machine account than the second-installed Windows? And AD
requires that a PC name always have one machine account
associated with it?
If I clone a hard drive to a second hard drive, and then
leave the first hard drive offline, will I encounter
problems if I use the the second hard drive in the same
domain as the first hard drive?
Thanks
-----Original Message-----
Joe's correct, each instance needs it's own machine
account (and name).
confers no rights.
might work for a
out of sync.
Services
www.joeware.net
Amir M. wrote:
What if you join the first partition to the domain and
then clone from
this resolve the
wrote in