Deploying an Outlook Setup

[Migration User]

Hi,

 

I am trying to use Ghost Console V8.2.0.1117 to manage the builds of machines for our teaching lab. All the machines are Dell Poweredge 840 servers running Windows 2003 Server SP2.

 

First up, some background (this is relevant, honest!). I work for a company in our education department providing training to both internal staff and our customers on our range of products. The product runs on Windows 2003 Server and each student is given a Poweredge server for the duration of the course. These servers are named ServerXX where XX is the seat number of the student in question. The classoom has its own domain which has the servers in it and also some "back room" machines running things like Exchange and Ghost (and a PDC). Each stdent also has a domain account with the generic name StudentXX.

 

Ok, now our product relies on Outlokk (2000 at the moment) being configured on the server prior to being installed (in actual fact, it needs the profile set up). However some of the courses deal with the installation of the product and therefore creating the profile is part of an exercise. Other courses start with a functioning system and therefore the profile needs to be there.

 

For various reasons, I want to keep the number of actual images to a minimum (disk space and also maintenance when SPs come out and the like).

 

At the core of my question is, "How can I roll out the Outlook profiles"? I have tried various things so far, but run into various issues, which someone might be able to help me with..

1. I tried doing it the "Microsoft way". This simply din't work. Did it all by the book, but still when I crank up Outlook I get the wizard starting asking me for server name etc.
2. I tried Imaging the Outlook setup using AI but as each server needs a different user set up, this didn't work.
3. My latest brainwave is to use the AUTOEXNT service to run a batch file at boot (following config). I have created a snapshot of each of the users' Outlook install which is stored on a public share on the GhostCast server. The AutoexNT.BAT file is dropped onto the machine as a file at the end of the build task. This batch file modifies the registry to force an auto-login of the appropriate user and also to RunOnce a batch file which executes the appropriate AI executable, re-modifies the registry to take out the autologin and then reboots the machine. This NEARLY works. The problem is that the Autologin doesn't happen. If I go to the machine and do a <ctl><alt><del> to start a login, it immediately auto logs in and the build proceeds to successful completion. So I know the system works in principle. If I remote reboot the machine, again it will come up, auto login and complete successfully. I'm guessing that the problem is that the registry mod happens too late to be of use on that boot, but here's the odd thing.... If I put a reboot command at the end of AutoexNT.BAT, (using either shutdown or psshutdown), the MACHINE DOESN'T reboot following the build. If that reboot commnad is left there and the machine manually booted, then it DOES reboot! So something to do with the initial build of the system by Ghost is peventing the boot. I have also tried issuing the reboot command as a post-install task and it doesn't happen.WHY NOT?????? I can post the various files if that would help....

So, how do other people do this? Does anybody have a way of setting doing any (or all) of the following:-

1. Deploying an Outlook profile to a machine (where are these stored? Rgistry? Files? Both?)
2. Forcing a reboot of a machine once it has completely finished building.
3. Forcing an auto-login of a particular user to the machine at the end of the build process.
4. Hacking the registery to remove the <ctl><alt><del> requirement to bring up the login box.

Many thanks for reading this and even more if you reply ;-) Any and all suggestions welcome.

Paul