>From Mote, Todd [email protected] via<http://support.google.com/mail/bin/answer.py?hl=en&ctx=mail&answer=1311182&authuser=1> lists.myitforum.com
Not as elegant as it could be, but I have a couple of batch files I use for this, first one detects the architecture, subsequent ones have the ccmsetup. exe stuff in it, per architecture: ====Install.bat==== goto [%PROCESSOR_ARCHITECTURE%] goto end :[x86] "%~dp0Install SCCM Client x86.bat" goto end :[AMD64] "%~dp0Install SCCM Client x64.bat" goto end :end =============== I tried putting the ccmsetup stuff directly in this file, but it errored out saying the command was too long. All three files are in my sccm client package directory. I put the patchfiles in i386 and x64 respectively. Takes all my clients directly to .1202, which is nice, because installing it via SCUP usually means waiting a week for the console to update the version. Thanks William Jackson for reminding me of goto in batch files for this. Todd On Tue, Jun 11, 2013 at 8:22 AM, Benjamin Monrad <[email protected]>wrote: > This thread?CCMSETUP.EXE PATCH= 32-bit vs 64-bit? > > > On Tue, Jun 11, 2013 at 7:54 AM, Brian McDonald > <[email protected]>wrote: > >> I saw an email a while back and can't find it. It was around how to >> install the SCCM 2012 client and include the CU1 hotfix as part of the >> install, but had logic built in to determine if it was x86 or x64. Does >> anyone have this handy? >> >> Thanks, >> >> Brian >> >> > >
