ENGIE IT - How To Update SEP Client With BAT File v1.2

You might also like

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 6

INFORMATION

Classification Internal Status : Approved


Version V1.2 creation date : 11/10/2016
Author Elvin RAHAMEFY Date : 11/10/2016
Reviewed by Date : Cliquez ici pour
entrer une
date.
Approved by Date : Cliquez ici pour
entrer une
date.

HOW TO UPDATE THE SEP CLIENT ON


A SERVER USING BAT FILE
SHORT DESCRIPTION

This document describes how to perform the update of SEP client on a server using a BAT file
that scans the server and automatically choose the right SEP version to install

VERSION DATE UPDATE DESCRIPTION RELATED SECTIONS


1.0 11/10/2016 Initial document

1.1 8/11/2016 Modification due to 7004 to 7061

1.2 14/12/2016 Share update/ credential info

645653757.docx E
Internal

SUMMARY

1 Introduction.............................................................................................3
1.1 Requirements........................................................................................................3
1.2 Task order..............................................................................................................3

2 Access the Share containing the Sources...........................................3


2.1 Share.....................................................................................................................3
2.2 Checking access....................................................................................................4

3 Installation of the SEP update...............................................................4

4 Verify the update.....................................................................................6

V1.0 645653757.docx 2/6


Internal

1 Introduction
This document describes how to perform the update of SEP client on a server using a BAT file.

1.1 Requirements
- The session opened on the server has to have Admin rights
- SEP installed version must be at least 12.1.x
- A Network Drive has to be mounted on the target share server (example DSL)

- To Avoid GPO Blocking, The server needs to be in the target OU Waiting according to its OS
Example : Isz.isinfra.net\Servers Acceptance\Member Servers XXXXXX\Waiting
Please write down the source OU of the server so you can put it back correctly after the installation.
Note : If the server is in the DelegatedProvider Tree View, it isn’t impacted by GPO. you don’t
need to move it in Waiting OU

- Access to the share (see Chapter 2)

1.2 Task order


STEP TASK
1 Put the server in the target OU Waiting (if needed)
2 map the target share that contains the sources + Copy bat file locally
3 Update the SEP client using the BAT file and reboot
4 Verify the Installation

2 Access the Share containing the Sources

2.1 Share
Depending on server’s location the target share will be different. Different version of the script
have been created to match the different locations.

SERVER
LOCATIO
N SCRIPT TO USE SHARE URL
GDC,DCB SEP12_7004_GDC_DCB_CREALYS.ba \\xsr08294.isz.isinfra.net\SEPClient_Patches7061
CRELYS t
S1 SEP12_7061_S1.bat \\H1W1SSR00W.dc.infra.com\
SEPClient_Patches7061
S2 SEP12_7061_S2.bat \\H1W1SSR01T.dc.infra.com\SEPClient_Patches7061
S3 SEP12_7061_S3.bat \\h1w1ssr02q.dc.infra.com\SEPClient_Patches7061
S4 SEP12_7061_S4.bat \\h1w1ssr03N.melinda.local\SEPClient_Patches7061

V1.0 645653757.docx 3/6


Internal

2.2 Checking access


Verify that you have access to the
target share by opening an explorer
window and copying the link you
identified in 2.1

1 Use your SSR local Admin


Account (S1, S2, S3) or your
Domain admin account (GDC, S4,
DCB, DCC)

Example for GDC:

\\xsr08294.isz.isinfra.net\
SEPClient_Patches7061

You must see the X86, X64 and


Script folders.

If you can’t access the share, the


script won’t work

3 Installation of the SEP update

1 Copy the BAT file from the Script


folder of the share.

Paste it on the C:\Temp of the


server.

d2Go to the C:\Temp of the server and


execute the BAT as administrator
by right clicking on it

A CMD Window appears showing


you the status.

The script automatically retrieve the


good executable from the share and
3 launches the installation. (the

V1.0 645653757.docx 4/6


Internal

executable is copied is C:\Temp)

The installation takes about 8


minutes. A countdown has been
created to help you.

During the installation, you can see


in task manager a process named
after the executable name.

As long as the process is up, the


installation is processing

4
In this example :

SEP64_6860To7004_ClientDAXM
SI.exe *32

After about 8 minutes, once the


process disappears, it means that
the installation is over.
5
the CMD Window can be closed

6 If you start SEP Client on the server


by double clicking on the shortcut in
task bar, you’ll see that a reboot is
required.

If you have a maintenance window


you can now reboot the server

V1.0 645653757.docx 5/6


Internal

Only if you moved the server to


Waiting OU :

-After the reboot, put the server


back in its source OU
7
-Open a command prompt, type :
gpupdate /force

-Then reboot again the server

4 Verify the update


To be sure that the update is installed, start SEP Client on the server by double clicking on the shortcut in
task bar.
Then go the Help/About…

You should see that version 12.1.7061.6600 is installed

V1.0 645653757.docx 6/6

You might also like