I occasionally work from home (I don’t really like doing so as I prefer to keep work and home separate). My problem is that at home I have a four monitor setup (2 x 27″ @ 2560×1440, 1 x 23″ @ 1920×1080 and 1 x 19″ @ 1280×1024) and when I am connecting to work I want to use two of the monitors for the remote system I am connecting to and two for local programs or files.
However, the Windows remote Desktop Connection only allows you to use a single monitor or to mark a checkbox to use all monitors:
I added a suggestion via the Windows Feedback Hub asking for this to be amended to allow a choice over the number of monitors to use. I’d appreciate it if people would up vote so we can get RDP enhanced/
This is only something I need to do occasionally so am posting this as a reminder.
Most of the demo VMs I create are on my local Client Hyper-V, but occasionally I make one available to a prospect or client and need to give them a user other than the administrator account.
Creating the user account itself is easy, but the bit I usually fail to remember how to do, is to give the user the rights to sign in remotely.
When this right has not been granted, an error message like the below will be displayed:
To sign in remotely, you need the right to sign in through Remote Desktop Services. By default, members of the Administrators group have this right. If the group you're in doesn't have this right, or if the right has been removed from the Administrators group, you need to be granted this right manually.
One of the perks of being a Microsoft Most Valuable Professional (MVP) is the fRee MSDN VisualStudio account. This gives access to pretty much all of Microsoft’s software for development and testing purposes.
The main pieces of software I use is Windows and SQL Server. Usually when writing blog posts about Microsoft Dynamics GP, I use Windows 2012 or 2012 R2, but occasionally I create a Windows client machine with Windows 10.
Usually these machines don’t last long enough to need registering, but I have lately been working on one or two projects which required a somewhat longer life than the free registration period. For Windows Server, this isn’t a problem as the server version of Windows registers online without problems. However, registering Windows 10 Enterprise is not so simple, as the Enterprise editions of Windows requires a Key Management Server to successfully register.
I have never configured one of these as my installations for development and testing are usually fleeting. Instead, there are a couple of commands which can be run which will allow Windows 10 Enterprise to be registered online.
The first command is where you install the KMS key:
I had my work laptop rebuilt recently after having numerous faulty components replaced. After the rebuild, the Windows lock screen remains black and doesn’t show the background image. I changed it to a static image rather than the Windows spotlight. Unfortunately, this didn’t resolve the issue.
The answer for fixing this is actually very simple, but not obvious. To correct the problem, open the System properties window by opening Windows Explorer and right clicking on This Computer and then clicking on Properties (or by pressing Win + Pause|Break).
Once the System window is open, click on Advanced system settings:
This post is a diversion from the usual Microsoft Dynamics GP focused ones, but is related to Microsoft. The admin team at work recently emailed everyone asking for a list of all the applications installed on laptops and desktop machines for a licence audit. They asked for a screen shot of the Add/Remove Programs window, but one of the developers replied with an email containing a set of commands which would list all programs. Which is much easier when you have a lot of software installed which would require multiple screenshots.
To run the script, open a command prompt in administrator mode and type:
cd c:\windows\system32\wbem (hit enter)
wmic (hit enter)
/output:C:\InstallList.txt product get name,version
The first highlighted section above contains the output location and the second shows the fields to return.
You can use the following to get a list of available fields:
cd c:\windows\system32\wbem (hit enter)
wmic product get /?(hit enter)
I make a lot of use of virtual machines for both testing and demonstrating Microsoft Dynamics GP. As a company, when I joined, Perfect Image tended to use VMware (I’ll reserve comment, which I realise tells it’s own story), but more recently have started making more use of Microsoft Hyper-V, which is what I also use at home for testing and writing my blog and books.
After installing Hyper-V on my work laptop I created a virtual machine and clicked start. Unfortunately, I received the below error messages:
I did some digging around and found that although Hyper-V was installed, the hypervisor wasn’t running. Fortunately, the laptop I have does support Hyper-V and I only had to do one thing which was to enable the hypervisor by opening an elevated command prompt and type the following command:
bcdedit /set hypervisorlaunchtype auto
Once I had run the command I was able to start the virtual machine without further problem; at least with Hyper-V.
What I found was that with the hypervisor running, I wasn’t able to start a VMware virtual machine. So a second command can be used to disable the hypervisor for those times when I need to use a VMware virtual machine:
bcdedit /set hypervisorlaunchtype off
Hopefully, I’ll be able to complete the transition away from VMWare very soon and stop toggling from one to the other.
Taking a slight diversion from my usual subject matter with this post. I was trying to connect to a clients system via VPN a short while ago when I received error 778:
Error 778: It was not possible to verify the identity of the server
I did a little digging and found that this error actually relates to the username and password being incorrect. I checked our records and found that the password had been reset since the last time I logged on; after entering the new details I was able to log in successfully.
It would be nice if the error message had been a little more descriptive of the actual problem, but at least it was a simple solution.
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 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
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 cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.