Logs not collected from Widows XP desktops/laptops if in the same domain as windows servers
Originally Published: 2009-09-30
Last Modified: 2023-10-06
Article Number
Applies To
2003 Server SP1
Issue
Resolution
Create two Windows domains, one for servers and the other one for XP workstationand laptops. The best way to achieve this is to use the the standard FQDN for the servers account ie: example.com, with say username of server_admin and then create a second collection domain that uses the NETBIOS resolved name for the same Windows domain for the workstations ie: EXAMPLE with the username of workstation_admin.
You can refine it further by using $Domains and specifiying the fully qualified domain as part of the username eg: server_admin@example.com or example.com\server_admin. $Domains assume localhost for authentication, but the fully qualified username will force the local machine to authenticate via the domain controller.
Related Articles
Installing the same RSA SecurID Software Token 5.0 for Windows on different machines without reimporting 380Number of Views Leaver Rule–Deprovision is not moving Disabled Accounts to the Disabled OU in RSA Governance & Lifecycle 17Number of Views Cannot link the runtime identity source because no administrative identity sources reference this runtime source in RSA Au… 461Number of Views How to troubleshoot RSA SecurID Access identity source errors 492Number of Views Creating a RADIUS monitoring account for Citrix NetScaler in RSA Authentication Manager 8.x 97Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.9 Setup and Configuration Guide RSA SecurID Software Token Administrator's Guide RSA Authentication Manager 8.2 Token Management Snap-In for MMC Readme
Don't see what you're looking for?