Travis Kimmel
Member
- Joined
- Mar 25, 2015
- Location
- Pennsylvania
We have in place Microsoft System Center 2012 which houses our imaging server. We have one 'gold' standard image that we use for all of our devices. When migrating to Windows 7 32-bit, we discovered that the computer when first booting up after imaging that users have issues with double clicking icons. This happens under the Admin account as well as other AD users. You are unable to open any application (web-based or local). This includes opening Recycle Bin, Computer, etc. This is usually alleviated after rebooting the computer 4-5 times. This occurs intermittently as well. Not always able to have it recreate itself.
We are now having the issues being escalated and requests to get it fixed. We are using a combination of HP 600's & HP 6000s as main desktops. We originally thought it may have been an issue with the models as the majority of these have occurred on the HP 600 models. This was proven wrong as we discovered it happened on one of our HP z600 PCs we used previously. I would like to narrow down between either the image we are using or if it is possibly group policy.
I am leaning away from the image as this is the same image that we used to build our IT workstations and no one has reported this issue. This issue occurs in departments outside of IT, which makes me believe that it is some sort of policy that we are pushing out causing the conflicts.
Any assistance is appreciated.
We are now having the issues being escalated and requests to get it fixed. We are using a combination of HP 600's & HP 6000s as main desktops. We originally thought it may have been an issue with the models as the majority of these have occurred on the HP 600 models. This was proven wrong as we discovered it happened on one of our HP z600 PCs we used previously. I would like to narrow down between either the image we are using or if it is possibly group policy.
I am leaning away from the image as this is the same image that we used to build our IT workstations and no one has reported this issue. This issue occurs in departments outside of IT, which makes me believe that it is some sort of policy that we are pushing out causing the conflicts.
Any assistance is appreciated.