Have you verified that it's a DHCP problem and not a connectivity issue? Try connecting a host to a switchport with a static IP configured in 10.192.x.x/16 and verify that it can ping 10.192.0.1 .
Your configuration has something I've not seen before. The VLAN interfaces have a double negative. I'm surprised that the parser allowed "no no shutdown", but logically and grammatically this would shut down the VLAN interface. Try entering "no shutdown" instead of "no no shutdown". Note that the VLAN interfaces are logical layer 3 interfaces. The switch ports will still get link but the IP addresses won't be active if the VLAN interface is shut down.
Having a DHCP pool of size /16 is not an issue. Practically, you don't want more than a couple of hundred devices in the same broadcast domain, but a large pool won't slow down the lease assignment.
You are correct that non-trunked ports by default are access ports on VLAN 1.
Thank you for your insight, good to know that Vlan 1 is on switch ports by default and now that I have looked over my config again only the one that I had omitted the sensitive data did the "no no shutdown" entry appear, I must have not noticed it added in extra "no" to my interface when doing a replace all. I ended up essentially just dropping the config again after I removed one or two minor duplicated entries, but the entries that were duplicated I can't imagine would have affected the DHCP pool. Like you said I believe it was an issue with the device that was being connected to the router as it was one of those slim line laptops that do not have an ethernet port but a USB dongle was being used instead. I strongly feel that is was an issue with the USB to ethernet adapter causing an issue. Appreciate the quick reply and good eye on catching those double negatives.