Building 1 XP image for all PC's
Walter
tried numerous methods, scripts... none seem to work.
I tried Johan Arwidmarks script with changes the sysprep.inf while in
PE.
I am trying this trough SMS with PE2005 OSD (ZTI)
Has anyone succesfully accomplished this without great difficulty?
Stefan Olsson
I would go with Johans guide, http://www.myitforum.com/articles/15/view.asp?id=8997
Its the best I have come across so far.
----------------------------------------
Stefan Olsson
MCSA:Messaging
E-Mail: ste...@msfaq.se
www.msfaq.se
-----------------------------------------
Walter
>
> - Show quoted text -
Hi Stephan , thanks I have tried that and I must be missing something
because my image blue screens on anything except where is was created.
According to that article all I should have to do is add that script
to my POST install phase in SMS. That where is is but no luck.
Do use that with sucess?
AdamR
What kind of machines does it blue screen on?
Chances are 99% that these machines have SATA/RAID disk controllers.
Please confirm machine types and disk controller types.
If this is the case, then you will need to provide these disk
controllers in the Sysprep.inf file...
Adam
> Do use that with sucess?- Hide quoted text -
Walter
>
> - Show quoted text -
Dell C640 D600 D610, all IDE drives.
Will also have D620 which I know is SATA.
Thanks
Eric Giroux
models. These don't have any SATA controller issues. You need a
basic vbscript that gets called during the PostInstall phase. It
should use a Select Case statment to check for all your known hardware
models. Based upon the hardware model on the target computer, the HAL
files need to be swapped as needed. If you created the image on one
of the non-D620 models, you should only need a HAL swap if the image
is coming down on a D620, which is MultiProcessor. The rest have a
common HAL.
Walter
Hmmm.... I must be doing something wrong. I created the image on the
c640 since it was the oldest machine... but no joy.
BSOD
Any idea where to go from here?
Eric Giroux
that working first. You should be able to put them image down on the
machine it was created on without issue since there are no additional
or different drivers involved. Are you using the OSD Capture CD to
capture your image or some other means?
Walter
>
> - Show quoted text -
Yes it works fine on the 640. I used the OSD capture CD to create the
image.
Just won't work on any other hardware get the BSOD Stop000000X7B
Crashball
have been using VirtualPCs for a couple years to create the base image and
never have had an issue until we started getting new HALs. Worked on
GX110-GX280 and C600 - D610s, about 12 models. Now with the dual core PCs, i
use a script in the POSTINSTALL to read the regkey
"HKLM\SYSTEM\CurrentControlSet\Enum\Root\ACPI_HAL\0000\HardwareID". The value
will be acpiapic_up (uniprocessor) or acpiapic_mp (multiprocessor, also for
dual core). Then if it is a MP it adds to the [UNATTEND] section of the
sysprep.inf, ACPIAPIC_MP,%WINDIR%\Inf\Hal.inf" which will make it use the MP
HAL - and even if it is a uniprocessor, so make sure the logic is right.
Back to the VPC, since VirtualPC environment is virtualized, it emulates
only very basic hardware when it comes to controllers and HALs. Then you
just have to worry aboutgetting the right drivers on the images and
specifying them in the SYSPREP.INF file. Another area i have seen issues is
the Mass storage. Try setting buildMassStorageSection = YES
niklauz
master image on VPC and then just build Mass Storage with Sysprep. So
my Sysprep file looks like:
_______________________________
[Sysprep]
BuildMassStorageSection=Yes
[MassStorageSection]
______________________________
Note: Make sure you include [MassStorageSection] in your sysprep file
otherwise sysprep cannot add to the file. If you dont include this in
your sysprep file you may encounter BSOD's when booting on different
harware so make sure you add this section or run sysprep -bmsd to pre-
populate this before capturing the image and set
BuildMassStorageSection=No
In BDD 2.5, I used a script to update the HAL based on Johan's article
after OSD had layered down the image but before rebooting into Windows
(post install task). Worked a dream.
In BBD 2007 I use the HALName variable to do this for me so I no
longer need the script. In my Rules:
Priority=HALName
Properties=UpdateHAL,UpdateUPHAL
[ACPIAPIC_MP]
UpdateHAL=ACPIAPIC_MP,%DeploySystemDrive%\Windows\Inf\Hal.inf
[ACPIAPIC_UP]
UpdateUPHAL=ACPIAPIC_UP,%DeploySystemDrive%\Windows\Inf\Hal.inf
This basically does the same this as Johan's article but you dont need
to run a script.
My image works on all our hardware without a problem using both the
above methods and I havent as yet had any probs.
Just to verify that the changes are getting applied boot into WinPE
after OSD has layered down the image instead of booting into windows
and pull up sysprep.inf, you should see that Sysprep.inf has been
updated with the correct HAL and [MassStorageSection] should have a
load of entries.
Hope this helps
niklauz
Crashball
alternatively, if you open the command prompt (labshell) before it even
images and leave it open, it will not reboot after the postinstall. it will
wait until the CMD window closes. That way you don't have to babysit it and
you can go right to the file.
fatosarifi
Walter wrote:
Re: Building 1 XP image for all PC's
20-Jun-07
Previous Posts In This Thread:
On Wednesday, June 20, 2007 3:40 PM
Walter wrote:
Building 1 XP image for all PC's
I am trying to build 1 image that will work on all my PC's. I have
tried numerous methods, scripts... none seem to work.
I tried Johan Arwidmarks script with changes the sysprep.inf while in
PE.
I am trying this trough SMS with PE2005 OSD (ZTI)
Has anyone succesfully accomplished this without great difficulty?
On Wednesday, June 20, 2007 7:32 PM
Walter wrote:
Re: Building 1 XP image for all PC's
On Thursday, June 21, 2007 7:58 AM
AdamR wrote:
Re: Building 1 XP image for all PC's
I have done it
What kind of machines does it blue screen on?
Chances are 99% that these machines have SATA/RAID disk controllers.
Please confirm machine types and disk controller types.
If this is the case, then you will need to provide these disk
controllers in the Sysprep.inf file...
Adam
On Jun 21, 12:32 am, Walter <LetsM...@gmail.com> wrote:
On Thursday, June 21, 2007 1:12 PM
Walter wrote:
Re: Building 1 XP image for all PC's
Thanks
On Tuesday, June 26, 2007 7:17 AM
Eric Giroux wrote:
Re: Building 1 XP image for all PC's
I have 1 XP image that works on these 4 as well as about 10 other Dell
models. These don't have any SATA controller issues. You need a
basic vbscript that gets called during the PostInstall phase. It
should use a Select Case statment to check for all your known hardware
models. Based upon the hardware model on the target computer, the HAL
files need to be swapped as needed. If you created the image on one
of the non-D620 models, you should only need a HAL swap if the image
is coming down on a D620, which is MultiProcessor. The rest have a
common HAL.
On Tuesday, June 26, 2007 7:07 PM
Walter wrote:
Re: Building 1 XP image for all PC's
On Jun 26, 7:17 am, Eric Giroux <egir...@unumprovident.com> wrote:
Hmmm.... I must be doing something wrong. I created the image on the
c640 since it was the oldest machine... but no joy.
BSOD
Any idea where to go from here?
On Tuesday, June 26, 2007 11:38 PM
Stefan Olsson wrote:
Re: Building 1 XP image for all PC's
Hello Walter,
I would go with Johans guide, http://www.myitforum.com/articles/15/view.asp?id=8997
Its the best I have come across so far.
----------------------------------------
Stefan Olsson
MCSA:Messaging
E-Mail: ste...@msfaq.se
www.msfaq.se
-----------------------------------------
On Wednesday, June 27, 2007 11:19 AM
Eric Giroux wrote:
Re: Building 1 XP image for all PC's
Can you get the image to come down on the C640? If not, I would get
that working first. You should be able to put them image down on the
machine it was created on without issue since there are no additional
or different drivers involved. Are you using the OSD Capture CD to
capture your image or some other means?
On Jun 26, 7:07 pm, Walter <LetsM...@gmail.com> wrote:
On Wednesday, June 27, 2007 8:59 PM
Walter wrote:
Re: Building 1 XP image for all PC's
On Jun 27, 11:19 am, Eric Giroux <egir...@unumprovident.com> wrote:
Yes it works fine on the 640. I used the OSD capture CD to create the
image.
Just won't work on any other hardware get the BSOD Stop000000X7B
On Monday, July 09, 2007 10:12 AM
Crashbal wrote:
Re: Building 1 XP image for all PC's
Since VirtualPC 2007 is now free, maybe try that to create base image. I
have been using VirtualPCs for a couple years to create the base image and
never have had an issue until we started getting new HALs. Worked on
GX110-GX280 and C600 - D610s, about 12 models. Now with the dual core PCs, i
use a script in the POSTINSTALL to read the regkey
"HKLM\SYSTEM\CurrentControlSet\Enum\Root\ACPI_HAL\0000\HardwareID". The value
will be acpiapic_up (uniprocessor) or acpiapic_mp (multiprocessor, also for
dual core). Then if it is a MP it adds to the [UNATTEND] section of the
sysprep.inf, ACPIAPIC_MP,%WINDIR%\Inf\Hal.inf" which will make it use the MP
HAL - and even if it is a uniprocessor, so make sure the logic is right.
Back to the VPC, since VirtualPC environment is virtualized, it emulates
only very basic hardware when it comes to controllers and HALs. Then you
just have to worry aboutgetting the right drivers on the images and
specifying them in the SYSPREP.INF file. Another area i have seen issues is
the Mass storage. Try setting buildMassStorageSection = YES
"Walter" wrote:
On Monday, July 09, 2007 11:01 AM
niklauz wrote:
Re: Building 1 XP image for all PC's
_______________________________
[Sysprep]
BuildMassStorageSection=Yes
[MassStorageSection]
______________________________
Priority=HALName
Properties=UpdateHAL,UpdateUPHAL
Hope this helps
niklauz
On Monday, July 09, 2007 11:30 AM
Crashbal wrote:
Re: Building 1 XP image for all PC's
alternatively, if you open the command prompt (labshell) before it even
images and leave it open, it will not reboot after the postinstall. it will
wait until the CMD window closes. That way you don't have to babysit it and
you can go right to the file.
"niklauz" wrote:
Submitted via EggHeadCafe - Software Developer Portal of Choice
Sending SMTP email from within BizTalk Orchestration
http://www.eggheadcafe.com/tutorials/aspnet/9dd0f346-baf9-4674-a50f-1716445b26bc/sending-smtp-email-from-w.aspx