We are using RIS here to deploy Windows XP images. It does work quite

One thing to note is that a warning is put in place if the process
detects multiple profiles, so it may not work as anticipated (I have not
tried it).

There are other issues if you get into it, but I find them to be minor.

|            Michael Surato                 |
|      Resource Center for Persons          |
|           with Disabilities               |
|      Michigan State University            |
|            120 Bessey Hall                |
|        East Lansing, MI 48824             |
| Voice: (517) 353-9643 Fax: (517) 432-3191 |
|      E-mail: [log in to unmask]        |

-----Original Message-----
From: Matthew C. Jackson [mailto:[log in to unmask]]
Sent: Thursday, October 02, 2003 12:37 PM
To: [log in to unmask]
Subject: Re: Problem with Profiles on Cloned Computer

I'm curious if anyone out there has any experience using the Microsoft
Remote Installation Services (RIS). in Microsoft(r) Windows(r) 2000.
Sounds like it could be used instead of Ghost.

According to Microsoft website...

IHVs, ISVs, and OEMs who create tools that help network administrators
and end users perform tasks such as system BIOS updates, standalone
system diagnosis, and virus scanning and repair can use the Remote
Installation Services (RIS) in Microsoft(r) Windows(r) 2000 to provide
an independent setup routine that is executed on the RIS Server. RIS
provides a centralized location to integrate maintenance and
troubleshooting tools that are accessible through a network boot.

RIS provides network administrators with the capability to easily
install the base operating system onto a new PC or to replace a system
that has failed. RIS allows the administrator to do these things without
ever having to visit the individual machine.

RIS enables remote installation of Windows 2000 Professional through
server-side image management capabilities. No hardware-specific images
for clients are required: Plug and Play is used to detect client
hardware during Windows 2000 Professional Setup. The operating system
and machine can be recovered in the event of a system failure; this
provides the ability to boot and operate in a "disconnected" state and
to support security after the operating system has booted.


Matthew C. Jackson
MEC Operations Supervisor

Email:    [log in to unmask]
Phone:  (248) 879-2456
Fax:       (248) 879-6125
----- Original Message -----
From: "Margaret Wilson" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Thursday, October 02, 2003 12:07 PM
Subject: Re: Problem with Profiles on Cloned Computer

> Consensus in my shop is that you must use the latest version of
> Sysprep
> works with XP.  Denyson Figueiredo is the Ghost image expert.  He's
> been rolling out XP for sometime now.  ([log in to unmask])
> Margaret
> --
> Margaret Wilson, MCSE
> Manager
> College of Human Medicine Information Systems
> Michigan State University
> 517.355.1839
> ----- Original Message -----
> From: "Chris Wolf" <[log in to unmask]>
> To: <[log in to unmask]>
> Sent: Thursday, October 02, 2003 11:36 AM
> Subject: Problem with Profiles on Cloned Computer
> > We have been using Ghost for years to clone Windows master-setup
> > images onto other identical hardware.  In the last month we've
> > started to run
> into
> > a problem we haven't seen before, and I'm hoping someone can shed
> > some light on this.
> >
> > When we put one of our master images onto a new machine, we use
> > Ghost Walker to change the SID.  We do not use SYSPREP.  This used
> > to work
> > with no glitches.  Now after we run Ghost Walker and then restart
> > and log on as administrator, Windows seems to lose track of the
> > profile
> for
> > the administrator and creates a new one (C:\Documents and
> > Settings\administrator.computername).  Similarly, when we log on as
> > a domain user that already has a profile on that computer, it
> > creates a
> > profile (C:\Documents and Settings\domainuser.domain) instead of
> > using
> > existing one.
> >
> > We've tried all sorts of different sequences and ways of changing
> > the
> > changing the computer name, changing domain membership, etc., and we
> cannot
> > get it to not create a new profile.  This has happened with two
> > Windows XP images now, even though we know that we have successfully
> > one of those exact images previously on identical hardware without
> > the extra profiles.
> >
> > Can anyone tell me why this is happening and how to  avoid it?
> > Thanks.
> >
> > --Chris
> > ==============================================
> > Chris Wolf                    Computer Service Manager
> > Agricultural Economics        [log in to unmask]
> > Michigan State University     517 353-5017
> >