I have the CM Remote Control tool published over citrix so that employees 
working from home or wifi are able to get through the client based firewall 
without needing to be connecting from a known IP address.   I am using the  
instructions on creating a stand-alone SCCM Remove viewer by making the 
necessary files available via file share to the Citrix servers and then 
launching remote control via a published app.

This was working fine in CM 2012R2, however after updating to 1602, the 
CMRCViewer wont launch on Citrix anymore.  I suspect that the problem is that 
the application is trying and failing to open the SMS namespace in WMI.  The 
Citrix server does not have the CCM agent installed.

For the time being, I have switched the files back to the 2012 versions, but I 
am unsure if the 2012 Remote Control viewer will continue to be able to remote 
control clients as they are upgraded to the 1602 version of the agent.

Has anyone else tried to make remote control available via Citrix in Current 
Branch?

This is the way I am making remote control available independent of the 
console, and then publishing CMRCViewer.exe basically.

http://ccmexec.com/2012/05/running-configuration-manager-2012-remote-control-standalone/


________________________________
Notice: This UI Health Care e-mail (including attachments) is covered by the 
Electronic Communications Privacy Act, 18 U.S.C. 2510-2521 and is intended only 
for the use of the individual or entity to which it is addressed, and may 
contain information that is privileged, confidential, and exempt from 
disclosure under applicable law. If you are not the intended recipient, any 
dissemination, distribution or copying of this communication is strictly 
prohibited. If you have received this communication in error, please notify the 
sender immediately and delete or destroy all copies of the original message and 
attachments thereto. Email sent to or from UI Health Care may be retained as 
required by law or regulation. Thank you.
________________________________



Reply via email to