Software Deployment

Anyone from Cisco reading this, kindly respond guys.Best laugh of the day so far, thank you.

I believe you can use the same inf taken from C:\ProgramFilesFolder\Cisco\WaveDrivers as i mentioned above. Now this is the only driver needed for this app. Just follow these steps,

1. Copy the entire WaveDrivers folder with everything in it, ie, .sys,.inf etc to your project directory.
2. Now Edit the [Version] section in the oemsetup.inf file by adding CatalogFile=<YourCatFile>.cat. You can copy the inf below:

[Version]
Signature="$WINDOWS NT$"
Class=MEDIA
ClassGUID={4d36e96c-e325-11ce-bfc1-08002be10318}
Provider=Cisco
DriverVer=10/01/2007,5.1.1.7
CatalogFile=AVAudio.cat

[SourceDisksNames]
1 = %DISKID%,,,""

[SourceDisksFiles]
avaudio.sys=1,,
avaudio32.dll=1,,

[DestinationDirs]
CiscoWave.NT.CopyFiles.User = 11
CiscoWave.NT.CopyFiles.Kern = 12

[Manufacturer]
%Manufacturer%=Cisco

[Cisco]
%DeviceDesc%=CiscoWave

[CiscoWave.NT]
AddReg=CiscoWave.NT.AddReg
CopyFiles=CiscoWave.NT.CopyFiles.User,CiscoWave.NT.CopyFiles.Kern

[CiscoWave.NT.Services]
AddService=avaudio,0x2,CiscoWave.NT.ServiceInstall

[CiscoWave.NT.ServiceInstall]
DisplayName = %ServiceName%
ServiceType = 1
StartType = 3
ErrorControl = 1
ServiceBinary = %12%\avaudio.sys

[CiscoWave.NT.AddReg]
HKR,Drivers,SubClasses,,"wave"
HKR,"Drivers\wave\avaudio32.dll", Driver,,avaudio32.dll
HKR,"Drivers\wave\avaudio32.dll", Description,,%DeviceDesc%

[CiscoWave.NT.CopyFiles.User]
avaudio32.dll

[CiscoWave.NT.CopyFiles.Kern]
avaudio.sys

[Strings]
Manufacturer="Cisco Systems"
DeviceDesc="Cisco Unified Communications Manager TSP Wave Driver"
DISKID="Cisco Audio Driver Installation Disk"
ServiceName="Cisco Audio Driver Service"

3. Run the inf2cat tool and you should get the avaudio.cat file in the project dir. ignore the missing hardware id warning.

Please follow these steps and you really shouldn't get any errors. Let me know if you still have them errors.

How do u do it manually?

Do you mean adding the CiscoTSP to the List of Providers in Phone & Modem Options in Control Panel?

Your contact with Cisco will be fruitless. If they're distributing unsigned drivers for software which is almost by definition solely destined for corporate distribution, asking them for a signed version will be like asking if they would mind moving the beach closer to your home. Of course, that shouldn't stop you sending a strongly-worded, mocking letter to your sales contact, enquiring exactly when they're likely to catch up with technology which is almost 15 years old. Anyway...

Sign the driver yourself and package that. There's plenty of detail in other posts here on AppDeploy on signing drivers.

Actually installing the setup does not install the drivers. The finish dialog mentions a text file to be read which provides the steps for manual installation of the drivers. Since it is an unsigned driver the only think I feel is to sign them, as Ian rightly pointed out.
I dint expect to hear from Cisco anytime soon which made me post this.

Anyone from Cisco reading this, kindly respond guys.

Cheers

I have just repackaged the application, created a valid catalog file for the driver and installed it using IS Device Driver Wizard earlier this week and it has been tested working by the application owners.

The only extra step you need is to pickup the driver file installed with the original setup from C:\ProgramFilesFolder\Cisco\WaveDrivers and then follow the simple steps below:

1. Edit the [Version] section in the oemsetup.inf file by adding CatalogFile=YourCatFile.cat
2. Create the catalog file using Inf2cat tool
3. Create a standard certificate if you have one yet using MakeCert
4. Wrap the certificate into a PKCS #7 Software Publisher Certificate (SPC) using Cert2Spc
5. Sign the catalog file using signcode tool
6. Install the certificate during package installation and remove it on removal using CertMgr tool.

I can'y give detailed step by step info here but you may have a look at other posts here on Driver Signing and it involves a lot of reading as well. Not to forget that there's a loads of information in MSDN as well. AngelD has got a lot of posts with regards to Driver Signing and Packaging like the one below

http://itninja.com/question/how-do-you-roll-out-new-machines?0873&mpage=1&key=Sign,Driver

Hi

I used the INF2CAT.exe to create the catalog file. However i get the following error -

Signability test failed.
Errors: No installation INF found in the root path of the driver. For the driver to be digitally signed, and for it to install properly the installation inf must be in the root of each driver path you have provided. If you have separate folders with different driver packages for different languages, operating systems or device categories then specify each driver set as a separate driver. Each driver package must be selected separately and must contain an installation INF.
Warnings: None

I have used the msdn command line and provided the path of the directory that holds the .inf file. The package is installed. Is there something I am doing incorrectly or something more than I need to do something more?

When it comes to software for Cisco phone systems I suspect that there budget was about $20. Hardware is pretty good but there software blows. I nominate Cisco CTIOS 7.5 as the worst piece of software to come my way. It was a legacy InstallShield setup 1.2 GB in size including additional legacy InstallShield updates. Repackaging into a final msi of 26Mb. For some reason the vendor thought it best if they deploy a setup.exe installer for each component into the program files folder and all updates backed up all files in new folders in Program Files as well.

This is the command I use when signing unsigned drivers:

[font="arial, sans-serif"]Inf2Cat.exe /driver:”path to folder containing inf and driver files” /os:XP_X86 /verbose

The standard command to create a catalog file out of the inf is as follows:-

Inf2Cat.exe /driver:"<Path to driver files>" /os:XP/Vista_x86/x64 /verbose

Let's say we are creating this driver for Vista, the command would be

Inf2Cat.exe /driver:”<path to driver files folder>” /os:Vista_x86 /verbose

Note that the driver path is the folder path containing the INF and not the direct INF path itself. Let's say the inf is located in "C:\Users\Public\Drivers\yourinf.inf" the command would be

Inf2Cat.exe /driver:”C:\Users\Public\Drivers” /os:Vista_x86 /verbose

I did use the command line specified on msdn and it works for creating a catalog file for another driver that I have installed on the machine. That means that the command line i use is okay however the contents of the setup inf file may be not.

Then I opened the inf file in 'C:\Windows\Inf' for the same driver and copied the contents in the oemsetup.inf file that is used to create the cat file. Now i get a new set of errors and warnings.

Errors:
22.9.4: Missing 32-bit CatalogFile entry (CatalogFile.ntx86, CatalogFile.nt, Cat
alogFile) from [Version] section in \oemsetup.inf
22.9.6: DriverVer missing or in incorrect format in \oemsetup.inf
Warnings:
22.9.3: Missing hardware ID (cannot have just compatible ID) in line %soundsys%=soundsys in section [olddrvs] of \oemsetup.inf

Has anyone encountered a similar situation with a driver package? I am currently doing a trial and error with the .inf file.

Cheers

Good one Harjinder. Thanks a ton. I used the inf that you posted and it worked. However there are a couple of changes that I see from the setupapi.log and the information that goes into the inf file that you provided. I dont know whether that it is a point of concern but will look into it in detail.
I am going to proceed with rest of the package simulataneously. However you have created many new sections in the setup .inf file which werent present in the one that was put by the setup. I had been trying to do the same and getting many different errors and warnings. Did you follow any specific method for this?

Cheers

the version that I worked with was UnifiedCallManagerTSP_5.1.1.602. is your's the same? I didn't change anything in the original INF other than adding the line for the catalog file. If you're to edit the INF, always use the /verbose switch which tells u what went wrong and there's lot's of reference on the net for the solution to these errors.

I am working on version 3.1.0.3 and in this case the .inf file was almost empty. It did not have any details about the sections that you mentioned in your .inf file. Actually I populated the .inf by looking at the setupapi.log file. Couldnt get the correct format until your provided me with your .inf file. I have changed the details according to my application.
But here is where I m stuck. I have a .cat, .sys and .inf file so do I go ahead and create a certificate or ask the client for the same. The .cat file that we created using the INF2CAT is an unsigned file which needs to be signed to go ahead with Difx. Any other way to do this?

the INF2CAT is an unsigned file which needs to be signed to go ahead with DifxWhy is the sentence "Sign the driver yourself and package that." rolling round in my head? It'll come to me in a while...

Ian, you have got me wrong. I am following the procedure by MS to create a certificate and then sign the catalog file using SignTool. However I am facing errors for which I am not getting many cues on the internet.
I have created a certificate added it to the Trusted Root but signing the file is giving me errors like 'SignTool Error: File not found:'. Hence all I wanted to do was to confirm, if I must go ahead the way I am or reconsider this solution. Kindly let me know in case you have any suggestions.

I think most people have abandoned SignTool and are using INF2CAT. Remember to specify just the INF's parent folder as the argument, not the INF file itself.

ORIGINAL: VBScab

I think most people have abandoned SignTool and are using INF2CAT. Remember to specify just the INF's parent folder as the argument, not the INF file itself.


i think those 2 serve 2 different purposes....SignTool to sign the catalog file and Inf2cat creates them from INF. SignCode is the one replaced by SignTool....but still my preferred tool for signing catalogs...

Anyway...Rajit, try this after u have generated the cat file...

I believe you have already created the certificate and has it in the same folder with Software Publishing Certificate (SPC) and Private Key (PVK) files.

SignCode is the tool used to sign catalog files using following command:-

Signcode.exe -spc <path to spc file> -v <path to pvk file> -t http://timestamp.verisign.com/scripts/timstamp.dll <Path to catalogfile>

You will be prompted to key in the password for your PVK.

I have created the Signed catalog file and also cross checked the same using DPinst tool. However when I added the catalog file and Difx MM to the package it does not work. It gives an error for the MSIProcess Drivers. The .cat, .sys, and .inf are in different components. I have also populated the MsiDrivePackages with the name of the component that houses the inf file and flag set to '0' and sequence to null. There is no entry in the setupapi.log file which indicates that the driver isnt installed and ofcourse it does not appear in the Device Manager tab. Is there something I doing incorrectly. Also I have noticed that adding the Difx the MsiInstallDrivers & MsiUninstallDrivers action is not sequenced.

Any ideas?

I haven't messed with WPS for sometime but here's a few links which may help:-

http://www.symantec.com/connect/articles/how-package-signed-device-driver-using-wise-package-studio
http://itninja.com/question/faulttree-103803

i think it is pretty useless to reply to a more-than-2-year-old post!

Kards, this is just another loser whose idea of marketing is to spam a forum about application packaging. Just report posts like this to Bob.

oh yeah. i see that now.

monday morning, uh?

i'm out for a coffee now!