Is Windows 2012 still to new to deploy to SMB

In my opinion new is not always better when it comes to the OS.  I am waiting to upgrade until a Service Pack or R2 comes out.

I have migrated a couple of domains from both 2003 and 2008 to 2012. I have encountered no issues other than the normal things you run in to with 3rd party applications. Backup software etc has to be updated to run on more current versions. Printer setups get a little more complex because the new platforms are 64 bit but you would run in to that with 2008 R2 as well.

Exchange migrations can be a little more technical in the "standard" world but there are technet guides that are a mere Google search away.

In short, I would not recommend upgrading to yesterday's technology. 2012 and Exchange 2013 are stable in my opinion.

HTH

Gary

that's exactly what we have been thinking, just wanted to know what other admins are doing.

I have been migrating clients with 2008r2 and 2012.  Since 2012 standard has the 2 free hyperv machines, we almost exclusively use 2012 for the host os.  The DC can be 2008r2 or 2012 depending on the clients needs. I've only done 1 Exchange 2013, usually I do 2010 on a 2008r2 machine.  I'll also make a 2008 32bit VM for those old apps and printers.

2012 R2 will be out in October some time, so by the time you get approval and get it implemented you will be able to install that instead.

As stated above by Stoner79 you could just do a dummy install of server 2012 just to get use to the GUI and how it all works.  It is different and has a little bit of a learning curve just to get use to the features.  There are a lot of really nice guides for setup if you need any help

Setup Guide:  http://social.technet.microsoft.com/wiki/contents/articles/12370.step-by-step-guide-for-setting-up-windows-server-2012-domain-controller.aspx

I have just been playing around with 2012 so far in my test environment

Thanks All,