I have a problem with Windows Server 2012 R2 for memory leaks (nonpaged pool problem).
I noticed the patches associated with older Windows versions, but not for this version of Windows.
Do you think that changing to Windows 2016 could be a good solution? If you have a better or different solution, please guide me.
Thanks
Related
Does anyone know which Windows 10 setting fixes this? Some of my dialogs are enormous, like in Sql Server Management Studio.
After installing Sql Server Management Studio 2012, my 2014 version worked again. No more giant font sizes. Not sure why that did it, but all is well now. In case anyone else runs into this same issue.
Does anyone have an idea if it is possible to downgrade IIS version 7 to lower version of IIS on windows server 2008?
I have an ASP program on win 2000 server and I am planning to migrate this program on new setup on better hardware and software but I am getting HTTP 500 which in detail error logs I see complain of classic asp and IIS 7. In my case obviously the the ASP used (by another programmer) is and old classic ASP platform and now with this conflict I cannot get my web sever operating properly.
Any help/idea would be really appreciated.
Thanks,
Alan
Azure service configuration allows to alter osFamily. Currently there're two options. Value 1 (the default) selects Windows Server 2008 and value 2 selected Windows Server 2008 R2.
I'm currently with the default (2008).
What changes should I expect if I just change to R2? Will it be faster? Will anything likely break?
You should see this as if you were upgrading from Windows Vista to Windows 7, as described in this question: What's the difference between Windows Server 2008, 2008 SP2 and 2008 R2?.
If you're building web applications the largest impact will probably come from IIS. Windows Server 2008 uses IIS 7.0, Windows Server 2008 R2 uses 7.5. Read about the differences here: What's New in the Web Server (IIS) Role (IIS 7)
There's also a whitepaper that describes the new and changed functionalities and features: Changes in Functionality in Windows Server 2008 R2.
To answer your question if anything will break I would say no (although something could always go wrong). I've deployed many applications to Windows Azure and this never caused issues for me. When I upgraded from Windows Vista to Windows 7 it felt like I was using a more mature, stable and better performing system, and I would dare to believe the same applies to the server releases. And advantage is that you'll have new features available, like the Win32 support to mount VHD files (I think this relates to your VHD question).
I am specing out new development workstations for my team and I am running into a conflict. I am a developer and I want Windows Server 2008 R2 because that is what our production servers are running. The IT guys want to give us Windows 7 because that is where they have tested all their infrastructure.
My question is this: is there enough of a difference between the two to push for 2008 R2? I know MSFT has crippled IIS in previous versions of Windows unless it was the server edition so I am skeptical about Win7 giving me what we need.
You can use Windows 7 for your development machines and have one Windows Server 2008 R2 for UAT deployments. This way you can have the best of both worlds. IT will be happy that you are all running Windows 7 and you will be happy that you're able to test your application in windows server 2008.
This question answer might be helpful.
Differences between Windows 7 and Windows Server 2008 R2
Your IT guys are correct aside from licensing issues such cost as Office without workstation on OpenValue, OpenSelect etc.. (remember they are packaged together) etc.. there are hardware issues and compatibility with future software.
There is no way you need 2008 R2 Server, do you want to work in the data center too? or have a full copy of the live database? You should have a CI server though that represents the live environment , the IT guys should provide this for you - probably as a VM.
Could anyone suggest me on this- we have sharepoint 2007 running on win server-2008 64bit
and we are about to upgrade to 2010 sharepoint, problem is do we keep the 2008 64bit as is or
upgrade to R2 and install SP 2010 on it.
obviously R2 must be more reliable than 2008 but just asking if we can we just upgrade
2008 to R2 with out a new server?
any help is appreciated!
Consider
Have the 2008 installation been unreliable and if so is it really windows? If it has it might be time to buy some new hardware
Are you worried about the support and update cycle for windows 2008? Obviously the ones for R2 will extend further into the future
However, If it's a dedicated SharePoint server machine that has been running just fine I see little or no reason to upgrade to R2.
If you choose to keep your server upgrading to Windows 2008 R2 remember to install the sp2 for SharePoint 2007 (wss3) BEFORE you upgrade.
Windows SharePoint Services 3.0 Service Pack 2 (SP2) - English
http://www.microsoft.com/downloads/details.aspx?FamilyID=79bada82-c13f-44c1-bdc1-d0447337051b&displaylang=en
When i first started doing sp2010, i used windows2008. That was a real pain, things were just buggy. As soon as i moved to r2, no more bugs. So i would say go with r2. It also means you can install r2 sp1.