Print
Category: Uncategorised
Hits: 2636

More and more often I stumble into the darkness of unexplained problems regarding the stability of my servers, hence the idea that servers are there to serve-you, but mine's annoying us a lot more. 

I have decided to split the main server up, gonna buy very soon a new machine and make it simple Windows 2012 R2 and install all needed and then pick a server and transfer the software to the newer machine.

This way I can appoint more memory to the single process.

 

I started out with one server, using only 8 Gb memory, and I did try to get to the bottom and pulled out all the power the machine could give. Once I installed twice the amount of memory, my server (windows 2012) had a real hard time adressing this newly added memory. Resulting in constant reset of the machine...

So I had to remove the memory from the motherboard, darn! Because I remembered that Windows server 2012 and all its predecessors have had problems upgrading after installation is done, it might have something to do with registering the memory and Windows being unable to see that the newly installed memory is good-enough-to-go. Same goes for all other upgrades, but I noticed a difference...  Memory is the real problem if there was a piece of hardware like harddisk, graphics, expansioncards..... etc....that would be accepted all the time.  This is a simple action, deregister item, (remove from hardwarelist), restart server, install / import the new item, check if server says it is ok, then start working and watch behavior...

 

Something like that.

Microsoft never gives info about this procedure, but it makes sense.....

Well, If you have similar results like I did, then I hope you won't have to buy a new server...

 

Good luck