Re: Imaging and HP DL360/DL380 Servers
- From: "Laurent Bertin" <LaurentBertin@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 28 Feb 2006 14:39:18 -0800
yes i just saw it now thanks...
but my answer is still the same i did to him...
something that worked in windows 2000 just disappeared...
Also i found stupid not to put a link to that Kb under for example
http://support.microsoft.com/kb/302577/
or http://support.microsoft.com/kb/892778
which is the link that appears under the download of sysprep
http://www.microsoft.com/downloads/details.aspx?FamilyID=a34edcf2-ebfd-4f99-bbc4-e93154c332d6&DisplayLang=en
(i know mvp have connections to m$ so if i write it it is because many
others guys
may also have the same problems so if you can just make a small remark i am
sure they will handle the documentation links and thus help a bit guys
looking during a week why something doesn't work !)
Thanks a lot for both of you !
"Johan Arwidmark" wrote:
As posted by Darrell Gorter[MSFT] in another thread of yours.....
Sysprep has a limitation that the Windows installation must be on the
C drive.
Summary of the limitations of the System Preparation tool
http://support.microsoft.com/default.aspx?scid=kb;EN-US;830958
regards
Johan Arwidmark
Microsoft MVP - Setup/Deployment
On Tue, 28 Feb 2006 06:01:28 -0800, "Laurent Bertin"
<LaurentBertin@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Well it works if you try on a C drive as system; mine are on D and there is
no C...
and then sysprep just resets all drive letters which is really anoying...
well it is what i have on all kind of servers i tried with the
[sysprepMassStorage] build using the -bdms switch...
We need this because servers are booting from a remote storage with a boot
bios where my C resides... so in case of hardware failure we can easily
recover the system (one hour time) by just restting the disk signatures in
the registry of both the C drive on the system and the D locally.
so i think we'll install a system on C, a system on D and delete the C drive
(yes i know we make weird things)
and maybe is this problem simply due to windows as we were never able to
just install a system on D Drive directly without the system renaming the
system disk to C...
"Johan Arwidmark" wrote:
Yes, it works... :)
Important: Before sysprep starts the mini-setup, the drivers for the
new model must be in place, sysprep.inf oempnpdriverspath and
devicepath value in registry must be updated. Otherwise you will get
the symptoms you describe.
This is normally done by a hardware detection process directly after
the image is applied on the disk, but before sysprep starts minisetup.
If your deployment solution does not support this, you either have to
script it yourself or add drivers for all hardwares in your master
image (not recommended, but it works)
Storage drivers must be added before sealing the reference computer.
I was recently involved in building a deployment solution for
installing 1000+ Windows 2003 Servers. I have found very few issues
with sysprep and the core Windows Server 2003 SP1 os (make sure you
use the correct sysprep version)
Applications and server roles are another story, they should be
deployed after laying down the image (post-installation processes)
regards
Johan Arwidmark
Microsoft MVP - Setup/Deployment
On Tue, 28 Feb 2006 01:57:27 -0800, "Laurent Bertin"
<LaurentBertin@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Say if it works...
cause for my part it is just corrupting my server... no more access to
network connections, 80% of the snap-ins does not work anymore...
I am trying on a windows 2003 without sp1 on HP Blade 20Gp, 580G2 and
380G3... and got the same problem on all servers...
"Johan Arwidmark" wrote:
As long as you include the mass-storage drivers (and build them
through sysprep) and they have the same HAL yes...
regards
Johan Arwidmark
Microsoft MVP - Setup/Deployment
On Sun, 26 Feb 2006 11:31:33 -0800, stosti
<stosti@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Great! So I can make an image for an HP server without issue? If the image
has all the drivers for both machines will it be hardare independent?
Thanks,
Scott
"Johan Arwidmark" wrote:
Sysrep works great with Win2003....
regards
Johan Arwidmark
Microsoft MVP - Setup/Deployment
On Sat, 25 Feb 2006 06:14:27 -0800, stosti
<stosti@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Is it possible to image an HP server with Windows 2003 SP1 VL? I just bought
12 DL360's and would like to configure one with my base image and push it out
with Ghost 8.5 or LiveStateRecovery 3.03. I'm not even worried if the image
is hardware independant or not. I just want to build an image for a DL360
and DL380 G4 system I can reuse with like hardware.
Does SYSPREP work with 2003 Server? Is it necessary or can I use the
Sysinternals tool that changes the sid?
Thanks in advance!!!
Scott
- Prev by Date: RE: Sysprep 2003 buggy when system on D Drive
- Next by Date: Re: Can't install components on 2003 SP1 R2 upgrade
- Previous by thread: RE: Sysprep 2003 buggy when system on D Drive
- Next by thread: Re: Can't install components on 2003 SP1 R2 upgrade
- Index(es):
Relevant Pages
|
Loading
