Duplicating Workstation on Network

I recently purchased another computer for a second
workstation. Both computers are the same make and model
(Compaq) both come with XP Professional they will be on
a Windows Server network with 6 other computers and the
Server.

The first workstation has been up and running for
several months. It has a number of programs which I will
need to be set up exactly the same way on the second
computer.

Installing XP pro and the 5 programs I use will take
hours as database programs use Mapped drives and the
Borland BDE which requires duplicating . Cloning the
image (with Acronis True Image) to the second computer
would only take 6 minutes. I would obviously change the
computer name on the second machine when the image is
restored. Are there problems with doing this on a
Windows Server network?

Do I need to run Sysprep on the first machine before
cloning (ie change the SID)?

If so which parameter do I use for Sysprep?

Thanks

--
jerry

In news:(E-Mail Removed) om,
Gerald Fay <gejfay___remove___@comcast.net> typed:
> I recently purchased another computer for a second
> workstation. Both computers are the same make and model
> (Compaq) both come with XP Professional they will be on
> a Windows Server network with 6 other computers and the
> Server.
>
> The first workstation has been up and running for
> several months. It has a number of programs which I will
> need to be set up exactly the same way on the second
> computer.
>
> Installing XP pro and the 5 programs I use will take
> hours as database programs use Mapped drives and the
> Borland BDE which requires duplicating . Cloning the
> image (with Acronis True Image) to the second computer
> would only take 6 minutes. I would obviously change the
> computer name on the second machine when the image is
> restored. Are there problems with doing this on a
> Windows Server network?
>
> Do I need to run Sysprep on the first machine before
> cloning (ie change the SID)?
>
> If so which parameter do I use for Sysprep?
>
> Thanks

From Acronis' website:

http://www.acronis.com/homecomputing...ge/faq.html#17

Was looking for Sysprep on the computers, but these are
Compaq and XP installation is for these machines only.
Now at least I have sysprep.

One problem is that the systems only come with a restore
disk, there is no XP serial number.

I may in fact just do an Acronis restore, rename the
computer, then join the Domain

In article <(E-Mail Removed)>,
(E-Mail Removed) hoo.co
m says...
>
>
> In news:(E-Mail Removed) om,
> Gerald Fay <gejfay___remove___@comcast.net> typed:
> > I recently purchased another computer for a second
> > workstation. Both computers are the same make and model
> > (Compaq) both come with XP Professional they will be on
> > a Windows Server network with 6 other computers and the
> > Server.
> >
> > The first workstation has been up and running for
> > several months. It has a number of programs which I will
> > need to be set up exactly the same way on the second
> > computer.
> >
> > Installing XP pro and the 5 programs I use will take
> > hours as database programs use Mapped drives and the
> > Borland BDE which requires duplicating . Cloning the
> > image (with Acronis True Image) to the second computer
> > would only take 6 minutes. I would obviously change the
> > computer name on the second machine when the image is
> > restored. Are there problems with doing this on a
> > Windows Server network?
> >
> > Do I need to run Sysprep on the first machine before
> > cloning (ie change the SID)?
> >
> > If so which parameter do I use for Sysprep?
> >
> > Thanks
>
> From Acronis' website:
>
> http://www.acronis.com/homecomputing...ge/faq.html#17
>
>
>
>

--
jerry

In news:(E-Mail Removed) m,
Gerald Fay <gejfay___remove___@comcast.net> typed:
> Was looking for Sysprep on the computers, but these are
> Compaq and XP installation is for these machines only.
> Now at least I have sysprep.
>
> One problem is that the systems only come with a restore
> disk, there is no XP serial number.

There has to be one ...not even on a sticker on the chassis?
>
> I may in fact just do an Acronis restore, rename the
> computer, then join the Domain

For one computer, I'd do the same. Just remember to disjoin the computer
from the domain before taking the image. ;-)
>
> In article <(E-Mail Removed)>,
> (E-Mail Removed) hoo.co
> m says...
>>
>>
>> In news:(E-Mail Removed) om,
>> Gerald Fay <gejfay___remove___@comcast.net> typed:
>>> I recently purchased another computer for a second
>>> workstation. Both computers are the same make and model
>>> (Compaq) both come with XP Professional they will be on
>>> a Windows Server network with 6 other computers and the
>>> Server.
>>>
>>> The first workstation has been up and running for
>>> several months. It has a number of programs which I will
>>> need to be set up exactly the same way on the second
>>> computer.
>>>
>>> Installing XP pro and the 5 programs I use will take
>>> hours as database programs use Mapped drives and the
>>> Borland BDE which requires duplicating . Cloning the
>>> image (with Acronis True Image) to the second computer
>>> would only take 6 minutes. I would obviously change the
>>> computer name on the second machine when the image is
>>> restored. Are there problems with doing this on a
>>> Windows Server network?
>>>
>>> Do I need to run Sysprep on the first machine before
>>> cloning (ie change the SID)?
>>>
>>> If so which parameter do I use for Sysprep?
>>>
>>> Thanks
>>
>> From Acronis' website:
>>
>> http://www.acronis.com/homecomputing...ge/faq.html#17

Yes there is a serial number on the chassis.

I created, then restored the image to the new computer.
Turned off the first computer, booted the second,
renamed the computer and had it join a "workgroup", then
had it rejoin the domain with the new name.

Worked like a charm. Took 8 minutes from start to
finish. Would have taken hours to install XP and all the
software I needed

Thanks


In article <u#(E-Mail Removed)>,
(E-Mail Removed) hoo.co
m says...
>
>
> In news:(E-Mail Removed) m,
> Gerald Fay <gejfay___remove___@comcast.net> typed:
> > Was looking for Sysprep on the computers, but these are
> > Compaq and XP installation is for these machines only.
> > Now at least I have sysprep.
> >
> > One problem is that the systems only come with a restore
> > disk, there is no XP serial number.
>
> There has to be one ...not even on a sticker on the chassis?
> >
> > I may in fact just do an Acronis restore, rename the
> > computer, then join the Domain
>
> For one computer, I'd do the same. Just remember to disjoin the computer
> from the domain before taking the image. ;-)
> >
> > In article <(E-Mail Removed)>,
> > (E-Mail Removed) hoo.co
> > m says...
> >>
> >>
> >> In news:(E-Mail Removed) om,
> >> Gerald Fay <gejfay___remove___@comcast.net> typed:
> >>> I recently purchased another computer for a second
> >>> workstation. Both computers are the same make and model
> >>> (Compaq) both come with XP Professional they will be on
> >>> a Windows Server network with 6 other computers and the
> >>> Server.
> >>>
> >>> The first workstation has been up and running for
> >>> several months. It has a number of programs which I will
> >>> need to be set up exactly the same way on the second
> >>> computer.
> >>>
> >>> Installing XP pro and the 5 programs I use will take
> >>> hours as database programs use Mapped drives and the
> >>> Borland BDE which requires duplicating . Cloning the
> >>> image (with Acronis True Image) to the second computer
> >>> would only take 6 minutes. I would obviously change the
> >>> computer name on the second machine when the image is
> >>> restored. Are there problems with doing this on a
> >>> Windows Server network?
> >>>
> >>> Do I need to run Sysprep on the first machine before
> >>> cloning (ie change the SID)?
> >>>
> >>> If so which parameter do I use for Sysprep?

--
jerry

You never changed the SID. You have to alter the SID which takes a special
utility to do that, such as GhostWalker. Machines are idetified by the SID
to each other,..the Name is more for "human consumption".

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/IS...cessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/t...dance/2004.asp
http://www.microsoft.com/isaserver/t...dance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp
-----------------------------------------------------


"Gerald Fay" <gejfay___remove___@comcast.net> wrote in message
news:(E-Mail Removed) om...
> Yes there is a serial number on the chassis.
>
> I created, then restored the image to the new computer.
> Turned off the first computer, booted the second,
> renamed the computer and had it join a "workgroup", then
> had it rejoin the domain with the new name.
>
> Worked like a charm. Took 8 minutes from start to
> finish. Would have taken hours to install XP and all the
> software I needed
>
> Thanks
>
>
> In article <u#(E-Mail Removed)>,
> (E-Mail Removed) hoo.co
> m says...
> >
> >
> > In news:(E-Mail Removed) m,
> > Gerald Fay <gejfay___remove___@comcast.net> typed:
> > > Was looking for Sysprep on the computers, but these are
> > > Compaq and XP installation is for these machines only.
> > > Now at least I have sysprep.
> > >
> > > One problem is that the systems only come with a restore
> > > disk, there is no XP serial number.
> >
> > There has to be one ...not even on a sticker on the chassis?
> > >
> > > I may in fact just do an Acronis restore, rename the
> > > computer, then join the Domain
> >
> > For one computer, I'd do the same. Just remember to disjoin the computer
> > from the domain before taking the image. ;-)
> > >
> > > In article <(E-Mail Removed)>,
> > > (E-Mail Removed) hoo.co
> > > m says...
> > >>
> > >>
> > >> In news:(E-Mail Removed) om,
> > >> Gerald Fay <gejfay___remove___@comcast.net> typed:
> > >>> I recently purchased another computer for a second
> > >>> workstation. Both computers are the same make and model
> > >>> (Compaq) both come with XP Professional they will be on
> > >>> a Windows Server network with 6 other computers and the
> > >>> Server.
> > >>>
> > >>> The first workstation has been up and running for
> > >>> several months. It has a number of programs which I will
> > >>> need to be set up exactly the same way on the second
> > >>> computer.
> > >>>
> > >>> Installing XP pro and the 5 programs I use will take
> > >>> hours as database programs use Mapped drives and the
> > >>> Borland BDE which requires duplicating . Cloning the
> > >>> image (with Acronis True Image) to the second computer
> > >>> would only take 6 minutes. I would obviously change the
> > >>> computer name on the second machine when the image is
> > >>> restored. Are there problems with doing this on a
> > >>> Windows Server network?
> > >>>
> > >>> Do I need to run Sysprep on the first machine before
> > >>> cloning (ie change the SID)?
> > >>>
> > >>> If so which parameter do I use for Sysprep?
>
> --
> jerry

Duplicate SIDs aren't an issue in a Domain-based
environment since domain accounts have SID's based on
the Domain SID. But, according to Microsoft Knowledge
Base article Q162001, "Do Not Disk Duplicate Installed
Versions of Windows NT", in a Workgroup environment
security is based on local account SIDs. Thus, if two
computers have users with the same SID, the Workgroup
will not be able to distinguish between the users. All
resources, including files and Registry keys, that one
user has access to, the other will as well "

In article <epVnog#(E-Mail Removed)>,
"Phillip Windell" <@.> says...
> You never changed the SID. You have to alter the SID which takes a special
> utility to do that, such as GhostWalker. Machines are idetified by the SID
> to each other,..the Name is more for "human consumption".
>
>

Machines still have to join the domain themselves and their SID is involved.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/IS...cessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/t...dance/2004.asp
http://www.microsoft.com/isaserver/t...dance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp
-----------------------------------------------------


"Gerald Fay" <gejfay___remove___@comcast.net> wrote in message
news:(E-Mail Removed) om...
> Duplicate SIDs aren't an issue in a Domain-based
> environment since domain accounts have SID's based on
> the Domain SID. But, according to Microsoft Knowledge
> Base article Q162001, "Do Not Disk Duplicate Installed
> Versions of Windows NT", in a Workgroup environment
> security is based on local account SIDs. Thus, if two
> computers have users with the same SID, the Workgroup
> will not be able to distinguish between the users. All
> resources, including files and Registry keys, that one
> user has access to, the other will as well "
>
> In article <epVnog#(E-Mail Removed)>,
> "Phillip Windell" <@.> says...
> > You never changed the SID. You have to alter the SID which takes a
special
> > utility to do that, such as GhostWalker. Machines are idetified by the
SID
> > to each other,..the Name is more for "human consumption".
> >
> >