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. ________________________________
