dbradtbe

I am pretty sure I have gotten this to work. Long winded approach though. First you need to start the install manually and when it stops at the untrusted driver stage look in the TEMP folder and find the sub folder that contains the extracted Clone Drive Files. Take a copy of the vclone.cat file in this folder. Cancel the installation. This may still say this has installed but the driver will not work. Just got to Add/Remove programs and remove it. Using the vclone.cat file from the files you copied right click and select properties. Select Digital Signatures Select Elaborate Bytes AG in the Signature list box. Click Details On the Digital Signature Details window select the General Tab Click View Certificate On the Certificate window select the Details Tab Click Copy to File On the Certificate Export Wizard window click Next I chose the Cryptographic Message Syntax Standard - PKCS #7 Certificates (.P7B) radio button and then ticked the Include all Certificates in the certification path if possible. Click Next Save the file to where you want to keep it. Click Next Click Finish Click Ok Close all the open windows. Now to pre import the certificate into the certificate store so that the software will install silently I used the following command line with administrative priviledges. certutil -addstore "TrustedPublisher" vclone.p7b This import the certificate that we exported before and now run setupvirtualclone.exe /S to install silently. So with a little prepartion it should be possible to completely silently install Virtual Clone Drive With these two commands. certutil -addstore "TrustedPublisher" vclone.p7b setupvirtualclone.exe /S

Not sure if it is related or may help but someone I was talking to the other day said that they where having a problem with a package they where deploying which had the same guid as an existing package and the error they got sounded very much like this error. Don't know if it will help but maybe someone can look to see if their is a guid issue for Media Center and something else that exists in Server 2008

Is the insatllation point an administrative installation. If so this will not work you cant get the cache to work from a Administrative installation point which also means that you cant slipstream the service pack into your installation files and still bea bel to cache them. You must use an original CD or a copy of the files from an original CD and then apply the service pack to the installation after the initial install is completed.

I found a missing line in the BTS_DPs_ATI_Mobility.INF file the ATIVCOXX.DLL list is missing in the [sourceDisksFiles] section and you are prompted for a location for the file when trying to install it. All you need to do is add the following line to that section of the file ativcoxx.dll=1 David Bradtberg

You will need to put the new INF and SYS file for the driver into the i386 folder for your source OS on your RIS server and then stop and start the BINLSVC on the RIS server. This is to cause the recreation of the PNF files on the RIS server. I have just finished doing this at work this week. I also found that I have to edit the INF file to take out any references to to a B57w2k.sys and replace that with B57xp32.sys otherwise it will complain about an error in the B57w2k.sys file which doesn't exist anyway. I downloaded the latest drivers from Broadcom and used them when I did this.

Sounds great Bâshrat look forward to it. About the only other Video driver that I have in my collection is the Intel video drivers.