Endpoint Protection

after cacheing RU5 to install over MR4, smcinst.exe does not want to launch the install of RU5. No logs etc. have been created, all I have to go from is an SMCINST.exe error 1063, after running smcinst manually

any ideas?

Stewartk

Normally the logs for smcinst.exe are created in %installdir%\SmcLU directory.  There should be a smcinst.log

isnt sep_inst.log file not generated, if you find post the logs here

Seems the SmcLU directory is empty

What I'm looking for is what criteria smcinst.exe uses to launch the RU5 install. No MSI logs are generated, as the install never gets launched.

smcinst.exe will work when you use autoupgrade only; how are you upgrading your clients?

Hmmm ok,    Verify the config.xml on the client, you should be able to open the file and see if it has the version data for the new package. Its in the symantec endpoint protection folder.

run the install manually on one client check if that works;
make sure you have assigned 32 bit pacakge to your group of 32 bit os only; it wil not work for 64 bit
http://service1.symantec.com/support/ent-security.nsf/docid/2009101503293948?Open&seg=ent

The package will install when run manually, but not when initiated through the SEPM console

Hi Koosah, the config.xml has the new version to be installed, the new install is downloaded from the SEPM console, smcinst.exe seems to launch, but never initiates the locally cached install of the new client.

May want to check that as well...

FW would not prevent the install from happening if it is already cached!

k_o

Sounds like the launch criteria for SMCINST.EXE needs to be known.... have you opened a case w/ Symantec?

k_o

I/we have established communication with Symantec about this, but they have to run some "tests".

Somehow, smcinst.exe has a set of criteria it has to pass in order for the cached install to run. So, what I need to know is what smcinst.exe is looking at/for before it determines all is go for launch. If I can find that out, I might be able to <jedi mind trick wave> "these arent the criteria you are looking for, move along" </jedi mind trick wave> kinda thing

smc should tell it to launch; thats how it knows that a latest version is available.

If I read correctly, that's what StewartK is trying to find out; what is the criteria for SMCINST.EXE to launch and handover [the install] to SETUP.EXE to lunch the install process?

Koosah, do you have insight?

"Exxxactly"

Hi Koosah, is the criteria that SMCINST.exe uses to determine if the install should procede documented anywhere?

 

Thanks

StewartK