240 likes | 1.01k Views
Microsoft Systems Management Server (Topaz): Understanding Remote Control Options Wally Mead Program Manager Systems Management Server Microsoft Corporation Agenda Review of Microsoft® SMS 2.0 Remote Tools Overview of Topaz Remote Tools features Interoperability between versions of SMS
E N D
Microsoft Systems Management Server (Topaz): Understanding Remote Control OptionsWally MeadProgram ManagerSystems Management ServerMicrosoft Corporation
Agenda • Review of Microsoft® SMS 2.0 Remote Tools • Overview of Topaz Remote Tools features • Interoperability between versions of SMS • Questions and answers
Review of SMS 2.0 Remote Tools • SMS 2.0 provides Remote Tools functions: • Remote Control • Remote Execute • Remote Reboot • File Transfer • Chat • Ping Test • SMS 2.0 provides access to common Microsoft Windows® administrative tools • Event Viewer • Windows Diagnostics • Performance Monitor
SMS 2.0 Remote Tools Security • 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
SMS 2.0 Remote Tools Traffic • SMS 2.0 uses TCP, IPX, or NetBIOS to access remote client • SMS 2.0 uses ports TCP 2701-2704 • SMS 1.2 used 1761-1764 • SMS 2.0 Administrator console would try SMS 2.0 port first, and then try SMS 1.2 port • 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
Topaz Remote Control Options • Topaz provides many options • SMS Remote Control • Windows XP/.NET Server Remote Assistance • Windows Terminal Services • All integrated into the SMS Administrator console • Options available for appropriate client platform • SMS Remote Control for all client platforms • Remote Assistance for Windows XP/.NET Server only • Terminal Services for Windows NT® 4.0, Windows 2000 Server, and Windows XP/.NET Server • No difference between mobile and standard client behavior • Can create a MOF file to provide local policy override of site settings
Topaz and Remote Control • Topaz Remote Control function essentially the same as SMS 2.0 • Still provides same Remote Tools • Same security configuration • Same basic network traffic requirements • Can remotely control all platforms supported by Topaz • Windows 98, Windows NT 4.0, Windows 2000, Windows XP, and Windows .NET Server • Any child site clients running Windows
Topaz and Remote ControlChanges from SMS 2.0 • Some performance improvements over SMS 2.0 • Less CPU consumption for graphics rendering of screen images • Only uses TCP for Topaz clients • No support for IPX or NetBIOS • Can use IPX or NetBIOS to SMS 2.0 clients • No longer use the SMS site database’s IP address for the client • Additional driver verification • Additional logging enabled for Remote.exe
Topaz and Remote Assistance • Topaz SMS Administrator console can launch Remote Assistance session • Integrated into SMS Administrator console • All Tasks option for Windows XP and Windows .NET Server client computers • Nothing additional required on client systems • SMS Administrator console must be run from Windows XP or Windows .NET Server system • Can use Remote Assistance only from another Remote Assistance enabled system
Topaz and Remote AssistanceConfiguration • SMS administrator can configure Remote Assistance interaction • Manage and Override RA settings • Level of access (none, full control, or remote viewing only) • User permission is always required for RA sessions • Regardless of SMS configuration • SMS Permitted Viewers list is used for Unsolicited RA access • Solicited access supported as well • Group Policy may be used for configuration • This overrides SMS configuration
Topaz and Terminal Services • Topaz SMS Administrator console can launch Terminal Services session • Integrated into SMS Administrator console • All Tasks option for Windows NT 4.0 and higher client computers • Requires Terminal Server installed on client computer • Windows NT 4.0 • Windows 2000 Server and Advanced Server • Windows XP • Windows .NET Server • Nothing additional required on administrator computer
Topaz and Terminal ServicesWindows XP and Windows .NET Server • Windows XP uses Remote Desktop • User credentials used for remote session • See remote console on local console • Administrators create a new session • Logs off remote user and starts a new session • Windows .NET Server supports both remote console session and new session • Depends on privileges supplied for connection
Which Option Should You Use? • SMS Remote Control • Included with Topaz • Works on all clients • Remote Assistance • Use for Windows XP clients • Great performance • No additional drivers, so no issues with drivers • Terminal Services • Good for server-based clients • Great performance • .NET Server can remotely control console session
Interoperability • Topaz SMS Administrator console can remotely control SMS 2.0 clients • Topaz uses only TCP • SMS 2.0 uses TCP, IPX, or NetBIOS • Topaz can use any method to control SMS 2.0 client • Topaz and SMS 2.0 use same ports for standard Remote Tools
Summary • SMS 2.0 provided Remote Tools support • Remote Control, Remote Execute, Remote Reboot, File Transfer, Chat, Ping Test, and Administrative Tools • Topaz includes the same Remote Tools support • Supports all Topaz client platforms • Performance improvements included
Summary (2) • Topaz adds integration with Remote Assistance and Terminal Services • SMS Administrator console action to appropriate client platform • Topaz can successfully use appropriate Remote Tools to full client base • Including SMS 2.0 child site clients
Thank you for joining us for today’s Microsoft Support WebCast. For information about all upcoming Support WebCasts and access to the archived content (streaming media files, PowerPoint® slides, and transcripts), please visit: http://support.microsoft.com/webcasts/ We sincerely appreciate your feedback. Please send any comments or suggestions regarding the Support WebCasts to supweb@microsoft.com.