IMHO, with the availability of Operating System Deployment Feature Pack (OSDFP) for SMS 2003, one of the most important enrichments of Systems Management Server was launched. It contains the all functionality to create an WIM-based  image (WIM = filebased, no partition destruction as with RIS or Ghost etc.) and deploy it through SMS. One other tool that could be imported within the deployment proces is User State Migration Tool or USMT. The current version could capture the User State of a system, saved it locally during the OSD fase and re-apply after the new image was placed. Because User State is saved locally, it is not possible to restore User State to another workstation during a scenario where hardware-replacement is neccesary.

 

Now, in Configuration Manager 2007 this will be possible because of a new serverrole that will be availlable: User State Migration Server. I do not know yet if this will be a mullti-server role like a DP or single server like a MP, but i expect it to be multi-server due to the neccesary datatraffic during large deployment scenario's.

MMS San Diego 2006: Microsoft decided that after more than 15 years, the name Systems Management Server wil be changed to System Center Configuration Manager, starting from the now in beta availlable SMS v4. A sneak-peak uncovered multiple enhancements as WOL, a branch-office solution without the need of a DP available (kind of P2P like E1 already uses, but not that smart |-( ) and an extension to patch third-party updates (ITCU). A great deal of partners like Citrix, 1E and Adobe already have ITCU packages available for testing purposes an TAP partners

I'm already 4 days in San Diego Cal to attend the Microsoft Management Summit. This is the most important conference on Systems Management. And I am excited! Especially the information unveiled on the pre-conference sessions were very useful to get an idea where the intentions and investments on Systems Management will lie. Can't tell you to much about it, it's still under NDA ;-) !