Why would you try to use /mp during a TS? That's very counter-productive as the TS already downloads the client installation files to the local system. /mp has *nothing* to do with setting the MP for a client.
J From: [email protected] [mailto:[email protected]] On Behalf Of Miller, Todd Sent: Thursday, July 23, 2015 11:39 AM To: [email protected] Subject: [MDT-OSD] RE: Client Settings come from Build and Capture You are right, I mean the settings provided in the client installation command-line. Since the client is installed during the build and capture, it is only reconfigured by the reinstall during the Deployment. So I have the client install properties set to ... /mp:SCCMcm12mp1Contoso.com SMSMP=SCCMcm12mp1Contoso.com SMSSITECODE=XXX SMSCACHEFLAGS=PERCENTDISKSPACE SMSCACHESIZE=10 CCMLOGMAXSIZE=1000000 CCMLOGMAXHISTORY=5 But not much (if any) of these settings are applied to the client during the (re)installation of the client during the Deploy task sequence. Instead, they are all left at the values set during the Build/Capture Task Sequence From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Thursday, July 23, 2015 10:48 AM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] RE: Client Settings come from Build and Capture Cache size is not set in "Client Settings". I don't think that's what you meant, but you must be careful with how you say things as "Client Settings" has a very specific meaning in ConfigMgr. Some of the properties of the client set on the command-line are not reset when the client is re-installed, the cache size is the most notorious of these. You need to run a script to reset the cache size; this can be done in the TS after the Setup Windows and ConfigMgr task or as a software package. To my knowledge, this is something the product team is aware of, but I'm not sure if they've addressed it or not. J From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Daniel Ratliff Sent: Thursday, July 23, 2015 10:22 AM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] RE: Client Settings come from Build and Capture We don't see that behavior and do a full B&C using SCCM and deployment with SCCM+MDT. We have separate settings in our deployment TS and the agent settings are what we have specified in the 'Setup Windows and ConfigMgr' step. Does your B&C have the 'Prepare ConfigMgr client' step? Can you verify in the logs its running successfully? Daniel Ratliff From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Miller, Todd Sent: Thursday, July 23, 2015 10:52 AM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] Client Settings come from Build and Capture Using OSD+MDT to do build and capture and also for deploying the OS to the bare metal computers. I notice that the settings for the SCCM client are set by the SCCM Agent installation process in the build and capture Task Sequence and are not reset during the client installation step in the Deployment task sequence. So if cache is left at the default 5GB during the build and capture phase, it is not reset to a higher level specified in the SCCM Agent installation step in the deployment task sequence. Is this normal and is there any way around it? I would like the settings in my Deployment task sequence to take precedent over the client settings in my Build and Capture. There are other settings like log size and log history that take on values of the agent install in the build and capture task sequence and if they are different in the Deploy task sequence - they don't change. If I wanted to change the log retention or size for new deployments, I need to rebuild the base OS rather than just change the Deployment Task Sequence. Normal? Or is there a way to essentially reinstall the SCCM agent during the Deployment Task Sequence in a way that the settings specified in the Agent install step in the Deploy TS overrides what is in the Base OS image? ________________________________ Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error, then delete it. Thank you. ________________________________ 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. ________________________________ Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error, then delete it. Thank you. ________________________________
