Windows scripter (BE-Brussels)

Delivering Microsoft Windows Installer (MSI) packages

Mission:

Mission of I&O-Wintel Release Services:
· Inside I&O Technical Services, our Wintel Release Services team of about 25 collaborators takes care of a portfolio of 1.500 applications and delivers 2.300 changes per year to realize new projects and to support the stability and evolution of the end user computing environment.
· Before it reaches the end users, every Windows application is subject to a software release process to ensure that it meets the corporate standards (technical, security, compliance) and that it does not show undesirable behaviour (quality).

The deliverables of the team consist of quality assured Microsoft Windows Installer (MSI) packages created using Install-Shield Admin-Studio and/or Microsoft Softgrid packages, following our company wide standards for software in the Windows environment. These releases are deployed on front end and/or back end Windows infrastructure (workstation and servers).
The list of software to be released is dependant on the projects or update releases. Each request for deployment of an application/software is subject to a release process that consists of the following phases:
1. Intake (information gathering & proposal)
2. Build (Package development + technical testing)
3. Deployment (Users functional testing + put in production)
4. After care
As a single point of contact for the customer the role of Wintel Release Officer is, according to his situation on the “learning curve”, to observe, participate in, lead the activities and the production of deliverables in these phases :
1. Intake phase
The purpose of the intake phase is to prepare the Wintel Release:
- Collect the information to understand the demand of the customer
- Analyze the request.
- Propose a solution to the customer in order to build the solution according the request and existing standards.
2. Build phase
The purpose of build phase is to package the software for delivery to end users:
- Put the application in the right format for distribution to end users (Packaging)
- Test the packaged application from a technical point of view (Technical testing) and control its quality (Basic Generic Tests).
3. Deployment phase
The purpose of the production phase has 2 major parts: Users functionality tests and put the request in production respecting the ”change implementation process” (the standards):
User Functionality Test:
- Make the solution/software available for the user functionality tests by deploying in QA (dry run of the production installation script)
- Give support to the users during the test
Put in production:
- Make the solution/software available for deployment eventually with a pilot deployment phase
- Manage the different software versions on the different platforms.
4. After care
The purpose of the After-care phase is to ensure the support of the delivered kits during a fixed time after:
- Analyze the incidents due to the delivered kits
- Build solutions to solve those incidents
- Give support to the second line support (SO-OS)
- Make the necessary documentation available for support team and future upgrade-demands

Profile:

Microsoft Windows XP
Microsoft Windows Server 2003
Microsoft App-V (Softgrid) or Microsoft
Windows Installer
Windows Scripting

Please send your CV by email, or contact Kees Maenhout on +32 (0)473 883 856

| 7/17/2009 | Print |