Appendix. Fractalia Manager Version 5.0 FRACTALIA Software

Appendix Fractalia Manager Version 5.0 FRACTALIA Software

2 A. SERVER TOOLS... 3 1. SYNCHRONIZER WITH ACTIVE DIRECTORY (AD)... 3 1. SyncAD2IRM.exe.config... 3 2. Installation... 4 2. PROCESS AND URLS ANALYZER... 5 1. Configurating ProcessAndUrlAnalyzer.exe.config... 6 2. Task programmed with the ProcessAndUrlAnalyzer... 7 3. LICENSEACTIONS... 10 1. IRMLicenseActions.exe.config... 10 2. Enterprise License... 11 4. ODP/OTP TOOL... 15 5. REPEATERS... 16 1. Normal... 16 6. CONFIGURATION OF SQL REPORTING SERVICES... 19 7. GENERATING CUSTOMER REPORTS... 24 1. Creation of models... 24 2. Report Builder... 33 B. CLIENT TOOLS... 40 1. IRM CONFIGURATION FILES... 40 1. Config.xml... 40 2. Updates.xml... 43 3. PatchClientModule.config... 45 4. SelfServiceTool.exe.config... 45 5. Registering terminals by command line... 45 2. FRACTALIA MANAGER MOBILE CONFIGURATION FILES... 46 1. Config.xml... 46 C. UTILITIES... 47 1. INSTANT RECOVERY SYSTEM UNATTENDED INSTALLATION... 47 1. Normal installation... 47 2. Unattended Installation... 47 3. Update... 49 4. Disk Write Strategy... 49 2. INSTANT RECOVERY SYSTEM COMMAND LINES... 49 1. VirtualDiskControl.exe... 57 3. GENERATING INVENTORY TEMPLATES... 59 1. Format of the inventory template... 60 4. UNATTENDED INSTALLATIONS... 66 1. deploy.bat... 66 2. Creating the installation... 66

3 A. Server Tools 1. Synchronizer with Active Directory (AD) The synchronizer of the Active Directory (AD) with IRM takes care of dumping the information necessary to integrate IRM with AD. The information is only transferred from AD to the IRM database so that it never modifies the information in the AD. On synchronizing the AD data against the IRM, the unit organisational structure is copied converting them into IRM groups and positioning the machines in the same place as in the AD. 1. SyncAD2IRM.exe.config The configuration file is used to introduce the synchronization characteristics. <syncad2irm> <domains> <domain server="eccweb48" aduser="administrator" adpass="p@ssw0rd" nbdomain="" adroot="dc=irm48,dc=ecc" syncpart="0" descriptiontoalias="true" /> </syncad2irm> Server: introduces the domain server against which the replica will be made. You can specify the complete domain name with which it will search for the closest domain server. aduser: introduces the AD user name that is used to connect to it. If the machine belongs to the AD then this field can be omitted, indicating the synchroniser to use the user that is functioning already. adpass: introduces the user password with which you access the AD. If the user is omitted then this field will not be valid. nbdomain: introduces the domain name. This parameter is only necessary if the machine in which the synchroniser is running does not have access to the DNS server associated with the active directory. If you omit this parameter and specify the user you must specify in the form: user@domain (for example administrator@fractalia.es) adroot: introduces the AD root partition that you want to synchronise. It must have the form DC=fractalia, DC=biz. Sync Part: introduces partial synchronisation instead of a total one. The synchroniser will only take into account those elements that have been modified since the last synchronisation. If various domain servers are used, the synchroniser cannot detect changes made in a domain server other than the one indicated, so it is not recommendable to put a very high value for this parameter.

4 <sync2irm connectionstring = "Data Source=ECCWEB48\SQL2005;Initial Catalog=IRM48;User ID=sa;pwd=P@ssw0rd;Application Name=SyncAD2IRM" idclient = "3" timesleep="0" defaultrollbackmode="manual" timepoll="1" timeretry="1" numretry="1" connectiontype="1" /> Connection String: configures the connection string to the IRM database. Pressing on Check, you can verify that the connection string to the IRM database is correct. IdClient: when you are using multiple clients identify the IRM client to which the synchronisation data is assigned. Time Sleep: to configure the delay, in milliseconds, between the synchronisation of the AD elements. This field is used to slow the service so as not to consume all the machine s resources. Default Rollback Mode: configures the Rollback mode as manual or automatic, with which new machines detected in AD will be configured. Time Poll: configures the time, in seconds, of the call to check the inventory with which the new groups detected in AD will be configured. Time Retry: configures the time, in seconds, of the call to check the updates with which the new groups detected in AD will be configured. numretry: configures the time, in seconds, of the call to check the state of the Rollback with which the new groups detected in AD will be configured. This call time is different from the one in the IRM platform group properties tab. 2. Installation The synchronizer can be installed in any machine, even if it is not registered in the AD, although it is recommendable to install it in a domain server for security and performance. It is necessary to create a service using the executable of ADSync, and initiate it, so that it functions correctly. For this, execute from the command line: sc create ĄServicenameą binpath= ąpath where the SyncAD2IRM.exe is to be foundą start= auto Every time a change is made in the configuration file the service must be rebooted. Configuration example:

5 Figure 1. Example of synchroniser configuration <syncad2irm> <domains> <domain server="172.16.0.64" aduser="administrator" adpass="pass" nbdomain="" adroot="dc=tests,dc=fractalia" syncpart="0" descriptiontoalias="true" /> </syncad2irm> <sync2irm connectionstring = "Data Source=172.16.0.64;Initial Catalog=IRM48;User ID=sa;pwd=pwd;Application Name=SyncAD2IRM" idclient = "3" timesleep="0" defaultrollbackmode="manual" timepoll="1" timeretry="1" numretry="1" connectiontype="1" /> 2. Process and URLs Analyzer In order to execute the Process and URLs application, the file, ProcessAndUrlAnalyzer.exe.config, must be configured and a scheduled task for Windows must be created.

6 1. Configurating ProcessAndUrlAnalyzer.exe.config <?xml version="1.0" encoding="utf-8"?> <configuration> <appsettings> <add key="sourcepath" value="c:\inetpub\wwwroot\irm\pub\receivedfiles\" /> The local path where the files uploaded from the platform are stored is configured. <add key="processedpath" value="c:\inetpub\wwwroot\irm\pub\receivedfiles\processed" /> The local path where the processed files once they have been processed by the analyser are stored. <add key="erroneouspath" value="c:\inetpub\wwwroot\irm\pub\receivedfiles_diff\" /> The local path where the erroneous processed files once they have been processed by the analyser are stored. <add key="connectionstring" value=" data source=127.0.0.1;initial catalog=irm; persist security info=false; user id=sa; pwd=; packet size=4096" /> data source=.; initial catalog=irm; persist security info=false; user id=sairm; pwd=sairm; packet size=4096 PROPERTY data source initial catalog persist security info user id pwd packet size DESCRIPTION The name of the SQL server is introduced, and such usually matches the IP or host name of the machine. The database to be used is introduced; in this case, IRM. Introduce this if you want the security to be integrated with Windows, or not if you want security to be integrated with the SQL Server. If the value is set to false, then security is not integrated with Windows, and if the value is set to true, it is integrated. This option is set, by default, to false. The user name is introduced in order to access the database indicated to the initial catalog. The password corresponding to the login session introduced with the previous property is introduced. The maximum size of the packets to be introduced into the database is introduced. This property can be omitted. </appsettings> <system.windows.forms jitdebugging="true" /> </configuration>

7 2. Task programmed with the ProcessAndUrlAnalyzer The Scheduled Task is accessed through the Control Panel (Figure 6), and Figure 7 is shown, where a new scheduled task must be added. Figure 6. Open Scheduled Tasks through the Control Panel Figure 7. Scheduled Task When Add Scheduled Task is clicked, Figure 8 is shown, which is a window in which a process must be followed for a program to be executed when the user has scheduled it. Figure 8. Scheduled Task Wizard

8 After clicking on Browse, a window is shown (Figure 9) that will allow you to go to the path where the executable file, ProcessAndUrlAnalyzer, is stored in order to open it. Figure 9. Select the executable file, ProcessAndUrlAnalyzer In the windows in Figure 10 and Figure 11, you can select when the task is to be executed, that is, the time and date when the task must begin execution. Figure 10. Select when the task is to be executed Daily is selected in the window in Figure 10 and Every Day in the window in Figure 11.

9 Figure 11. Select the time and date you want this task to begin execution In the window in Figure 12, the user name and password needed to access the Server are requested in order for the execution of the task to start once that user is logged in. Figure 12. Introduce the user name and password for the Server Below (Figure 13), select the option of opening advanced properties when the configuration of the task is finalised. Figure 13. Select open advanced properties when finalising

10 When the advanced properties of the scheduled task are open, you must click on the Schedule tab in order to schedule when the task is to be executed after the machine is turned on. Figure 14. Schedule the task 3. LicenseActions LicenseActions is a tool that uses a super administrator to create several enterprises for the use of the platform, and administrator users for the created enterprises. It is also used to generate a number of licenses for the enterprises. When double clicking on the executable file, the window in Figure 15 is shown, where you must authenticate in order to access the configuration tool. Figure 15. Authentication window 1. IRMLicenseActions.exe.config <nhibernate> <add key="hibernate.connection.provider" value="nhibernate.connection.driverconnectionprovider" /> <add key="hibernate.dialect" value="nhibernate.dialect.mssql2005dialect" />

11 <add value="nhibernate.driver.sqlclientdriver"/> key="hibernate.connection.driver_classą <add key="hibernate.connection.connection_string" value="data source=.; initial catalog=irm;persist security info=false;user id=sa;pwd=;packet size=4093" /> data source=.; initial catalog=irm; persist security info=false; user id=sairm; pwd=sairm; packet size=4096 PROPERTY data source initial catalog persist security info user id pwd packet size DESCRIPTION The name of the SQL server is introduced, and such usually matches the IP or host name of the machine. The database to be used is introduced; in this case, IRM. Introduce this if you want the security to be integrated with Windows, or not if you want security to be integrated with the SQL Server. If the value is set to false, then security is not integrated with Windows, and if the value is set to true, it is integrated. This option is set, by default, to false. The user name is introduced in order to access the database indicated to the initial catalog. The password corresponding to the login session introduced with the previous property is introduced. The maximum size of the packets to be introduced into the database is introduced. This property can be omitted. </nhibernate> <appsettings> <add key="pathsetupconfig" value="c:\_utils\platformconfigurator\serverconfig.xml"/> The path where the ServerConfig.xml file is located is introduced. </appsettings> 2. Enterprise License With this tab, enterprises are created, as well as an administrator user for each of the created enterprises. Also, a number of licenses can be allocated, without exceeding the number of total licenses, to each of the enterprises (Figure 24).

12 License Information Figure 24. Entreprises Licenses tab With this panel, enterprises are created and deleted, and information related to each of them is shown: name of the enterprise (Enterprises), administrator user (Master User), number of licenses allocated (Licenses), number of active licenses (Activated), beginning date for licence operation (Initial Date) and end date for licence operation (Final Date). : a new enterprise is created. When clicking the button, the window in Figure 25 is shown, where the data regarding the enterprise must be introduced. Figure 25. Enterprise Data window Name: the name of the enterprise is introduced. Address: the address of the enterprise is introduced. Postal code: the postal code of the enterprise is introduced. City: the city where the enterprise is located is introduced. Country: the country where the enterprise is located is introduced.

13 : the enterprise selected in the panel is deleted. Once the enterprise is created, an administrator user for this enterprise must be created. To do so, you must click the Master User field of the enterprise, and the window in Figure 26 will be shown, where the user s data must be filled in. Figure 26. Generic tab for the Agent window Under the Generic tab (Figure 20), you must introduce the new user data, as well as the name with which s/he will use to log into the platform and his/her password. Name: the user name is introduced, 50 characters maximum. Surname 1: the first surname of the user is introduced, 50 characters maximum. (Optional field) Surname 2: the second surname of the user is introduced, 50 characters maximum. (Optional field) E-mail: the e-mail address of the user is introduced. The admitted mail format is inbox@subdomain.domain (optional field) Description: some comment about the user is introduced, 50 characters maximum. (Optional field) Login: the user name used to access the platform is introduced, 20 characters maximum. Password: the user key used to access the platform is introduced, 6-15 characters maximum. Retype password: the user key used to access the platform is repeated, 6-15 characters maximum. Under the Configuration tab (Figure 27) the user language is selected.

14 Figure 27. Configuration tab Under Additional Data (Figure 28), the user data is introduced. It is not necessary to fill in all those details, as they are optional. Figure 28. Additional Data tab Department: the department to which the user belongs is introduced, 50 characters maximum. Address: the address of the user is introduced, 50 characters maximum. Locality: the locality of the user is introduced, 50 characters maximum. Postal Code: the postal code of the user is introduced, 10 digits maximum. Province: the province of the user is introduced, 50 characters maximum. Country: the country of the user is introduced, 50 characters maximum. Contact person: the contact person corresponding to the user is introduced, 50 characters maximum. Telephone: the telephone number of the user is introduced, 10 digits maximum. Web page: the web page of the user is introduced, 50 characters maximum. Mobile pone: the mobile telephone number of the user is introduced, 10 digits maximum. Company: the company the user belongs to is introduced, 50 characters maximum. Then the initial date and final date for licence operation must be selected. To do so, the Initial Date and Final Date fields must be clicked and the relevant dates must be selected.

15 License Management With this panel, a number of licenses can be assigned to the enterprise, and the enterprise s assigned licenses, which can be selected under the License Information panel, are updated. : the number of licenses, introduced in the upper field, is assigned to the selected enterprise. : the active licenses of the selected company are updated. License Expire Date This panel shows the expiry date of the licenses introduced in the Expire Date field of the License Generator application, which is explained below. 4. ODP/OTP tool ODP/OTP is a tool used by an administrator to generate a key. This key is provided to the user so that he can access the Instant Recovery System. Figure 31. Password provided to the administrator (graphic mode) Figure 32. Password provided to the administrator (text mode)

16 The password, which is marked in red in Figure 31 or Figure 32, is provided to the administrator so that, through the use of the ODP/OTP tool, it generates a key so that the user can introduce it in the Password field, which is marked in green in Figure 31 or Figure 32. When the administrator receives the password, s/he executes, per command line, the tool, depending on whether the key that the user needs is for once (OTP) or for a day (ODP), using one argument or another. The ODP (One Day Password): generates a password for each day. It must be requested from the system administrator. The format of the instruction the administrator must introduce per command line is: ODTPTool.exe ODP dd.mm.yyyy Where dd.mm.yyyy is the present date format ( dd : day, mm : month, yyyy : year). The OTP (One Time Password): generates a password every time the console is accessed. 5. Repeaters ODTPTool.exe OTP passworduser PasswordUser is the password that the user provides to the administrator, which is marked in red in Figure 31 or Figure 32. 1. Normal You need to mount a server, outside the LAN, with the IRM Repeater vx.x, Setup.exe application. This application acts as a Bypass for the user petitions to take remote control of other terminals, if this application is deactivated the connections die, and it will not be possible to establish remote connections in accordance with petitions. On installing the application, the notification area will show that the Repeater is executing. you press on it with the right hand button of the mouse (Figure 2), you can access the Repeater adjustments (Figure 3). Figure 2. Icon in the notification area To configure the Normal mode introduce the Viewer and Server port. The Viewer port must be mapped in the router input and with the terminal over which you want to take remote control.

17 Figure 3. Repeater Adjustments For the client it is necessary to configure the Remoting fields so that it connects correctly. The configuration can be made with the local client configurator or by modifying the client configuration file. If you do it through the local configurator, you have to execute the application (Figure 4), click on Proxy and configure the part corresponding to the Remoting channel (Figure 5) Figure 4. Opening local client configurator

18 Figure 5. Local client configurator Server: introduces the server name or IP where the Remoting module is installed. Directory: introduces the path to the Remoting module folder. Port: introduces the port through will go to Remoting. Resource: introduces the Remoting resource name. If you do it through the configuration file, you must edit the Config.xml file in the path %PROGRAMFILES%\4.8\Iriscene Remote Manager\" and reboot the IRM service. <remotingchannel> <Enabled>true</Enabled> Enables Remoting. <ReconnectionTime>15</ReconnectionTime> Reconnection time for Remoting. <HttpSleepRetryConnectionTime>500</HttpSleepRetryConnectionTime> <UrlGenuineChannelLog>D:\IRM\log\</UrlGenuineChannelLog> <Url> <Protocol>ghttp</Protocol> <Host>ECCWEB48</Host> Public IP or DNS of the server where you find the Remoting module. <Port>80</Port> Remoting port <Dir>Fractalia/IRM/IRMRemotingServiceHost</Dir> Path to the IRMRemotingServiceHost folder in the Server <Resource>IrmRemotingService.rem</Resource> </Url>

19 </remotingchannel> Figure 6. Normal 6. Configuration of SQL Reporting Services Report Server is a complete server solution to allow you to create, administrate and deliver Web reports. Figure 7. Reporting Services Configuration Execute the Reporting Services Configuration (Figure 7) and connect with the database server (Figure 8).

20 Figure 8. Connection with database server Next, you have to create the Report Server virtual directory, to do this, click on Report Server Virtual Directory, press the New button and select the WebSite where you want to create it. (Figure 9 and Figure 10) Figure 9. Create a Report Server virtual directory

21 Figure 10. Virtual directory successfully created Then you have to create a Report Manager virtual directory, to do this, click on the Report Manager Virtual Directory, press the New button and select the WebSite where you are going to create it. (Figure 11 and Figure 12)

22 Figure 11. Create a Report Manager virtual directory Figure 12. Virtual directory successfully created Lastly, you have to connect with the Report Server database, to do this, you have to introduce the credentials to connect you with the database, click on the Connect button and apply the changes by pressing the Apply button. (Figure 13 and Figure 14)

23 Figure 13. Connect to the Report Server database Figure 14. Connection to the database successful

24 7. Generating Customer Reports The Customer Reports are reports generated by the Report Server that have been created by the administrator with the Report Builder tool. To generate them it is necessary to follow certain rules, which are explained in the following text. 1. Creation of models To create the models to be used in the next step you have to open the program SQL Server Business Intelligence in the server where the Report Server is installed. (Figure 56 and Figure 57) Figure 56. Open SQL Server Business Intelligence Figure 57. SQL Server Business Intelligence Next, you have to create a new Project Report Model (Figure 58 and Figure 59)

25 Figure 58. Create a new project Figure 59. Create a Report Model Project In Solution Explorer (View Solution Explorer), you have to click on the folder Data Sources with the right hand button of the mouse and select the option to add a new Data Source. Figure 60 will be shown. Figure 60. Add a new Data Source Next, you have to press on the New button and insert <Name or IP of server>\instance of database, the user and password to access the database from which you are going to do the reports, the corresponding database (Figure 61). Pressing OK will display (Figure 62). On

26 pressing finish, you will have to insert the name of the new Data source (Figure 63) and so complete the process of adding a new Data Source. Figure 61. Configure the connection string for the new Data Source Figure 62. Configuration finalized

27 Figure 63. Completion of the creation of a new Data Source Figure 64. New Data Source created successfully Next, you have to click on the Data Source Views folder with the right hand button of the mouse and select the option to add a new Data Source View. Figure 65 will be displayed. Figure 65. Add new views of de Data Source Next, select the Data Source created previously (Figure 66) and select the tables on which you are going to make a customised report (Figure 67). If you wish to select all the tables that depend on the one selected, you have to select the table in Included objects and press on the Add Related Tables button.(figure 68 and Figure 69) and then press Next. Insert the name for the new Data Source view to finish the process. (Figure 70 and Figure 71)

28 Figure 66. Selection of Data Source Figure 67. Select tables to include in the report

29 Figure 68. Add tables that depend on one that has been selected Figure 69. Tables added

30 Figure 70. Insert a name for the Data Source view Figure 71. New Data Source view successfully created Next, click on the Report Models folder with the right hand button of the mouse and select the option to add a new Report Model. Figure 72 will be displayed. Figure 72. Add a new Report Model Following this, select the Data Source created previously (Figure 73) and the elements to be created will be displayed (Figure 74) (the default values are recommended). Insert a name for the Report Model to complete the process and then press Run. (Figure 75, Figure 76 and Figure 77)

31 Figure 73. Select the view created previously Figure 74. Select the options on which the reports are generated

32 Figure 75. Insert a name for the Report Model and press Run Figure 76. Start of the Report Model creation process

33 Figure 77. Report Model completed Next, you have to deploy the solution, to do this press on the button marked in Figure 78. 2. Report Builder Figure 78. Deploy the solution To open the Report Builder application in the server you have to open the Internet Information Server (IIS), click on the virtual directory created in Report Manager Virtual Directory in the Report Server configuration tool (Figure 79). Next, click with the right hand button..

34 Figure 79. Report Manager Virtual Directory in IIS Figure 80. Open the Home.aspx page in the explorer

35 Figure 81. Home.aspx To open the Report Builder application in a machine execute the following from the explorer Error! Referencia de hipervínculo no válida. or IP of the server>/< Report Manager Virtual Directory >/Home.aspx and Figure 81 will be displayed. To show (Figure 82, Figure 83 and Figure 84) you must execute Report Builder. Figure 82. Execute the Report Builder Figure 83. Download the Report Builder application

36 Figure 84. Report Builder Next, double click on one of the models displayed in the Figure 85 panel and the report designer will open. It is here that you will create a personalised report by dragging the entities or fields that we want to appear in the report. Figure 85. Select one of the available models in the panel

37 Figure 86. Designer of reports for personalised reports Once the reports are finished, save them in the ReportServer folder. (Figure 87) NOTE: The name used to save the report must not have blank spaces. Figure 87. Save the description of the reports You have to create a shared folder in the server to keep the file.rdl with the same name used in the previous step. (Figure 88, Figure 89, Figure 90, Figure 91, Figure 92, Figure 93 and Figure 94)

38 Figure 88. Create a new folder in the server Figure 89. Share the folder I Figure 90. Share the folder II Figure 91. Share the folder III

39 Figure 92. Save the rdl file Figure 93. Select the shared folder created previously in the server Figure 94. Save the rdl file in the shared folder on the server

40 B. CLIENT TOOLS 1. IRM configuration files 1. Config.xml This file is to configure the internal parameters of the client. It is to be found in the directory: Ą%PROGRAMFILES%\Iriscene Remote Manager\4.8" The code lines that are configured in this file will appear in bold. Normally this file is modified with the IRM configurator program; nevertheless, it is always possible to do it manually. <general> <GuidTerminal>SOFTWARE\Fractalia\Irm\</GuidTerminal> In this line, the part of the register where the terminal identifier is kept is configured. <LogFile>D:\IRM\log\IriSceneRemoteManager.log</LogFile> Configures the path where the log of calls between client and platform is stored. <CentralPlatform> http://www.fractaliasoftware.com/applications/irm_ws.asmx </CentralPlatform> Configures the address in the IRM server where the Web Service connection with the client can be found. <Client>ECC</Client> Shows the company where the client is registered. <ServiceStartTime>30</ServiceStartTime> Configures the delay, in seconds, which the IRM service takes before initiating after starting the machine. <ReconnectionTime>1</ReconnectionTime> Configures the time, in minutes, of reconnection with the Web Service, in case this is interrupted. <RestartInterval>60</RestartInterval> Configures the time, in seconds, that is displayed in the countdown window when the computer has to reboot for some action taken in the platform. <User>Fractalia</User> Configures the administrator s user name. <Password>82ZuX+E=</Password> Shows the coded password of IRM. <Language>es</Language> Configures the default language for IRM tools in the client.

41 <EnableInstallLog>true</EnableInstallLog> Enables the IRM logs in the client. </general> <proxy> <IpProxy> </IpProxy> Configures the Proxy IP. <PortProxy> </PortProxy> Configures the Proxy port. <UserProxy> </UserProxy> Configures the user for Proxy authentication. <PasswordProxy> </PasswordProxy> Configures the password for Proxy authentication. <DomainProxy> </DomainProxy> Configures the Proxy domain. </proxy> <inventory> <InventoryPath>D:\IRM\Datos</InventoryPath> Configures the address where the client inventory is going to be stored. </inventory> <upload> <UploadTime>1</UploadTime> Configures the time frequency, in minutes, the data found in the send data path is sent. <UploadPath>D:\IRM\Datos\Envio</UploadPath> Configures the address to upload data. Any file placed in this folder will be sent in UploadTime seconds to the platform. <NumberRetry>2</NumberRetry> Configures the number of attempts to upload to the server. <Icon> <Path>Images\Subida.gif</Path> Configures the address of the upload icon. This icon is displayed in the notification area. <Message>Uploading file to Central Platform</Message> Configures the message that will be displayed in platform events when uploading data. </Icon> </upload> <rollback>

42 <password>82zux+e=</password> Shows the coded password of rollback. </ rollback > The IRM Windows applications (IRS console and configuration) have different types of security: Authentication integrated with Windows. Only those users that are system administrators can access the applications. Authentication IRM. The applications will request authentication on initiation, (as defined in the general section of the present file). Authentication ODP. The applications will request authentication on initiation. This will be a key obtained through the ODP/OTP tools. <security> <authentication> <Windows>1</Windows> Authentication of Windows, if it is 1 the value is true and if it is 0, false. <IRM>1</IRM> Authentication of Iriscene Remote Manager, if it is 1 the value is true and if it is 0, false. <ODP>1</ODP> Authentication of Instant Recovery System One Day Password, if it is 1 the value is true and if it is 0, false. </authentication> </security> <remotingchannel> <Enabled>true</Enabled> Enables Remoting. <ReconnectionTime>15</ReconnectionTime> Remoting reconnection time. <HttpSleepRetryConnectionTime>500</HttpSleepRetryConnectionTime> <UrlGenuineChannelLog>D:\IRM\log\</UrlGenuineChannelLog> <Url> <Protocol>ghttp</Protocol> <Host>ECCWEB48</Host> Public IP or DNS of the server where the Remoting module is to be found. <Port>80</Port> Remoting Port <Dir>Fractalia/IRM/IRMRemotingServiceHost</Dir> Path to find the RemotingServiceHost folder in the Server <Resource>IrmRemotingService.rem</Resource> </Url> </remotingchannel>

43 <TerminalControlServer> <Enabled>true</Enabled> Enable or disable the Callback Port. <CallBackPort>27027</CallBackPort> Inserts the port that is going to function as callback. </TerminalControlServer> <information> <CallInterval>15</CallInterval> </information> This is the time interval, in minutes, with which the information module calls the platform. <remoteconfig> <CallInterval>15</CallInterval> </remoteconfig> This is the time interval, in minutes, with which the configuration module calls the platform. <remotecontrol> <Password>82ZuX+E=</Password> Shows the remote control codified password. <Port>5900</Port> Configures the remote control port. <MSSecurity>0</MSSecurity> Security is integrated with Windows, if it is 1 the value is true and if it is 0, false. </remotecontrol> </remoteconfig> <actualizacion> <Password>82ZuX+E=</Password> </actualizacion> 2. Updates.xml This file allows the configuration of the download parameters of the client. It is to be found in the directory: Ą%PROGRAMFILES%\Iriscene Remote Manager\4.8" <P2P_Temp>d:\IRM\p2p\temporal</P2P_Temp> Configures the path where the temporary files are going to be stored. <Shared_Path>d:\IRM\p2p\shared</Shared_Path> Configures the path where the downloaded updates are going to be stored. <Shared_Mb>2048</Shared_Mb>

44 Configures the maximum folder size where the updates are going to be downloaded. <Share_Files>1</Share_Files> Indicates the number of updates that have been downloaded from the platform. <Path_ini>d:\IRM\p2p\ini</Path_ini> Configures the path where the download configuration files are going to be stored. The download configuration files are stored in the server with the extension.ini. <Shared_HTTPServerPort>8182</Shared_HTTPServerPort> Configures the server port for TCP protocol petitions. It is the port for sharing the P2P files. <Mirror>0</Mirror> Shows if the client is in Mirror mode. If it is in Mirror mode it will show a 1 and, if not, a 0. <WAN>1</WAN> Shows if the client is in WAN mode. If it is in WAN mode it will show a 1 and, if not, a 0. <LAN>1</LAN> Shows if the client is in LAN mode. If it is in LAN mode it will show a 1 and, if not, a 0. <BroadcastPort>20082</BroadcastPort> Configures the server port for UDP protocol petitions. It is necessary to be able to share P2P files. <Icons> <Icon Name="Download"> <Path>Images\Descarga.gif</Path> <Message>Downloading updates</message> </Icon> <Icon Name="Installation"> <Path>Images\Instalando.gif</Path> <Message>Installing updates</message> </Icon> </Icons> Configures the images and messages that will be shown during and after the download of updates. Configures the path where the contents for Iriscene Public Media are left when they are received from Iriscene Remote Manager. <SpeedLimit> <! -- Speed limit is in Bytes per second (BPS) --> <Download>-1</Download> <Upload>-1</Upload> </SpeedLimit> Configures the bandwidth, in bytes per second, of uploading and downloading updates. If the value is -1 bandwidth control is inactive.

45 3. PatchClientModule.config This file allows you to configure the path of the FPDServiceSetup service that is installed as part of Patch Management in the client. It is found in the directory: Ą%PROGRAMFILES%\Iriscene Remote Manager\4.8" <setting name="patchmanagerwebservicereferences_fpcservice_service" serializeas="string"> <value>http://10.110.0.89/fpcservicesetup/service.asmx</value> </setting> It is necessary to reboot the IRMService.exe service to make the changes correctly. 4. SelfServiceTool.exe.config This file allows you to configure the path for the platform web service if you have installed the Self Service part in the client. It is in the directory: Ą%PROGRAMFILES%\Iriscene Remote Manager\4.8" <setting name="proxywrapper_irm_platform_irm_service" serializeas="string"> <value>http://10.110.0.89/fractalia/irm/ws_platform/service.asmx</value> </setting> To make the changes correctly you must restart the IRMService.exe service. 5. Registering terminals by command line Iriscene Remote Manager gives you the possibility to register a terminal by command line instead of having to run the configurator. To do this you have to access the path by the Windows terminal: Ą%PROGRAMFILES%/Iriscene Remote Manager/ą and execute the instruction RegisterTerminal.exe. The format for this instruction is: RegisterTerminal.exe <WebService> <License> <WebService>: inserts the URL of the platform WebService. <License>: inserts the group serial number where you will register the terminal. To obtain the serial number of the terminal you must access the platform and you get it by clicking, with the right-hand button of the mouse, on the group where you wish to register the terminal, and looking at the properties of the group in the Generic tab (Figure 95).

46 Figure 95. Getting the serial number of a group in the platform 2. Fractalia Manager Mobile configuration files 1. Config.xml <Configuration> <License>LicenseKey</License> This inserts the group licence you wish to register in the terminal. <UrlService>http://169.254.2.2/IRM50/WS/Client/IRM_WS.asmx</UrlService> This inserts the connection URL with the platform client web service. <PathDownload>Program Files\Fractalia Manager Mobile\data\downloads\</PathDownload> This configures the path for keeping the files of the distribution of downloaded software. <PathLogFiles>Program Files\Fractalia Manager Mobile\data\logs\</PathLogFiles> This configures the path for the storage of the client logs. <PathStorage> Program Files\Fractalia Manager Mobile\data\storage\</PathStorage> This configures the path for the storage of the client internal files. <ReconnectionTime>30000</ReconnectionTime> This configures the platform reconnection time. (In milliseconds) <VNCPort>5900</VNCPort> This configures the VNC port. (5900 by default) </Configuration>

47 C. UTILITIES 1. Instant Recovery System unattended installation 1. Normal installation Execution of the Instant Recovery System can be done in two ways: Clicking directly on the IRS32.msi icon Executing the instruction msiexec /i Ą%rutaDelIRS%IRS32.msią from the command line, where %rutadelirs% is the path where the msi is to be found. 2. Unattended Installation The basic syntax for unattended installations is the following: msiexec /i IRS32.msi /qn <Other options msi> <IRS_OPTION=ąvalueą> <IRS_OPTION=ąvalueą> This table contains the options to personalise the IRS default installation options. Option Description Values By default TARGETDIR Installation Directory Any valid directory. If no directory exists, it will be created. C:\%program Remote files%\iriscene Manager\4.8\IRS PASSWORD IRS password Any alphanumeric Admin chain. AXSNAPSHOTS Maximum From 2 to 10. 10 number of Recovery Points DRIVES Disks to protect Any valid disk Active disk (normally C:) BOOTMENU Show or hide On Off On the load start menu OTP Enable or On Off On disable one time Password ODP Enable or On Off On disable Password for one day PROTECT Protect or not 0 1 1 the disks ROR Specifies the disk to configure the restore on /none any valid disk /none

48 CONFIGLOG RESTART ALGORITHM SNAPFILEPERC SNAPFILESIZE OOTCACHELOCK COUNT OOTRECOVERY STRATEGY restarting Specifies the log file path for the configuration phase Enable or disable the restart after installation Disk Write Strategy (copy on write, redirect on write) See paragraph C.1. Error! No se encuentra el origen de la referencia. Percentage of the disk that takes the snapshot file that grows Initial size of the snapshot file (MB). It is recommended that exceed 1000 In Windows Vista Minimum number of cache blocks required to start Strategy to follow in case you do not have enough memory to boot the IRS /none any valid file (If exists it will be overwritten) yes no /cow /row 0-40 5 200- The size should never exceed 45% of disk size /none Yes /cow 200 Any integer 10 Message RollbackToBaseSnapshot RollbackToLastSnapshot Message <Other msi options > Option /norestart /l* log_file /lx log_file Description No restart after installation (NOT RECOMMENDED) Normal installer log (NOT of the IRS protection) Detailed installer log (NOT of the IRS protection)

49 Note: If the User Access Control (UAC), a Windows Vista improvement, is active the installation process must have high administrator permissions or the installation will be cancelled, as the Windows Installer does not allow silent installation without said permissions. Examples To Install IRS in C:\IRS and the results of the detailed log in C:\irs_install.log msiexec /i IRS32.msi /qn /lx c:\irs_install.log TARGETDIR=ąc:\IRSą To Install IRS, protected disks C: and D: and without rebooting: msiexec /i IRS32.msi /qn DRIVES=ąc: d:ą /norestart To Install IRS but not protect any disk: msiexec /i IRS32.msi /qn PROTECT=ą0ą To Install IRS without the boot menu msiexec /i IRS32.msi /qn BOOTMENU=ąOffą To install IRS with Restore On Restart and select Disk Write Strategy: Copy on Write msiexec /i IRS32.msi /qn ROR=ąc:ą ALGORITHM=ą/cową 3. Update Execution of the update in normal mode: msiexec /i IRS32.msi REINSTALL=ALL REINSTALLMODE=ąvomusą Execution of the update in silent mode: msiexec /i IRS32.msi REINSTALL=ALL REINSTALLMODE=ąvomusą /qn 4. Disk Write Strategy There are two strategies with opposite properties that can be used when you check a disk partition with IRS: COW (Copy On Write): changes are made on the current state. In favour: instantaneous reading Against: It penalizes the disk write for the reallocation of sectors and also takes longer to return to a previous ROW (Redirect On Write): changes are made on the initial state. In favour: writing and recovery instant Against: slow reads. 2. Instant Recovery System Command lines In the path %PROGRAMFILES%\Fractalia\iRollback various applications exist that can be run by a terminal. The syntax is obtained keying in the name of the application without adding any type of parameter: ActionOnRestart.exe obtains information of the actions programmed after the reboot or cancels the planned actions.

50 ActionOnRestart.exe [ <disk-letter> <password> ] get disable AutoRollback.exe activates or deactivates the automatic mode. If it is in automatic mode, each time the machine is rebooted, it returns to a previous Recovery Point. AutoRollback.exe [ <disk-letter> <password> ] on off BootMenu.exe activates the start menu and the One Time Password/One Day Password (ODP/OTP). BootMenu.exe [ <password> ] <menu> <OTP> <ODP> specify on turn on off turn off - leave unchanged BootRecoveryStrategy.exe strategy to select if there is insufficient system memory to boot the IRS BootRecoveryStrategy.exe get BootRecoveryStrategy.exe [<password>] <boot-recovery-strategy> boot-recovery-strategy = Message RollbackToBaseSnapshot RollbackToLastSnapshot Config.exe launches the graphic application (Figure 96) that allows you to protect more than one partition. Config.exe To protect a disk you must press (Figure 96) and that will show all the unprotected disks in the equipment (Figure 97). To continue the process you must mark the disks that you want to protect, if you want to restore the previous state each time you reboot the machine and insert the IRS password (Figure 98, Figure 99 and Figure 100).

51 Figure 96. Protect a disk from the IRS configurator Figure 97. Select the disk to protect Figure 98. Insert the IRS password

52 Figure 99. Protected disk I Figure 100. Protected disk II

53 To unprotect a disk press on (Figure 101) and all the disks in the machine that are protected will be displayed (Figure 102). To continue the process you have to mark the disk that you want to unprotect, select the recovery point you want to restore or leave in its present state and insert the IRS password. (Figure 102 and Figure 103). To unprotect a disk you have to reboot the equipment. (Figure 104 and Figure 105) Figure 101. Unprotect a disk from IRS Configurator Figure 102. Selection of disk and recovery point to restore inserting the IRS password

54 Figure 103. Unprotect disk I Figure 104. Reboot to finalise unprotection of the disk Figure 105. Unprotect disk II Current Status.exe obtains the latest SnapShot made in the machine and its status. CurrentStatus.exe ChangeMode.exe changes the IRS mode, automatic or manual, on the selected protected disk.

55 ChangeMode.exe [ <disk-letter> ] AUTOMATIC MANUAL <password> DeleteRecoveryPoint.exe deletes a Recovery Point. DeleteRecoveryPoint.exe [ <disk-letter> <password> ] <recovery-point-number> Disable.exe returns to the true disk on the next reboot. This action has to be before uninstalling the Instant Recovery System. Disable.exe [ <disk-letter> <password> ] <recovery-point-number> [ /u ] For <recovery-point-number> 1 is the baseline and 0 the present status /u Ā uninstall IRS after rebooting the machine, this option is only valid for <recovery-point-number> = 0 FixedSnapshot.exe deactivates the Fixed Recovery Point. FixedSnapshot.exe [ <disk-letter> ] status FixedSnapshot.exe [ <disk-letter> <password> ] disable GetInfo.exe displays basic information of protected disks. GetInfo.exe Getversion.exe verifies the dll and driver versions of the installation. GetVersion.exe dll driver [ <disk-letter> ] IRSDefrag.exe frees the space of Recovery Points removed. IRSDefrag.exe [<disk-letter> <password>] [files] [boot on off] boot - enabled or disabled defragmentation at boot LockRecoveryPoint.exe blocks or unblocks the recovery point given as an argument. LockRecoveryPoint.exe [ <disk-letter> <password> ] <rec-point-number> [unlock] MaxSnapshot.exe used to establish the maximum number of snapshots. MaxSnapshots.exe [ <disk-letter> <password> ] <max-rec-point-count> MaxSnapshots.exe [ <disk-letter> ] get NextRecoveryPoint.exe creates a new Recovery Point. NextRecoveryPoint.exe NextRecoveryPointReboot.exe programs the creation of a Recovery Point after a reboot of the machine.

56 NextRecoveryPointReboot.exe Password.exe verifies or changes the password. Password.exe check <password> Password.exe change <old-password> <new-password> RestoreToSnapshot.exe restores the Recovery Point indicated as an argument. RestoreToSnapshot.exe [ <disk-letter> <password> ] <rec-point-number> last Rollback.exe programs the restoration of a prior Recovery Point for the next reboot. Rollback.exe SetBaseline.exe changes the baseline image to the image corresponding to the number introduced as the argument. SetBaseline.exe [ <disk-letter> <password> ] <recovery-point-number> SnapShotFileDump the internal information of snapshot file is displayed. SnapshotFileDump.exe /g <disk-letter>: general information is obtained SnapshotFileDump.exe /c <disk-letter>: <cluster-number>: cluster information is obtained SnapshotFileDump.exe /f <full-file-path>: file information is obtained SnapshotFileDump.exe /v <disk-letter>: [ range <first-cluster-number> <cluster-c ount> ]: specific information is collected every cluster of a unit SnapshotNumber.exe displays the number of recovery points currently existing in the machine. SnapshotNumber.exe UserStorage data are stored in protected memory of IRS, which does not change between snapshots. UserStorage.exe <password> getsize UserStorage.exe <password> write <offset> <string> UserStorage.exe <password> read <offset> <length> VirtualDiskControl.exe mounts and unmounts a virtual unit with the Recovery Point indicated as an argument. VirtualDiskControl mount <virtual-disk-letter> <protected-disk-letter> <RP> VirtualDiskControl unmount <virtual-disk-letter> where <RP> = <recovery-point-number> fixed

57 1. VirtualDiskControl.exe This is a command of the Instant Recovery System that allows you to recover the contents of a disk with a damaged Recovery Point. To do this, before loading the operating system, select in the menu, if you wish to use the preloading console of the IRS operating system in graphic mode (F3 or D) or in text mode (F4 or F). Graphic mode Select the protected disk that you want to act on (Figure 106), mark the checkbox Use Fixed Recovery Point and select the Recovery Point from which you want to obtain the information from the disk (Figure 107) and press the escape key. Figure 106. Protected disk selection

58 Figure 107. Use fixed This action creates a fixed Recovery Point, not visible for the user, with the disk contents of the damaged Recovery Point. Text mode Select the protected disk that you want to act on (Figure 108), press the F4 or F key to enable the option Fixed Recovery Point is enabled, introduce the Recovery Point number that you want recover the information from (Figure 109) and press the escape button. Figure 108. Protected disk selection

59 Figure 109. Use fixed This action creates a fixed Recovery Point, not visible for the user, with the disk contents of the damaged Recovery Point. There are two possibilities to recover the contents of the disk: From the command line. You must execute the instruction VirtualDiskControl.exe mount <Disk unit to mount> <Protected disk unit> fixed to mount the disk contents from the damaged Recovery Point in a virtual disk. From the IRS console. Press the button and this will display Figure 110, where you select the disk you want to mount the disk contents of the damaged Recovery Point. 3. Generating inventory templates Figure 110. Mount the Fixed Recovery Point The inventory template is based on a number of calls to registration and calls to the attributes of WMI classes. All of these calls are defined in an xml file, which is uploaded to the platform, and terminals which have, due to their group, this template assigned; such will download it, take the data requested from the template of the Terminal itself, and return them, in another XML file, to the platform. The other XML file must then be processed by the AnalyzerInventory application.

60 1. Format of the inventory template Elements of the structure REPORT - <REPORT> <TITLE>Canaries - example</title> + <PAGE> + <PAGE> + <PAGE> + <PAGE> + <PAGE> </REPORT> PAGE </PAGE> - <PAGE> <TITLE>Operating System</TITLE> <MENUTITLE>Configuration</MENUTITLE> +<DEVICE> +<DEVICE> +<DEVICE> +<GROUP> +<GROUP> +<GROUP> +<ITEM> +<ITEM> +<ITEM> +<ITEM> </PAGE> --------- Section DEVICE There are three options: SPECIFIC DEVICE: all items have a WMI class indicated, as well as a specific entry, if there are several, for example, caches, network cards... - <DEVICE> <TITLE>Test</TITLE> +<GROUP> +<GROUP> +<GROUP>

61 +<ITEM> +<ITEM> +<ITEM> +<ITEM> </DEVICE> EXPAND TO ALL OF THOSE IN THE SYSTEM (NO HARDWARE), THROUGHOUT SEVERAL DEVICES: This will be used as the name of the device that returned by way of the field NAME of the WMI class. Therefore, it is not necessary to indicate the element (for example, Windows XP Professional ) through which it is being accessed. All ITEMS below the device that uses WMI will have access through the class indicated in the device, so that the class does not need to be stated in the ITEM. - <DEVICE> <TITLE>*</TITLE> <CLASS>Win32_OperatingSystem</CLASS> +<GROUP> +<GROUP> +<GROUP> +<ITEM> +<ITEM> +<ITEM> +<ITEM> </DEVICE> EXPAND TO ALL OF THOSE IN THE SYSTEM (HARDWARE, the WMI class must have a DeviceID field, which will be used for the name of the devices), THROUGHOUT SEVERAL DEVICES Therefore, it is not necessary to indicate the element (for example, cache L1) through which it is being accessed. All ITEMS below the device which use WMI will access through the class indicated in the device, so the class does not need to be stated in the ITEM. - <DEVICE> <TITLE>*</TITLE> <CLASS>Win32_CacheMemory</CLASS> +<GROUP> +<GROUP> +<GROUP> +<ITEM> +<ITEM> +<ITEM> +<ITEM> </DEVICE>

62 GROUP OF ITEMS It serves as a grouping entity, for example, Version, System directories, etc. - <GROUP> <TITLE>Version</TITLE> +<ITEM> +<ITEM> +<ITEM> +<ITEM> </GROUP> ITEM Values will be taken for the terminal. The ID can be indicated in the database, if it is known. If the device contains * it will not be taken into account, since the generic device will expand to all of those existing in the system. - <ITEM> <TITLE>WMI Test - 2</TITLE> <IDITEM>2</IDITEM> +<ACTION> +<CONDITION> - <WMI> <CLASS>Win32_BIOS</CLASS> <ELEMENT>Phoenix FirstBIOS(tm) Notebook Pro Version 2.0</ELEMENT> <ATTRIBUTE>BIOSVersion</ATTRIBUTE> </WMI> </ACTION> </ITEM> - <ITEM> <TITLE>Version</TITLE> +<ACTION> </ITEM> Actions for the calculation of values in the terminal (ACTIONS) The following actions have been defined for the calculation of the values (both hardware and software or configuration) of the terminal. WMI REGISTRY CONST: Specifies a constant string to be printed in the inventory. It mainly serves to complete, through composition, the values returned by a WMI or REGISTRY-type action. CONVERT: Allows the system to perform conversions between values returned by other actions (BYTE<->KILOBYTE<->MEGABYTE <->GIGABYTE) COMPOSE: Allows the user to combine the results of a list of actions-

63 Below, the syntaxes of each of these actions are presented, in detail. WMI The WMI action is indicated between the <WMI> and </WMI> labels, and the attributes it uses are: <CLASS>: WMI class over which the query will be made. <ELEMENT>: Entry of the WMI-class table (there can be tables with several entries, for example, the hardware or system dlls) <ATTRIBUTE>: Column from which the value to be returned will be obtained. - <ACTION> - <WMI> <CLASS>Win32_BIOS</CLASS> <ELEMENT>Phoenix FirstBIOS(tm) Notebook Pro Version 2.0</ELEMENT> <ATTRIBUTE>BIOSVersion</ATTRIBUTE> </WMI> </ACTION> The name of the value is in the property <TITLE> of the ITEM. If it is the action of an ITEM from a DEVICE to be expanded, it is not necessary to indicate the class, since all items will use the class indicated in the DEVICE. The element over which the query is made does not need to be indicated either, since it is an expanded element (For example, Cache Memory Cache L1, Cache L2, Cache L3) - <WMI> <ATTRIBUTE>TotalVisibleMemorySize</ATTRIBUTE> </WMI> REGISTRY - <REGISTRY> <HIVE>HKEY_LOCAL_MACHINE</HIVE> <KEY>HARDWARE\Description\System</KEY> <ENTRY>Identifier</ENTRY> </REGISTRY> - <REGISTRY> <HIVE>HKEY_LOCAL_MACHINE</HIVE> <KEY>HARDWARE\Description\System</KEY> <ENTRY>Identifier</ENTRY> </REGISTRY> If you wish to take out the value of an entry for all of the sub-keys of a key, it must be indicated in the TITLE of the ITEM.

64 For example: If you want to obtain a list of applications, it must be indicated in the TITLE of the ITEM * - <ITEM> <TITLE>*</TITLE> - <ACTION> - <REGISTRY> <HIVE>HKEY_LOCAL_MACHINE</HIVE> <KEY>Software\Microsoft\Windows\CurrentVersion\Uninstall </KEY> <ENTRY>DisplayName</ENTRY> </REGISTRY> </ACTION> </ITEM> CONST <CONST>constant string</const> CONVERT The entry unit, the exit unit and an action that will generate the value to be converted must be indicated. -<CONVERT> <IN>BYTE</IN> <OUT>KILOBYTE</OUT> -<ACTION> <CONST>4096</CONST> </ACTION> </CONVERT> --- It can be any action It can be converted between: BYTE, KILOBYTE, MEGABYTE and GIGABYTE. COMPOSE The size (<SIZE>) of the list (number of actions) must be indicated, and below, the actions: - <COMPOSE> <SIZE>7</SIZE> <CONST>This</CONST> <CONST>is</CONST> <CONST>a</CONST> <CONST>test</CONST> <CONST>regarding</CONST> <CONST>multiple</CONST>

65 <CONST>composition</CONST> </COMPOSE> - <COMPOSE> <SIZE>2</SIZE> - <WMI> <CLASS>Win32_ComputerSystem</CLASS> <ELEMENT>IMASD-PORTATIL</ELEMENT> <ATTRIBUTE>TotalPhysicalMemory</ATTRIBUTE> </WMI> <CONST>Bytes</CONST> </COMPOSE> - <COMPOSE> <SIZE>2</SIZE> - <CONVERT> <IN>BYTE</IN> <OUT>MEGABYTE</OUT> - <ACTION> - <WMI> <ATTRIBUTE>FreePhysicalMemory</ATTRIBUTE> </WMI> </ACTION> </CONVERT> <CONST>Megabytes</CONST> </COMPOSE> Expansion of * multiple entries With the aim of making inventory taking flexible, the previous specification is modified so that each level can expand from an action. This was already being made for devices and items. It is generalised here, extending to all levels. This generalisation will have the following form: <element><title>*</title><action>ć</action> Where the element can be a <device>, <group> or <item>, and the list to which they expand is calculated through the assessment of the action, replacing the value of the title with the result of the action. In previous points, it was seen that the information of the action of an element passed to the elements that were below it in the hierarchy. The WMI class used in the title for the elements below it in the hierarchy was transmitted. This also generalises the data, so that not only the WMI class is transmitted, but also the conveyance of registry to all lower levels.

66 Summing up: Any element can be expanded with any action (usually, this only happens for WMI and registry actions). The WMI class and registry key are transferred to lower levels. 4. Unattended installations In order to perform an unattended installation through WinRaR, it is necessary to create the file, deploy.bat, and have the folder where the executable file for the program you want to install is located. 1. deploy.bat This file is edited to introduce the instructions for creating the unattended installation. Name_folder_executable\executable.exe <unattended installation parameters > An example would be: MicrosoftNETFrameworkv20\install.exe /q 2. Creating the installation The deploy.bat file must be selected, and the folder where the executable is located must be right-clicked. When the option Add to archive is marked, the window in Figure 46 is shown. Figure 46. Select Add to archive from the drop down menu In the window in Figure 47, the Create SFX archive option must be marked in order to create an executable file.

67 Figure 47. Configuration of unattended installation parameters Then you click on the Advanced tab in the window that displays the SFX options. When clicking such button, the Advanced options for the SFX (Figure 48) will be shown. Figure 48. General tab for Advanced SFX options In the Path to extract, the path where the installation files are located will be temporarily extracted. In the Setup Program, you must choose if you want to execute a file before (Run before extraction) or after (Run after extraction) extraction. In this case, the name of the file, deploy.bat, must be introduced in the Run after extraction file. Then, you must click the Modes tab and select the option, Hide all, so that it does not show the installation window, and Overwrite all files, so that it overwrites all of the files, if they are already stored in the folders where the files will be extracted.figure 49)

68 Figure 49. Modes of the advanced SFX options tab