myITforum.com Community Forum myITforum.com Community Forum

Home  Forums  Blogs  Live Support chat  Search Articles  Wiki  FAQ  Email Lists  Register  Login  My Profile  Inbox  Address Book  My Subscription  My Forums 

Photo Gallery  Member List  Search  Calendars  FAQ  Ticket List  Log Out

All Forums RSS Feed Subscription:


  


OSD and HAL Replacement

 
View related threads: (in this forum | in all forums)

Logged in as: Guest
  Printable Version
All Forums >> [Management Products] >> System Center Products >> System Center Configuration Manager >> OSD and HAL Replacement Page: [1]
Login
Message << Older Topic   Newer Topic >>
OSD and HAL Replacement - 1/4/2008 8:34:55 AM   
direland


Posts: 129
Score: 0
Joined: 3/26/2004
From: Bedford, IN
Status: offline 		I'm trying to get a single XP image going and am stuck at HAL replacement.  I am using Johan's ZTIHalDetect script - but have also tried a modified sysprep.inf with the UpdateHAL statement in.

HAL replacement works just fine - provided I do not have the Setup Windows and ConfigMgr task sequence run.  Enabling this task sequence results in the HAL staying at what my reference computer was imaged with.

Anyone else have this issue or know a work around?  I need the SCCM client to install as I have other Install Software tasks I need to run during a deployment.

Thanks,

Dan
Post #: 1
RE: OSD and HAL Replacement - 1/7/2008 4:26:11 AM   
Jorg

 

Posts: 4
Score: 0
Joined: 12/4/2007
Status: offline 		A fast workaround is to make 3 windows xp images one for a uniprocessor computer, one for multiprocessor computer and one for a ACPI computer. Works all fine here.

When using the hall script add it to your .wim image with the hall file ntoskernell.exe. And use a run command line in you taks sequence to run the script (place it after the applying os image part in your task sequence). Also see to it your pe boot images are able to run vbscript.

(in reply to direland)
Post #: 2
RE: OSD and HAL Replacement - 1/7/2008 9:02:01 AM   
wbracken


Posts: 1023
Score: 22
Joined: 4/12/2002
From: St. Louis
Status: offline 		I would tend to disagree here (sorry Jorg!!) but maintaining a single image across the enterprise is going to yield much better managability and supportability.

Unfortunately I cannot comment on Johan's script since I do not use it however I do have a custom process I use myself that effectively just adds the following entry into Sysprep.inf just after the image is finished copying to the hard drive (before the first reboot).
[Unattended]
UpdateHAL = ACPIAPIC_MP,%windir%\inf\hal.inf

I have found the HAL thing to be fairly easy...the more tricky part for me has been getting the Mass Storage Controller setup so that the machine does not blue-screen on first reboot.  The HAL doesnt typically cause a blue screen.  In my testing it simply just installs the single processor hal.

Just verifying that the symptoms match the issue?  :)


_____________________________

William Bracken

Visit my new Blog
http://wbracken.wordpress.com/

(in reply to Jorg)
Post #: 3
RE: OSD and HAL Replacement - 1/7/2008 10:55:25 AM   
direland


Posts: 129
Score: 0
Joined: 3/26/2004
From: Bedford, IN
Status: offline 		wbracken,

Are you runing the Setup Windows and ConfigMgr sequence during your OS deployments?  The Johan script does the same thing you are doing.  But, the task sequence mentioned above seems to undo modification made to the sysprep.inf.

(in reply to wbracken)
Post #: 4
RE: OSD and HAL Replacement - 1/7/2008 3:09:26 PM   
direland


Posts: 129
Score: 0
Joined: 3/26/2004
From: Bedford, IN
Status: offline 		After enabling command support on the boot image and hitting F8 during the deployment, I noticed that after the Setup Windows and ConfigMgr task has completed, the UpdateHAL statement in the sysprep.inf was being modified.  The %WINDIR% was being changed to X:\Windows.  So, I modified the ZTIHalDetect.vbs script to hard code it to C:\Windows.  Seems to be working now.

(in reply to wbracken)
Post #: 5
RE: OSD and HAL Replacement - 1/7/2008 7:04:04 PM   
wbracken


Posts: 1023
Score: 22
Joined: 4/12/2002
From: St. Louis
Status: offline 		Excellent.  Glad to see its working for you now.

_____________________________

William Bracken

Visit my new Blog
http://wbracken.wordpress.com/

(in reply to direland)
Post #: 6
RE: OSD and HAL Replacement - 1/20/2008 12:52:41 PM   
Or.Tsemah

 

Posts: 109
Score: 1
Joined: 11/12/2006
Status: offline 		I think that the "Updatehal" option makes the image supportable by microsoft while the ZTIHALDETECT doesn't ...
Or am i wrong ?

_____________________________

Or Tsemah
or.tsemah@gmail.com

(in reply to wbracken)
Post #: 7
RE: OSD and HAL Replacement - 1/21/2008 4:00:00 PM   
wbracken


Posts: 1023
Score: 22
Joined: 4/12/2002
From: St. Louis
Status: offline 		Although it can and does work both ways, Microsoft does not support any cross HAL imaging in Windows XP/2000.  With Vista the HAL requirement is gone so they official support mutliple HAL's with a single image in Vista.

_____________________________

William Bracken

Visit my new Blog
http://wbracken.wordpress.com/

(in reply to Or.Tsemah)
Post #: 8
RE: OSD and HAL Replacement - 3/11/2008 4:26:10 PM   
smurdock

 

Posts: 155
Score: 0
Joined: 5/28/2002
Status: offline 		Direland, what task sequence did you use to get the ztihaldetect.vbs to work?  I've used it in BDD 2007/SMS 2003 and had no problems.  However, when I'm running it as a task sequence using a command line I'm getting an 0x00000001 error that it can't be run.  My command line is cscript.exe "%deployroot%\scripts\ZTIHalDetect.vbs"  Thanks.

Stephen

(in reply to direland)
Post #: 9
RE: OSD and HAL Replacement - 3/11/2008 5:12:10 PM   
smurdock

 

Posts: 155
Score: 0
Joined: 5/28/2002
Status: offline 		I think I might have found my solution, similar issue with the C drive now being the X drive.  I had seen your earlier post about hard coding everything to C but then realized when using the command prompt for testing that I need to change the writeini value of the ztihaldetect.vbs script to be X and not C.  I originally did a global replace of %windir% with c:\windows.

Stephen

(in reply to smurdock)
Post #: 10
RE: OSD and HAL Replacement - 3/12/2008 7:01:53 AM   
direland


Posts: 129
Score: 0
Joined: 3/26/2004
From: Bedford, IN
Status: offline 		Hi,

I actually embedded two modified ZTIHalDetect.vbs scripts into an SMS Installer package.  Depending whether or not the system has CDROM drive changes the drive letter that OSD is installing to (drive E: with CD and drive D: without).  The SMS Installer package looks for the drive with the sysprep folder then runs the appropriate HalDetect script.  Probably could have done this outside of SMS Installer, but I'm still new to SCCM and OSD.

I run the executable as a Run Command Line task right after the Apply Operating System task.

(in reply to smurdock)
Post #: 11
RE: OSD and HAL Replacement - 3/12/2008 7:04:01 AM   
direland


Posts: 129
Score: 0
Joined: 3/26/2004
From: Bedford, IN
Status: offline 		Yes, that stumped me for a while.  The driver letter must be hard coded in the script and the drive letter could be different on machines with CDROM drives and/or multiple hard disks.  %windir% won't work unfortunately.

(in reply to smurdock)
Post #: 12
RE: OSD and HAL Replacement - 4/23/2008 5:16:06 PM   
travisl

 

Posts: 4
Score: 0
Joined: 4/23/2008
Status: offline 		I am using SCCM 2007 and trying to incorporate this script into the Install and existing image package task sequence.  I have added the step Run Command Line (cscript.exe "%deployroot%\scripts\ZTIHalDetect.vbs) directly after the Apply Operation System step.

How do I need to to edit ZTIHalDetect.vbs in this scenario if there is only one CDROM and no other Partions or am I on the wrong page completely?  From the previous posts I'm guessing the lines similiar to...
WriteIni "c:\sysprep\sysprep.inf", "Unattended", "UpdateUPHAL", "ACPIAPIC_UP,%WINDIR%\Inf\Hal.inf"
should be..
WriteIni "c:\sysprep\sysprep.inf", "Unattended", "UpdateUPHAL", "ACPIAPIC_UP,C:\Windows\Inf\Hal.inf"
 
Any help or more in depth information would be helpful.

(in reply to direland)
Post #: 13
RE: OSD and HAL Replacement - 4/23/2008 5:27:04 PM   
smurdock

 

Posts: 155
Score: 0
Joined: 5/28/2002
Status: offline 		My lines in the script are:

writeini "e:\sysprep\sysprep.inf", "Unattended", "UpdateHAL", "ACPIAPIC_MP,c:\windows\Inf\Hal.inf"

This is because the E drive is where the image is being written to during the image download.  Thus, if you have the %windir% variable it would write to the sysprep.inf file to have e:\windows\inf\hal.inf.  Forcing that to be c:\windows\inf\hal.inf enables the file to be updated properly so when the image drive transitions from the temporary E drive to the normal C drive, it will work.

Stephen

(in reply to travisl)
Post #: 14
RE: OSD and HAL Replacement - 4/23/2008 5:59:23 PM   
travisl

 

Posts: 4
Score: 0
Joined: 4/23/2008
Status: offline 		Thanks that info that definately helps.  Another question, I'm adding Use Toolkit Package (MDT files w/ ZTIHalDetect.vbs included) before Run Command Line but using F8 to debug I see the variable %deployroot% is not being set so I'm wondering if my command is even running?  Am I doing this correct or do I have to recreate a new boot image with the ZTIHalDetect.vbs in it; it would be easier if I could just use it from the MDT files where I copied it into.

(in reply to smurdock)
Post #: 15
RE: OSD and HAL Replacement - 4/23/2008 6:12:25 PM   
smurdock

 

Posts: 155
Score: 0
Joined: 5/28/2002
Status: offline 		I have mine setup as a seperate action in my task sequence.  It is set to run right after the Apply Operating System Image task.  It runs the command line cscript.exe %deployroot%\scripts\ZTIHalDetect.vbs".  If your not getting the %deployroot% variable to resolve correctly I would suggest checking your smsts.log file for any errors (file will either be at %temp%, c:\windows\system32\ccm\logs or c:\smstslog.

Stephen

(in reply to travisl)
Post #: 16
RE: OSD and HAL Replacement - 4/24/2008 9:31:27 AM   
travisl

 

Posts: 4
Score: 0
Joined: 4/23/2008
Status: offline 		Thanks looks like everything is working, I ran it on a Dell Dimension 2400 and it updated the HAL correctly and it finished the imaging task sequence (before using ZTIHalDetect.vbs that machine would reboot indefinately after the first reboot).  I just need to add some code to deal with the different drive letters(D,E,F) which should be simple.

(in reply to smurdock)
Post #: 17
RE: OSD and HAL Replacement - 4/24/2008 10:36:20 AM   
iburnell


Posts: 251
Score: 1
Joined: 5/14/2003
From: London, UK
Status: offline 		You don't need to hard code the drive letter - use the OSDTargetSystemDrive variable - check the attachment

I created an SCCM package containing different hal files e.g. halacpi.dll, halaacpi.dll, ntoskrnl.exe, and ztihaldetect then just call ztihaldetect.vbs from the package as a TS item - works fine

Attachment (1)

_____________________________

Ian Burnell
London UK

(in reply to travisl)
Post #: 18
RE: OSD and HAL Replacement - 4/24/2008 10:49:16 AM   
travisl

 

Posts: 4
Score: 0
Joined: 4/23/2008
Status: offline 		iburnell, What is the need to include those hal files in a package, aren't they just pulled from the dllcache folder automatically?  Also what is ntoskrnl.exe for?

(in reply to iburnell)
Post #: 19
RE: OSD and HAL Replacement - 4/24/2008 11:39:16 AM   
iburnell


Posts: 251
Score: 1
Joined: 5/14/2003
From: London, UK
Status: offline 		Well I **thought** you had to have each file present so the correct file could be pulled in - I may be wrong :) - I was looking at Johan's Geeks guide http://www.myitforum.com/articles/15/print_view.asp?id=8997 and pulled all the files from the 3 different HAL types into the package. If it does it from dll cache from the updatehal entry in sysprep so much the better, but I had assumed that you need the original file to be present so it could be correctly put in place

_____________________________

Ian Burnell
London UK

(in reply to travisl)
Post #: 20
Page:   [1]
All Forums >> [Management Products] >> System Center Products >> System Center Configuration Manager >> OSD and HAL Replacement Page: [1]
Jump to:





New Messages No New Messages
Hot Topic w/ New Messages Hot Topic w/o New Messages
Locked w/ New Messages Locked w/o New Messages
 Post New Thread
 Reply to Message
 Post New Poll
 Submit Vote
 Delete My Own Post
 Delete My Own Thread
 Rate Posts



  
Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI

0.438