Common RDP Problems


If your entire workflow happens on a remote desktop, having problems with missing features or even not being able to connect to the RDP server can bring that workflow to a screeching halt. Here are a couple common problems and suggestions on how to resolve them.

Logon Attempt Failed: If you are unable to connect and the RDP window says “logon attempt failed” at the bottom, it is because the username or password used are incorrect. This occurs more often when the RDP file has credentials saved and the password has recently changed. If the credentials are saved, you can simply right click and edit the RDP link file and then delete the stored credentials. It will then ask you to enter new credentials when you try to connect again.

















Printer Issues: Another common problem with RDP connections is the printers from your local computer not appearing on the remote desktop session or your print jobs are not printing. This often occurs due to one of two things: either the printer’s driver needs to be explicitly loaded on the RDP server, or the printer redirection is not enabled in the RDP connection file. To resolve the printer not redirecting, simply right click and edit the RDP file, select the Local Resources tab, and verify that Printers is checked. If the printer is not printer your jobs, contact your system administrator to have the printer drivers for that printer loaded on the remote server. Be sure the save the file from the general tab after making changes.




















Display Size: When connecting to a remote server, the display settings are controlled by the file used. If the remote session window size is either too small or too large, you can simply edit the file just like above and go the display settings to set the display size. Checking the box Use all my monitors for the remote session will cause the session to span across multiple monitors. As with the above, make sure you save the file after modifying the configuration options.



The Best Computer You Should Buy to Run Dynamics GP


As a software professional, I often get asked questions about computer hardware.  Spending most of my career in the accounting software industry and being part of the team that designed and developed the product we now know as Microsoft Dynamics GP, I am commonly asked:





“What computer should I buy for my business?”

 For years, the unfortunate answer to this question involved a long list of hardware specifications which were difficult for most business professionals to understand and successfully purchase. Furthermore, if we were talking about a new server (or multiple servers) for an accounting system, the answer was even more complex.

 Fortunately, there is a better way to deal with this business challenge. One that every professional can understand:

 Buy any computer you want!

 I can assure you that accounting software solutions, such as Microsoft Dynamics GP, are built upon extremely complex technology and have significant hardware requirements. Successfully operating a system such as this not only requires management of the hardware, but also management of the software, backups, updates, servers, and workstations on a regular basis. To be direct, this level of technology is too complex for most businesses to manage.

 So you are probably now wondering how I can say “Buy any computer you want!”  The solution is:

 Move your Microsoft Dynamics GP solution online or “to the cloud”

 For people that do not live in the computer technology industry, you see commercials and ads describing Microsoft Azure, talking about the cloud, and promoting online business management systems; and it seem overwhelming. They love to talk about big businesses that are saving money and doing amazing things online, and that is true, but the reality is that it is much easier to do than you think, and it is definitely an option for all sizes of businesses today.

 Whether your business is new to Microsoft Dynamics GP or you have been using it for years, you can move your accounting solution online and remove your staff from the task of managing computers. This allows you and your team to focus on your business and those items which make you successful. Once your solution is up and running online, you simply need an internet connection and any modern computer to use Microsoft Dynamics GP and then you too will be running your business “in the cloud” just like those large businesses in the ads.

 At Njevity, we move customers “to the cloud” every day. We have an amazing team of professionals who can help you take advantage of having your business solutions online, so that all of the complex hardware and software management is handled by our team. That way, the next time you need to buy a computer you can simply buy any computer you want.

Disable / Turn off UAC on Server 2012


While User Access Control can protect our servers from malicious attacks on Server 2012 it is a pain. Setting UAC to Never Notify does not turn it off.

The following link explains how:

Set HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\system EnableLUA value = 0

A Window is Not Visible: How to Move Off-Screen Windows Back into View

Every once-in-a-while we receive a call from a client who launched an application, but the application didn't show up on their screen. They confirmed in the taskbar that the application was running. However, the window was not visible on their screen.

If you use a secondary monitor, and/or if you operate within a remote desktop environment, you may have experienced this issue. When a secondary monitor is disconnected, or the display settings are altered, sometimes applications will still operate as if nothing had changed with the monitor or display. The window opens in an "imaginary" place off to the side, where that monitor used to be.

Here are simple steps to move an off-screen window back to your screen:

1. Make sure the application is selected (choose it in the taskbar, or use the ALT-TAB keys to select it).

2. Type and hold down ALT-SPACE, then type M. (IMPORTANT NOTE: If you're working on a remote desktop or cloud, use ALT-DELETE instead if ALT-SPACE.)

3. Your mouse pointer will change to have 4 arrows.

4. Use the arrow keys on your keyboard to move the window back onto your screen.

Some tips to avoid this happening in the first place:
-- Move open windows to your primary monitor before disconnecting the secondary monitor.
-- If shutting down, do so before disconnecting the secondary monitor.
-- When working in a remote desktop, do not disconnect from the remote desktop using the "X" key at the top. Instead, close all open applications, and then go to the Start menu and select "Log Out". (This is a good practice in general, as failure to log out of a remote session could cause several other problems.)

Hypervisor Virtual Machine Vanished from host.


A Virtual Machine on one of our Hyper-Visor hosts vanished. It was no longer listed. When I opened the Fail-Over cluster management console to see if it had failed over to another node it was marked as a failed service.

I checked the for the VM Configuration Files and the Virtual Hard Drives on the shared storage. All files existed.

After a quick Google search I found several articles pointing to a corrupt configuration file.

I opened the .xml file and sure enough a closing HTML tag was incomplete:

After closing the Hyper-Visor Console and reopening it on the host I was able to see the VM and restart it.

If the above doesn't work. Delete the virtual machine and recreate it. Here is how I do that:
1. Note the node that owns the virtual machine
2. In Fail-over Cluster Manager delete the resource.
3. On the Node that owns the missing virtual machine open Share and Storage Manager and go to Manage Open Files
4. Close all connection files and folders that have to do with the missing machines Configuration.
5. Rename the Configuration folder
6. On a Fail-over node create a new machine and pick the existing vhd file for the missing server.
7. Go to the settings of the new virtual machine and make sure it is set to migrate to machines with different hardware.
8. From Fail-over Cluster Manager add the new server
9. Start the new virtual machine
10. Connect to it from its Host
11. Set the IP address.

NOTE: If MS Office is installed you have to re-register it.

Syndicate content