Application Mapping for Computer Replacement
I have a client that wants to do application mapping for PC replacement. So if OldPC had Visio 2003, the NewPC gets Visio 2003 (or newer) based on the mapping. I have done this with MDT 2010 UDI but on a refresh. Any ideas how to accomplish this?Jay Parekh Project Leadership Associates
October 26th, 2010 1:49pm
Last time I did this: we used collections and software inventory. I told software inventory to inventory certain files.(or if you have the old packages it was even easier) I made a collection that was based on what applications were discovered. If the system matched the query it was added to the collection. The software I wanted to install was advertised to the collection. (So if a system showed up on the network and reported it had Office 2000 it would get an advertisement to install Office 2007.) this worked best for us because of the huge numbers of mobile sales workers. edit* We also based new installs off of AD membership. If you were in "sales" you got "X" number of packages, if in "Operations" then "Y" number of packages. the hardest part for me designing this was to get my mind around "we don’t push software, we tell SCCM what logical groups will need for software". it was hard on me :) You will have to modify this some to get what you’re looking for but it should work. I hope this helps.
November 11th, 2010 4:20pm
Not sure how but it can be done. I know both SCCM Expert and FyrSoft have solutions around this. http://www.fyrsoft.com/Solutions/ITAutomation/DesktopLifecycleAutomationFDLA/tabid/79/Default.aspx John Marcum | http://myitforum.com/cs2/blogs/jmarcum |
November 11th, 2010 4:37pm