Bitdefender total security 2017 activator Archives

This document intends to go through the logical steps through the process of setting up your Update Server on your core down to troubleshooting common client issues.

Ivanti Antivirus 2017 Error Codes

Further information is available here: About Ivanti Antivirus 2017 (Bitdefender Engine) Error Codes

1. Ensure that your Core Server and clients will have access to the following URL: http://ivanti-60013e4c-1d97-4269-b5b7-625530f25c30.2d7dd.cdn.bitdefender.net/.
2. You will likely need to whitelist *.cdn.bitdefender.net or *.bitdefender.net on your firewall or other network security appliances.
3. Be sure that the connection to the Cloud services is not blocked by the corporate firewall or network filtering solution. You should whitelist the nimbus.bitdefender.net address on port 443 and allow other addresses originated from there.   

   You can test the connection using telnet nimbus.bitdefender.net 443 or a web browser by accessing for example https://nimbus.bitdefender.net/url/status?url=http://ivanti.com

4. It is also best to exclude your core server from caching information in Internet Caching appliances as it has been seen that quite often the caching appliance servers up outdated information when compared to the Core Server resulting in multiple issues.

5. Make sure port 7074 is open and accessible on the Core Server.

After purchasing the license/subscription for the new Ivanti Antivirus product and installing 2017.3 Service Update 2 on the core server, the following steps must be performed prior to deploying the new solution to your managed endpoints. If transitioning from the previous Ivanti Antivirus offering to the NEW Ivanti Antivirus offering, no additional purchase is required. You will need to consult with your Sales representative to ensure the license is updated.  In the event that these two licenses are not showing up, you need to reactivate your core server by going to the Start Menu on the Core Server and typing "Core Server Activation" and <Enter>.  After core server activation please verify one of the following sets of licenses exist:

Ivanti EPM Version 2017.x

• Ivanti Antivirus Manager 2017 License             
• Ivanti Antivirus Manager 2017 Subscription

Ivanti EPM Version 2018.xx

• Ivanti Antivirus Manager 2018 License
• Ivanti Antivirus Manager 2018 Subscription

The update server cannot be installed on any other server other than the core server.

1. Run a Download Updates manually with any item(s) selected. (Recommended: Download Ivanti 10.x.x Software Updates as it is a short process.
2. After completion, reopen Download Updates.  The Ivanti Antivirus Core Installation Files option should be present.
3. Check the box and run Download Updates again to get the needed antivirus install files.

You should see the following UI after a successful install:

A successful log file will look like this after AVSETUP  installation:

3356 4 2018-02-22 11:46:12Z INFO install pkg path: C:\Program Files\LANDesk\ManagementSuite\ldlogon\avclientbd\updateserverinstall\..\epsecurity_x64.exe

3356 4 2018-02-22 11:46:59Z INFO install process exit code 0

3356 4 2018-02-22 11:46:59Z INFO install update server successfully

3356 4 2018-02-22 11:46:59Z WARN Failed to create shortcut.

LinkSource:

LinkDestDirectory:

LinkName:

3356 4 2018-02-22 11:47:01Z INFO Json request result:0

3356 5 2018-02-22 11:47:01Z INFO set proxy for update server successfully!

Possible Issues with AVSetup installation

1. AVSETUP will fail to complete if it is run before the Ivanti Core Installation Files is downloaded in the patch content.  The AVSETUP file will look for epsecurity_x64.exe in the \\coreservername\ldlogon\avclientbd folder.  This file will not exist until the Core Installation files are downloaded.
2. AVSETUP will not run if a competing and possibly conflicting anti-malware program is installed on the core server.  In most cases removal of that software would be recommended and replaced by the Ivanti Antivirus solution, however, we realize this is not always possible.
   
   You can make an XML edit to enable the AVSETUP to install anyway.  (However, Ivanti Support will not be responsible for conflicts in this case)

Add the following line to \ManagementSuite\LDLogon\avclientbd\updateserverinstall\InstallerConfig.xml

<skipRemOtherProducts var="SkipCompetitors">1</skipRemOtherProducts>

AVSetup Installation Logging

AVSetup does a full scan of the Core Server during installation and installs the

AVSetup creates four services on the Core Server:

Pattern files are updated on the Core Server using the EPUpdateServer process.  Ensure that this service is running if you are experiencing pattern file update issues.  In addition, check the Antivirus 2017 tab in the Download Updates tool within the Security and Compliance Manager tool to ensure you have the right interval set and also check the last pattern file update date and time.

You can check the update server on the core by looking at the log here:

C:\Program Files\Ivanti\Update Server\var\log\arrakis\update.log

Server Update Activity Logging

Ivanti Antivirus 2017 will not install as part of the Agent Configuration.  The Ivanti Antivirus within the Agent Configuration options refers to our Kaspersky version of our Antivirus product.

Two different methods can be used to install Ivanti Antivirus on a client.

Installed through an Install/Update Security  Components Task

Click

1. 1. Open the Agent Settings Tool within the Ivanti Endpoint Manager console.
   2. Select the Calendar icon drop-down and select "Install/Update security components"
   3. Check the box next to "Ivanti Antivirus 2017"
   4. Choose whether to show the installation progress dialog on the client
   5. Select whether to "Troubleshoot Ivanti Antivirus installation using interactive mode".
      (This mode will allow you to click through the installation manually)
   6. Select whether you want to force the installation of Antivirus even if the same version is already installed.
      (Unless this is selected it will not install again on top of itself)
   7. Click "Save"
   8. At this point, the Scheduled Tasks tool will open with a task named "Install or update Security Components" or another name if you chose to rename the task.
   9. Select your targets and start or schedule the task.

Installation log files

Two different methods can be used to uninstall Ivanti Antivirus from a client.

Uninstall through an Install/Update Security  Components Task

Click

1. 1. Open the Agent Settings Tool within the Ivanti Endpoint Manager console.
   2. Select the Calendar icon drop-down and select "Remove security components"
   3. Check the box next to "Ivanti Antivirus 2017"
   4. Select the desired Reboot Setting
   5. Choose whether to show the Uninstallation progress dialog on the client.
   6. Click "Save".
   7. At this point, the Scheduled Tasks tool will open with a task named "Remove Security Components" or another name if you chose to rename the task.
   8. Select your targets and start or schedule the task.

          Uninstall from a command line on the client computer

            From the client "Run" line or search box run "Vulscan /removeavnew".  You can add the parameter "/showui" if

Uninstall log files

Uninstall activity is logged into "ldav_install.log" and the same rules apply to it starting out as vulscan.pid_xxxx.log  and then renamed to "ldav_install.log" after, just the same as the installation log file.

Logging for client pattern file update activity is stored in the following log:

To force an immediate update on the client run  "C:\Program Files (x86)\LANDesk\LDClient\Antivirus\LDAV.exe" /update

Note: The "Check for updates" button in the Client UI does not work at this time.  Clicking this button will do nothing.  Instead, the "'ldav /update" option should be used.

The pattern file updates reach out to two sources by default:

• The Core Server
• av-update.ivanti.com which is changed to ivanti-60013e4c-1d97-4269-b5b7-625530f25c30.2d7dd.cdn.bitdefender.net in the agent's AVNewBehavior_xxxx.xml file.
• The core server needs to be able to reach "ivanti-60013e4c-1d97-4269-b5b7-625530f25c30.2d7dd.cdn.bitdefender.net"
  (If you want the clients to update from the internet in case the core server is down, make sure the clients also can reach the bitdefender.net address)
• The client needs to be able to reach the core server on port 7074.

The Registry key HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\landesk\managementsuite\WinClient\Vulscan\OtherBehaviors should have an "avnewbehavior" and then as a string the data "CORESERVERNAME_vxxx" for the version number.

If this is not there try running a change settings task and select the specific Antivirus 2017 setting name and push it to the client.

Within the AVNewBehavior XML file, there is a section called UPDATESERVER_URLS which tells the client where to go for updates.

<Name>UPDATESERVER_URLS</Name>

<Val>["EPM2018-1:7074","ivanti-60013e4c-1d97-4269-b5b7-625530f25c30.2d7dd.cdn.bitdefender.net"]</Val>

Also, the pattern updates can be failed due to a lack of proper configuration on the Bitdefender endpoint app side.

You can check what update-source has been used during the last update update_statistics.xml.
C:\Program Files\Ivanti\Endpoint\update_statistics.xml

---FAILURE---

<Antivirus>
        <Check time="1571826542" succtime="1571416036" error="-1004" id="0" location="" size="0" server="localhost:7074" proxy="" updater="AutomaticUpdate" updtime="0" updavailable="0" current_ring="0" prev_ring="0" />
        <Update time="0" succtime="0" error="0" id="0" location="" size="0" server="" proxy="" updater="" updtime="0" current_ring="0" prev_ring="0" />
    </Antivirus>

---SUCCESS---

<BDVaccine>
        <Check time="1574929625" succtime="1574929625" error="0" id="12" location="bdvaccine64" size="0" server="EPM2019:7074" proxy="" updater="OnDemand-Update" updtime="1526292903" updavailable="0" current_ring="0" prev_ring="0" />
        <Update time="0" succtime="0" error="0" id="0" location="" size="0" server="" proxy="" updater="" updtime="1526292903" current_ring="0" prev_ring="0" />
    </BDVaccine>

Check time="1574929625" - its a unit timestamp. Use the Unix decoder to convert the time.
https://www.unixtimestamp.com/

server="EPM2019:7074" - Server used for update.

If you see the "localhost:7074" address so that means that Bitdefender did not get all the configuration from the EPM agent.

You can confirm that by looking at Update.conf
C:\Program Files\Ivanti\Endpoint\settings\system\Update.conf

You have to see there both update servers from the AVNewbehavior*.xml file.

                    "host" : "http://EPM2019:7074",
                    "useFor" : [ "product", "signatures" ],
                    "useProxy" : false
                },
                
                {
                    "host" : "http://ivanti-60013e4c-1d97-4269-b5b7-625530f25c30.2d7dd.cdn.bitdefender.net",
                    "useFor" : [ "product", "signatures" ],
                    "useProxy" : false


If you see there the only localhost that means that something went wrong during transferring the configuration:

                    "host" : "http://localhost:7074",
                    "useFor" : [ "product", "signatures" ],
                    "useProxy" : false

In two words the update process looks in a next way:

After you are pressing the "Check for Updates" button "LDAV.exe" checks what is the current AVNewbehavior*.xml is in use at "HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\landesk\managementsuite\WinClient\Vulscan\OtherBehaviors" then reads the content and translates it to "EPUpdateService.exe" through the secured connection. "EPUpdateService.exe" gets the config and updates the "Update.conf" with the update sources and then it's being used for the update.

There is one known issue when the configuration transfer fails.
Check if the LDAV.exe process is running. If it's not even after the reboot and manual run you can take a look at the Event viewer.


That issue is connected to a "VeriSign universal root certification authority".  It's being used for setting a secure connection like between LDAV.exe and  EPUpdateService.exe so LDAV.exe could not be started.
In this case, we see that OS could not update the certificate because of security and FW limitations.

Once the URL was whitelisted issue was solved.

These pattern files are hosted at port 7074.  So the connection to this port must be open and available.

To check if port 7074 is open on your core server you can run "Netstat -ab | more" and you should see it near the top of the list'

                     Ports 7074 and 7076 opened by "EPUPDATESERVER"

You can also Telnet to the hostname of the core to the 7074 port to see if it responds with anything by running "Telnet {coreservername} 7074".  If the screen clears and it shows a prompt in the upper left corner the connection was successful.

The other reason for failing to get fresh patterns can be hidden on the EPM Core in UpdateServer configuration.
When you configure the proxy server in EPM Console->Patch and Compliance->"Download updates"->Proxy Settings  you also set the proxy server for Bitdefender UpdateServer in generalSettings.xml



First of all check the C:\Program Files\Ivanti\Update Server\var\log\arrakis\update_0.log to see if UpdateServer has an issue with getting the updates.
If there is so check your proxy settings in EPM Console->Patch and Compliance->"Download updates"->Proxy Settings.
If they are set correctly but the server still fails to connect to update sources go to C:\Program Files\Ivanti\Update Server\etc\generalSettings.xml.




If your proxy requires the authentication so be attentive with the way you enter the credentials.

user@domain - correct set
domain\user - incorrect

domain\user - will not be accepted by BD SDK and will not be applied to generalSettings.xml.

Files that have been quarantined are stored in C:\Program Files\Ivanti\Endpoint\Quarantine

Log Files

Core Server

Client

Support Tool

For all Client issues please run the following program on the client and provide the results to the Ivanti Support Technician.

Support Tool - 64-bit  (Download)

Support Tool - 32-bit   (Download)

This will create a file on your desktop to provide to the support technician.  This file will be in the following format: supporttool_computername_year_month_day_hour_minute.

If applicable it is imperative to duplicate the issue you are seeing prior to running the support tool.


An alternative way to gather Bitdefender advanced logs is next:
* - You will need administrator rights

1. Go to Ivanti Endpoint Security installation folder: cd C:\Program Files\Ivanti\Endpoint
2. Run: product.console.exe /c Support.StartSession scenarioId=generic
3. Reproduce the issue (run update)
4. Run: product.console.exe /c Support.EndSession outputPath=C:\Windows\temp
(this will stop the logging process and dump the log in the provided path)
5. Send the generated report archive as an attachment or upload it and provide the link.
 

Blue Screens

If the issue is a Blue Screen error (BSOD) follow these instructions to gather the MEMORY.DMP file to provide to Ivanti support

Core Side

Installation Issues

ISSUE: Failure to install the services related to the Ivanti Antivirus 2017 Product

AVSetup creates four services on the Core Server:

RESOLUTION: Run the AVSetup program once more on the Core Server (Run as Administrator)

Client Side

Installation Issues

Issue: BitDefender will not Install on a device that has Ivanti Antivirus (Kaspersky Engine) or Ivanti Bitdefender previously installed.

Resolution:

Make sure that the Kaspersky engine is completely uninstalled.  If it doesn't uninstall from Security Activity task you can use the removal tool found here: Removal tool for Kaspersky Lab products

After you have made sure it is uninstalled check the client for the existence of this folder:

If it exists, rename the Antivirus folder to something else and try the installation again.

Issue

The task to install the new Ivanti Antivirus on a client failed with: Ivanti Antivirus failed to Install code: 448.

Resolution

Step 1: On the core itself, navigate to %ldms_home%\ldlogon\avclientbd.  Make sure the epsecurity_x64.exe and epsecurity_x86.exe files exist.  If they do not, go and run Download Updates again with the Ivanti Antivirus Core Installation Files option checked so the files download.

Step 2: Make sure you ran the AVsetup.exe file on the core and it completed successfully as outlined in https://community.ivanti.com/docs/DOC-62435#jive_content_id_Core_Install_files_in_Default_Drive_Letter_C  The installation of the definition download utility on the core is needed before you can install the client portion on devices.

Step 3: Make sure any other Antimalware/Antivirus programs are removed prior to installing the new Ivanti Antivirus.  Currently the New antivirus solution does not auto uninstall other security applications.  You will need to uninstall sure programs before you install our antivirus solution. Windows Defender is the exception this can be left running on the client devices if you like.

Removal tools (uninstall tools) for common antivirus software

Step 4: Log information on the installation of antivirus can be found in C:\ProgramData\LANDesk\Log\ldav_install.log

Issue

Ivanti Antivirus GUI says "Antimalware-Advanced Threat component(s) are disabled" and a message: You are at Risk.

Resolution

It is normal for the Advanced Threat Control module to be disabled.  In the future, this will be enabled as we improve the product.  To clear the You are at Risk message, Run a full scan on the device and allow it to complete.  Click the radar icon and then click Full Scan.  Allow the scan to complete.  When done the main window should display You are Protected in green.

Issue

Antivirus 2017(Bitdefender)  Failed to install,  Now other attempts to install also fail.

Resolution

See Document: https://community.ivanti.com/docs/DOC-69442

Client Pattern File Update Issues

Error: 1003 (Could not resolve proxy) or 1004: (Could not connect to proxy or server) or 1005: (Could not authenticate to proxy or server)

Possible Causes

• The endpoint is not configured correctly to communicate over the internet through a proxy.
• The endpoint cannot resolve the proxy due to a DNS issue.
• There is no proxy configured in the Bitdefender policy.

Error: 1011 (I/O Timeout)

Possible Causes

• The update server is offline
• The update server port is closed on 7074
• The endpoint does not have access to the update server network location

Issue: The Check for Updates button on the Bitdefender client is not working

The Check for Updates button in the GUI is not functioning at this time.  It may be functional in the future as we improve the product.  You need to schedule definition updating on the clients through the Agent Settings.  By default, definition updates are not turned on in the agent settings.

Open Agent Settings. Expand Security and Ivanti Antivirus New.  Double Click your agent setting in the right window.  Click Scheduled Tasks and Check the Update box then Change Settings to adjust the update times.  When done Save the settings.  The agent settings will get applied to the client devices the next time a security scan is run.

To force an immediate update on the client run  "C:\Program Files (x86)\LANDesk\LDClient\Antivirus\LDAV.exe" /update

(Remember the above command must be run as administrator.)

Again, update progress will be logged in C:\ProgramData\LANDESK\Log\ldav_update.log

Client virus scanning issues

Issue: High CPU and disk I/O during full scan

Please note that the default values of the FullScan are set so that the scan is completed as soon as possible. In addition, while the scan is running for the first time on the system, the Smart Scan database is being built and this is expected to take more resources than at a normal run.

Once the first scan is completed and the database is in place, subsequent scans will be faster and will take fewer resources.

In any case, we recommend our customers to schedule the full scan once a week and preferably when the system is not in use.  Considering the real-time scanning capabilities of the product it is not recommended to run a full virus scan more often than this.

CPU Usage and Disk I/O performance can be improved by doing the following:

1. Uncheck the box for "Faster File Scan"
2. Check the box for "Lower the priority of scanning threads"

✿ LICENSE ✿
⇨ NJCS3-58S8M-QMX1D-6FN69

⇨ NJCXR-F61JH-QDNRC-C2QC5

⇨ NJDAG-U75DF-12TGB-Z7TD8

⇨ NK2N5-DXZJ6-DVPPT-K262V

⇨ NKASW-E3B75-RXKVH-3Y72R

⇨ NNKH2-PVYRZ-A64T9-4JCN2

⇨ NNKT6-TY5VX-AZXX3-TUNNX

⇨ NNQ5N-3V2UR-SBJPE-7K3K2

⇨ NP6FD-RV3UC-JMHHP-P1RQA

⇨ NPCP1-ADRS1-Q34M1-N52YC

⇨ NPFQQ-VE44S-YSDF2-MWA87

⇨ NPFVE-53PTF-78XQV-JX165

⇨ NPH1N-YBJYG-4ARWM-3G2XR

⇨ NPH75-GUBYP-YYZ97-GHXD4

⇨ NPPR1-U5HAH-RB4PJ-8R8PZ

⇨ NPRVA-K8GQN-8XN4P-W8FPA

⇨ NPSEB-UXE8Z-R56D6-3GZ86

⇨ NRKR8-XX8FN-JSSYB-BBS3W

⇨ NRVCE-E62M2-1F22Y-6MPG3

⇨ NRWE1-CVRNV-KXTNX-WUGKR

⇨ NRXTF-8EYFG-2KAMN-2D7CU

⇨ NS9MZ-D5W4T-PX8HP-TRQBC

⇨ NSEJD-ZKPH1-KK27R-SBXET

⇨ NSMC3-UW48W-1ZAJA-A9X8Y

⇨ NSPH7-ZC5VB-7YW14-59YPA

⇨ NSPNV-PXM65-VJZ8B-A6M68

⇨ NTPVD-CRSHM-MPV55-ZQU9V

⇨ NTRKY-RANJ1-UVC23-H8EEH

⇨ PFY81-U6A76-9R82K-JHW31

⇨ PFYNV-9TM57-3MN3S-EP498

⇨ PHM4N-QVTZ9-TTQA7-ZJKS7

⇨ PHY9W-624JX-VB1FP-4HTQG

⇨ PHZYP-X9TMB-5DB6Y-5HF8E

⇨ PJ3CN-V6HKS-22AK3-TGG24

⇨ PJD4S-45M3J-6X5KZ-ZPP9T

⇨ PN8Q2-V17KX-YN69D-A7G6W

⇨ PNBDA-3WCTQ-GARFZ-MAFPS

⇨ PNHA1-S7HTV-X7P53-Q2U5U

⇨ PNPTA-2S4SG-225KP-ZFTFC

Bitdefender is a Romaniancybersecurity and anti-virus software company.^[1] It was founded in 2001 by Florin Talpeș who is currently the chief executive officer.^[2] Bitdefender develops and sells anti-virus software, internet security software, endpoint security software, and other cybersecurity products and services.

As of 2018, the software has about 500 million users worldwide.^[3]

History[edit]

Bitdefender software was originally developed by SOFTWIN and sold as AVX (Antivirus Expert) from 1996 until 2001, when its name was changed. In 2007, SOFTWIN spun off Bitdefender.^[4]

Bitdefender products[edit]

Bitdefender develops and markets anti-virus, internet security, endpoint security, and other cyber security products and services.

Consumer products[edit]

Bitdefender's Internet of things device protection solution is called Bitdefender BOX. The box is a router designed to protect smart home products and Internet of Things devices by blocking malicious internet traffic. It is available on both Windows and Mac.

Bitdefender offers a cloud-based security solution with anti-malware and anti-theft capabilities for Android and iOS users that is called Bitdefender Mobile Security.

Business products[edit]

For businesses, the company markets the Bitdefender GravityZone for Enterprise Security. It includes Self-configuring kits for deployment from desktop to datacenter to cloud, software that secures physical, virtual and cloud-based endpoints, and software that uses a Network of malware data to stay updated.^[5] Its software product for small businesses looking for simple security called Bitdefender GravityZone Business Security.

Bitdefender technologies[edit]

Bitdefender Antispam NeuNet[edit]

Bitdefender Antispam NeuNet,^[6] is an antispam filter trained by the Bitdefender Antispam Lab on a series of spam messages, so that it learns to recognize new spam by perceiving its similarities with the messages it has already examined.

B-HAVE[edit]

In May 2006 Bitdefender developed a new technology, B-HAVE, to reduce dependency on virus signatures through proactive detection of unknown threats. This technology is based on a behavioral analysis in a virtualized environment.^[7]

Active Virus Control[edit]

Bitdefender introduced Active Virus Control in August 2009. This technology continuously monitors each program (specific processes) running on the PC as it executes, and it notes any malware-like actions. Each action is scored and, when a given threshold is reached, the process is reported as harmful.

Photon Technology[edit]

In its 2014 version, the company claimed to feature a new technology called "Photon Technology", which it says visibly improves computer speed and performance by gradually adapting to each PC.^[8]

Content filtering technologies[edit]

Content filtering technologies have been developed to filter raw online content and are applicable and used in antispam, anti-phishing, web filtering, scanning of spam and social networks. They facilitate the creation of signatures to proactively detect never-before-seen malicious files.

Machine learning[edit]

The company claims that Bitdefender is using cloud-based machine learning to identify new malware, malicious URLs and other online threats by processing and analysing big data to obtain behavioral patterns and predict future advanced threats.

Licensing[edit]

In 2015, Qihoo 360 acknowledged accusations by three antivirus testing companies of providing for their testing a version of its anti-virus equipped with a antivirus engine licensed from Bitdefender, while the consumer version used Qihoo's own QVM engine instead.^[9][10] Currently,^[when?] Qihoo's 360 product includes Bitdefender, Avira and Qihoo-developed engine.^[11]

Criticism[edit]

Support[edit]

In May 2009, customers criticized Bitdefender's support service for lack of responses.^[12] Bitdefender responded by saying they were aware of the problems, and that they would take steps to solve it. They attributed the problem to an unexpectedly high surge in customers.^[12] Currently,^[when?] the company's website claims that support is available 24/7 on telephone, email, online chat, and an online knowledge base.^[13]

Trojan.FakeAlert.5[edit]

On 20 March 2010, computers running Bitdefender under 64-bit versions of Windows were affected by a malfunctioning update which classified every executable program as well as dll files as infected. These files were all marked as 'Trojan.FakeAlert.5' and were moved into quarantine. This action led to software and systems malfunctions that affected users around the world.^[14] Bitdefender representatives announced the removal of the faulty update and a workaround for the users affected,^[15] except for those using the 2008 version.^[16]

Asus AiSuite incompatibility[edit]

Bitdefender is incompatible with Asus AiSuite2 and Asus AiSuite3, a motherboard optimization suite of software bundled with Asus motherboards which enables automatic overclocking, power tuning and fan control. Bitdefender claims that the incompatibility is due to "NDIS Asus driver (WinpkFilter LightWeight Filter), which prevents the installation of some Bitdefender files".^[17]

See also[edit]

References[edit]

External links[edit]