GPLv2 is less nuanced than GPLv3 in terms of source code availability. It prescribes in s3 that
You may copy and distribute the Program [...] in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following:
a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,
b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange
So although you're only distributing a compiled copy of somebody else's source, you are still obligated to distribute source as well, either alongside the binary, or on demand. It'll probably be simplest if you put a link to the source alongside the download link for the binary.
You say also that the "GPL software is [a] separate executable and will be part [of] a commercial solution". I presume you're aware of the degree of separation required between the GPL software, and your software which invokes it, to avoid your software becoming a derivative work of the GPL code, and thus subject to a requirement to distribute under GPL. But if not, you should acquaint yourselves with the rules.