Hello Craig,
Thanks!
You are right. I was editing the sysprep of the old revision.
(it is getting late..)
I am very glad you pointed this out so I can still get this fixed for my
deadline tomorrow.
Kind regards,
Ivar
Craig Bender schreef:
Hi Ivar,
It's a bit of chicken/egg thing.
When do the "prepare for system preparation" sysprep is ran with the
-quiet -reseal -etc options. This then created a subdirectory under
c:\sysprep called C:\sysprep\i386
This is where the inf will be.
But, I'd suspect you problem is that you didn't create a new revision
of your master template that contained C:\VDI\install.cmd
You can't just fire up your current revision make changes and have
that take affect.
Select the top level machine in your you pool (i.e. the "template" or
the one without any revision names). This will start the revision
that you've made master.
Open Console, and start the VM. Make your changes (i.e. put your
install.cmd file in c:\VDI)
Shut down your machine, then *Create Revision*.
Change your Sysprep settings on the cloning tab, then go back to the
templates tab and prepare for System Preparation. This creates the
sysprep.inf file in C:\Sysprep\i386. The revision should now show a
state of "Sysprep". Now mark that revision as Master by clicking the
Make Master on the Templates Tab.
If you have cloning set to automatically happen, it should kick off.
If you have existing machines in the pool under the Desktop Tab,
select those at the older revision and select reset cloning.
Now when the Machine boots, it will run the mini-installer, and have
access to your C:\VDI\install.cmd specified
On 9/15/10 11:54 AM, Ivar Janmaat wrote:
Hello Guys,
I need some help quickly so I though I try this list first.
I want to make some adjustments when the clones are first booted in the
pools.
So I thought I could add a run {GuiRunOnce] option by editing the pools
sysprep file.
I added:
[GuiRunOne]
"c:\VDI\install.cmd"
I save the file.
Then I open the file again with "edit"
The sysprep file now contains:
[GuiRunOne]
But the
"c:\VDI\install.cmd"
Is missing.....
Is this a bug?
Where is the sysprep.inf file stored so I can check if it contains the
c:\VDI\install.bat?
I suppose this is a feature that is used a lot, so I am a bit amazed
that it is not working the way I expected.
Kind regards,
Ivar Janmaat
I am using VDI 3.2 on Solaris 10u8 x64.
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
