/build/static/layout/Breadcrumb_cap_w.png

Error "The language of this installation is not supported by your system"

We are in the middle of a 2200 PC migration to Win 7 x64. Some of the links between my virtualized K2000 and the sites are rather slow so I thought I would setup a Remote Site Appliance at one of our larger sites with a slower connection. Setup was easy enough and the initial sync from the K2 to the RSA went without a hitch. I sync'd over a boot environment and the scripted install that I needed.  I changed DHCP Option 66 on my test vlan to point to the RSA and everything went well. PXE worked and the scripted install kicked off like it was supposed to.

After the machine rebooted and started into my post install tasks I get the following error. "The language of this installation is not supported by your system"  This error occurs during Office 2010 install and the Office install does not complete. All other post instal jobs work great.  If I change my DHCP options back to the K2000 everything works fine.

Any ideas of what is going on with this?  I searched the forums and did not find mentions of this error in regards to a RSA.


0 Comments   [ + ] Show comments

Answers (1)

Posted by: Nico_K 10 years ago
Red Belt
0

It is an Office 2010 issue.

Please check the technet-blog:

https://blogs.technet.com/b/jks/archive/2009/04/23/how-to-fix-the-error-the-language-of-this-installation-package-is-not-supported-by-your-system-during-office-products-installation.aspx?Redirected=true

Also be shure that .NET 3.5 is installed already. before starting the Office Installation.

If you have a K1000 I really suggest to install Office via the K1000.


Comments:
  • My issue is that this is the exact same setup that IS working from the K2000, but it does not work from the Remote Site Appliance. Installing Office using the K2000 as a post installation task has worked for the other 1200 machines I have done this on, the only machines it does not work on are the ones that were using the RSA. - ScottinOkla 10 years ago
    • That's very strange. Try removing the PO task from your RSA, syncing, adding the task back and then syncing again. There may have been some data corruption when the initial transfer took place. - mpace 10 years ago

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ