Well, I did some exploring and investigation, and it turns out that the Server Manager is being launched at user log on by a Scheduled Task:
The series index for this series of posts is here and will automatically update as posts go live.
Before Microsoft Dynamics GP 2018 RTM, or any of the related additional products, can be installed there is one prerequisite which cannot be handled by the installer process. This is the .NET Framework 3.5 feature which is installed using the Add Roles and Features Wizard available via Server Manager on Windows Server or using Turn Windows features on or off accessible via Program and Features on Windows.
If the PC or server you’re planning to install Microsoft Dynamics GP 2018 RTM onto has an Internet connection, then the .NET can be installed simply by using the wizard. However, if, for whatever reason, you don’t have an Internet connection available, the install process isn’t quite that smooth.
On both server and PC you can do an offline install and I have blogged about this previously:
Both of the above posts were for previous versions of Windows, but both are still relevant for the later versions.
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.
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:
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:
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:
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.
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:
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:
In this post I’m going to do a step by step guide to installing the .NET Framework 3.5 on Server 2012 when there is no Internet connection available; many to serve as a reminder to me next time I try to do this.
The first step is to open Server Manager and click on Add roles and features;