RIS and Sids

[Lurch]

For testing some of our products it requires a clean installation of the OS.
To do this the group is currently using Drive Image. We are running into the
problem where the PC is imaged and when it boots it can not connect to the
domain controller. This happens because the Computer object already exsists
in the AD, but the SID does not match.

Instead of calling us 3 or 4x a day, will RIS solve this?

 

[NIC Student]

We use RIS to deploy test-bed images, which are then quickly mucked up and
reimaged. The best thing at that point is to have the machine pulled off
the domain before reimaging. Even if the users don't do that, you can still
RIS the machine - you are reminded that several computer accounts already
exist for that GUID.

--
Scott Baldridge
Windows Server MVP, MCSE


"Lurch"

 

[Daniel Chang [MSFT]]

If sysprep is not an option, you may be able to use RIS to deploy the
system, or use a bootable floppy to do an unattended install from a network
share.

--
--
Daniel Chang
Server Setup Team

Search our Knowledge Base at http://support.microsoft.com/directory
Visit the Windows 2000 Homepage at
http://www.microsoft.com/windows2000/default.asp
See the Windows NT Homepage at http://www.microsoft.com/ntserver/

NOTE: Please reply to the newsgroup and not directly to me. This allows
others to add to and benefit from these threads and also helps to ensure a
more timely response. Thank you!
This posting is provided "AS IS" without warranty either expressed or
implied, including, but not limited to, the implied warranties of
merchantability or fitness for a particular purpose.
The views and opinions expressed in this newsgroup posting are mine and do
not necessarily express or reflect the views and / or opinions of Microsoft.


: For testing some of our products it requires a clean installation of the
OS.
: To do this the group is currently using Drive Image. We are running into
the
: problem where the PC is imaged and when it boots it can not connect to the
: domain controller. This happens because the Computer object already
exsists
: in the AD, but the SID does not match.
:
: Instead of calling us 3 or 4x a day, will RIS solve this?
:
:
:

 

[Tim Willingham]

We use Ghost, but to avoid this problem, we don't join the domain until
after the imaging operation.

 

[andrew p]

I've never ran into the SID problem and I've "imaged" the same PCs multiple
times with RIS and RIPrep. I'm only doing tests in a lab environment,
though.