Custom Updates

Custom Updates
Custom Updates are updates where you can do actions before and/or after the update itself. As
these actions can write in registry, create folders these updates needs to be run with administrative
privileges. So, if you use the option Can Request User Input in the main Update Creation Wizard, the
user must belong to the administrators group.
These actions are:
- Execute a file (*.Exe, *.Msi):
- Run a Script (*.Vbs,*.Ps1):
- Create a Text File:
- Work with Files:
- Work with Folders:
- Work with Services:
- Work with Registry Keys:
- Work with Registry values:
WSUS Package Publisher Documentation 1

- Declare a Variable:
- Shutdown or Reboot computer:
- Wait x seconds:
- Kill a process:
- Return Code:
These Actions are simple. For more complex actions, you should write a VbScript and run it.
I) Detail view of Actions :

a. Execute a file :
This action is usually use to run the update itself (generally an EXE or a MSI).
Fill the Path to the File field. Dont use quote.
If you need to add some Parameters, put it in the next field. If some parameters have
space in it, use quote like this:
If you dont want this EXE to run too much time, you can set a maximum time.

If the EXE or MSI file returns a Return Code at the end, you can store it in a Variable.
You have to define this variable before.
b. Run a script :
This action is useful to run complex action that cant be performed with these simple
actions.
Choose between VbScript or Powershell script. Indicate the path to the script and eventually
Arguments.
If you dont want this script to run too much time, you can set a maximum time.
If the script file returns a Return Code at the end, you can store it in a Variable. You
have to define this variable before.
c. Create a Text File :

This action allows you to create a text file and define the content of this file.

d. Work with Files:
Copy, Delete or Rename a file.
File: The full path to the source file.

Destination: The full path to the destination file (when copying)
New name: The new name of the file (when renaming)
e. Work with Folders:

Add, Delete or Rename a folder.
Folder: The full path to the folder.

New name: The new name of the folder (when renaming)
When you create a new folder, you can create several folders at once. For example, if
only C:\Temp exists, you can create C:\Temp\folder1\folder2\folder3 in on
FolderAction.
When you delete a folder, if the folder is not empty, it will delete with all its content.

f. Work with Services :
With action, you will be able to Start, Stop or Unregister service. Or change the
starting mode of a service.
g. Work with Registry Keys:

Add, Delete or Rename a Registry Key.
Hive: Choose between HKLM and HKCU. Be aware that HKCU is only reachable if you
are using the option Can Request User Inputs in the main Update Creation window.
Key: Full path to the key, which you want to work with.
New Name: Name of the key after renaming.

h. Work with Registry Values:
Here, you will be able Add, Delete, Modify or Read a registry value.
Hive: Choose between HKLM and HKCU. Be aware that HKCU is only reachable if you are
using the option Can Request User Inputs in the main Update Creation window.
Key: Full path to the key, which you want to work with.
Value: Name of the Value, which you want to work with.
New Data: Data you want to put in the Value when Adding or Modifying a Value.
Value Type: Type of the Value, when you Adding a Value.
i. Declare a Variable :
Variable are useful to store Return code of an Exe or MSI, and using it later with
the Exit action.
j. Shutdown or Reboot computer :

Allow to shut down or reboot the computer.

k. Wait x Seconds :
Allow to wait for x Seconds.
l. Kill a process :
Allow to kill a process. If the process is start many times, all instance of this process
will be killing.
m. Return Code:
Usually, the last action. Allow to end the process by sending a Return code for this
custom update.
You can return always the same code, or return a code from a variable previously
filled.

II) Making a custom update :
Lets try it. We will publish an update for Adobe Reader XI and resetting a registry Data.
Start Wsus Package Publisher, connect to the Wsus Server. Right-click on the Adobe
Reader Product and choose Create a Custom Update
The Custom Update Wizard shows up.

Double-click on Declare a variable. Give a name to this Variable and choose Variable Type =
Int. This variable will be used to store the return code of the MSI that we will launch later.
Add an Execute file action.
In the Path to the File field, put the name of the MSI : AdbeRdrUpd11003.msp
You do not have to give the full path because we will provide the MSI file with the update, so the MSI
file will be in the same directory.
In the parameters, we need to indicate some switch to make this update silent :
This shouldnt take more than 10 minutes to update client computers, so we check the checkbox to
kill the process if it runs more than 10 minutes.
In the combobox, choose the variable previously define. So that, the code return by the MSI will be
store into this variable.

Then Add a Registry Element:
Setting it like above. This allows to set to zero the iProtectedView Value. This wills deactivate the
ProtectedView feature of Adobe Reader.
Then Add a Return Code Element:
And choose the variable you have defined above.
Click Ok to close the wizard and return in Wsus Package Publisher.

The Update Creation Wizard appears:
The Update File is pre-filled with the CustomeUpdateEngine.Exe, which is the engine who will run
customs actions. In Additional Files you can see the XML file which contains actions setting.
Add the MSP file for the Adobe update.
Dont forget it. Or else the Executable action wont run it.
Click on Next button.
Fill necessary fields. Dont touch the CommandLine. It contains the parameter for
CustomUpdateEngine.exe

In the IsInstalled rule Page, create a rule based on the File Version:

In the IsInstallable rule Page, create 3 rules based on the File Version:
Adobe Reader 11.0.3 can be installed over Adobe Reader XI, 11.0.1 and 11.0.2.
Publish the update. Check that it apply to computers that need it, and dont apply to computer that
dont need it.
If you are satisfied with your test, you can deploy it on test group to see if installation goes right.
Leave comments or questions to: https://wsuspackagepublisher.codeplex.com/discussions

Custom Updates

Uploaded by

Document Informationclick to expand document information

Copyright:

Available Formats

Custom Updates

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Custom Updates

Uploaded by

Copyright:

Available Formats

Custom Updates

These actions are:

- Execute a file (*.Exe, *.Msi):

- Run a Script (*.Vbs,*.Ps1):

- Create a Text File:

- Work with Files:

- Work with Folders:

- Work with Services:

- Work with Registry Keys:

- Work with Registry values:

WSUS Package Publisher Documentation 1

- Shutdown or Reboot computer:

I) Detail view of Actions :

WSUS Package Publisher Documentation 2

c. Create a Text File :

WSUS Package Publisher Documentation 3

File: The full path to the source file.

e. Work with Folders:

Folder: The full path to the folder.

WSUS Package Publisher Documentation 4

g. Work with Registry Keys:

WSUS Package Publisher Documentation 5

j. Shutdown or Reboot computer :

WSUS Package Publisher Documentation 6

WSUS Package Publisher Documentation 7

The Custom Update Wizard shows up.

WSUS Package Publisher Documentation 8

Add an Execute file action.

WSUS Package Publisher Documentation 9

Then Add a Return Code Element:

And choose the variable you have defined above.

Click Ok to close the wizard and return in Wsus Package Publisher.

WSUS Package Publisher Documentation 10

Add the MSP file for the Adobe update.

Click on Next button.

WSUS Package Publisher Documentation 11

WSUS Package Publisher Documentation 12

Leave comments or questions to: https://wsuspackagepublisher.codeplex.com/discussions

WSUS Package Publisher Documentation 13

You might also like

- Execute a file (.Exe, .Msi):

- Run a Script (.Vbs,.Ps1):