tweeny-love
asked on
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.
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.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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?
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?
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.
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.
ASKER
In case the office install needs to be repaired I meant.
Thanks for your advise - it was very helpful.
Thanks for your advise - it was very helpful.
ASKER