Can TLS 1.3 be enabled on Windows Server 2008 R2? If so, how?
Thanks in advance!
Based on wikipedia article (https://en.wikipedia.org/wiki/Transport_Layer_Security_Adoption) the TLS 1.3 is not supported by Windows Server 2008 R2, and knowing that end of support for Windows Server 2008 R2 was on 1/14/2020, there is no chance to enable it.
Related
Am currently working through the mspress book to do the exam 70-462 and one of the questions asks what versions of sql and windows server reporting services can be installed on.
I was quite shocked to find that it said that Reporting services cannot be installed on a windows server 2008 R2 SP1 for SQL Enterprise edition.
I really dont see how this could be the case and having trawled through the msdn documentation cannot find any evidence to support this.
Can anyone shine any light on whether this is the case?
Thanks
You should be able to install it on Windows Server 2008 R2 according to the following paragraph found on the link below it:
"Starting in SQL Server 2008 R2, the Reporting Services component no longer supports Itanium-based servers running Windows Server 2003 or Windows Server 2003 R2. Reporting Services continues to support other 64-bit operating systems, including Windows Server°2008 for Itanium-Based Systems and Windows Server°2008°R2 for Itanium-Based Systems. To upgrade to SQL Server 2008 R2 from a SQL Server 2008 installation with Reporting Services on an Itanium-based system edition of Windows Server 2003 or Windows Server 2003 R2, you must first upgrade the operating system."
http://technet.microsoft.com/en-us/library/ms143506(v=sql.105).aspx
It is under: Processor, Memory, and Operating System Requirements.
I am getting the following error while trying to configure FileStream in SQL server 2012.
There was an unknown error applying the filestream settings. check the parameters are valid. (0x80041008)
I am configuring it using SQL server configuration manager.
Where as I am able to setup it for SQL server 2008 R2.
I had this same problem just yesterday.
In my case it was because I had a 64-bit Windows and a 32-Bit SQL Server.
You do not see the exact error, but if you try to do it with T-SQL, then the proper error comes up in SQL, telling you something about "WOW64" not supporting filestream.
I just uninstalled and installed the right bit version of SQL, and all worked 100% again.
In my case the problem I was running the SQL Server 2014 configuration manager. While this usually shouldn't cause problems, in my case it did. Configuring FILESTREAM using the SQL Server 2012 configuration manager worked.
If it still doesn't work, make sure you're up-to-date. SQL Server 2012 has received quite a lot of patches (SP2, SP3, and some updates).
TL;DR
I simply installed Service pack 2 (SP2) patch of SQL Server 2008 R2 and everything started working for me.
Read on if you want to know more. Configuration wise my box was all correct and the file stream feature should have been working on my default instance of SQL Server 2008 R2. Here are my box details:
Operating System: Windows 7 Ultitmate SP1 (64 Bit)
SQL Server Version: SQL Server 2008 R2 SP1
On SQL Server if I run this query select ##version it was returning following details:
Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64) Apr 2 2010 15:48:46 Copyright (c) Microsoft Corporation Developer Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
Whenever I opened SQL Server 2008 Configuration manager I will face this issue. Luckily I also had SQL Server 2014 installed on my machine. So I tried enabling File Stream feature from configuration manager GUI of SQL Server 2014 but it started giving error mentioned in current post.
I simply installed Service pack 2 (SP2) patch of SQL Server 2008 R2 and everything started working for me. SQL Server Configuration manager for 2008 R2 also works fine and I'm able to enable File Stream feature also without any trouble. SQL Server 2008 R2 SP2 can be downloaded from here.
I have some basic experience using sql server 2008 R2 (server management studio). I was wondering if the express version can be installed and used on a non server computer (os = MS XP). I have a simple web app that I want to test/practice connecting to the db, and performing simple insert/delete/update commands on a table. Can this be done?
Thank you
Yes, SQL Server Express can be installed on any Windows operating system, including the "client" OSes, except Windows CE of course, but that's something else.
You can use SSMS against SQL Server Express too, although some features of SSMS will be disabled becuase the server doesn't support them.
Yes, it can be done.
Supported operating systems: Windows 7, Windows Server 2003, Windows
Server 2008, Windows Server 2008 R2, Windows Vista, Windows XP
Check this:
Microsoft SQL Server 2008 R2 RTM - Express
Microsoft does offer SQL express, which probably offers more functionality than you would probably need right now.
http://www.microsoft.com/sqlserver/en/us/editions/2012-editions/express.aspx
Not only would you need MSSQL, you would need to have a current version of IIS installed. Is there a reason you are particularly interested in MSSQL? There are other "package" installations available of PHP/MYSQL which are more simple in setting up such as XAMPP:
http://www.apachefriends.org/en/xampp-beta.html
We have a Windows 2008 server with SQL Server 2005 SP3 with a bunch of classic ASP sites that are using SQLOLEDB to connect.
We have a new application that requires SQL Server Native Client 2008 R2 installed because it is using the SQLSRV PHP Driver. SQL Server Native Client 2005 is already installed (as part of SQL Server install).
Are there any issues with installing SQL Server Native Client 2008 R2 and connecting using SQLOLEDB? I'm assuming that 2008 client is backward compatible with the 2005 client?
Can the 2008 client be uninstalled back to 2005 if we need to roll-back?
I'm concerned that installing this could cause issues for the sites already using OLEDB.
Any help or insight is greatly appreciated.
Thanks
Dave
You can install them side by side no problem.
Are there any issues with installing SQL Native Client 2008 R2 and
connecting using SQLOLEDB?
No (apart from the lower functionality set of SQLOLEDB)
I'm assuming that 2008 client is backward compatible with the 2005
client?
Yes.
Can the 2008 client be uninstalled back to 2005 if we need to
roll-back
Yes
Is it possible to install SQL Server 2005 (Enterprise Edition) on Windows Server 2008?
Sure, why shouldn't it be possible to do that???
Just do it! I don't see any reasons why you should have any issues with this setup.
Go ahead and try it - if you run into any actual problems, come back (but preferably to http://Serverfault.com) and ask for help.
Yes. The SQL Server version doesn't have to match the operating system version, as it is for example with the IIS.
Yes.
What does the MS site for SQL Server 2005 say? (my bold)
SQL Server 2005 on Windows Server 2008
and Windows Vista
In an effort to provide customers with
more secure products, Microsoft
Windows Server 2008 and Microsoft
Windows Vista are supported by SQL
Server 2005 Express Edition Service
Pack 1 (SP1), and for all other
editions will be supported by SQL
Server 2005 Service Pack 2 (SP2) or
later when it becomes available.
Earlier versions of SQL Server,
including SQL Server 2000 (all
editions including Desktop Engine
edition, a.k.a MSDE), SQL Server 7.0,
and SQL Server 6.5, will not be
supported on Windows Server 2008 or
Windows Vista.