Call Us +31 (0)20-4822603|info@itamsoft.com
FAQ2017-10-13T16:35:48+00:00

Frequently Asked Questions – FAQ

Cyber Crime Tutorial Video2017-01-10T23:34:44+00:00
Subscribe to Newsletter2016-12-11T12:50:26+00:00

Subscribe to our Newsletter to be the first to hear about the latest product releases, collaborations and online exclusives.



Microsoft SQL Server Licensing Rules2016-12-11T12:50:26+00:00

Microsoft SQL Server Licensing

These are the licensing rules used in the Belarc Data Analytics module.:

Terms used:

  • An OSE is an Operating System Environment.
  • A POSE is a Physical Operating System Environment.
  • A VOSE is a Virtual Operating System Environment.

General rules

  • SQL Server licenses are assigned only to physical servers.
  • The number of SQL Server instances in an OSE is unlimited.
  • A physical OSE is counted as having a minimum of 4 cores.
  • Counting must be done according to the Core Factors
    [1].
  • A virtual OSE is counted as having a minimum of 4 cores.
  • A physical hyper-thread is counted as a virtual core, but is not counted as a physical core.

Datacenter per Processor (2008 R2)

  • One license entitles to one physical processor.
  • Must license all physical processors.
  • Number of VOSEs is unlimited.
  • Number of physical cores is unlimited.
  • No CALs.

Parallel Data Warehouse per Core (2012)

  • One license entitles to one core, physical or virtual.
  • If running in POSE, must license by physical core.
  • If running in VOSEs only, may license by physical cores or virtual cores.
  • To license by physical core, must license all physical cores.
    ▶ May run SQL Server in a number of POSEs or VOSEs up to the number of licenses.
    ▶ Counting the physical cores must be done according to the Core Factors.
    ▶ Escapes the VOSE-uses-at-least-4-cores rule, making it more economical when using all or most of a large server via VOSEs.
    ▶ Cannot add licenses to run more VOSEs.
  • To license by virtual core, must license all virtual cores in all VOSEs running SQL Server.
    ▶ Each VOSE is treated as having at least 4 virtual cores.
    ▶ May run SQL Server in VOSEs only.
    ▶ Is more economical when using a small portion of a large server via VOSEs.
  • No CALs.
  • Software Assurance does not entitle to unlimited virtualization.

Parallel Data Warehouse per Processor (2008 R2)

  • One license entitles to one processor, physical or virtual.
  • If running in POSE, must license all physical processors.
  • If running in VOSEs, must license all used virtual processors.
  • Total number of licenses required is sum of POSE and VOSE licenses.
  • Number of physical cores is unlimited.
  • No CALs.

Enterprise per Core (2014 and 2012)

  • One license entitles to one core, physical or virtual.
  • If running in POSE, must license by physical core.
  • If running in VOSEs only, may license by physical cores or virtual cores.
  • To license by physical core, must license all physical cores.
    ▶ May run SQL Server in a number of POSEs or VOSEs up to the number of licenses.
    ▶ Counting the physical cores must be done according to the Core Factors.
    ▶ Escapes the VOSE-uses-at-least-4-cores rule, making it more economical when using all or most of a large server via VOSEs.
    ▶ Can add licenses to run more VOSEs (one additional license per one additional VOSE).
  • To license by virtual core, must license all virtual cores in all VOSEs running SQL Server.
    ▶ Each VOSE is treated as having at least 4 virtual cores.
    ▶ May run SQL Server in VOSEs only.
    ▶ Is more economical when using a small portion of a large server via VOSEs.
  • No CALs.
  • Bonus: If have Software Assurance and license by physical core, then entitled to unlimited virtualization (i.e., only need as many licenses as physical cores, regardless of number of VOSEs running SQL Server).

Enterprise per Processor (2008 R2)
Note: we ignore the option of the POSE using only a subset of the physical processors.

  • One license entitles to one processor, physical or virtual.
  • If running in POSE, must license all physical processors.
    ▶ One license entitles to four VOSEs.
  • If running in VOSEs only, must license all used virtual processors.
    ▶ Usage examples: in case of a physical processor with 4 cores: using 4 cores means using 1 processor; using 5 cores means using 2 processors.
  • Number of physical cores is unlimited.
  • No CALs.

Enterprise per Processor (2008 and 2005)
Note: we ignore the option of the POSE using only a subset of the physical processors.

  • One license entitles to one processor, physical or virtual.
  • If running in POSE, must license by physical processor.
  • If running in VOSEs only, may license by physical processors or virtual processors, whichever is cheaper.
  • To license by physical processor, must license all physical processors.
    ▶ Number of VOSEs is unlimited.
  • To license by virtual processor, must license all virtual processors in all VOSEs running SQL Server.
  • Number of physical cores is unlimited.
  • No CALs.

Enterprise per Server (2014 and 2012)
Available to existing Software Assurance customers only. Not available under new licenses.

  • One license entitles to four OSEs, physical or virtual.
  • Must license all OSEs running SQL Server.
  • POSE has core limit of 20.
  • Set of VOSEs has a total virtual core limit of 20.
    ▶ Can add licenses to run more VOSEs (one additional license per four additional VOSEs).
    ▶ Each additional set of VOSEs has a total virtual core limit of 20.
  • User and/or Device CALs required.

Enterprise per Server (2008 R2)

  • One license entitles to four OSEs, physical or virtual.
  • Must license all OSEs running SQL Server.
  • Number of physical processors is unlimited.
  • Number of physical cores is unlimited.
  • User and/or Device CALs required.

Enterprise per Server (2008 and 2005)

  • One license entitles to one POSE and an unlimited number of VOSEs.
  • Number of physical processors is unlimited.
  • Number of physical processors is unlimited.
  • Number of physical cores is unlimited.
  • User and/or Device CALs required.

Standard per Core (2014 and 2012)

  • One license entitles to one core, physical or virtual.
  • For SQL Server running in POSE, must license all physical cores.
    ▶ There is a 4-core minimum.
  • For SQL Server running in VOSE, must license all virtual cores in all used VOSEs.
    ▶ There is a 4-core minimum in each VOSE.
  • Total number of licenses required is sum of POSE and VOSE licenses.
  • No CALs.

Standard and Workgroup per Processor (2008 R2)

  • One license entitles to one processor, physical or virtual.
  • If running in POSE, must license all physical processors.
  • If running in VOSEs, must license all used virtual processors.
    ▶ Usage examples: in case of a physical processor with 4 cores: using 4 cores means using 1 processor; using 5 cores means using 2 processors.
  • Total number of licenses required is sum of POSE and VOSE licenses.
  • Number of physical cores is unlimited.
  • No CALs.

Standard and Workgroup per Processor (2008)

  • One license entitles to one processor, physical or virtual.
  • If running in POSE, must license all physical processors.
  • If running in VOSEs, must license all used virtual processors.
  • Total number of licenses required is sum of POSE and VOSE licenses.
  • Number of physical cores is unlimited.
  • No CALs.

Standard and Workgroup per Processor (2005)
Note: we ignore the option of the POSE using only a subset of the physical processors.

  • One license entitles to one processor, physical or virtual.
  • If running in POSE, must license all physical processors.
  • If running in VOSEs, must license all used virtual processors.
  • Total number of licenses required is sum of POSE and VOSE licenses.
  • Number of physical cores is unlimited.
  • No CALs.

Standard and Business Intelligence per Server (2014 and 2012)

  • One license entitles to one OSE, physical or virtual.
  • Must license all OSEs running SQL Server.
  • Each OSE is limited to 16 cores.
  • User and/or Device CALs are required.

Standard and Workgroup per Server (2008 R2 and 2008 and 2005)

  • One license entitles to one OSE, physical or virtual.
  • Must license all OSEs running SQL Server.
  • Number of physical processors is unlimited.
  • Number of physical cores is unlimited.
  • User and/or Device CALs are required.

Footnotes

[1] A “Core Factor” must be applied to certain AMD processors and to CPUs with single or dual cores:

Processor Type Core Factor
AMD Series 31XX, 32XX, 33XX, 41XX, 42XX, 43XX, 61XX, 62XX, 63XX, with 6 or more cores 0.75
Single core 4
Dual core 2
Other 1

How does the subscription model work?2016-12-11T12:50:26+00:00

BlackFog Privacy software is available according to the subscription model. That means you can use the software for a minimum period of one year or several years. It is also possible to take a license for 2 or 3 years. The cost for the whole period will be paid at once. After the expiry of the period of 1, 2 or 3 year the subscription will be automatically renewed for another same period as the initial period of 1, 2 or 3 years. The Family Pack is a subscription to five computers within the same company or family for a period of one year.

With a blackFog subscription you also have the right to use the customer portal. Which can be found in the menu at customer support.

blackfog-pricing

Which payment methods can I use?2016-12-11T12:50:26+00:00

ITAMSoft B.V.is using the following payment methods:

payment-methods

Is your payment is not listed, please contact us and we look for a solution. For larger companies we work with purchase orders and invoicing.

How big is the ransomware problem?2017-05-19T18:19:17+00:00

Ransomware is growing exponentially over the Internet right now. By holding your device and more importantly your data to ransom you have little choice but to pay the cyber criminals to get it back. Let’s face it, no one wants to lose all their photos, music or customer records (along with massive fines). Even if you have diligently backed up, what is to stop them coming back again. Not to mention all the time it is going to take you to recover your files.

The only way to prevent Ransomware is to ensure you are protected with a product like BlackFog which stops the activation and installation in the first place.

From Wikipedia, the free encyclopedia
Ransomware is computer malware that installs covertly on a victim’s computer, executes a cryptovirology attack that adversely affects it, and demands a ransom payment to decrypt it or not publish it. Simple ransomware may lock the system in a way which is not difficult for a knowledgeable person to reverse, and display a message requesting payment to unlock it. More advanced malware encrypts the victim’s files, making them inaccessible, and demands a ransom payment to decrypt them. The ransomware may also encrypt the computer’s Master File Table (MFT) or the entire hard drive. Thus, ransomware is a denial-of-access attack that prevents computer users from accessing files[5] since it is intractable to decrypt the files without the decryption key. Ransomware attacks are typically carried out using a Trojan that has a payload disguised as a legitimate file.

Why do I need BlackFog if I have an Anti-Virus product already?2016-11-28T15:19:25+00:00

Anti-Virus products focus on what to do AFTER you have been infected and provide little or no solution to prevention. BlackFog focuses specifically on real-time network threat detection and preventing spyware and ransomware from infecting your machine in the first place.

By proactively blocking threats and distribution networks associated with infections and focusing on prevention through anomaly detection and outbound activation we can eliminate over 99% of threats.

For an in depth look at our technology we highly recommend you look at our technology presentation.

How many resources does BlackFog consume?2016-12-11T12:50:26+00:00

From a system resource perspective BlackFog Privacy was designed to be very lightweight. In fact, the BlackFog Privacy executable occupies approximately 2MB of drive space and the whole package around 20MB. It has been developed in the same language as the underlying operating system and has no dependency on other runtime frameworks, so it is very fast.

 

OSI model Blackfog cyber security

OSI model Cyber Security & Cyber Privacy

BlackFog Privacy has a small memory footprint of around 25MB and uses less that 5% CPU at its peak. Routinely you will see it around 1-2% on a very active machine.

Will BlackFog slow down my machine?2016-12-11T12:50:26+00:00

blackfog verbeter prestaties

BlackFog has been specifically designed to have little to no impact on your machine in terms of performance. If anything you should notice your machine is noticeably faster because it is preventing the transfer of vast amounts of information from your machine over the network.

From a CPU perspective BlackFog uses around 1-5% (depending on Operating System and processor) during normal network operation and 0% on idle. Your browser typically uses 20% or more depending upon the site you are visiting. BlackFog also uses only small amounts of other system resources such as memory and drive space.

How is BlackFog updated?2016-11-28T15:14:15+00:00

BlackFog utilizes different rule sets to protect your device. These rules are managed and updated within the application automatically. BlackFog periodically checks BlackFog servers for updated rules and downloads new ones as necessary.

In addition, BlackFog periodically provides application updates to providing additional features and bug fixes. The application checks for updates every few days and allows you to install the update if desired.

Does BlackFog collect information about me?2016-12-11T12:50:26+00:00

The short answer is NO. BlackFog is very conscious about Privacy and we do not collect information about you. In fact, BlackFog makes you aware of what information other applications are collecting and where all your information is going (whether you have consented or not).Blackfog geolocate verkeer

The only information that is sent to our servers is the IP address of the destination request so that we may geo-locate it for you and send back the result. We do not keep log files about this activity and the results are only consumed by BlackFog and cached locally for later use.