the 64 bit package from the XP client should work with it the same way . Let us know. I don't forsee you need a new package.

Why are you suggesting to upgrade to MR4 MP1...because this is a Vista client and you know that release works with Vista...?

Thanks

 You will have to use the same package 32 bit for ( 200,2003,XP,vista,2008 ...works with windows 7 as well.)
64 bit package the same thing which ever OS you deploy it does not matter.

It was in SAv 10.x that for vista symantec came out with a diffrent version 10.2 ( for 2008 as well)

But in SEP 32 bit packages work on all 32 bit and 64 bit packages work on all 64 bits.

If you are just using AV/Aspy and it is working flawlessly then there is no need to upgrade.
Only if you plan to have WIndows 2008 you can not use 11.0.2020 as win 2008 was only supported after 11.0.3000

hi,

Ken might have suggested to have the latest build becuase it contains fixes for earlier versions.

However answering to your query

Anyway, we just acquired a 64-bit Vista client --- can we use the same client package that we used for the 64-bit XP clients (called WIN64BIT in package name column)?
The same installation package can/should be used. Since SEP supports 64 bit win xp/vista/2003 (not 2008 - since its MR 2).

Also we have a Windows 2003 member Server - should we just choose the WIN32BIT package or is there a separate server package?
The installation package is for all flavor of OS ( exception for 32 bit client package and 64 bit client package). If win 2003 member server is using 32 bit OS the same installation package will be used.

I too suggest go for latest build :-)

Cheers
Pete

Thanks Pete for the clarification and direct answers.

Do you know if we have to run the setup manually on the Vista client or can we push it using the Migration/Deployment Wizard?

Typically we go with the latest build on any product but we are hesitate to do so with SEP since we have not had any issues with the build we are using and it is not reliable when it comes to upgrades, etc.

The actual build is at MR4 MP2, and I would suggest using that one over the MR4 MP1a build. 
There was some initial problems with MP1 build and they created a second packgae, calling it 1a, however on Fileconnect it is indeed indicated as MP1. 

If you are to insistt on using MR4 MP1, just ensure you have the correct of the 2 builds.

You can deploy to Vista clients as you would with any other client.

Note however, that there are still features which are not functionning in any 64 bit build.  Recommended would be to use AV/AS.  Device and App control do not work as well as tamper control.  Same with PTP (proactive threat protection) in 64 bit has no or very limited functionality.

Also note, that the same is true for Server OS, 32 bit or 64 bit.  There are limitations to it's functionalities and not all components are functional yet.  There are many discussions on these in the forums, here.

The 32 bit client is working just fine.

Sossym,
I didn't mean to say upgrade to that specific build. But you should upgrade to minium of that. Due to all the previous fixes in the MRs. I heard MR2 is quite stable at the moment. But I only tested my environment (xp, 2008, 2003, 2000, vista, windows 7) up to MP4 MP1a. I do suggest you to use MR4 MP2. Will you be using window 2008 by any chance ?