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:
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
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:
In the last post I took a look at how to install the .NET Framework 3.5 while the server is not connected to the Internet. At the same time I installed the server I was also installing a Windows 8 client as well and needed to install the .NET Framework 3.5 on it as well. Being client software I expected the process to work, if not better than, then the same as the one on Windows Server 2012.
I recently encountered a problem trying to install the .NET Framework 3.5 in a virtual machine on my test server which is not connected to the Internet (I wish it was but I am currently renting and don’t have a broadband connection). I am used to dealing with Windows Server 2008 R2 where the install just happens, but in Windows Server 2012 the Add roles and features wants to download the install files from the Internet.
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;
In this post I’m stepping away, briefly, from Microsoft Dynamics GP but will return in to it in my next post.
Microsoft have recently released a raft of new versions, including Microsoft Dynamics GP 2013 and Management Reporter 2012 Rollup 3, and to test I’ve been installing a few new virtual machines with Windows Server 2012 and have also updated a couple of machines with Windows 8 and, because they’re new machines without DVD players in them, to do this I used the Windows USB/DVD Download Tool which is available for free download from the Microsoft CodePlex|Project Hosting for Open Source Projects site in order to create a bootable USB drive.
I thought a step by step guide for others needing to install Windows 8 (or other version of Windows) might be of benefit. So after downloading the utility from the above link, double click the downloaded setup file to install the Windows 7 USB/DVD Download Tool Setup Wizard;
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;
Well, Windows 8 has landed on MSDN and TechNet for subscribers and is due for general release in, I believe, October.
This means it is time to interrupt the scheduled posts on installing the Web Services for Microsoft Dynamics GP. Having got my hands on an MSDN version I thought a quick run through on how to install it might be in order.
I am installing this into a virtual machine so I can have a little test before replacing one of my main systems with it.
I mounted the ISO image from MSDN in the virtual machine settings and launched the VM. The first part of the installer shows the new Microsoft Windows
Metro Modern logo;
I was just catching up on the blogs this morning and caught David Musgraves post on the release of Windows 8 and Windows Server 2012 to manufacturing.
Great news and must mean about two weeks before they’re on MSDN and TechNet. Can’t wait