For Vista, Windows 7, Server 2008, and Server 2008 R2, sysprep as a whole is completely different. Adding drivers involves one of a few methods.

1. Get to know the Windows System Image Manager from the WAIK. The WAIK for Windows 7 & Server 2008 R2 changes a few things, but for the most part the GUI-end of things is the same.
2. In order to add drivers to Vista, 7, and Server '08 (& R2) you either need to:
   a) Run %systemdrive%\Windows\System32\sysprep\sysprep.exe /audit /reboot /unattend:<path to your sysprep.xml file>

   Your sysprep file needs to have a few things in it if you're going to run Audit. Namely you should have, in the auditSystem pass,if you're running in a 32-bit environment:

   1. x86_Microsoft-Windows-Deployment_neutral
       a) With a "Reseal" line in there too. Reseal can be set to "ForceShutdownNow" as "False" and "Mode" to "Audit"
   2. x86_Microsoft-Windows-PnpCustomizationsNonWinPE_netural
       a) With a Path line in there too. The path should point at a directory containing your drivers. Again, Vista, 7, and Server '08 search recursively. So you can have one path that points at a parent directory with sub-directories in it. This way you can keep things real organized however way you want. Up until recently (because I'm using point "b" below, with DPInst now, primarily) I had all my drivers stored in the image. Unfortunately with all drivers this was beefing up my image by a few Gigs. Now I only have S-ATA/AHCI/LAN drivers stored locally. All other drivers are stored on a server and get installed via point "b" below.
   3. x86_Microsoft-Windows-Shell-Setup_neutral
       a) With an "AutoLogon" line in there too. This is so the machine has something to log into during the Audit phase. In my case, because I'm also using the built-in admin to setup a custom default profile (see "CopyProfile" in the WSIM), I set this to log into the built-in admin. By default the built-in admin is disabled. It gets enabled during Audit for however many times you have it set to auto-login during Audit. When I'm logged in as the typical admin account, outside of the Audit phase, I have set the built-in admin's password to some value. You need to insert that value in the "AutoLogon" as well in order to have Audit completely succeed.

   4. Once you're done with Audit, you can create your image. Tell Ghost (via Task in my case) to start creating your image. Use sysprep with /generalize. I do this while logged in as the built-in admin during the Audit phase.

   5. Stick in a similar x86_Microsoft-Windows-PnpCustomizationsWinPE line in the windowsPE pass in the WSIM in your answer file. Insert a Path line there too with the path & the credentials matching what you put in for it during the auditSystem pass.

   or

   b) In the WSIM, in the Specialize pass , you can insert a RunSynchronous command using DPInst. Get to know this tool if you choose this route. It's from Microsoft and obtainable in the Windows Driver Kit (think that's the name). In my Synchronous Command I run: 

   %systemdrive%\Scripts\DPInst\x86\installUnattended.cmd

   And in that .cmd file:

   @echo off
   @echo Installing 32-bit drivers in silent mode now...
   set server=<your server FQDN or WINS equivalent>
   set share=<your share name>
   set drive=s:
   set domain=<Your domain>
   set user=<Your user>
   set password=<Your password with quotes if it has spaces>
   set arch=x86
   net use %drive% \\%server%\%share% %password% /user:%domain%\%user% /persistent:no
   @echo Network share connected
   start /w %systemdrive%\Scripts\DPInst\%arch%\dpinst.exe /path %drive%\
   @echo Done installing 32-bit drivers in silent mode
   net use %drive% /delete
   @echo Network share disconnected
   exit

   Now, see where I call dpinst.exe? In the same directory as dpinst.exe there exists a file that MUST be named dpinst.xml, this is where I call the flags for dpinst.exe. Nice part about dpinst.exe is that it's fairly modular. No dll's to really rely on, you can tote the .exe just about anywhere. Here's my dpinst.xml file:

   <?xml version="1.0" ?>
   <dpinst>
       <search>
         <subDirectory>*</subDirectory>
       </search>
       <language code="0x0409">
         <dpinstTitle>Driver Install Wizard</dpinstTitle>
         <welcomeTitle>Welcome!</welcomeTitle>
         <welcomeIntro>This wizard is for staff only. It is used to install device drivers.</welcomeIntro>
         <installHeaderTitle>Installing drivers...</installHeaderTitle>
         <finishTitle>Congratulations! You are finished installing drivers.</finishTitle>
       </language>
       <deleteBinaries/>
       <quietInstall/>
       <suppressEulaPage/>
       <suppressWizard/>
       <scanHardware/>
   </dpinst>

   When DPInst is done installing drivers, I have a second RunSynchronous command that deletes that .cmd file, given I have a password stored in the cmd file. That's the downside. Be responsible with your server shares, accounts, etc. The account I use has read-only access to only that share and that's it.

   So with all that, I can get my drivers installed in the Specialize pass during Sysprep. Now this thing WILL BREAK if you do not get your LAN drivers installed during the WinPE pass first, because if the LAN drivers are installed during Specialize, and the network connection is broken because a newer driver is installed, or the network connection can't be made because the LAN drivers weren't there in the first place, it stops this thing dead in its tracks.

   This hasn't been a problem for me as long as I include the LAN drivers in the image, using /audit like I mentioned. Using DPInst isn't some requirement, it's something I've picked up and pieced together over numerous forum postings, checking MS's MSDN & TechNet sites, etc. As long as you run /audit and have all drivers in there, you should be ok. If you want to reduce the overall size of your image and speed up the Audit phase, then adding in this DPInst strategy works really well.

   As as word of caution, during Audit, if you choose to just go with it and forego using DPInst, thus having all your drivers in your image, Audit can take a while depending on how many drivers you have. We had about 7+ Gig's of drivers for our models with Vista. With 7 I really streamlined it by paying attention to which drivers apply to multiple models (thus reducing overlap, duplication, etc). With Vista, Audit used to take 3+ hours on an Optiplex 760, which was the machine I used to create my builds. I have found that Windows 7 takes about 30 minutes, a HUGE difference, even with my old driver set; 7+ Gigs.

   I hope this all makes some sense.