SMS Remote control Tool - Unleashed Oren Zippori Team Computers Israel System Management User Group

Meeting Subjects Review of SMS 2.0 Remote Tools Review of SMS 2.0 Remote Tools  Remote tool settings  Remote tool Security  Remote tool Traffic Some Tips and Tricks. Some Tips and Tricks. Overview of SMS 2003 Remote Tools Overview of SMS 2003 Remote Tools Interoperability between versions of SMS Interoperability between versions of SMS Questions Questions

Review of SMS 2.0 Remote Tools SMS 2.0 provides Remote Tools functions: SMS 2.0 provides Remote Tools functions:  Remote Control  Remote Execute  Remote Reboot  File Transfer  Chat  Ping Test

SMS 2.0 Remote Tools Security Security is required for access to remote client Security is required for access to remote client  Must have Use Remote Tools security right to collection  If not, will not be able to start Remote Tools  Must be a member of the Permitted Viewers list  If not, will be prompted for credentials  Must be local administrator on remote client  If not, will be prompted for credentials Security rights set for users/groups to all or individual collections Security rights set for users/groups to all or individual collections

Remote Tools Security

Remote tool settings Compression for Remote Control: Compression for Remote Control:  Automatically Select  Low (RLE)  High (LZ) Remote access Protocol: Remote access Protocol:  TCP/IP – IPX – NetBIOS (NetBEUI) Install accelerated Screen on windows NT Clients. Install accelerated Screen on windows NT Clients.

Remote tool settings

SMS 2.0 Remote Tools Traffic SMS 2.0 uses TCP, IPX, or NetBIOS to access remote client SMS 2.0 uses TCP, IPX, or NetBIOS to access remote client SMS 2.0 uses ports TCP SMS 2.0 uses ports TCP SMS Remote Control session startup: SMS Remote Control session startup:  Register SMS Administrator console name  Resolve client’s IP address  Connect over port 2701  Connect over LANA  Connect over port 1761

Remote Tools Traffic

Remote control Flow SMS Console SMS Server SMS Client Query Database with Client Resource ID SMS Returns Client Is the user in the Permitted Viewer list? Is the user Permitted to remote control the Collection? Is the user a local administrator? Remote.exe Runs with 0 and Network Name ResolutionNetwork Name Resolution NetBIOS – DNS WINS LMHostsNetBIOS – DNS WINS LMHosts SMS IO InformationSMS IO Information Is the “Permission Required” Key is set?

Some Nice Remote control Tips and Tricks. (Unsupported style)

Disable Security Munging “HKLM\SOFTWARE\Microsoft\SMS\Client\Client Components\Remote Control“ “HKLM\SOFTWARE\Microsoft\SMS\Client\Client Components\Remote Control“ Registry Key “UpdateEnabled” Registry Key “UpdateEnabled”  Yes = Enabled updates  No = Disable Updates Registry key "Permission Required“ Registry key "Permission Required“  0 = No permission  1 = Ask for Permission

Remote.exe command line Remote.exe [\\SMSserver] = =  1 for IPX  2 for IP  3 for LM or NetBIOS = IPX, IP or NetBIOS name. = IPX, IP or NetBIOS name. /SMS:NOSQL /SMS:NOSQL Example: Remote.exe 2 Computer /SMS:NOSQL

Remote.exe Files Needed remote.exe remote.exe Ldftrans.dll Ldftrans.dll Ldwmnt.dll Ldwmnt.dll mmcpgres.dll mmcpgres.dll msvcp5o.dll msvcp5o.dll multprot.dll multprot.dll sms_nwbm.dll sms_nwbm.dll sms_rmgr.dll sms_rmgr.dll sms_rwbm.dll sms_rwbm.dll uitlures.dll uitlures.dll uitoolsu.dll uitoolsu.dll sms_nmgr.dll sms_nmgr.dll The Remote Tools files are installed on the Site Server in : SMS\Bin\i386

Using SMS Installer to Control Remote Control

Troubleshooting Video Acceleration Mode By default Enabled. By default Enabled. Client Try’s to load Video Acceleration after being installed. Client Try’s to load Video Acceleration after being installed. Add your Video card to the list!!! Add your Video card to the list!!!  Check SMS Resource Explore. “Rchwcfg.exe install” to force Video Acceleration “Rchwcfg.exe install” to force Video Acceleration

Disabling Wallpaper and Specifying Video Configuration

SMS 2003 Remote Control SMS 2003 provides many options SMS 2003 provides many options  SMS Remote Control  Windows XP/.NET Server Remote Assistance  Windows Terminal Services All integrated into the SMS Administrator console All integrated into the SMS Administrator console No difference between mobile and standard client behavior No difference between mobile and standard client behavior  Can create a MOF file to provide local policy override of site settings

SMS 2003 Remote Control Some performance improvements over SMS 2.0 Some performance improvements over SMS 2.0  Less CPU consumption for graphics rendering of screen images Only uses TCP for SMS 2003 clients Only uses TCP for SMS 2003 clients  No support for IPX or NetBIOS No longer use the SMS site database’s IP address for the client No longer use the SMS site database’s IP address for the client NO need administrative rights to remote control. NO need administrative rights to remote control.

SMS 2003 Remote Control

Interoperability with SMS 2.0 Topaz SMS Administrator console can remotely control SMS 2.0 clients Topaz SMS Administrator console can remotely control SMS 2.0 clients  SMS 2003 uses only TCP  SMS 2.0 uses TCP, IPX, or NetBIOS  SMS 2003 can use any method to control SMS 2.0 client SMS 2003 and SMS 2.0 use same ports for standard Remote Tools SMS 2003 and SMS 2.0 use same ports for standard Remote Tools

Some Links and KB’s SMS: Explanations of Remote Control Screen Acceleration (200430) SMS: Explanations of Remote Control Screen Acceleration (200430) SMS: Support for Third-Party Video Drivers with Remote Control Video Acceleration (248989) SMS: Support for Third-Party Video Drivers with Remote Control Video Acceleration (248989) Stop Error During Startup Of Systems Management Server Clients After Upgrade (329764) Stop Error During Startup Of Systems Management Server Clients After Upgrade (329764)

Questions Please?!?! Oren Zippori Team Computers