Secure configurations for automated installation testing

[Gary Feldman]

I'd like to automate the testing of our installation kits. This means having the host machine fire up the virtual machine, and then fire up the install on the virtual machine.

I think I can get part way by using the "run script at startup" feature, and having that script look at another script in the folder that's shared with the host. The host machine could then populate that folder with whatever was needed before firing up the virtual - all very easy to do via NAnt or other scripting on the host.

The issue I'm worrying about is logging on and perhaps system security. I'm assuming that the "run script at startup" runs at the SYSTEM user (or something similar). But for testing purposes, I'd really prefer it run as a real user with minimal admin privileges (to match the way the product will actually be installed). I'm not sure what the best way is to do that? I suppose I've been spoiled by the UNIX world, where I use ssh for this purpose. And that might be the answer, since I know I can run an sshd daemon on Windows 2K. But the tester in me really dislikes having any other software on the virtual machine that isn't required by the installation being tested. So I'm wondering if Windows provides any other hooks that would be appropriate?

This is the first time I've tried automating Windows installation testing, so I also welcome any comments or criticisms on my overall approach.

Gary

[Nephi]

From what I understand is that you want to be able to script the
installation
of Windows, so you can leave it to install, then for it to log in and run a
test
application?

If so, there are 3 possible options. I know these are used quite a bit.

1) Use Norton's Ghost. And remember to change the network name.

2) Use RIS (Remote Installation Service), found in NT based servers. To
push out Windows, and install it how you want it installed. You can do
funky stuff with RIS, but I dont know RIS that well to say much about
it. I know it can log into a user to install an application. With this
option
you can have the lastest patches, software, etc. pushed out to the VPC
that is currently installing. Saves about 1 hour or more of your time,
of
not having to wait around for the installation to do stuff.

3) Edit one of the .inf files to have windows automate its installation.
Can't
remember which file or how to edit it correctly. MS's knowledge base
has the information, and there are plenty of websites that tell you how.

-- Nephi

Post by Gary Feldman
I'd like to automate the testing of our installation kits. This means
having the host machine fire up the virtual machine, and then fire up the
install on the virtual machine.
I think I can get part way by using the "run script at startup" feature,
and having that script look at another script in the folder that's shared
with the host. The host machine could then populate that folder with
whatever was needed before firing up the virtual - all very easy to do via
NAnt or other scripting on the host.
The issue I'm worrying about is logging on and perhaps system security.
I'm assuming that the "run script at startup" runs at the SYSTEM user (or
something similar). But for testing purposes, I'd really prefer it run as
a real user with minimal admin privileges (to match the way the product
will actually be installed). I'm not sure what the best way is to do
that? I suppose I've been spoiled by the UNIX world, where I use ssh for
this purpose. And that might be the answer, since I know I can run an
sshd daemon on Windows 2K. But the tester in me really dislikes having
any other software on the virtual machine that isn't required by the
installation being tested. So I'm wondering if Windows provides any other
hooks that would be appropriate?
This is the first time I've tried automating Windows installation testing,
so I also welcome any comments or criticisms on my overall approach.
Gary

[Gary Feldman]

Post by Nephi
From what I understand is that you want to be able to script the
installation
of Windows, so you can leave it to install, then for it to log in and run a
test
application?
If so, there are 3 possible options. I know these are used quite a bit.
1) Use Norton's Ghost. And remember to change the network name.

Both your second and third suggestions look like they'd work, so I'll probably start by investigating RIS.

But I don't understand what Ghost buys me that I can't get from using VMware snapshots?

Thanks,

Gary

[Nephi]

Ghost, gives you the advantage of been able to set windows up in 1 install,
and using it on multiple PCs to replicate it.

-- Nephi

Post by Gary Feldman

Post by Nephi
From what I understand is that you want to be able to script the
installation
of Windows, so you can leave it to install, then for it to log in and run
a test
application?
If so, there are 3 possible options. I know these are used quite a bit.
1) Use Norton's Ghost. And remember to change the network name.

Both your second and third suggestions look like they'd work, so I'll
probably start by investigating RIS.
But I don't understand what Ghost buys me that I can't get from using VMware snapshots?
Thanks,
Gary