Why does MBSA require a client agent on the target computer?
Windows Update Agent is a Windows component. This component provides update management and is tightly integrated into the Windows platform. With the recent increase in security, it has become preferable to access and assess machines using a dedicated client present on the machine, rather than leaving the client open to easy access to its root directory and its local registry. For customers with clients that do not connect to the Internet or an Update Services server, MBSA can be used to automatically deploy this Windows component using the “Configure computers for Microsoft Update and scanning prerequisites” option or the /ia option in the command-line interface.
Related Questions
- I have started up my server (Your PC Network Clone Server CD) and my target (client) computer is connected to the local network, But I can not use the PXE boot. Any suggestion?
- Does GEM require remote agent installation on the target machines, and what tracks are left behind?
- Why does MBSA require a client agent on the target computer?
