Deployment Solution

Hi

we using ITMS 7.1 SP2 and deployment solution 7.1sp1 MR1

In that we found drive database management deployanywhere showing empty but in task handler driver DB is present

Please check the driver list by refreshing the page , either use the refresh button or close and reopen the DS console , you should see the list ;

If you still don't see the list add any driver and see now if you can see the list.

Let us know your observation.

Hi

I am trying to load drivers but i am not able to browse inf files

You will not be able to see INF files when you browse for driver import; You could only see the driver folder and you need to import a driver source folder.

If you still see an issue , by following above (second comment) , i suggest to restart the NS server and see if you can have the driver list.

No. This i done several time. no any change

What size is drivers.manifest.txt?  It's found within the DriversDB folder within the Deployment Task Handler folder.  Check this KB:
http://www.symantec.com/docs/TECH182708

I have the exact same problem. I had over 350 drivers in the DeployAnywhere driver database. But after adding an audio driver, this seems to have corrupted it and now it just says "No data to display".

The drivers.manifest.txt file is 432 KB in size and appears to contain all the drivers.

A reboot of our NS server did not resolve the issue.

This problem now renders our imaging solution completely useless as the Deploy image step now fails every time it gets to the driver injection part.

An urgent fix would be appreciated.

If the driver database shows empty, this is generally because the manifest file is also empty.  Generally, we've seen this when Package Services have been installed on the NS.  If you have Package Services installed on the NS, please remove it, then launch the console again and try seeing if it will re-generate the manifest file.  Every time you hit that page, it should generate a new manifest file.

If either that is NOT the issue, OR it still doesn't work after removing the package services, check the logs when you hit that page to see if you're getting errors, and unless you can quickly solve from there, I suggest calling support.

At least, that's a short answer.  :D  Or you can keep coming here of course.  :D

Hi Thomas

We will be raising a support call with Symantec today, we just wanted to exhaust all simple fix possibilities first. Our NS server only has Task and Monitoring services running on it.

As a quick update to this thread, last night I tried renaming the drivers.manifest.txt file to -bad to see if I could get it to regenerate a new blank one. I could at least then start to populate the drivers again, even if I did have to start from a clean slate.

Strangely though, Altiris did regenerate the file, but it regenerated it full of drivers. In fact the file size ended up being bigger than the old one that I had renamed.

No effect on the console though, still said "No Data To Display". Also my image deployment tasks also continue to fail right after the ghost image goes on, presumably at the driver injection part.

Will check the logs on the server shortly for any clues.

Can you check the size of the list.xml file which is located in NScap\bin\win32\x86\deployment\driverslist on the Notification server,If its 1kb the drivers list may not get populated.

No the driverlist file is not 1kb its 584 kb

Hi 

Yes exactly i am facing same. See the screenshot

There's rumor's of a single driver that does this - that is, that if you add a driver of a single type, it's known to have this effect, though I've not personally seen or documented it.  What drivers, if any, have you added - or is it too many to list?  ;-)

If imaging fails right after Ghost lays down the image, turn off DA.  Does it work?  If so, we have some work-arounds for DA that may be possible just to get you by until we know what is making the console not see anything.

Finally, if we KNOW that DA is failing, we can take steps to troubleshoot that.  For instance, in the samples posted, there are instructions to run DA manually.  Also, when you run DA as part of the job, it builds a BAT file you can capture and modify to run in the root of X.  Pulling out parts of this can help isolate the problem.  for instance, you can pull out the critical, or non-critical drivers, to see if either makes a difference.  OR you may find that running DA stand-alone works but not with the job, or ... whatever.

Some thoughts.  Keep us posted to what you discover from the case, OK?

Hello All

I check drivers.manifest.txt file it was 1KB. I replace that from different NS server size of 345KB and restarted NS server it will reserve my problem.

Now I am able to see Driver Database Management Deployanywhere and Preboot drivers over there.