SCCM 2007 - Windows Installer Source Management - Should I Use It?

Posted on 2012-08-23
Last Modified: 2012-08-24
Regarding the "Windows Installer" tab on the Properties screen of a program in Software Distribution - should I use this for all our software that is MSI based?

I work in a fairly small organisation with only around 400 desktops and one SCCM 2007 server - I can't seem to find any best practise guides on using this feature -  software is installed directly from a UNC path on the SCCM server itself - is there any point in me using this feature? Just looking for the pros and cons.
Question by:tweeny-love
    LVL 10

    Accepted Solution

    If ALL your software points to that one server, then there isn't much point in using it.

    One exception is if you have installed software by any other means, you can point it's source lists to the SCCM server.

    A lesser known secret to the source management feature is that it can manage the source lists of ALL MSI packages, not just the ones installed via SCCM.

    Author Comment

    Ah cool, so the SCCM client basically over-rides the source installation for all msi based installs in "add and remove programs/programs and features" ? That's good to know.

    Author Comment

    Oh, and yes all the programs have been installed from the SCCM server.

    However this SCCM server is replacing an old one that was corrupted and we had no valid backups (don't ask!) - so if we use this feature we can basically change the installation source in the background to point to the new SCCM server in case the clients somehow get corrupted - right?
    LVL 10

    Expert Comment

    I'm not following this statement => " case the clients somehow get corrupted..." - the SCCM Client, MSI or the entire Desktop OS ?

    Assuming you can resume normal operations with the clients and the new SCCM server you should be able to repoint the source lists to the new server.

    You will obviously have to setup and replicate the package files first.

    I know you are probably a small environment, but it would be best practice to put your DPs on other servers.  You can use Server Share DPs so that no software is installed on the DPs.

    Author Comment

    In case the office install needs to be repaired I meant.

    Thanks for your advise - it was very helpful.

    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    What Should I Do With This Threat Intelligence?

    Are you wondering if you actually need threat intelligence? The answer is yes. We explain the basics for creating useful threat intelligence.

    Consider a situation when you deploy a seemingly harmless software package to your network without testing and therefore without fully knowing the implications of your actions. I was recently involved in just this situation when a corporate IT netwo…
    Have you considered what group policies are backwards and forwards compatible? Windows Active Directory servers and clients use group policy templates to deploy sets of policies within your domain. But, there is a catch to deploying policies. The…
    how to add IIS SMTP to handle application/Scanner relays into office 365.
    Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.

    737 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    15 Experts available now in Live!

    Get 1:1 Help Now