Windows Thread, Creating a Workstation Image in Technical; Hi,
We're in need of some help/advice. We're a small Warwickshire LEA school and due to 'budgetary concerns' we've gone ...
13th August 2008, 12:44 PM #1
Creating a Workstation Image
We're in need of some help/advice. We're a small Warwickshire LEA school and due to 'budgetary concerns' we've gone from the luxury of paying the LEA to do almost everything for us to now having to get off our backsides and do it all ourselves.
We got a small number of new PCs delivered and now we've got to create an image for them.
The instructions given to us by the LEA are:
1. Create Image.
2. Copy NTUSER.DAT from the account used during the image build to ALL USERS.
4. Create Ghost image.
5. Deploy image to PCs.
Now we're happy with 3, 4 and 5 having done this all before many times, but never for our curriculum network as the county engineers used to create our workstation images for us.
We've created an image on one of the PCs which consists of all the software applications that will be needed on them, all updates, and printers and so forth but is there anything else we need to do?
Is it literally a case of copying the NTUSER.DAT files from the account used to create the image to ALL USERS?
Sorry if these are dumb questions but help will be much appreciated! If anyone has a SOP on image creation it would also be much appreciated!
S P D.
13th August 2008, 12:58 PM #2
you will need to run sysprep if you don't want to have issues with SID's (Unique security identifiers)
You can also use this to remove the workstation name so you don't have to remname every pc on boot (post imaging)
There's some good advice here:- Deploying Windows XP
and here: How to use the Sysprep tool to automate successful deployment of Windows XP
Are you using an OEM copy of XP? (Assuming your deploying XP that is) or a volume licence? if OEM EVERY PC will need to be activated via the web or phone. do your master builds using a VL copy if at all possible as this avoids product activation.
Last edited by MGSTech; 13th August 2008 at 12:59 PM.
13th August 2008, 01:04 PM #3
Many thanks for the advice. Yes, it's a VL copy of XP Pro we're deploying.
Originally Posted by MGSTech
13th August 2008, 01:10 PM #4
Seeing as you're using a VLK, you should create a folder C:\Sysprep copy all sysprep components in here and create an answer file. It's quite straight forward to follow. When Mini Setup runs (when you restart the workstation after imaging), C:\Sysprep will automatically be deleted (which is very convenient).
As for NTUSER.DAT your authority have included this as presumably you're using local profiles and not roaming profiles. I personally would recommend roaming profiles however!
13th August 2008, 03:51 PM #5
Make sure you use the correct Sysprep as MS changed it with each Service pack!
You can extract sysprep and its associated files from the deploy.cab in the support tools folder of the XP CD
If you edit the sysprep.inf file after you have run the manager, you can delete the computer name, this way each workstation will ask for a name before it joins the domain.
As Michael pointed out if you expand Deploy.cab to C:\Sysprep it will delete the folder as part of running. If you expand it anywhere else it will leave it complete with unenencrypted passwords in the inf file!
Do remember to select sysprep build when running setup manager or you'll undo all your hard work by installing a base image of XP
it may also be worth running a pre sysprep image as its not unknown for sysprep to hang and leave your master build non-functional.(Speaking from experience here!)
Last Post: 14th January 2008, 12:39 AM
By sLiDeR in forum Windows
Last Post: 6th January 2008, 10:53 PM
By Danielstaunton in forum Learning Network Manager
Last Post: 16th September 2007, 06:33 PM
By sLiDeR in forum Windows
Last Post: 17th August 2007, 10:59 AM
By ninjabeaver in forum Windows
Last Post: 14th July 2005, 11:33 PM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)