this is an off topic post which I’m posting mainly as a memory prompt for myself. I was working with a set of virtual machines the other day on my test server and received the following error when I tried logging in:
Remote Desktop Connection
An authentication error has occurred.
The Local Security Authority cannot be contacted
Remote computer: azc-gp2013-wc-8
I logged onto the Hyper-V server and launched the VM from Hyper-V Manager and was able to log in without issue. I did some fiddling around and realised that my Domain Controller wasn’t accepting connection requests.
One quick reboot later and I was able to log into the VM without error.
The System Requirements for Microsoft Dynamics GP 2015 are now available from CustomerSource (login required).
The stand out items for me is that support has been dropped for several older versions of Windows, SQL Server and Office:
- Windows XP all editions
- Windows Vista all editions
- Windows Server 2003 all editions
- SQL Server:
- 2008 all editions (including R2)
The only surprise on the above list is that some of the software listed as no longer supported was also listed as no longer supported with Dynamics GP 2013; in fact only SQL Server 2008 is new to the list.
Apart from the above retired software, the recommendations look pretty much the same as Dynamics GP 2013; Windows 8.1 and SQL Server 2014 have been added as supported.
The Win+Tab key combination was introduced in Windows Vista and appears to have been removed in Windows 8, but is back in Windows 10.
The initial display is very like Alt+Tab which allows task switching, but also has an Add a desktop option:
The task switching feature in Windows 10 has also undergone a revision. The small previews of Windows 8 have been replaced with larger ones, as you can see below:
As I covered in this post the Start menu is being reintroduced in Windows 10 and will include a side panel containing the live tiles previously used on the Start screen.
The image below shows the default layout of the Start menu when Windows is first installed:
With the reintroduction of the Start menu, the ability to search is also available in the Start menu again, as it was in Windows 7. To search simply press the Windows button and type the name of the item you’re looking for:
Windows 10 is to see the re-introduction of the Start menu. The Start menu was initially introduced in Windows 95 and continued unchanged until it was given a makeover in the 2007 released Windows Vista.
This makeover saw the ability to conduct a search by simply starting to type after pressing the Windows button.
Windows 8 saw the removal of the Start menu and introduction of the Start screen; the start menu had occupied a small cramped area in the bottom left of the screen next to the Windows button, whereas the Start screen occupies the whole screen. The Start button was also removed and replaced with a hot corner in the bottom left from which to launch the Start screen.
Both of these choices proved to be very controversial and led for calls to reintroduce the Start button, which Microsoft did in Windows 8.1 although the Start screen remained.
Well, Windows 10 has had the Start menu reintroduced:
Before taking a look at the new features in the Windows 10 Technical Preview, we need to first install it.
To do the install I created a new virtual machine in Hyper-V and added the downloaded iso image to the virtual optical drive.
When I started the VM, the installer automatically started and progressed to the language selection window.
As I downloaded the UK version, the language has defaulted to English (United Kingdom); if you need to change the language, do so now and then click Next:
With the release of the Windows 10 Technical Preview, it is time for a divergence from posting about Microsoft Dynamics GP. It doesn’t seem all that long ago that I was posting about the Windows 8 Developer Preview, but looking back it was actually just over three years ago.
In this series, I’m going to start with the installation process and then take a look at some of the new features and differences between Windows 8.1 and Windows 10.
Microsoft Dynamics GP and related products, such as Integration Manager, have a few files which need to be shared between client machines. This can, and in a lot of cases should, be done using a shared folder accessed via the UNC path (e.g. \\file\Dynamics Central to access the Dynamics Central folder on the server called file).
However, if any of these files need to be accessed by users then using the UNC path isn’t the friendliest of ways. Instead a mapped drive can be used which shows up in Windows Explorer and allows the user to easily access it and each user needs the drive mapped under the same folder.
While mapped drives can be created manually on each client machine this would take while. Instead we can create a batch file which can be run on each machine which will add the mapped drive for us:
net use M: /delete
net use M: "\\file\Dynamics Central" /persistent:YES
The first line deletes any existing M: and the second then creates a persistent (one which will be retained when the PC is rebooted) mapped drive on the drive letter M using the Dynamics Central folder on the server called file.