any ideas on this one? i'm still stuck with this after the upgrade. i'm tempted to just rebuild the server at this point because i've found no way to fix it. updating to 6.9 sp1 has caused us all sorts of little bugs like this - i'm tempted to think that if i build a 6.9 sp1 server from scratch maybe some of these issues won't show up......



help?

There is another thread that deals with this same topic from a different direction. It seems like the MP1 doesn't update bootwiz.exe to the newest version that should fix the problem with adding NIC drivers. I've asked Altiris about it already. Once I get an answer I'll post it here.

Have you installed MP1? That seems to fix this problem.

what is mp1? there was some hotfix i installed that was supposed to resolve the issue, but I don't recall it being named Mp1...

AKB 44867

Thanks Anthony...i'm going to download and try that today!

You're welcome. Post back if that works.

i'm hoping it fixes that, and the other issue i'm now having with trying to create a WinPE 2.1 boot where it just stops once WinPE loads....i'll let you know - testing shortly...

now i'm getting an error message trying to start DS:



"There are no Database Management Services registered. Please make sure the Deployment Server Database Management Service is running".



So I checked...and it wasnt, but weird thing is - it changed 3 of the services to use my login account for some reason after installing MP1:

'Altiris Deployment Server Data Manager'

'Altiris Deployment Server DB Management'

'Altiris eXpress Server'



so I switched them back to local services. started them up, tried again and got the same error message. I restarted the server, check the services were running, tried again - same error message. So at this point i'm completely broken. I did take a snapshot if I have to roll back, but i'm hoping this might be something simple to fix?

That is very strange. I didn't have any problem with MP1. It installed fast and I'm not even sure if the services restarted.

Hopefully rolling it back will at least get you up and working again.

Ok...i found the issue. The services that it placed my name in - the password was not correct, so it did not connect to the SQL database. I switched it to a master sql access account login and now it's working. Only needed 2 of the 3 set that way - the eXpress Server obviously doesn't need that...



so NOW i'll try to do the testing for the original issue and let you know :-)

Issue #2 - now none of the agents are reporting back. I tried updating the agent on 2 machines, and they still won't report back. restarting the Client service doesn't bring them back either.



this mp1 patch is causing more trouble than it's worth at this point. unless I can get this fixed i'm not even going to try testing...

nevermind...that was because of the eXpress Server service....i didnt think that one had to have the same login, but apparently it did.



now i can really REALLY actually finally test.........i think....

ok, so after all of that, i tried and still get the same message 'Boot Disk Creator could not add the driver xxxxx'



Not good...not good at all...



any other ideas? :-)

I'm having this problem too, seems no matter what driver you try to add to to Boot Disk Creator, it never appears in list! Is this ANOTHER bug in Altiris??

Sorry Anthony, but I applied that patch and it did not fix the issue unfortunately. We're still stuck as is and at this point i'm probably going to end up having to rebuild the server once our facility moves unless someone can come up with a resolution...

I know after I applied MP1 it seemed like the drivers weren't being added but they actually worked when I tried to image a computer that needed the driver.

did you get that error message...or it just worked?

After MP1 I didn't get that error when adding a driver but the driver also didn't show up in the list after I added it so it didn't seem like it was working. But when I tried to pull an image after I had added the driver it worked.

Hi,

I followed the advice of Cobra7 about installation of a LM82567 network driver.   Extracted the Intel file and tried to add them using the Boot Disk Creator of Altiris Deployment Server 6.9.

When I add the files, I point in the browser to the file "e1k6032.inf" and the Boot Disk Creator shows that it contains the information for the Intel LM82567 -driver.  Then I click OK and don't get any message but the windows closes. 

Then, it seems that the driver has not been added.  When I go in
.\Deployment Server\Bootwiz\Platforms\WinPE2\x86\Drivers\CUSTOM\Drivers

...I can see that a new folder has been created called "e1k6032" but it only contains one file called "e1k6032.txt".  Source files for the drivers are not copied to the folder and the file only contains the following header but no information about the driver files:
[MAIN]
OS=WINPE 2.1
PROCESSOR=X86
NAME=e1k6032
DATE=2009/03/26 13:09 UTC
SOURCE=USER

So, it seems that the driver does not get included in the WinPE configuration....same problem i think.

Anyone who knows why it doesn't work?

DS is now running 6.9.355

Thanks a lot!

I installed the MP1 and it works now.  The Source files are also added to the CUSTOM -folder like required.

Only did get an error on the PxeCfgService.exe -file during update but everything was functioning fine after...

I seem to have to restart the PXE services a couple times after I update my PXE Boot Disks since going to MP1. PXE just doesn't seem to respond right after updating. Not sure whats causing it but a couple restarts of the service and I'm good to go.

Well, I rebuilt the server from scratch, new DB, fresh base install of 6.9 SP3 and guess what.  Same problem!!!

Doesn't work for NIC, SATA, RAID, anything.

So now what?  I'm assuming that a base install of SP3 supercededs installing MP1, but if not, someone let me know and i'll install it on here.