Preventing remote control functionality in 7.5.
I know that the answer to this question will not be supported by the moderators, so I am putting it out to the general user community.
I currently am looking to upgrade to 7.5 in our production network. Our security admin won't allow me to do this with the current state of the remote control functionality (no prompting or lockdown of remote sessions). I need to come up with a way to restrict this function until a hotfix fixes it, and I was wondering what other people may have done.
Here is what I am thinking:
1. Find where the ActiveX controls get deployed from on the server, and move them to a different location.
2. Find out what port the remote functionality uses and block it on the ServiceDesk server firewall.
3. Somehow push a policy that restricts IE from installing that particular control. Possibly this would be by adding a specific URL to the untrusted zone.
Not quite sure if anyone has thought about this, but there must be a way.
I currently am looking to upgrade to 7.5 in our production network. Our security admin won't allow me to do this with the current state of the remote control functionality (no prompting or lockdown of remote sessions). I need to come up with a way to restrict this function until a hotfix fixes it, and I was wondering what other people may have done.
Here is what I am thinking:
1. Find where the ActiveX controls get deployed from on the server, and move them to a different location.
2. Find out what port the remote functionality uses and block it on the ServiceDesk server firewall.
3. Somehow push a policy that restricts IE from installing that particular control. Possibly this would be by adding a specific URL to the untrusted zone.
Not quite sure if anyone has thought about this, but there must be a way.