Endpoint Protection

I have clients in Panama that can only speak Spanish therefore their PC's have a Spanish layout, the whol operating system is written for Spanish. My SEPM and the rest of my sites are all in English. When I attempted to roll the English package onto a Spanish XP PC, it failed every time. I have asked this before, and it seems as if I would need to build a 2nd SEPM in Spanish and designate Spanish pakages to be installed on the clients. Is there any way around this? I want everyone on one SEPM, and since there are such a small amount  of Spanish XP's I would be of the mind that creating another SEPM structure would be too much overhead.

Thank you.

when you are installing the SEP client
change the os language ,to english under regional settings
install it
put the  language back to spanish.

can you post the install log..we should be able to install(not sure ) 

It did not work. I will try again.

I had to do the same thing I did yesterday. Install it from the SEP folder. Push was not working then get it to fall in line by replacing the SYLINK.XML file. The other solutions don't work, but this has yet to fail me.

I'm working on that, created a small network in VM
if works, but trying to fail it what failing me now,,will fixed it up
you were able to install on the spanish box?  

whats the version of msiexe.exe? on those machines? 

Had to copy from the SEP folder, then replace the Unmanaged sylink.xml and it falls in line.

i read it somewhere where it said about msiexec.exe file version being outdated one thats y , the install failed, on any box can you check whats the version of msiexe.exe? 

It is possible that I was using the 11.04 package. I have re created the package to use with an 11.5.

It was something to do with the LiveUpdate, once that installed it was free sailing.

I'm sorry ,I"m was referring to your other issue where the remote push was not working
(where setup files lost)
on the target machine if the version of msiexec.exe is older then it would run the install. 

It is the same exact package that worked perfectly on 20 other machines. The one machine was the hold out. The way I am doing this now, is I will use the work around, I just need to get it right ONCE on the PC, then take it from there and take care of policy and upgrades from SEPM.