Endpoint Protection

Is there a way to identify if a 64 bit machine was installed with a 32 bit package?

The install would fail and it would give you error messages in the SEP install files saying that its's the wrong installer.

We use SCCM so, it does not reject the installation. It goes thru with the installation but updates fail.

use the naming convention on package while pushing to 32 bit OS and 64 bit OS.

Pete, we don't control the installation, it is done by the SCCM guys. apparently there are a few 64 bit machines where i suspect a wrong package was pushed. I couldn't check with the local SCCM team. So i thought there might be a way to find out what was actually installed after the installation.

the MSI Product code is different for the 32 and 64 bit versions of the client.  Just search the "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\" key for the relevant entries.

It is my understanding that every package has a unique pdt code. So since this package was pushed to a set of machines, all the machines will be having the same pdt code, right?

So you'll be searching the registry of your 64bit machines for the product code of the 32bit sep client

But i should know the pdt code of 64 bit right? This is a package that was created long back and sent to the local team. So we do not know where they have installed a 32 bit package to compare it with :(

I was actually hoping for a simpler suggestion like a registry entry or a driver process information......

...for the comparison yourself.  If you still have the original package handy you can grab it from that.

I can't seem to find any kb article with a list of the SEP Client product codes, maybe contact Symantec Support to see if they have a list handy?

when you create apackage from SEPM you get the name in this fashion, default being the group

"My Company_default_WIN32BIT", which will identify which package it is the compatible with.

As mentioned, these were given to the local teams long back, before my time, so no chance of knowing what it is.

So there isn't any way you can tell if the package is 64 / 32 bit after installation!

Just an idea ...

If SEP_INST.log exists, at the begining of the file there should be a line something like this:

32-bit:

******* Product: C:\Programme\Symantec\Symantec Endpoint Protection\12.1.1000.157.105\Bin\SmcLU\Setup\Sep.msi

64-bit:

******* Product: C:\Windows\Temp\Symantec\Sep64.msi

is it single exe file?

can you extract and check for a file setaid.ini 

PlatformType=WIN32BIT

Unfortunately, no log file

Pete, I don't have the setup file.

Neither in %TEMP% nor in %WINDIR%\Temp?

Yes. And if it may help it is a Win 7 VDI.

you may ask the team whom you are in touch with for this setting.

You can check the drivers in the registry of the client machines to verify whether a SEP client is installed in 32 or 64bit.

SEP 32bit:

HKLM\SYSTEM\CurrentControlSet\Services\SRTSP

ImagePath: System32\Drivers\SRTSP.SYS

SEP 64bit:

HKLM\SYSTEM\CurrentControlSet\Services\SRTSP

ImagePath: System32\Drivers\SRTSP64.SYS

Thank you.

you will get to know only if it is installed, since your question was answered first by Simpson you should be marking his answer as a solution :-).

Pete. That is the whole problem. It is installed and there is no way that i can find out what is installed.

if the OS is 64 bit then the 64 bit package will be installed similarly for 32 bit, which i think has been answered by Simpson.

You did not understand the issue at all then. We push the package from SCCM & the installation goes thru without issues. 32 bit package on 64 bit machine and vice versa. Then the upgrades fail. 

So i wanted to know if there is a way to identify this after the installation went thru.