Microsoft Dynamics GP v10 displays new OS compatibility badge!

It's official! A few days aback, I announced that Microsoft Dynamics GP v10 compatibility with Windows 7 and Windows 2008 was going to be made formal with the public availability of the RTM versions of Windows 7 and Windows Server 2008 R2 - click here for the article. Apparently, the Product Management team could not wait anymore and have decided to go public with the announcement.

If you go to v10's System Requirements page (CustomerSource, PartnerSource) you will now see that Windows 7 and Windows Server 2008 R2 are now a part of the client and server operating systems' compatibility list, respectively -- see pictures below.























The good news? You will not be required to install any new service packs or hotfixes! On the otherside, as mentioned in my previous post, v9 will remain compatible with the current OS platforms with no announcements made to support Windows 7 or Windows Server 2008 R2.

Word of caution: before planning to upgrade to Windows 7 and/or Window Server 2008 R2, check the System Requirements page for other product compatibility requirements. If you are using any third party product that interacts with the OS, such as special printing add-ons or bar code reader programs, check with the corresponding ISVs.

Congratulations to the Testing, Product Management, and Development teams for this accomplishment.

Until next post!

MG.-
Mariano Gomez, MVP
Maximum Global Business, LLC
http://www.maximumglobalbusiness.com/

Comments

Richard said…
What I found odd was GP 10 before SP2 is supported on Windows Server 2008 R2 (NT 6.1) while GP 10 needs at least SP2 to be supported on the earlier version of Windows Server 2008 (NT 6.0).

My assumption would have been GP 10 would have needed at least SP2 to be supported on the later Windows Server 2008 R2 (NT 6.1) and not needed on Windows Server 2008 (NT 6.0). From the GP system requirements on Partnersource this does not seem to be the case.

Cheers


Rich
May 12, 2016 at 10:34 PM
Post a Comment

Popular posts from this blog

DBMS: 12 Microsoft Dynamics GP: 0 error when updating to Microsoft Dynamics GP 2013 R2

Image
Hello all! It's been quite a while since I've actually written anything of remote interest to anyone who follows my blog, but at the same time, you will be pleased to know that I've been quite busy in the consulting front, with upgrades, server migrations, complex multi-instance postings involving 10's of thousands of transactions, wrapping up some Field Service Automation projects, and the list goes on and on. This time around I want to bring to the forefront, an issue I encountered updating  from Microsoft Dynamics GP 2013 SP2 to Microsoft Dynamics GP 2013 R2 plus the latest service pack. Background My client requested a server migration to a new environment where they wanted to deploy Dynamics GP 2013 R2 web client (plus the latest service pack) and upgrade their relational database management system to Microsoft SQL Server 2014. This is something I'm absolutely comfortable with (for the most part) given also that my client was sitting at Microsoft Dynamics...
Read more

Do I have to use those "Z-" currency IDs in GP?

Image
I know this seems like a trivia question, but recently I have come across a number of clients who have been using Microsoft Dynamics GP for a number of years and have been told by their former partners that they *must* use the predefined currency IDs created after adding the sample company, with no real explanation to support these claims. Case in point, my new client in Saudi Arabia, has been struggling for years to understand why they were told to prefix all currency IDs with the "Z-". So they went ahead and setup "Z-SR" for the Saudi Real. If you are familiar with Microsoft Dynamics GP and the sample company, Fabrikam, you may have noticed by now that after adding the sample company (which is not a requirement by any means), you will get a number of predefined currencies such as Z-US$ (US Dollars), Z-UK (British Pounds), Z-C$ (Canadian Dollars), Z-AUD (Australian Dollars), and so forth, accompanied by a number of exchange rate tables. If you are not familiar wi...
Read more

Microsoft Dynamics GP Scrolling Windows and Line Sequence Numbers

Image
I thought I would write about something meaningless that no one really thinks about. However, I realized that this is a compelling topic since it makes for some interesting discussion around the ability to insert line items withinin most transaction scrolling windows. Let’s take some time to understand where Line Sequence Numbers come from. A Line Sequence Number is auto generated by Dynamics GP and uses a seed value of 16,384 as a basis for the first line. Each subsequent line in the scrolling window is incremented by this number, so line number 2 would have a Line Sequence Number value of 32,768, line number 3 would have Line Sequence Number Value of 49,152, and so on. Since most GP transaction entry scrolling windows allow inserting rows in between line items, the newly inserted Line Sequence Number value is calculated as an average between the previous and the next line item sequences, i.e., if you were to insert an item in between row 1 and row 2 in the scrolling window -- keep in...
Read more