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.
Microsoft Dynamics GP has traditionally had it’s own log on which means for a user who’s day job is based within GP, they need to log into Windows and then log into GP.
If you are using the web client Microsoft Dynamics GP 2013 R2 saw the introduction of Identity Management – Login which will provide single sign-on functionality. However, for those using the desktop client the best that Dynamics GP has to offer is the Remember User and Password introduced in Dynamics GP 2010.
However, Dynamics GP has a thriving community surrounding it which includes many ISVs (Independent Software Vendors), one of which is called Fastpath; this company has developed an add-on for Dynamics GP called Config AD which makes single sign-on with Dynamics GP.
Typically my posts have all been around the Dynamics GP core product or the add-ons from Microsoft with only a small number of posts on products from other vendors. In this series of posts I am stepping outside of this area as I am going to cover the install, configuration and use of Fastpath’s Config AD. The index for this series is below and will expand as posts are made.
When you log into Windows Server, the Server Manager opens automatically, but I rarely want to use it. In Windows Server 2008 R2 there was a checkbox on the main window which would allow you to dismiss the window and prevent it appearing again.
This option still exists in the Windows Server 2012 Server Manager, but it is no longer front and centre.
To prevent Server Manager loading automatically when logging into Windows, click Manage and then Server Manager Properties:
Continue reading “Stop Windows Server 2012 Server Manager Loading Automatically”
This perhaps isn’t the best time of the year to be posting about trust relationship breakdowns, but this is the only post I have ready to go (I have a couple of series of posts I intend to do soon).
I make quite a lot of use of virtual machines for testing and writing because of the flexibility and ease of taking a snapshot before doing something risky so the machine can be reset. After doing so one day, I ran into a problem I hadn’t seen before after restoring one virtual machine to a snapshot:
The trust relationship between this workstation and the primary domain failed
Continue reading “Trust Relationship Between This Workstation And The Primary Domain Failed”
While VBA is falling out of favour with Microsoft Dynamics GP (by dint of not being supported in the web client) it is still useful for those clients who do not use, and have no intention of using, the web client.
One such client was recently installing some new XenAPp servers using Windows Server 2012; when they tried to open a window with a VBA customisation they received the following error:
File Not Found: VBA6.DLL
Fortunately, Beth Gardner posted the answer to the Developing for Dynamics GP blog.
This is not something I need for the series of posts I am currently writing on the Microsoft Dynamics GP 2013 SP2 Web Client Scale-Out Deployment as my web server is running Windows Server 2012, but you may be performing the install on Windows Server 2008 R2 so I thought I would include this for completeness.
If you are running Windows Server 2008 R2 then extending a website with ASP.NET 4.5 required the use of the command line.
Open a Command Prompt with Administrative permissions and type the following and then hit Return:
Then type the following and hit Return:
Once the command has finished running, the website will be extended with ASP.NET 4.5 and be ready for the Session Control Service to be installed.
Extending a website with ASP.NET 4.5 required the use of command line (which I will cover in the next post), but Windows Server 2012 requires this be done using the Server Manager (there may be a PowerShell command to do this, but, if so, I don’t know what it is).
As I mentioned in a comment in the last post, if you’re installing IIS to configure the web client then you don’t need to treat this step separately, but merely add the step to the installation options for IIS.
To extend IIS on Windows Server 2012, you need to open Server Manager and click Add roles and features:
Continue reading “Microsoft Dynamics GP 2013 SP2 Web Client Scale-Out Deployment: Extending IIS With ASP.NET 4.5 On Windows Server 2012”
Before we can start installing the Microsoft Dynamics GP 2013 SP2 Web Client, there are a few steps which need to be completed.
The first of them is to install the IIS Web Server on the machine which will operate as the Session Control Server. In my case, this is the SC1 machine which is running Windows Server 2012. IIS is installed via Server Manager by clicking Add roles and features:
Continue reading “Microsoft Dynamics GP 2013 SP2 Web Client Scale-Out Deployment: Installing IIS On Session Control Server”
I think I mentioned the other week that I had built a new Hyper-V server to use a as a test bed. I did run into an issue when I created the second virtual machine and tried to install SQL Server into it when it was complaining about S IDs.
I did a quick look around and realised that the problem was because I had created a virtual machine with Windows installed and made a backup of this VM which I had been copying to create subsequent machines.
The first VM I configured properly became my Domain Controller and had worked fine.
The second machine, and every subsequent ones needed to be tweaked using the System Preparation Tool before it is used.
To run the System Preparation Tool (sysprep), open the Run window and type sysprep;
Continue reading “SysPrep Virtual Machine After Replication”