• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 741
  • Last Modified:

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

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.
0
tweeny-love
Asked:
tweeny-love
  • 3
  • 2
1 Solution
 
CSI-Windows_comCommented:
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.
0
 
tweeny-loveAuthor Commented:
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.
0
 
tweeny-loveAuthor Commented:
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?
0
 
CSI-Windows_comCommented:
I'm not following this statement => "...in 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.
0
 
tweeny-loveAuthor Commented:
In case the office install needs to be repaired I meant.

Thanks for your advise - it was very helpful.
0

Featured Post

Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now