Scripting

Kim, I originally posted a reply to the effect that it could probably be captured. Then I had a vague recollection that certificates put a huge binary string into a registry entry and that the string is different for every user/machine and would thus be no good. So, I deleted my original post. Then I did part of the OP's work and Googled for 'vbscript +".pfx" '. The first hit (I think) was the Chilkat site but pretty close was an MSDN post about that script.

Max, given the absence of any volunteers for script-writing, it looks like you're going to have to do it youself, something you'll probably have to get used to. I posted a similar request for a script to concatenate .REG files into one. After a couple of days of no replies, I realised no-one had such a thing and rolled my own. It strikes me that a d/l of the SDK would probably provide a shell script which you could adapt.

My reading of http://msdn2.microsoft.com/en-us/library/bb394689.aspx suggest that you cn donwload an SDK and within that find a sample script, enrollSimpleUserCert.

Alternatively, since you're willing to pay, there's a component available from Chilkat http://www.example-code.com/vbscript/ImportPfx.asp

I did try to capture the import of the .pfx certificate to see what changes are being made and it comes up with 2 files so to check i copied those 2 files on to another system and tested. The results did show that the certificate was available in IE certificates, but it fails when i try to go to the secure website it's for.

Can someone please write me a vbscript that would install this .pfx and i will pay for it.

What is wrong with the methodes Ian (VBScab) gave you?

Use the script from http://www.example-code.com/vbscript/ImportPfx.asp and add it as an custom action or Active Setup.
Pay for the ActiveX (ChilkatPfx.ChilkatPfx) component

Hello,

I need a VB Scripts that Wraps an exe and suns it in silent installtions and at last displays a message that state "Installation complete". and also need a script to uninstall the application..

Hello I need a vbscirpt to wrap a .msi which installs to a local system and also could be used to deploy the app via SMS.

Thanks

Why do you need a script to do either of those things? A command line which passes arguments to MSIExec.EXE is all you need.

Not even that - with SMS, you can even point the "program" inside of the package to the MSI file directly - SMS will handle the command line/switches for deployment...

The reason why I am doing in such a way is because while deploying the package via SMS it is not recognizing the specified drive say(X:\), which the package looks for, and giving me an sms error message 1327. which could be anything. But if I run it manually the package works fine. So what I am trying to do is somehow transporting the .msi to the local machine's TEMP folder and run it locally so it gets installed without having to deal with the X:\ issue. And local install just works fine.
I have a script to do it as well:

Set FSO = CreateObject("Scripting.FileSystemObject")
FSO.CopyFile "software.msi", "c:\windows\temp\" ,True
FSO.CopyFile "softwareSecurity.EXE", "c:\windows\temp\" ,True
Set WshShell = WScript.CreateObject("WScript.Shell")
Dim msi
Set msi = CreateObject("WindowsInstaller.Installer")
msi.UILevel=2
msi.InstallProduct "c:\windows\temp\software.msi", ""
WshShell.Run "C:\windows\Temp\softwareSecurity.exe /qn", 1, True
Set WshShell= Nothing
This don't do the job either as far it goes is transporting the files to the TEMP folder but not installing for some reason.
This is the issue I am facing.

Thanks for the Help!

The reason why I am doing in such a way is because while deploying the package via SMS it is not recognizing the specified drive say(X:\), which the package looks for, and giving me an sms error message 1327. Some basic understanding of Windows systems would be in order here. Most deployment mechanisms use the local System account to run the installer. That account has no concept of networking, much less any network access so any reference to non-local drives will cause the install to fail.

In the latest case outlined in this thread (why DO people insist of resurrecting old threads?), some thought needs to be exercised in working out why the package needs to be reference network resources. My guess is that it contains a shortcut pointing to a network-located EXE. In that case, switching the (probably) advertised s/c to a simple .LNK file would work round the issue, rather than over-complicating the install with ill-conceived and poorly-written script.