Symantec 14541094 Administration Guide - Page 72

Implementing DCOM in Windows NT/2000/2003 Server/XP, Implementing DCOM in Windows 98/Me

Page 72 highlights

72 Performing centralized management About the Microsoft Distributed Component Object Model (DCOM) DCOM runs on a variety of network protocols and, by default, attempts to make connections on all installed protocols. After connecting to the network, DCOM uses Windows NT authentication to verify the necessary access rights. For example, an administrator with the appropriate access rights can perform management tasks on a locked pcAnywhere host from any location. To ensure that NT authentication is used for pcAnywhere DCOM management tasks, pcAnywhere connection items should be configured to use the same domain or a trusted domain. Implementing DCOM in Windows NT/2000/2003 Server/XP To remotely configure and control pcAnywhere on Windows NT/2000/2003 Server/XP using a centralized management tool, you must meet the following system requirements: ■ The administrator must be logged on as a domain administrator. ■ The administrator's computer and the client's computer must be in the same domain. The Windows NT default configuration requires all manager activity to be authenticated on the Windows NT domain. Implementing DCOM in Windows 98/Me To remotely configure and control pcAnywhere on Windows 98/Me using a centralized management tool, you must meet the following system requirements: ■ The Windows 98/Me client must be logged on to the same Windows NT domain as the administrator. ■ The domain name and the workgroup name on the Windows 98/Me computer must be the same. ■ The Windows 98/Me computer must be configured with user-level access. This access is required to adjust the DCOM security settings when running the dcomcnfg.exe utility. ■ File and print sharing for Microsoft Windows Networks should be installed and enabled on the Windows 98/Me computer. Modifying DCOM settings Symantec pcAnywhere configures DCOM during the installation process. The default settings should be sufficient for pcAnywhere management applications to function normally and maintain a sufficient level of security. However,

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109

DCOM runs on a variety of network protocols and, by default, attempts to make
connections on all installed protocols. After connecting to the network, DCOM
uses Windows NT authentication to verify the necessary access rights. For example,
an administrator with the appropriate access rights can perform management
tasks on a locked pcAnywhere host from any location.
To ensure that NT authentication is used for pcAnywhere DCOM management
tasks, pcAnywhere connection items should be configured to use the same domain
or a trusted domain.
Implementing DCOM in Windows NT/2000/2003 Server/XP
To remotely configure and control pcAnywhere on Windows NT/2000/2003
Server/XP using a centralized management tool, you must meet the following
system requirements:
The administrator must be logged on as a domain administrator.
The administrator's computer and the client's computer must be in the same
domain.
The Windows NT default configuration requires all manager activity to be
authenticated on the Windows NT domain.
Implementing DCOM in Windows 98/Me
To remotely configure and control pcAnywhere on Windows 98/Me using a
centralized management tool, you must meet the following system requirements:
The Windows 98/Me client must be logged on to the same Windows NT domain
as the administrator.
The domain name and the workgroup name on the Windows 98/Me computer
must be the same.
The Windows 98/Me computer must be configured with user-level access. This
access is required to adjust the DCOM security settings when running the
dcomcnfg.exe utility.
File and print sharing for Microsoft Windows Networks should be installed
and enabled on the Windows 98/Me computer.
Modifying DCOM settings
Symantec pcAnywhere configures DCOM during the installation process. The
default settings should be sufficient for pcAnywhere management applications
to function normally and maintain a sufficient level of security. However,
Performing centralized management
About the Microsoft Distributed Component Object Model (DCOM)
72