I wrote a post a year ago or more about how to install the SCCM 2007 Admin Console including R2, this is something I use a lot in my projects as it is more and more to install when installing the Admin Console.
In the example below I install the Admin Console, the required hotfix(kb977384) and R3. If you are using Forefront Endpoint Protection you need to install the FEP Admin UI extensions as well on your client machines which should have the SCCM console locally installed, I will post an example of a script with the FEP integration later on.

When R3 came along the SCCM 2007 R3 requires a hotfix(KB977384) which restarts a lot of services on the computer during installation for instance ccmexec, WMI and so on, if a Task Sequence or application installation runs it will stop and return error.
so I wrote a little vbscript which uses a .MIF file to report the installation status back to the SCCM server. It will report any errors back to the SCCM server so that it is easy to troubleshoot.

The script can be downloaded here: Install

To implement the script do the following:

  1. Copy the needed installation media to a folder with the following sub-folders.
    sccm_adminui_r33Note: to save space I deleted files in the WAIK directory from the Configuration Manager SP2 installation source as these files are not needed to install the admin console.
  2. Save the downloaded vbscript to the folder you just created and rename it to install.vbs.
  3. Create a Unattend.ini file in the ConfigMgr_sp2 folder with the following content, you need to change the server name to your SCCM Primary Site server.

    SMSInstallDir=c:\program files\Configuration Manager 2007
  4. In SCCM Create a Package with the source folder beeing the folder structure just created.
  5. In the package properties configure the following under the reporting tab: (this is used to match the .mif file generated by the script with the package)
  6. Create a program with the following settings:
  7. If you want to display the installation progress in a cmd windows to the users, configure the program to “Allow users to interact with this program”
  8. Add the package to your Distribution Points
  9. Advertise the program to a test collection and start testing.

I hope this can be useful for more than me.