Excellent. Thanks!
On Wed, Jun 5, 2013 at 8:22 AM, Mote, Todd <[email protected]> wrote: > 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 patch > files 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**** > > ** ** > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Benjamin Monrad > *Sent:* Wednesday, June 5, 2013 10:14 AM > *To:* [email protected] > *Subject:* [mssms] CCMSETUP.EXE PATCH= 32-bit vs 64-bit?**** > > ** ** > > Hi,**** > > ** ** > > Is anyone doing anything clever to run a universal CCMSETUP.EXE command > line with the PATCH property that will handle both 32-bit and 64-bit > machines?**** > > In particular, I am looking at CM12 SP1 CU1 KB2817245**** > > I just experimented with specifying both versions of the patch, hoping a > 32-bit system would just ignore the 64-bit patch, but the install failed.* > *** > > ** ** > > ** ** > >
