Friday, July 22, 2011

HOSTS file entries don't apply in bubbles

Applications do not use the hosts file directly.  The hosts file is read by the TCP/IP subsystem which is running OUTSIDE the bubble.

Putting HOSTS files in the bubble and setting to override in an attempt to set name resolution will NOT work.

Thursday, July 21, 2011

Formatted Text

When using formatted text strings to reference other items within an MSI install table be aware of case.  A reference to [#filename.txt] is not the same as [#Filename.txt]

http://msdn.microsoft.com/en-us/library/aa368609(v=VS.85).aspx

This page refers to the correct method to write an environmental variable into a registry key.

e.g. [%environmentvariable]


Tuesday, July 19, 2011

Certificate Installation

The following command installs a certificate to the specified store on the local machine.  In this case the .cer file and certmgr.exe were in the same folder.

certmgr.exe -add -c certificatefilename.cer -s TrustedPublisher -r localMachine

I tried lots of variations but was unable to get certmgr.exe to delete a certifcate from a store using various parameters after the -del switch

Certutil.exe is a server utility but it does work on clients as well.  Example usage adding and removing certificates from stores is:
Adding:
certutil -addstore Root certificatefilename.cer
or
certutil -addstore TrustedPublisher certificatefilename.cer
Removing - first find the certificate serial number by viewing it withing the certificate management gui. Provide the serial number to the command line
certutil -delstore Root SerialNumber
certutil -delstore TrustedPublisher SerialNumber

Certutil.msc for user certs
certlm.msc for machine certs

Monday, July 4, 2011

Simfund Client - MSI Package

A main installation executable creates a temp folder containing the installation resources including an MSI.  An Installshield engine is also installed at this time.  Within the temp folder is an si_install.txt file which gives hints on how this can be installed silently.  Attempting to create a direct transform of the MSI file for installation was not possible which seemed to be due to the interoperation of the simfundclient.exe (setup.exe) and the vendors MSI custom actions.  Certain choices during the installation can be set to copy (possibly large amounts of) data from a network location to the client.  This can cause the installation to take a long time.