Jump to content

Recommended Posts

Posted

We have had a slight problem with a specific machine in our school. The machines this is mainly affecting is the NEC VL260.

 

What happens is, if you click on a thumbnail to pop it out to a windowed view or a full screen view, after so long a message appears asking the user if they would like to change the color scheme to improve performance. We have set the students from aero theme to the basic theme via Group Policy by enabling this setting:

 

User Configuration > Admin Templates > Windows Components > Desktop Window Manager > Do not allow desktop composition

 

But... we allow staff to have access to the aero theme (on machines which run it) and we are finding when we either control the machine just have it popped out, doesn't matter if the user is a teacher or administrator (as we have tested it with both), we get a message come up asking to "Do you want to change the color scheme to improve performance? There is nothing happening on the machine but yet it requires the theme. Could it be that these machines just don't like impero. I know that these machines are not fit for running Windows 7 as there is something missing in the BIOS which stops the machine licensing it's self against a KMS server.

 

I was wondering if anyone else has had this problem?

 

I have got a video of this if anyone from impero on here wants to see what is happening.

Posted

We have seen this on a couple types of machines and we changed code slightly in 3.5 to deal with this so once upgrade to 3.5 the message should go away.

 

Russell

Posted

Got this reply from Russ, hope that helps

 

Hi

 

We had to hold release of 3.5 as we found an issue we squashed that final bug today so we are testing a build tomorrow and hopefully we can start releasing it again end of this week. I will make a support ticket and when we can release 3.5 I will update you.

Posted

Hi

 

As pointed out we started rolling out but saw an issue we needed to fix hence why we stopped the roll out.

 

We are testing the build that has the issue fixed in it today/tomorrow. Once we done that if no issues we can start to roll out again but depends what happens with internal testing.

 

Sorry for the delay.

 

Russell

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...