rickallford, thanks for posting that; I do recall something about doing a slipstream with the CU, and that is a good point. I just installed the CU after the script failed trying to config the farm for the first time, thus SharePoint was already installed but not configured. Then re-ran the script after deleting the database from the SQL server, worked fine after that. only other issue I had was when it tried to do the remote install on the other servers in the farm, but that is neither here nor there (I will look into this at a later date).
I haven't figured out the slipstream script (SharePoint Auto Source Builder found here) that can create an installer with all of that stuff built in. My main intention for mentioning it here was because in doing my research I never found an answer that said this is what you needed to do to correct or this was the solution to this issue. The Auto source builder might be might next goal to learn how that works and what I can use it for.
I haven't figured out the slipstream script (SharePoint Auto Source Builder found here) that can create an installer with all of that stuff built in. My main intention for mentioning it here was because in doing my research I never found an answer that said this is what you needed to do to correct or this was the solution to this issue. The Auto source builder might be might next goal to learn how that works and what I can use it for.