Difference between revisions of "CTUpdate"

From WPKG | Open Source Software Deployment and Distribution
Jump to: navigation, search
(Proper reboot cycles)
Line 5: Line 5:
 
Download it here: http://www.heise.de/ct/projekte/offlineupdate/download_uk.shtml
 
Download it here: http://www.heise.de/ct/projekte/offlineupdate/download_uk.shtml
  
Note 1: CTUpdate cannot be run from a non-mapped drive, so make sure you map your repository first. The bat-file below expects %WPKG_DRIVE% to be set to this drive. Alternatively, you can modify the bat-file to temporarily map the drive.
+
Note 1: CTUpdate cannot be run from a non-mapped drive, so make sure you map your repository first. The bat-file below expects %WPKG_DRIVE% to be set to this drive. Alternatively, you can modify the bat-file to temporarily map the drive. (net use x: \\ntinstall\wpkg /PERSISTENT:no)
 
+
Note 2: Making proper reboot cycles etc. have not been paid attention to. CTUpdate does have functionality for resuming on reboot that is not enabled in the below setup.
+
  
 
Then run it in order to create a repository containing the languages and systems you want, but you do NOT need to create ISO files. The repository will be placed in the client subfolder. Then copy the entire tree over to the WPKG software folder and use the following entries:
 
Then run it in order to create a repository containing the languages and systems you want, but you do NOT need to create ISO files. The repository will be placed in the client subfolder. Then copy the entire tree over to the WPKG software folder and use the following entries:
Line 42: Line 40:
 
%WPKG_DRIVE%
 
%WPKG_DRIVE%
 
cd %SOFTWARE%\ctupdate4\client\cmd
 
cd %SOFTWARE%\ctupdate4\client\cmd
 +
del %windir%\ctupdate.done
 
cmd /c doupdate.cmd %*
 
cmd /c doupdate.cmd %*
date /T > %windir%\ctupdate.done
 
 
</source>
 
</source>
 +
 +
For '''proper reboot cycles''' you will need to add a line to ctupdate4/client/cmd/DoUpdate.cmd. See diff: (make sure you don't add it to the SuggestRecall part)
 +
<source lang="diff">
 +
--- C:/Users/Kalmi/Desktop/DoUpdate.cmd Sat Sep 13 19:41:10 2008
 +
+++ G:/wpkg/software/ctupdate4/client/cmd/DoUpdate.cmd Sat Jan 31 21:57:03 2009
 +
@@ -736,6 +736,7 @@
 +
echo Installation successful. Please reboot your system now.
 +
echo %DATE% %TIME% - Info: Installation successful >>%UPDATE_LOGFILE%
 +
echo.
 +
+date /T > %windir%\ctupdate.done
 +
goto EoF
 +
 +
:Cleanup
 +
</source>
 +
This will ensure that wpkg will only consider the install successful when ctupdate ends up in InstSuccess (and not in SuggestRecall). So if a restart is needed wpkg will restart(saying the the install failed, but it requires a resart, so I'm going to restart now) and try the install again...
  
 
[[Category:Silent installers for Windows Hotfixes]]
 
[[Category:Silent installers for Windows Hotfixes]]

Revision as of 19:48, 31 January 2009

CTUpdate is an alternative method for applying Windows and Office hotfixes and service packs. It consists of two parts:

  1. A program to automatically queries and downloads the latest packages into a repository.
  2. A program that reads the repository and applies any updates to the local machine.

Download it here: http://www.heise.de/ct/projekte/offlineupdate/download_uk.shtml

Note 1: CTUpdate cannot be run from a non-mapped drive, so make sure you map your repository first. The bat-file below expects %WPKG_DRIVE% to be set to this drive. Alternatively, you can modify the bat-file to temporarily map the drive. (net use x: \\ntinstall\wpkg /PERSISTENT:no)

Then run it in order to create a repository containing the languages and systems you want, but you do NOT need to create ISO files. The repository will be placed in the client subfolder. Then copy the entire tree over to the WPKG software folder and use the following entries:

<package id="ctupdate" name="Windows and Office hotfixes and service packs" revision="0" reboot="true" priority="0">
  <!--
  CTUpdate keeps its own state (by checking Windows and see which updates should be
  installed), so the wpkg integration is not entirely clean.
  
  The bat-file touches a statefile after the first successful run through.
  
  Increment revision each time the CTUpdate repository is updated, and it will be run
  again by wpkg and figure out what needs to updated itself.
  
  Prioritize below Office, as Office is updated by this as well.
  
  The uninstall simply removes the statefile - we don't provide for uninstalls of
  patches, however one might want to reinstall the package in order to rerun it.

  See ctupdate4\client\cmd\doupdate.cmd for other possible flags (IE7 install etc.)
  -->
   <check type="file" condition="exists" path="%windir%\ctupdate.done" /> 
   <install cmd='cmd /c "%SOFTWARE%\ctupdate4\runwpkg.bat" /nobackup' />

   <upgrade cmd='cmd /c "%SOFTWARE%\ctupdate4\runwpkg.bat" /nobackup' />
   <remove cmd='cmd /c del %windir%\ctupdate.done'/>

</package>

The referenced bat-file:

%WPKG_DRIVE%
cd %SOFTWARE%\ctupdate4\client\cmd
del %windir%\ctupdate.done
cmd /c doupdate.cmd %*

For proper reboot cycles you will need to add a line to ctupdate4/client/cmd/DoUpdate.cmd. See diff: (make sure you don't add it to the SuggestRecall part)

--- C:/Users/Kalmi/Desktop/DoUpdate.cmd	Sat Sep 13 19:41:10 2008
+++ G:/wpkg/software/ctupdate4/client/cmd/DoUpdate.cmd	Sat Jan 31 21:57:03 2009
@@ -736,6 +736,7 @@
 echo Installation successful. Please reboot your system now.
 echo %DATE% %TIME% - Info: Installation successful >>%UPDATE_LOGFILE%
 echo.
+date /T > %windir%\ctupdate.done
 goto EoF
 
 :Cleanup

This will ensure that wpkg will only consider the install successful when ctupdate ends up in InstSuccess (and not in SuggestRecall). So if a restart is needed wpkg will restart(saying the the install failed, but it requires a resart, so I'm going to restart now) and try the install again...