Windows 8.1 Update

April 7th, 2014 by Stephen Jones No comments »

Microsoft’s recent keynote for the BUILD developer conference detailed an update to Windows coming on the next scheduled patch Tuesday called 8.1 Update.
Microsoft will be bringing back a Start Menu and windowed Metro-Style/Modern apps.

Traditional PCs – desktops and laptops – will now boot to the desktop by default. PC makers building tablets or types of hybrid machines with touchscreens can now set a flag to identify the device as a Slate, which will make them boot to the Start Screen. The Modern interface is now aware of how it’s being used. If you are using touch, it acts just like 8.1, but if you are using a keyboard and mouse, there are now context boxes on the right click menus. Moving the mouse to the top of the screen reveals the traditional minimize and close options. The task bar is now available on the Start Screen. Hidden functions like Search and the Power button are now available right on the Start Screen by your login ID.

An interim step until further Desktop/Modern integration happens is the ability to pin Modern apps to the taskbar. These still open the full screen or snapped Modern app, but it’s an easy way to multitask with desktop and modern apps. Microsoft also demonstrated further integration coming in a future update. Whether that is an 8.1 Update 2 or Windows 9 wasn’t specified, but it brings Modern apps to the desktop in a window. This will increase the usefulness of Modern apps. Full screen on a 10” tablet is not the same as when a desktop is equipped with 22” to 32” monitors, when there’s a LOT of wasted real estate by running these apps in full screen, or even split screen mode. This is a huge change from the original vision of Windows 8, and if anything can make Modern apps more useful, this is it.

Microsoft plans to allow developers to build “Universal Apps” that will work across Windows Phone, Windows and Xbox devices. Given that the Xbox One operating system is based on Windows 8, this cross-Windows portability is possible. Universal Apps are applications built using a common Windows Runtime shared across these different flavors of Windows. Developers will be able to reuse more code and still target their apps for different form factors and experiences. Universal apps are a stepping stone on Microsoft’s path toward bringing its Windows versions closer together, in terms of programming interfaces, toolsets and user interfaces.

Android Botnet Targets Middle East Banks

April 6th, 2014 by Stephen Jones No comments »

The botnet — dubbed “Sandroid” — comes bundled with Android apps made to look like mobile two-factor authentication modules for various banks, including Riyad Bank, SAAB (formerly the Saudi British Bank), AlAhliOnline (National Commercial Bank), Al Rajhi Bank, and Arab National Bank.

. It’s not clear how the apps are initially presented to victims, but such scams typically infect the victim’s computer with a password-stealing banking Trojan. Many banks send customers text messages containing one-time codes that are used to supplement a username and password when the customer logs on to the bank’s Web site. That precaution requires attackers interested in compromising those accounts to also hack the would-be victim’s phone. Banking Trojans — particularly those targeting customers of financial institutions outside of the United States — may throw up a browser pop-up box that mimics the bank and asks the user to download a “security application” on their mobile phones. Those apps are instead phony programs that intercept and relay the victim’s incoming SMS messages to the botnet master, who can then use the code along with the victim’s banking username and password to log in as the victim.\

. Some 28,000+ text messageswere intercepted by the Sandroid botnet malware. This particular botnet appears to have been active for at least the past year, and the mobile malware associated with it has been documented by both Symantec and Trend Micro. The malware itself seems to be heavily detected by most of the antivirus products on the market, but then again it’s likely that few — if any — of these users are running antivirus applications on their mobile devices.

In addition, this fake bank campaign appears to have previously targeted Facebook, as well as banks in Australia and Spain, including Caixa Bank, Commonwealth Bank, National Australia Bank, and St. George Bank.

The miscreant behind this campaign seems to have done little to hide his activities. The same registry information that was used to register the domain associated with this botnet — funnygammi.com — was also used to register the phony bank domains that delivered this malware, including alrajhiankapps.com, commbankaddons.com, facebooksoft.net, caixadirecta.net, commbankapps.com, nationalaustralia.org, and stgeorgeaddons.com.

The registrar used in each of those cases was Center of Ukrainian Internet Names.

One problem with the whole banking infrastructure is that there are many targets for attackers. Researchers from consultancy MWR Infosecurity, uncovered four vulnerabilities in various mobile point of sale terminals – the ones that people behind the bar ask you to shove your card into, but the new ones that let the merchant set the thing up and manage it with their mobiles or tablets.( iZettle is the best known example in Europe ). In all cases, hackers can do what they want on the machine. The most likely scenario is they could change the code so that it reads the mag stripe… then they can clone the mag stripe after they’ve retrieved the PIN number. These point of sale devices are approved by Visa and MasterCard.

Malware appears to be well-detected by mobile antivirus solutions. Many antivirus firms offer free mobile versions of their products. Some are free, and others are free for the initial use — they will scan and remove malware for free but charge for yearly subscriptions. Some of the free offerings include AVG, Avast, Avira, Bitdefender, Dr. Web, ESET, Fortinet, Lookout, Norton, Panda Cloud Antivirus, Sophos, and ZoneAlarm. Incidentally, the mobile phone number used to intercept all of the text messages is +79154369077, which traces back to a subscriber in Moscow on the Mobile Telesystems network. Source – http://krebsonsecurity.com/2014/04/android-botnet-targets-middle-east-banks/ –

Third platform – Microsoft mobile push

April 6th, 2014 by Stephen Jones No comments »

Reuters recently reported that Microsoft Corp CEO Satya Nadella, set out Microsoft’s strategy for securing a greater share of the mobile computing market. This includes licensing Windows for free on some consumer devices and developing a voice assistant similar to Apple’s Siri,

A paid licence fee will still apply to business devices, however Windows will be free for consumer phones and tablets with screen sizes under nine inches.

Microsoft also announced a voice-activated phone assistant called Cortana, to compete with Apple’s Siri. The tool will allow users to verbally command a number of functions, including search the Web, set reminders and make calls. While still in beta, Cortana will soon be standard on Windows phones,.

Microsoft’s attempt to applied to charge Windows Phone hardware partners between $5 and $15 per device, failed to get market adoption and allowed Google to penetate with with its Android OS.

Microsoft’s strategy led to more expensive phones and a small user base, that did not generate adequate revenue ma from services like Skype and Office.

Microsoft now seems set to align itself with the mobile era with a version of Office for Apple’s iPad. Analysts believe this could add over $1bn per year in extra subscription revenue.

Nadella in a question-and-answer session at the developer conference said. “We are not coming at this as some incumbent trying to do the next version of Windows; we are going to come at this by innovating in every dimension.”

The so called ‘Third platform’ brings together four technologies that are driving fundamental operational and architectural changes to enterprise ICT frameworks: social, mobile, analytics (big data) and cloud. BYOD is also a factor as users have access to non corporate applications Some of these tools are adopted by conscious choice; others are changes that happen to organisations outside their control. For example, companies cannot stop customers tweeting about bad service. Nor can they stop employees from adopting the smartphone of their choice, at least not without a resultant impact on business performance.

IT strategies need to factor in Third Platform changes – because competitors are already doing so.
For example the number of smartphone shipments is expected to grow by over a billion units in emerging markets. For example a mobile banking hugely for the rest of the decade.

Dynamics Ax R3 introduction video

April 5th, 2014 by Stephen Jones 12 comments »

On the 10th of April there will be an on-line experience event- if you have not yet had an invitation then please contact us for more information. This is a free webinar on the updated Microsoft Dynamics AX 2012 R3 to learn how you can deliver amazing customer experiences

Join the CFO of Kathmandu, the CIO of Ashley Furniture, and the IT director of Kent Corporation as they discuss their “reimagined customer experience” and the success they’re achieving with Microsoft Dynamics AX. We’ll share a “digital view” of a dynamic business solution (Microsoft Dynamics AX 2012 R3) that helps you engage with your customers on their terms, run dynamics operations and expand rapidly to better serve your customers.

For more information call\; Bindu or Bikram 00971433655589

Dynamics CRM 2013 and UR2

April 5th, 2014 by Stephen Jones No comments »

Several issues are solved using through the UR2 for CRM 2013 (. A few relevant ones noted by Aishwarya:-

• CRM 2013 Outlook filtering did not work after you perform a quick find search.
• Users of the offline edition of the Microsoft Dynamics CRM Client for Outlook could not configure their Offline Scheduled Sync settings under Personal Settings.
• When you viewed completed activities, such as email, you could not select any text on the record. This includes the body control.
• Users of the offline edition of the Microsoft Dynamics CRM Client for Outlook could not configure their Offline Scheduled Sync settings under Personal Settings.
• When you used Chrome to view duplicate detection rules in Microsoft Dynamics CRM 2013, the criteria were not shown every time that you opened the record. You had t0 close and then reopen the record an undetermined number of times before the criteria were shown.
• After you upgraded Microsoft Dynamics CRM 2011 to Microsoft Dynamics CRM 2013 or imported Microsoft Dynamics CRM 2011 appointment customization, you received a pop-up error message while you are saving appointments:

These are now fixed.

The Foreign Account Tax Compliance Act (FATCA)-U.A.E update.

April 1st, 2014 by Stephen Jones 6 comments »

Companies doing business in the United Arab Emirates (UAE) may be affected by a number of recent developments, including:

– The new Intergovernmental Agreement between UAE and the United States under the US Foreign Account Tax Compliance Act (FATCA)
– UAE’s participation in the tax transparency forum of the Organisation for – Economic Co-operation and Development
– An increase in property transfer fees to 4 percent.

The UAE Central Bank has agreed to adopt the Model 1 IGA, an agreement stating that all financial institutions in the UAE will answer to the FATCA request of sharing information about any US accounts, assets, or transactions channelled through those banks.

The UAE has until June this year to commence disclosing basic information about accounts with transactions linked to the US.

After 3 three years of negotiation, regulation, and time framing followed, with a final regulation and timeline formed in October last year under these agreements, FFIs are subjected from July 1, 2014 to due diligence of all accounts except grandfathered accounts. From 15 March 2015, detailed reporting of accounts is required for transaction made in 2014.

The July 1 deadline: “Withholding agents generally will be required to begin withholding on withholdable payments made after June 30, 2014, to payees that are FFIs or NFFEs (non-financial foreign entity) with respect to obligations that are not grandfathered obligations, unless the payments can be reliably associated with documentation on which the withholding agent can rely to treat the payments as exempt from withholding,” states the IRS in its latest regulatory statement.

FATCA is aimed at identifying US taxpayers with bank accounts or investments worth more than $50,000 offshore. Taxpayers will have to report their cash and investments via tax filings, which will be compared to the figures supplied by up to 770,000 banks worldwide.

Grandfathered accounts are obligations that are outstanding on January 1, 2014.

The risk of an individual or financial institution failing to comply with FATCA is hefty fines, and for the financial organisation, including a 30% withholding tax on all transactions through US banks and even possible exclusion from the US banking system. Around 40 countries have already signed FATCA pacts with the US, while another 20 are negotiating inter-governmental agreements. Financial institutions in countries without inter-governmental agreements will have to deal directly with the IRS.

he term “Withholding” normally refers to the IRS giving instructions to hold back 30 per cent of any money that a non-compliant FFI receives in dollars passing through the US and Participating FFI (PFFI). If an FFI has not registered as intending to become compliant or has a national agreement (IGA) in place ‘withholding’ will have already started.

In the case of the banks in the UAE, this agreement has been made, and thus withholding should be already in place. All pre-existing accounts will have to be identified with basic information as per 1 July 2014. Basic information includes name, social security number/TIN, address, account number, current value etc.

The requirement is more than just reporting the accounts that the FFI know as being linked to US ‘persons’ – the FFI also has to do a manual search of all their files where the account has a value of $1,000,000 or more to check if there are links to the US. If the FFI has not complied by this date then they will suffer withholding tax of 30 per cent.

FFIs over the next couple of months will be registering the data required, as the FATCA registration website has opened on January 1, 2014.

It is important to note that by July 1, 2014, if not already, banks may adopt new rules regarding the opening of new accounts with US -linked transactions.

Annual reporting by PFFIs would be phased in starting in 2015 (with respect to information related to the 2014 calendar year), with reporting of the full scope of FATCA information required no later than March, 2017. stated the IRS.
The information reporting will have to include full details of the accounts, such as the underlying investments of funds, all transactions, interest earned etc.

The phasing in starts with “recalcitrant” (known or suspected offenders) accounts, large value accounts, pre-existing accounts and works its way down to the mass volume accounts with smaller sums.There is a lot of confusion about what is to be reported as there are different rules for new accounts, for “recalcitrant” accounts (naughty accounts) and for pre-existing accounts.
However, the information reported must be backdated to include information relating to the year 2014, and therefore January 1, 2014.

On February 20, 2014, the U.S. Department of Treasury (“Treasury”) and the Internal Revenue Service (“IRS”) released temporary regulations that revise and clarify the final FATCA regulations (“Temporary Regulations”).

The U.S. government also released temporary regulations coordinating the final regulations under Chapters 3 and 61 of the Internal Revenue Code (“Code”) with the final FATCA (Chapter 4) regulations (“Coordination Regulations”).

The new rules do not provide any further extensions to the effective date of FATCA, or to the required timeframes in which an FFI that has entered into an FFI Agreement (a “participating FFI” or “PFFI”) must comply with the due diligence, withholding or reporting obligations under the that agreement. The effective date for FATCA compliance remains July 1, 2014.

According to a notice1 from the UAE Central Bank, banks and other financial institutions in the UAE must complete the following actions to facilitate the signing of the IGA:

1.Identify customer accounts that are a “US Reportable Account”, which is defined as a financial account maintained by a reporting UAE financial institution and held by one or more specified US persons or by a non-U.S. entity with one or more controlling persons that is a specified U.S. person (implementation date: 19 November 2013).
2.Adopt FATCA’s due diligence procedures for identifying and reporting on US Reportable Accounts and for payments to certain nonparticipating financial institutions (
).
3.Prepare relevant systems for establishing electronic connection to the Central Bank’s FATCA Reporting System, currently in development. All banks and other financial institutions should expect to be contacted for this purpose during the first quarter of 2014 (implementation date: 1 March 2014).
4.Be prepared to register via the IRS portal to obtain a “Global Intermediary Identification Number” (final registration date: 1 November 2014).
5.Adopt reporting procedures specified in the IGA (first report for 2014 must be sent to the Central Bank by 1 August 2015).

The Central Bank, with help from a US law firm, will provide legal support and conduct workshops to assist banks and other financial institutions in implementing the FATCA requirements.

Bankers expect all banks in the UAE will be forced to comply because they must rely on US correspondent banks to clear dollar denominated transactions. Non-compliance could invite sanctions that could include withdrawal of US dollar clearing rights with correspondent banks.

If you need assistance with regulatory reporting then please contact us: 009713365589

Dynamics Ax 2012 – Retail enhancements

April 1st, 2014 by Stephen Jones 12 comments »

AX 2012 R3 Retail Enabling Enterprise Deployment

AX 2012 R3 Retail Integrated Catalog and Call Centre

Dive into Ax 2012 R3

April 1st, 2014 by Stephen Jones No comments »


This features the early beta release as of February 2014. Specialists from the Retail, Manufacturing, Professional Services and Public Sector groups walk you through key business scenarios, demos, resources and explain how R3 will enable an unparalleled industry offering.

Sunsystems 6.2 release now available – ask Synergy Software Systems, Dubai

April 1st, 2014 by Stephen Jones 3 comments »

Unicode
All text data in SunSystems version 6.2.0 is now stored as Unicode. This enables mixed languages to be used in one Business Unit Group, one Business Unit, or even in a single field. It avoids issues with code page conversions when copying data between Business Units and Business Unit Groups. Previously unsupported languages such as Hindi, and unsupported characters such as the Azerbaijani schwa ‘ə’ are now supported. The full length of a text field can now be used for all languages,

Caution: The database collation must still be binary. Also Business Unit codes and Operator Ids can only contain upper case non-accented alphabetic ASCII or numeric characters.

Changes to the Domain Database
In SunSystems version 6.2.0, 101 tables have moved to the Domain Database, including most of the tables for the Filters, Forms, Dictionary, Hierarchies, Languages, Standard Text, and User Labels. Where these tables were previously auditable, this is no longer the case.

The benefit of this change is to simplify the implementation and maintenance of systems with multiple Business Unit groups.

Business Unit Administration
With the introduction of the Business Unit Administration (BUA) console in this release, SunSystems contains greatly enhanced data integrity checking as part of the BUA functionality. This requires some additional maintenance tasks, especially immediately after upgrade. This is to help ensure that data integrity is maintained.

English/European Languages Data Migration
Users wishing to migrate data from SunSystems version 4 to version 6.2.0 must follow the instructions in the Infor SunSystems Guide to Migrating Data From SunSystems 4.

Ledger Setup
In SunSystems version 6.2.0, a new parameter, called Transaction Date Substitution, has been added to Ledger Setup (LES) >> Options, to limit the automatic substitution of Transaction Dates by Ledger Import.

Settings are:

• Allow on All (default) – any valid transaction dates will be substituted.

• Allow Order Fulfilment Only – any Order Fulfilment invalid transaction dates will be substituted, and all other invalid transaction dates will be rejected.

• Disallow – any invalid transaction dates will be rejected rather than substituted.

Changes to Balancing by Fourth Currency

In SunSystems version 6.2.0, Account Allocation/On Line Allocation, Ledger Entry, and Ledger Import are enhanced with functionality to enforce balancing by a common Value 4 Currency Code, (when Value 4 is defined as Variable, and with Automatic Balancing set).

So depending on the setup of the Business Unit, when the Value 4 Currency Code is common throughout the set of transactions in question, balancing is applied by Value 4 along with balancing by the other Currency Values, .

Using Extended Analysis and Enterprise Data Management

If you are using extended analysis and want to use the Enterprise Data Management (EDM) to enable business units to share key reference data, you should be aware of some limitations in using these features in combination.

Extended analysis data that you create, amend, or delete is not shared via EDM automatically. Only changes to the parent analysis record trigger the enterprise data management functionality.

If you are linking analysis to reference data, you must ensure that this exists in common between business units sharing an EDM relationship. This is best controlled if that data has the same pattern of publication and subscription as the analysis it is linked to.

If EDM integration is deployed across multiple domains, you must ensure that Additional Code Lists are maintained throughout these domains. These are held at domain level and cannot be shared automatically at this time.

You can define standard extension fields on Analysis Dimensions that are ‘linked’ to an Analysis table. However, if a published analysis dimension is processed by a subscriber Business Unit with the ‘linked’ flag unselected, then the standard extension fields and corresponding values in analysis codes will not be retained.

If you do not want to share extended analysis data you can suppress this when using EDM. The analysis extension fields will still be published, but they will be bypassed when the Subscriber Business Unit consumes the BOD:

1 Define a transformation in Transfer Desk, where each of the extension fields in the payload is set to ‘Undefined’.

2 Assign the transformations to the subscriber Business Unit, using ELS-Enterprise Data Subscription Configuration.

Indic Numerals for Arabic-speaking Users of SunSystems Web

Arabic-speaking users who wish to use Indic numerals can use this facility in version 6.2.0 of SunSystems Web by using Firefox or Internet Explorer 8. Versions 9 or later of Internet Explorer do not currently support Indic numerals.

This limitation does not affect right-to-left display, Arabic translations, or support for the Hijri calendar.

Dynamics Ax 2012 SP3 – Demand Forecasting

March 29th, 2014 by Stephen Jones No comments »

Microsoft Dynamics AX 2012 R3 Demand Forecasting is an easy yet powerful tool. It lets you predict demand based on historical data, change the predictions, and import them back into the Microsoft
Dynamics AX forecast models.

It’s a cost effective solution (included in the Enterprise CAL) that takes advantage of the Microsoft technology that you are already using and are familiar with.
– To generate the baseline forecast it uses the power of SQL Server Analysis Services.
– To visualize the forecast, make changes, view or create new KPIs, it uses the extensive functionality of Microsoft Excel.

It lets you define customer order decoupling points at any level and to forecast for subcomponents. It is an ideal solution for mass customization. You can of course still use it to predict only direct
customer demand.

Key features:
• Statistical forecast
• Baseline generation at different levels of aggregation
• Forecast visualization and modification
• Importing back into Microsoft Dynamics AX
• Forecast accuracy KPI