The sender.log got me going in the right direction, it seems to have been a problem with the credentils it was using to try and install on the secondary server. Once I got that fixed, the flood gates opened and stuff started happening.
Now I think i'm having problems with an install that didn't go through all the way on the secondary server, the SMS_Bootstrap.log looks ok until I get to this point...
Started "C:\4xu1zis4.TMP\SMSSETUP\bin\i386\setup.exe /script C:\SMS_BOOTSTRAP.ini /nouserinput" as PID 7948. SMS_BOOTSTRAP 1/1/1601 12:00:00 AM 1 (0x0001)
Waiting for PID 7948 to terminate... SMS_BOOTSTRAP 1/1/1601 12:00:00 AM 1 (0x0001)
PID 7948 exited with code 1. SMS_BOOTSTRAP 1/1/1601 12:00:00 AM 1 (0x0001)
FATAL ERROR: SMS_SITE_COMPONENT_MANAGER is not running, setup must have failed, bootstrap procedure aborted! SMS_BOOTSTRAP 1/1/1601 12:00:00 AM 1 (0x0001)
Deinstalling myself... SMS_BOOTSTRAP 1/1/1601 12:00:00 AM 1 (0x0001)
Deleted temp directory C:\4xu1zis4.TMP. SMS_BOOTSTRAP 1/1/1601 12:00:00 AM 1 (0x0001)
Deleted C:\SMS_BOOTSTRAP.pkg. SMS_BOOTSTRAP 1/1/1601 12:00:00 AM 1 (0x0001)
Deleted C:\SMS_BOOTSTRAP.ini. SMS_BOOTSTRAP 1/1/1601 12:00:00 AM 1 (0x0001)
Deleted C:\SMS_BOOTSTRAP.EXE. SMS_BOOTSTRAP 1/1/1601 12:00:00 AM 1 (0x0001)
Deinstalled the SMS_BOOTSTRAP service. SMS_BOOTSTRAP 1/1/1601 12:00:00 AM 1 (0x0001)
Deinstallation complete. SMS_BOOTSTRAP 1/1/1601 12:00:00 AM 1 (0x0001)
Bootstrap procedure unsuccessful. SMS_BOOTSTRAP 1/1/1601 12:00:00 AM 1 (0x0001)
Stopping SMS_BOOTSTRAP... SMS_BOOTSTRAP 1/1/1601 12:00:00 AM 1 (0x0001)
SMS_BOOTSTRAP stopped. SMS_BOOTSTRAP 1/1/1601 12:00:00 AM 1 (0x0001)
********************************************************************************