If your environment is heavily blocked with firewalls, you might need to resort to installing the agent manually. This could be any number of methods, including SCCM or another configuration management system.
Another option is to deploy a gateway server in the same logical boundary where your agents are to be installed, and discover the agents that way. However, the latter will add complexity and gateways are not intended to be used this way. I don't even like
offering this as an option, because gateways are inherently flaky in my experience, and I will not support implementing them in any environment, unless it is absolutely necessary.
The fact of the matter is, file and print sharing, and remote management need to be working in order to copy the installation files to the agent. There is no way around that, and these are standard ports that
should not be changed - probably wouldn't be able to if you tried.
Jonathan Almquist | SCOMskills, LLC (http://scomskills.com)
Microsoft is conducting an online survey to understand your opinion of the Technet Web site. If you choose to participate, the online survey will be presented to you when you leave the Technet Web site.