Hi, I've tried setting up a TS doing everything for a format of a win-xp machine and into a Win 7. This means full format, joining the domain ect. ect. I've been struggeling a bit with the HP Drivers, and still got ONE yellow ! on my device list. The 3D Driveguard does not want to install no matter what I do. I've tried calling the setup file with the "command line" option in the TS, and even added it as a software pack (along with Ricoh-, Quicklaunch and fingerprint drivers). I still can't get this working! I used this for the Quicklaunch (which also was tricky to figure out): setup.exe -s /f2c:\setup.log /V/qn Have anyone done the 3D Drive guard, and can point me in the right direction?

Hi,What does setup.log tell you?Cheers, Bess, Kenneth - http://www.systemcenterforum.net

Hi,What does setup.log tell you?Cheers, Bess, Kenneth - http://www.systemcenterforum.net

No idea tbh. How do I check? Do I have to set it up somehow to write a log? Or where do I find it?

No idea tbh. How do I check? Do I have to set it up somehow to write a log? Or where do I find it?

What HP model is it... ?I have managed to get the 3D Drive guard to work (at least at XP).But I can try to test it in Win 7.

What HP model is it... ?I have managed to get the 3D Drive guard to work (at least at XP).But I can try to test it in Win 7.

At the moment I'm using a 6910p for testing purposes. When I can get the DG working, it will be for a 6910p, 6930p and PERHAPS a nc6320 (dependant on schedule). Would appreciate if you could try it out and point me in the right direction!

At the moment I'm using a 6910p for testing purposes. When I can get the DG working, it will be for a 6910p, 6930p and PERHAPS a nc6320 (dependant on schedule). Would appreciate if you could try it out and point me in the right direction!

Let me try to test it on a 6910 and Win7.I know it works in XP.As far as I remeber I extracted the driver using spxxxxx.exe -e.Afterwards the drivers were copied into my "Driverpackages", I have for the different models.I use the same method like this: http://blogs.technet.com/deploymentguys/archive/2008/02/15/driver-management-part-1-configuration-manager.aspx

Let me try to test it on a 6910 and Win7.I know it works in XP.As far as I remeber I extracted the driver using spxxxxx.exe -e.Afterwards the drivers were copied into my "Driverpackages", I have for the different models.I use the same method like this: http://blogs.technet.com/deploymentguys/archive/2008/02/15/driver-management-part-1-configuration-manager.aspx

Already tried doing it that way.. It extracts a setup.exe file and other files needed by the setup. Just tried running a .bat script copying the entire setup folder onto the local machine, and then executing it - without luck. If you manage to do it on Win7, you're definitly my hero! As for now, I've spendt about a week trying different combinations and ways to do this.

Already tried doing it that way.. It extracts a setup.exe file and other files needed by the setup. Just tried running a .bat script copying the entire setup folder onto the local machine, and then executing it - without luck. If you manage to do it on Win7, you're definitly my hero! As for now, I've spendt about a week trying different combinations and ways to do this.

I'll try this evening to see what I can come up with.

I'll try this evening to see what I can come up with.

Great! Thanks a million!

Great! Thanks a million!

I had a similar issue with an nc6400 and the quick launch buttons. It turns out the drivers needed to be installed in compatibility mode, which requires a registry entry. I created a package contaning the batch file and registry entries. Copied the source to the local disc, set the registry entries, called the local installer, and then deleted the source files. I was able to get this to work using that method with some tweaks and testing.I have successfullt been able to pull the 3D Driveguard for the 8530P into SCCM and it installs as part of the driver package now. You may try extracting those files and looking for the .inf and see if SCCM can pull those in (looks like you already tried, but its always good to doublecheck). HTH.

Hey waynegro, yeah - I definitly have tried pulling just the .inf but I'll double check tomorrow! Only tried extracting the .inf from a machine which already had the driver installed (used DoubleDriver for this + all other drivers). I'll check the source for a .inf tomorrow. Can I find a more detailed description about the first thing you mention? I've gotten to the point that everything is worth a shot! So detailed pointers would be VERY MUCH appreciated!

I had to take a Windows 7 machine without the drivers, copy the installation files locally and then try to get it to install using the batch file. You'll need a registry file to tell it to run in compat. mode. I'll try to find that for you. First, try to install it locally using the compatibility mode and see if that works before wasting time trying to automate something that may not work.EDIT: I believe this is the registry key you are looking for. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\LayersAfter copying those files locally right click on setup.exe and find the compatibility tab. Set it and then look around in this location to verify if it is there. I would copy the files to the potential directory structure you'll use during the installation. Then you can simply export that registry key for use in your package and batch file. Found here:http://social.msdn.microsoft.com/Forums/en/windowscompatibility/thread/bc32887d-4fcf-4416-aa22-36a93dfeb644

I had to take a Windows 7 machine without the drivers, copy the installation files locally and then try to get it to install using the batch file. You'll need a registry file to tell it to run in compat. mode. I'll try to find that for you. First, try to install it locally using the compatibility mode and see if that works before wasting time trying to automate something that may not work.EDIT: I believe this is the registry key you are looking for. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\LayersAfter copying those files locally right click on setup.exe and find the compatibility tab. Set it and then look around in this location to verify if it is there. I would copy the files to the potential directory structure you'll use during the installation. Then you can simply export that registry key for use in your package and batch file. Found here:http://social.msdn.microsoft.com/Forums/en/windowscompatibility/thread/bc32887d-4fcf-4416-aa22-36a93dfeb644

Awesome! I'll definitly get to that first thing tomorrow morning! What is kinda wierd, is that any .bat script I run when the machine has finished my TS, and has entered the domain and a user is logged on - can run the .bat file from the share, and the driver will install. The same thing happens if I just navigate to the shared folder through cmd; setting the /qn and /norestart flags even works! Never had an issue with comp. - but it could definitly be something to it, and is worth checking into! Edit: The issue is getting it to run WITHIN my TS.. It's wierd that I'm the only one struggeling with this.. Perhaps SCCM doesn't like me!

Awesome! I'll definitly get to that first thing tomorrow morning! What is kinda wierd, is that any .bat script I run when the machine has finished my TS, and has entered the domain and a user is logged on - can run the .bat file from the share, and the driver will install. The same thing happens if I just navigate to the shared folder through cmd; setting the /qn and /norestart flags even works! Never had an issue with comp. - but it could definitly be something to it, and is worth checking into! Edit: The issue is getting it to run WITHIN my TS.. It's wierd that I'm the only one struggeling with this.. Perhaps SCCM doesn't like me!

I had to take a Windows 7 machine without the drivers, copy the installation files locally and then try to get it to install using the batch file. You'll need a registry file to tell it to run in compat. mode. I'll try to find that for you. First, try to install it locally using the compatibility mode and see if that works before wasting time trying to automate something that may not work. EDIT: I believe this is the registry key you are looking for. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags \Layers After copying those files locally right click on setup.exe and find the compatibility tab. Set it and then look around in this location to verify if it is there. I would copy the files to the potential directory structure you'll use during the installation. Then you can simply export that registry key for use in your package and batch file. Found here: http://social.msdn.microsoft.com/Forums/en/windowscompatibility/thread/bc32887d-4fcf-4416-aa22-36a93dfeb644 One question related to this though! Was the driver actually incompatible with Win7? or Was it one of their Win7 driver releases? Earlier on, I had the same problem on my own 6930p, and had to use comp. mode to install the driver (early stages of Win7 / just after release).

I had to take a Windows 7 machine without the drivers, copy the installation files locally and then try to get it to install using the batch file. You'll need a registry file to tell it to run in compat. mode. I'll try to find that for you. First, try to install it locally using the compatibility mode and see if that works before wasting time trying to automate something that may not work. EDIT: I believe this is the registry key you are looking for. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags \Layers After copying those files locally right click on setup.exe and find the compatibility tab. Set it and then look around in this location to verify if it is there. I would copy the files to the potential directory structure you'll use during the installation. Then you can simply export that registry key for use in your package and batch file. Found here: http://social.msdn.microsoft.com/Forums/en/windowscompatibility/thread/bc32887d-4fcf-4416-aa22-36a93dfeb644 One question related to this though! Was the driver actually incompatible with Win7? or Was it one of their Win7 driver releases? Earlier on, I had the same problem on my own 6930p, and had to use comp. mode to install the driver (early stages of Win7 / just after release).

I tried inserting a registry hack for first time logon before running another .bat, but that failed aswell.. Kinda running out of options.. Anyone got this working yet?

Hello, we've got quite a few HP notebooks and we are planning migration to Windows 7 somewhere in the future :) Any way i've just tested deploying Windows 7 x86 Enterprise on HP 6730b and it had no problems installing HP 3D DriveGuard as a packages: - download sp45248.exe (HP 3D DriveGuard v.4.0.4.1) to your package repository - create a package for it - create a program and use the following command line: "sp45248.exe -s -SMS". specify "program restarts computer" in "After running" field - use it in your TS or create an advertisement... Alternatively , you can unpack the sp45248.exe and use the unpacked version in your package...

Hello, we've got quite a few HP notebooks and we are planning migration to Windows 7 somewhere in the future :) Any way i've just tested deploying Windows 7 x86 Enterprise on HP 6730b and it had no problems installing HP 3D DriveGuard as a packages: - download sp45248.exe (HP 3D DriveGuard v.4.0.4.1) to your package repository - create a package for it - create a program and use the following command line: "sp45248.exe -s -SMS". specify "program restarts computer" in "After running" field - use it in your TS or create an advertisement... Alternatively , you can unpack the sp45248.exe and use the unpacked version in your package...

Hi! I'll definitly give it a go. Never thought of actually using the file that comes from HP.. This is a x64 system, and we're going to deploy x64 only. But I guess there's no diffrence really! So, thanks for the tip - and I'll post feedback!

Hi! I'll definitly give it a go. Never thought of actually using the file that comes from HP.. This is a x64 system, and we're going to deploy x64 only. But I guess there's no diffrence really! So, thanks for the tip - and I'll post feedback!

Just tested it Mikhail, and I can't get it working. Now it just stops when running the TS and the task containing the SP and settings you gave me. Where in the TS do you have it? And what other settings do you have?

Just tested it Mikhail, and I can't get it working. Now it just stops when running the TS and the task containing the SP and settings you gave me. Where in the TS do you have it? And what other settings do you have?

I am going to try testing the 3D Driveguard out with an 8530P using what is here on this page with a bare metal OS deployment now and see what happens. I'll let you knwo what I come up with.

I am going to try testing the 3D Driveguard out with an 8530P using what is here on this page with a bare metal OS deployment now and see what happens. I'll let you knwo what I come up with.

I've had to build the Windows 7 x64 deployment first, but then i could test it...I've tested it on both x86 and x64 platforms and i can conclude that this problem is related to 64-bit OS deployment only. During 32-bit OS deployment everithing works fine.I've waited till TS whent into "Installing updates" stage and i see that when you try to run either setup.exe or sp45248.exe they both generate error "... this is not valid executable..." or something like that.Any way it fails only within TS, if you create an advertisment for this program, it'll install.By the way, which fingerprint driver do you use? The one, i've got from HP doesn't automatically install on x84 Win7 either...

I've had to build the Windows 7 x64 deployment first, but then i could test it...I've tested it on both x86 and x64 platforms and i can conclude that this problem is related to 64-bit OS deployment only. During 32-bit OS deployment everithing works fine.I've waited till TS whent into "Installing updates" stage and i see that when you try to run either setup.exe or sp45248.exe they both generate error "... this is not valid executable..." or something like that.Any way it fails only within TS, if you create an advertisment for this program, it'll install.By the way, which fingerprint driver do you use? The one, i've got from HP doesn't automatically install on x84 Win7 either...

Cheers Waynegro! Will be waiting :) I still can't get it working on Win7 x64. Running x86 is not an option for us really. But if that's a problem, then I see why I can't get it working within a TS! If that's the case, I'll just have to try it then! What file do you run as an advertisment? the SP or the setup.exe? I use DriveGuard from HP - which doesn't install. My fingerprint wasn't any problems on Win7 x64 (from HP). Installed it on a ref. machine, extracted the files needed (.ini; with double driver) and added it to the driver package.

Cheers Waynegro! Will be waiting :) I still can't get it working on Win7 x64. Running x86 is not an option for us really. But if that's a problem, then I see why I can't get it working within a TS! If that's the case, I'll just have to try it then! What file do you run as an advertisment? the SP or the setup.exe? I use DriveGuard from HP - which doesn't install. My fingerprint wasn't any problems on Win7 x64 (from HP). Installed it on a ref. machine, extracted the files needed (.ini; with double driver) and added it to the driver package.

Even with the instructions in this thread I could not get the install to work. I have also noticed problems with importing drivers for Windows 7 that cause the machine to crash during a bare metal deployment b/c it could not locate the proper boot critical drivers, which Win 7 has natively, so go figure. My approach for now is to build the machine manually and take an image of it using a custom task sequence I found on windowsnoob.

Even with the instructions in this thread I could not get the install to work. I have also noticed problems with importing drivers for Windows 7 that cause the machine to crash during a bare metal deployment b/c it could not locate the proper boot critical drivers, which Win 7 has natively, so go figure. My approach for now is to build the machine manually and take an image of it using a custom task sequence I found on windowsnoob.

Well, I'm not the only one with problems then. Trying to build a .bat doing the heavy lifting for me now. Getting pretty far into it, and I'll see what happens. Yeah, that's definitly a possibility - but how nice it would be to have just 1 image!

I found a workaround... Extract the package to a shared folder Create a run command line in the OSD tasksequence and run it under a user account. This worked for me!

I found a workaround... Extract the package to a shared folder Create a run command line in the OSD tasksequence and run it under a user account. This worked for me!

Even with the instructions in this thread I could not get the install to work. I have also noticed problems with importing drivers for Windows 7 that cause the machine to crash during a bare metal deployment b/c it could not locate the proper boot critical drivers, which Win 7 has natively, so go figure. My approach for now is to build the machine manually and take an image of it using a custom task sequence I found on windowsnoob. Slightly off topic, but I had the same issue with my HP ProBook 6455b. After digging through logs I found windows 7 x64 enterprise was marking my Synaptics TouchPad driver as boot critical. WTH is that about? Removed it from the driver pack or disabled if you're using Auto Apply and it works. Still haven't gotten DriveGuard to work though.

Even with the instructions in this thread I could not get the install to work. I have also noticed problems with importing drivers for Windows 7 that cause the machine to crash during a bare metal deployment b/c it could not locate the proper boot critical drivers, which Win 7 has natively, so go figure. My approach for now is to build the machine manually and take an image of it using a custom task sequence I found on windowsnoob. Slightly off topic, but I had the same issue with my HP ProBook 6455b. After digging through logs I found windows 7 x64 enterprise was marking my Synaptics TouchPad driver as boot critical. WTH is that about? Removed it from the driver pack or disabled if you're using Auto Apply and it works. Still haven't gotten DriveGuard to work though.

I have the driveguard running I did an install without the device and then used windows update to download the missing driver.. then I searched for the cab on windows update catalog.. I downloaded it and added it to the driver package.

I have the driveguard running I did an install without the device and then used windows update to download the missing driver.. then I searched for the cab on windows update catalog.. I downloaded it and added it to the driver package. I can install the driver through both Auto Apply and Apply Driver package. It is the 3D DriveGuard software that is not being installed in my case. I am using an HP ProBook 6455b. HP package is SP47282. I don't think your post resolves this issue. Does it? When you open Control Panel do you have HP 3D DriveGuard?

I have the driveguard running I did an install without the device and then used windows update to download the missing driver.. then I searched for the cab on windows update catalog.. I downloaded it and added it to the driver package. I can install the driver through both Auto Apply and Apply Driver package. It is the 3D DriveGuard software that is not being installed in my case. I am using an HP ProBook 6455b. HP package is SP47282. I don't think your post resolves this issue. Does it? When you open Control Panel do you have HP 3D DriveGuard?

Ahh the software yes well then you are right.. You can try to see how HP does the install using there CD.. there is a script that they run...

Does anyone know how to dig into the original setup from factory? It is installed it seems through their scripts, but not for us!

Does anyone know how to dig into the original setup from factory? It is installed it seems through their scripts, but not for us!

I got it working! Model: HP ProBook 6455b SoftPaq: SP47282 HP 3D DriveGuard v4.0.5.1 Steps I took to install the 3D DriveGuard via SCCM. Download proper softpaq for your machine (durh) Extract the SoftPaq to a directory, I used WinRar so I wouldn't need to run the *.exe Contents: amd64 x86 accelerometer.inf hpqaccamd64.cat hpqaccx86.cat Setup.exe Open command prompt to the directory containing the files Run command: Setup.exe /extract:<path to existing folder> Setup.exe /extract:C:\HP_3D_DriveGuard This extracts the Setup.exe to the specified directory. The files my SoftPaq contained were: 1028 1029 1030 1031 1032 1035 1036 1038 1040 1041 1042 1043 1044 1045 1046 1049 1051 1053 1055 1060 2052 2070 3082 disk1.cab HPMDPAI3264.msi HPMDPAI3264.mst HPMDPAI3264.x64.msi Copied these files to my ditribution point Created a new package Created a new program for x64 Windows 7 and x64 Vista only with the following command line: msiexec.exe /qn /i HPMDPAI3264.x64.msi TRANSFORMS=HPMDPAI3264.mst Note: Make sure you are using the HPDMPAI3264.x64.msi. I assume the HPMDPAI3264.msi is for 32-bit installs, but I haven't tried a 32-bit machine yet. But it does NOT work properly on the 64-bit. It showed as installed in the Add/Remove, but the Control Panel app wasn't present. Make sure you have the box checked to allow it to be installed during a task sequence. Add it to your task sequence. This worked for me installing through SCCM. I made both a silent and a user driven install that can be interacted with by the user, but only run from within windows. Both seem to be working. I am going to run a test task sequence now. Hopefully that works too! ** I may need to add a suppress of the reboot, but for now I am running the command as shown above.

Tested and confirmed this worked for my task sequence!

Great news!

MOD: Can someone mark my above answer and correct. Original posted seems to be slipping...Find this post helpful? Does this post answer your question? Be sure to mark it appropriately to help others find answers to their searches.

MOD: Can someone mark my above answer and correct. Original posted seems to be slipping...Find this post helpful? Does this post answer your question? Be sure to mark it appropriately to help others find answers to their searches.

MOD: Can someone mark my above answer and correct. Original posted seems to be slipping...Find this post helpful? Does this post answer your question? Be sure to mark it appropriately to help others find answers to their searches.

Thanks for the info Chase. I was trying to work out how to extract the exe (7-zip wouldn't do it) so your post helped a lot.

Chase, I can confirm that this worked deploying on an HP Elitebook 8740w. Great Job! This ends a LONG torturous road through the depths of the InterWebs. Will be deploying a 6550b next, so I have high aspirations!

Chase, I can confirm that this worked deploying on an HP Elitebook 8740w. Great Job! This ends a LONG torturous road through the depths of the InterWebs. Will be deploying a 6550b next, so I have high aspirations! Glad it has worked for you. It worked great on our 6555b so I assume it will for yours also since only difference is 6550b = Intel and 6555b = AMD. Good luck!Find this post helpful? Does this post answer your question? Be sure to mark it appropriately to help others find answers to their searches.