gzande
asked on
Clone NT workstation with GHOST
In my organisation we are planning to install 130 PC's with
NT workstation 4.0. These PC's also must contain several office applications, like Lotus SmartSuite, Client Access for Win95/NT, virusscanning (Innoculan), CD-applications etc.
We want to setup 1 PC with these applications and then ´Clone´ this PC with GHOST or some other application.
Is this possible? I have heard that there is a possible
difficulty with de SID of the "Master" PC.
NT workstation 4.0. These PC's also must contain several office applications, like Lotus SmartSuite, Client Access for Win95/NT, virusscanning (Innoculan), CD-applications etc.
We want to setup 1 PC with these applications and then ´Clone´ this PC with GHOST or some other application.
Is this possible? I have heard that there is a possible
difficulty with de SID of the "Master" PC.
ASKER
The PC´s HW is identical.
After we setup the first PC ("master PC") we deliver the image to the distributer.
The distributer then pre-load´s the PC´s with the "image" from the "master PC", so there is no possibility to connect the PC´s to our network.
After we setup the first PC ("master PC") we deliver the image to the distributer.
The distributer then pre-load´s the PC´s with the "image" from the "master PC", so there is no possibility to connect the PC´s to our network.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I don't know what was wrong with ghinstek's answer?
Gzande, if you HW is identical, you're right, it's possible.
I'm actually doing it with 30 Workstations.
But you'll have to install your first station (the one that
will be ghosted) out of your network. So you'll have
a "personal" domain (like "temp"). then ghost it.
When connecting each of them on your network, you just have to do the following:
Log on with your personal domain name (temp)
change the station 's IP adress
Change the station 's name
Change your network domain to a workgroup (like 'dummy' )
choose OK
change your network back to your real domain and choose
create an account --> administrator (with its passwd).
Don't forget to allow your station on your real domain.
Regards, Jacoby
I'm actually doing it with 30 Workstations.
But you'll have to install your first station (the one that
will be ghosted) out of your network. So you'll have
a "personal" domain (like "temp"). then ghost it.
When connecting each of them on your network, you just have to do the following:
Log on with your personal domain name (temp)
change the station 's IP adress
Change the station 's name
Change your network domain to a workgroup (like 'dummy' )
choose OK
change your network back to your real domain and choose
create an account --> administrator (with its passwd).
Don't forget to allow your station on your real domain.
Regards, Jacoby
gzande,
Luckily I am not in here for the points... you reject my answer and then accept the same from someone else ??
Carmine,
No offense taken whatsoever.
Luckily I am not in here for the points... you reject my answer and then accept the same from someone else ??
Carmine,
No offense taken whatsoever.
ASKER
ghinstek,
Sorry that I didn´t understood your answer to my question. This is the first time I used this
web-site.
Is there a posiblity to gif you the 200 points anyway.
Sorry that I didn´t understood your answer to my question. This is the first time I used this
web-site.
Is there a posiblity to gif you the 200 points anyway.
Gzande,
I don't think so, but hey, apology accepted and like I said I'm not in here for the points, so just forget about it... Always glad I can help...
Regards
Koen
I don't think so, but hey, apology accepted and like I said I'm not in here for the points, so just forget about it... Always glad I can help...
Regards
Koen
Manipulating the SID after Ghosting is not supportable by Microsoft if your platform has problems afterward. We studied this option for thousands on NT Workstation and hundreds of NT Server installations. We decided to use the unattended method and create an OEM bootable CD for the client.
Microsoft is offering a machine prep utility for ghosting but you need a current license agreement with them to get it.
Good Luck
Backpack
Microsoft is offering a machine prep utility for ghosting but you need a current license agreement with them to get it.
Good Luck
Backpack
- If the PC are different (HW) I would run unattended setup instead (much more flexible, a little bit more time consuming)
- You have to alter the SID on each PC (You'll find documentation to do that in the deployment guide by MS on their site and also on Technet CD)
I am a consultant to large firms doing mainly migrations and rollouts and have on every occasion considered duplicating disk and have every time rejected it in favour of the unattended setup !