Also note that "update content" here won't actually push any files out as there haven't been any changes. The content version will increment and then the content will be evaluated for changes but since none will be found, nothing will actually get copied. The evaluation des have a small amount of overhead though so if you do this to a lot of content all at once, you will see some network load.
If you make the change via the console or PowerShell, ConfigMgr will initiate the update itself - you can watch distmgr.log or use DPJobMonitor to verify this. J From: [email protected] [mailto:[email protected]] On Behalf Of Marable, Mike Sent: Thursday, October 15, 2015 7:11 AM To: [email protected] Subject: [mssms] RE: Detailing data source for all packages Yes, the ConfigMgr will automatically update the DPs. I'm like Daniel though, I update the DPs just to be on the safe side. Mike From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Daniel Ratliff Sent: Thursday, October 15, 2015 8:01 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: Detailing data source for all packages Here is the SQL, not sure about #2. I always Update DPs to be safe. select PackageID, Manufacturer, Name, Version, PkgSourcePath from v_package Daniel Ratliff From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Corkill, Daniel Sent: Wednesday, October 14, 2015 10:04 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] Detailing data source for all packages I've stumbled upon a couple packages this morning that are referring to source locations on an old server. So a couple questions: 1. Anyone have an SQL query or other way to list all packages and their data source so I can see if there's any others 2. Just confirming I understand how to change the source correctly: copy the source to the new location, change the package's source to the new location, ConfigMgr will update the content on DPs Daniel. ********************************************************************* This email, including any attachment, is confidential to the intended recipient. It may also be privileged and may be subject to copyright. If you have received this email in error, please notify the sender immediately and delete all copies of the email. Any confidentiality or privilege is not waived. Neither the Council nor the sender warrant that this email does not contain any viruses or other unsolicited items. This email is an informal Council communication. The Council only accepts responsibility for information sent under official letterhead and duly signed by, or on behalf of, the Chief Executive Officer. Privacy Collection Notice Logan City Council may collect your personal information, e.g. name, residential address, phone number etc, in order to conduct its business and/or meet its statutory obligations. The information will only be accessed by employees and/or Councillors of Logan City Council for Council business related activities only. If your personal information will be passed onto a third party, Council will advise you of this disclosure, the purpose of the disclosure and reason why. Your information will not be given to any other person or agency unless you have given us permission or we are required by law. The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues
