Video Screencast Help

Forgot to put the 64 bit SEP client package into the Install Package tab

Created: 05 Feb 2013 • Updated: 05 Feb 2013 | 18 comments
This issue has been solved. See solution.

Hi All,

I realize that I forgot to put the 64 bit SEP package into the Install package and now I am afraid that my 64 bit server is now using the 32 bit client :-\

so what I'm supposed to do ?, the Client version is now showing uptodate 12.1.2015.2015

Comments 18 CommentsJump to latest comment

.Brian's picture

If the server has the 32 bit SEP installed, you will need to uninstall and re-install using the 64 bit package.

Just to note, 32bit can install on 64bit OS, although you would get optimum performance by installing 64bit on 64bit OS. But it won't hurt anything by leaving 32bit on 64bit OS.

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

Ashish-Sharma's picture

You can auto upgrade 32 bit to 64 bit

You can assign a 32-bit and 64-bit package to the same group when you do an auto-upgrade and both clients will automatically upgrade. You don't have to create separate groups for 32-bit and 64-bit clients.

Check this thread

https://www-secure.symantec.com/connect/forums/wrong-sep-client-installed-64-bit-server

Thanks In Advance

Ashish Sharma

 

 

SOLUTION
.Brian's picture

He is saying he already upgraded to the latest version but used 32bit package instead of 64bit.

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

John Santana's picture

Hi @shish,

I have now put the same version of 64 bit package into the Install package tab, hopefully they are goingh to be upgraded into 64 bit.

Kind regards,

John Santana
IT Professional

--------------------------------------------------

Please be nice to me as I'm newbie in this forum.

.Brian's picture

John,

Can you let us know the outcome of this?

Of course you can upgrade from 32 to 64 if your on an old SE version but since you were on the same version already, I don't believe it will upgrade from 32 to 64 already being on the same version.

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

pete_4u2002's picture

the clients are intelligent enough to take the package required by it. only 32 bit OS sysytem running SEP client will be upgraded.

.Brian's picture

But if he is already on the latest version as he said? So it can still update 32 to 64 even already being on same version, 32bit 12.1.2 to 64bit 12.1.2?

Never saw that before. Was always told to uninstall and reinstall when the wrong architecture was installed.

I already know you can upgrade from a lesser version to a newer version (ie 32bit 12.1 RU1 to 64bit 12.1.2) but the install should detect it is already at latest version and exit.

 

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

MASH1's picture

Hi John,

 

If a machine is 64 bit then only a 64 bit package will work on it .If you try to install a 32 bit it will not allow you to do so. It depens on the PlatformType while installing any product.

You will face an error as below.

This version does not support 64 bit Platforms.Please install Symantec Endpoint Protection for Win64 instead.

You dont need to worry as 32 bit package will not work on 64 bit OS. 

If you still want to confirm open SEP_INST file from %temp% and you will be able to find that a 64 bit platform software has been installed.

- MASH

- MASH

.Brian's picture

I've "accidentally" installed 32bit SEP package on a 64bit OS in the past and it still worked? I'm not sure I understand this

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

SebastianZ's picture

hmm... would this work at all? - I thought the installer will not allow 32bit package install on 64bit OS.

John Santana's picture

I don't know Sebastian, somehow they're all upgraded successfully :-| ?

Kind regards,

John Santana
IT Professional

--------------------------------------------------

Please be nice to me as I'm newbie in this forum.

.Brian's picture

Why would it not? 32bit will install sucessfully on 64bit, just not 64bit on 32bit

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

SebastianZ's picture

Well, I am affraid you are wrong here. Just tried to install a 32bit package (12.1 RU2) exported from SEPM on a windows 7 64bit and the installer fails at the beginning with error:

"This version of Symantec Endpoint Protection does not support 64-bit platforms. Please install Endpoint Protection for Win64 instead"

.Brian's picture

Ok than explain to me how I have a 32bit version of SEP running on 64bit XP, Vista, and Windows 7?

 

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

SebastianZ's picture

I don't know:D ...simply saying I am not able to install such 32bit package on 64bit OS.

btw. where do you see it is 32bit?

.Brian's picture

No worries cool I think he got he answer he needed.

In the past, our techs accidentally installed 32bit SEP package on a 64bit system. I got a call about what to do and it was simply "uninstall 32bit and reinstall with 64bit"

Now to be fair this was with SEP 11.x. But also, maybe the tech was mistaken? I really have no clue at this point since it was some time ago.

I don't have the ability to check what SEP architecture (32 or 64 is installed) other than looking in the SEPM to see what architecture the OS is, in which case I just assume it is 32 or 64.

Either way, I'm going on what our tech said so it is just word of mouth.

It's fine, it is solved so no biggie. I'll try to find a 64 bit box and try to install the 32bit version and change my procedure if I have to.

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

John Santana's picture

Brian, what I mean is that I only assign the 32 bit install package into the group of server in production :-/ so now they are all uptodate with 12.1 RU2.

Kind regards,

John Santana
IT Professional

--------------------------------------------------

Please be nice to me as I'm newbie in this forum.

.Brian's picture

Yes but as you said, the machines are 64bit correct? So now they have the 32bit SEP package on them instead of the 64bit? right? Am I reading this wrong?

What folder did it install to?

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.