Yes, the SID's and SID histories are part of AD and would be replicated to the new server when the new server is promoted to a DC, as would the Group Policies, logon scripts, etc.
With no Exchange, yes that cuts the workload down quite a bit.
I did understand in your original post that you're migrating to new hardware, but the benefits of the Transition Pack are greater than simply whether you're migrating to new hardware or keeping existing, and it goes along with transferring or seizing FSMO roles. There may still be a good reason for not using the transition pack, I would say because of the cost if you're not planning on using Exchange Server at that site.
I did not say that you won't or can't be successful seizing versus transferring FSMO roles. We only have general information so I can only speak in general terms. You can be successful seizing roles, but you have to understand the difference and your migration plan has to accomodate accordingly.
By not going to the Transition pack, your SBS while on the network will never allow another DC to be an FSMO role holder. This means that at some point when you feel you've transferred all data, shares, printers, DHCP, etc. off of the SBS, you will simply turn it off (or disconnect from the network) without demoting it, and must never connect it again to that network (as it will assume it still controls the network and you'll have problems). With the SBS disconnected from the network, you can then SEIZE all FSMO roles on the new server and you'll have to ntdsutil: metadata cleanup the SBS from the Production AD. From the point of seizing roles forward, you can never connect the old SBS to the same network. This just makes this step a significant go/no-go point in your migration plan in that you'll have to be sure that you got everything you need off of the old server, or if you haven't, you have to transfer any missed material in some way other than connecting the old server back to the same network.
Back to the transition pack. You may still have good reasons not to use the transition pack. As I said, general, and I just want to give you benefit of more detail here. The transition pack:
- Splits SBS into its fully licensed components, removing any SBS-specific limitations in those components
- Converts SBS licensing for Servers and CALs into the W2K3 Server, Ex2K3 Server, W2K3 CALs, and Ex2K3 CALs
- is transferrable to new hardware (with the possible exception of a vendor branded SBS)
So specific to your situation, the transition pack can help you by converting your existing SBS into W2K3 Server such that you would be able to TRANSFER FSMO roles off while leaving the old server in production a little longer to be sure all material was transferred off. This just gives you more flexibility from a planning standpoint. From a cost standpoint, you can transfer the W2K3 server license and CALs to the new server. If you plan on using Exchange Server, you would have the Exchange Server license and CALs which you could use when ready. You'll have to weigh this out from a cost standpoint to see if it makes sense for you.
Hope this helps.
--C