Please help Me figure out Ghostcast, sysprep and Vista
We have just purchased our first batch of Windows Vista based PCs after having used XP for many years and I am struggling to create an as fully automated Ghost setup as I would like (and have with XP).
With XP I would create a template PC with all our additional software and latest Microsoft updates, then I would create a sysprep.inf file with all our information and volume licence key in the install.
My ultamite goal was to create a completely unattended installation.
MY way of imaging computers was to use "Ghost Cast Server"
I would make a ghost network boot cd and boot my "template" pc and then join to my ghost cast server and image the computer with xp. THis would be my "master copy"
I would then boot the "dummy" computers from a "network boot package" cd with either PXE dirvers or acutual network drivers (depending on wether the pc had pxe cabablitlies or not) (say 12 computers) and use ghost cast server on my "ghost server" to start a multi-cast session and blow down the master image to 12 computers or so.
With Vista I would like to do something similar however I have come across a few problems that I would like either confirmation or even better a solution or work around.
I have to admit, that I am not to familar with how the following programs all interact with vista
Vista (ultamate or buisness)
sysprep (unattended.xml)
ghost 11
ghost cast server
I know there is something about WINPE but im not sure how that comes into play
I have tried and tried to find answers to this, but to no avail.
can someone please help me! give me steps on how to "ghost" a master copy of vista and deploy this to client computers using ghostcast server. Help please!!!!
Comments
bump
can somebody anybody please help me?
Thank you for your responce,
My problem is I dont know how to use unattended.xml and now to incorperate that into sysprep, or if you even still use sysprep
basicly how do you "sysprep" and use unattended.xml in vista? can someone please explain this step by step?
Thank you very much for your responce.
I have read both articles.
I now have 2 questions.
First,
when you used to use sysprep in XP you could create a section called
[sysprep]
buildmasssotragesection=yes
[sysprepmassstorage]
and also
[unattended]
updateHAL = "ACPIAPIC_MP, c:\WINDOWS\inf\Hal.inf"
these two sections were very important for me (and took me forever to learn) inorder to build an image that would not bluescreen on diffrent types of processors.
I do not see this option with sysprep.xml, can someone please tell me how to implenet this same functionality with sysprep.xml
Second question.
Instead of usinging ImageX, this is where I would do my normal ghosting operation correct?
Thanks very much to whoever replys, I think If i can get these 2 questions answered, I can start my work with vista.
There were a number of changes to Vista to make it possible for the operating system to dynamically load HALs and mass storage drivers at boot time – therefore there is no need for any manual steps to install drivers (the auto apply driver action is usually sufficient but the apply driver package action is still useful to pre-stage drivers that may be needed).
To answer your other questions:
1. Yes – the HDC fix is in ConfigMgr SP1
2. Yes – you can either specify a base unattend.xml file as part of the Apply Operating System action or add custom actions between the Apply Operating System action and the Setup Windows and ConfigMgr to customize the unattend.xml file (%OSDAnswerFilePath%)
Thank you for your reply,
There were a number of changes to Vista to make it possible for the operating system to dynamically load HALs and mass storage drivers at boot time – therefore there is no need for any manual steps to install drivers
This is great news!!!
(the auto apply driver action is usually sufficient but the apply driver package action is still useful to pre-stage drivers that may be needed).
To answer your other questions:
1. Yes – the HDC fix is in ConfigMgr SP1
2. Yes – you can either specify a base unattend.xml file as part of the Apply Operating System action or add custom actions between the Apply Operating System action and the Setup Windows and ConfigMgr to customize the unattend.xml file (%OSDAnswerFilePath%)
however I have virtually no idea what this means lol
the auto apply driver action is usually sufficient but the apply driver package action is still useful to pre-stage drivers that may be needed).
these 2 steps seem important, i'd like to know how to do them and when to implenent them. Is this a setting you need to add using Windows system image manager to your sysprep.xml file?
any more info you can find would be great!
thanks again
Not true, vista is completely different than XP. and i believe that there will be many people that need answers to this question.
Would you like to reply?
Login or Register to post your comment.